Quote:
Why it simply doesn't scan childs, well, because there is an offical way how sets are stored. rompath\setname\file 1..file n for decompressed sets or rompath\setname.zip (.rar/.7z) for compressed sets. Even sets with subfolders are supported, so of course you can't simply put everything into one big folder with subfolders. You need to make yourself some thoughts about rompaths are organized.
MAME by default has one roms folder. I have always been under the impression that additional roms directories are supported, but optional.
My arcade roms, devices and bios share the root of the roms folder and this has never been a problem. Arcade chds reside within their respective subfolders within the roms folder. Console (MESS) roms are separated by console. NES in one folder, megadrive in another, etc. Yes, they're all in the roms folder, but not all dumped together as they're subfoldered. MAME has no problem with this and detects/plays everything fine.
Leaving out the Sysdefpath stuff, the problem with clrmame is if I have an nes rom named XXX in one folder and a mega drive rom named XXX in another, its wanting to move the nes rom to the mega drive folder or vice versa. I think it was also incorrectly renaming rom files within the zip as well. Clrmame doesn't see that they're completely different roms for two different systems and even in separate folders. It's just seeing two zips with the same name and deciding one needs to go somewhere else. Seems like it should be matching hashes and doing something a bit more detailed than looking at names here.
Anyway, not knocking you or your work here. Importing the individual xml files from the hashes folder accomplishes what I needed without the problems/conflicts.
|
Previous 
Index 
Next 
Flat 
Re: CLRMAME and Softlist roms giving me fits!
Reply
