Wonderful tool Roman! Just a couple issues...

1. ClrMamePro keeps moving my rom sets to different folders when I do a full scan. I have a ROMS folder similar to this:

roms
roms/0-9
roms/A-L
roms/BIOS
roms/CHD
roms/LaserDisc
roms/M-Z

What I find is that the tool consistently takes sets that have changed with a new version of MAME and puts them into the roms/0-9 folder for some reason. I move them back, and when I do a full scan, they get moved back. Any ideas why?

2. Also, the latest version of CLRMamePro and 0.122u2 the mac2bios.zip file keeps getting stripped out of my BIOS folder and put into backup. That leaves me with 34 bios sets in my folder, but MAME still expects 35? What happened to this BIOS set? Did it get merged with a rom set? I searched my MAME folder and cannot find it anywhere.

Thank you for any help.
Matt

2) mac2bios is a 100% nodump set and so it gets marked as unneeded and it gets removed.

1) well...couple of reasons:

- "fix missing" for example got several rules which leads to the final destination folder. If you use system-default-paths and got the belonging scanner->advanced->fix missing options enabled, the rom will be put in the assigned system default folder. If you don't use these options and the set does not exist at all, it checks for the position of the parent and uses that rompath. (This of course kills your idea with A-L etc...since not all parent clone relationships start with the same letter). If it doesn't find a good rompath to put the missing file into, it uses the 1st setup and active rompath.

- rebuilder: if you use the rebuilder to add files, the rebuilder destination or - if enabled - system default paths are used.

- similar rules exist for other fixes in the scanner.

As you see, using rompaths with A-Z, etc. is not a clever way to go ;)


Roman Scherzer

and I thought I was being "clever"! Oh well...

Thanks Roman. I'll look at my settings and see if I can solve the issue.




> 2) mac2bios is a 100% nodump set and so it gets marked as unneeded and it gets
> removed.
>
> 1) well...couple of reasons:
>
> - "fix missing" for example got several rules which leads to the final
> destination folder. If you use system-default-paths and got the belonging
> scanner->advanced->fix missing options enabled, the rom will be put in the
> assigned system default folder. If you don't use these options and the set does
> not exist at all, it checks for the position of the parent and uses that
> rompath. (This of course kills your idea with A-L etc...since not all parent
> clone relationships start with the same letter). If it doesn't find a good
> rompath to put the missing file into, it uses the 1st setup and active rompath.
>
> - rebuilder: if you use the rebuilder to add files, the rebuilder destination or
> - if enabled - system default paths are used.
>
> - similar rules exist for other fixes in the scanner.
>
> As you see, using rompaths with A-Z, etc. is not a clever way to go ;)
>
>
> Roman Scherzer
>