I use clrmamepro with merged sets (which is probably 1/2 my problem) and I have been encountering some strange problems of late. In the last month I have noticed single rom updates to sets sometimes has wierd results. More than twice now the single rom updates itself at the expense of the rest of the archive (which usually completely or partially disapears instead of moving to the back up folder - though why would it as it wasn't meant to be deleted). I know these files were there previously as I have been able to restore them from my archived backups. It only ever seems to happen to one set only in a single update and not every update.
Tonight I tried to test my new compile using Bust a Move (pbobblen). Clrmamepro reported it as complete but mame correctly advised me there were a bunch of roms missing (which I found in the pspike archive). This may be totally unrelated to the other problem but I thought you may want to know about it.
Im sorry I cant be more specific about these problems as I didn't think much of them at first. I'll definitely keep a list from now on and report anything strange I find.
Cheers
Chook.

Sounds weird. Generally speaking, cmpro works correct. Be sure you used a correct datfile/mame.exe (i.e. database you check the sets with and emulator you use the sets with have to be the same). Next thing is, be sure to have all sets enabled and all check options enabled.

In current MAME there is no pbobblen and no pspike set. There are similary named sets however which e.g. share the neogeo bios set. So your scan should include checking that one as well.

As long as you can't name which files of the sets MAME is complainig about or you can't repeat the behaviour, it's hard to give you more help. Go and try to repeat the behaviour.


Roman Scherzer

MAME is now including identically named roms with different crc32s in parent/clone sets (such as freezeat) creating all sorts of havoc.

Time to remove merged mode from ClrMame I think :(

> Sounds weird. Generally speaking, cmpro works correct. Be sure you used a
> correct datfile/mame.exe (i.e. database you check the sets with and emulator you
> use the sets with have to be the same). Next thing is, be sure to have all sets
> enabled and all check options enabled.
>
> In current MAME there is no pbobblen and no pspike set. There are similary named
> sets however which e.g. share the neogeo bios set. So your scan should include
> checking that one as well.
>
> As long as you can't name which files of the sets MAME is complainig about or
> you can't repeat the behaviour, it's hard to give you more help. Go and try to
> repeat the behaviour.
>
>
> Roman Scherzer
>