3.108a

misc: nodump handling is now locked to 'hide missing', disabled 'create missing' and enabled 'mark no dumps as unneeded'.

Say goodbye to nodumps....you should rescan your sets to get rid of them.



Roman Scherzer

ha...it's very good, but i use it to scan my roms , it says:

Multi Amenity Cassette System 2 BIOS [system: Multi Amenity Cassette System 2 BIOS - folder: mac2bios - size: 1mb]
unneeded file: E:\MAME\BIOS\mac2bios\macs2os_h.bin
unneeded file: E:\MAME\BIOS\mac2bios\macs2os_l.bin

but this bios is correct, and when i click the button "AutodetectSysDefPaths...", the application crash...maybe there is something wrong with 3.108a

> but this bios is correct, and when i click the button
> "AutodetectSysDefPaths...", the application crash...maybe there is something
> wrong with 3.108a

No there isn't. The Mac2Bios is a nodump and so the bios roms are marked as unneeded.
I can't repeat any crash when auto-detecting sysdefpaths.


Roman Scherzer

My system is windows server 2003 sp2, when i click this button:
---------------------------
>clrmamepro<: cmpro.exe -
---------------------------
unknown software exception (0xc000000d),0x00566e35

3.108 is ok.

> 3.108a
>
> misc: nodump handling is now locked to 'hide missing', disabled 'create missing'
> and enabled 'mark no dumps as unneeded'.
>
> Say goodbye to nodumps....you should rescan your sets to get rid of them.
>
>
>
> Roman Scherzer


There seems to be a bug in the Rebuilder. I drag and drop a zip file containing ROM files that are marked as nodump, and those "nodump" files are still rebuilt into the collection, causing a later Scan to report them as unneeded.

3.108a doesn't have any changes related to the auto-sysdef detection....

I will have a look at it...but as long as I can't repeat it here...it's tough to fix it...

Maybe you can zip up your used *.cmp + *.dat file + cmpro.ini and mail it to me?



Roman Scherzer

hmm....the rebuilder swtich 'rebuild nodumps' is disabled and not checked, isnt it?

Hmm..can't repeat it here....dropped some nodump files and they get not created.

Maybe you can zip up your used *.cmp + *.dat file + cmpro.ini + the rebuilt nodump and mail it to me?


Roman Scherzer

i found it~
in the "scanner", if i click the "scan" first, then click "systems"->"Auto-Detect SysDefPaths...", the application will crash, but if i click the "Auto-Detect SysDefPaths..." first, it's ok...

> hmm....the rebuilder swtich 'rebuild nodumps' is disabled and not checked, isnt
> it?
>
> Hmm..can't repeat it here....dropped some nodump files and they get not created.
>
> Maybe you can zip up your used *.cmp + *.dat file + cmpro.ini + the rebuilt
> nodump and mail it to me?
>
>
> Roman Scherzer

After some further check I found that the file with this problem is chinagat.zip, which I believe is a special case. Files a12, a13, a14, and a15 are marked as "nodump" in sets chinagat and saiyugou, but are valid ROMs in sets saiyugb1 and saiyugb2.

However, this problem didn't happen before 3.108a, so I'm still not sure if this is my problem or a newly introduced bug. Anyway, some info of my settings:

"Merge Options" in Rebuilder: Merged Sets
"You prefer" in Scanner: Merged Sets
Questions answered during MAME listxml and dat generation: I believe I clicked "OK TO ALL", but I'm not quite sure.

Procedure to reproduce this issue:
My chinagat.zip contains all ROM files necessary for all the 4 sets. The Rebuilder would rebuild everything into the collection, but the Scanner would report the 4 files as unneeded for "chinagat" set.

...but that special case shouldn't be a problem since when importing the data from MAME, cmpro will ask you that you can't fully merge those sets since they got different checksums for equally named sets (valid crc vs nodump) and removes the parent clone relationship. Maybe you answered 'NO' when these prompts appear.

(update) it didn't do that in all cases, but will in the next version...thanks for the headup.



Roman Scherzer

hmm...I still can't repeat that. When exactly does it crash? When you hit the button? During the detection phase?, after that? As mentioned, please send me the cmpro.ini, *.cmp and belonging datfile...I can't repeat that behaviour here in any way at the moment.

(update): ok...I found a possible issue on this...but that would mean you scan, then remove/add/enable/disable some rompaths in the meantime and then go to autodetection...
Well...I fix it and I'm rather sure it fixes your reported thing as well.


Roman Scherzer