clrmamepro [English] > clrmame Discussion

Help with alphamc07 chsuper2 boobhack messages

(1/1)

windar:
Hi Roman or others:

I think I missed this a while back but have seen these messages pop up while reading databases from new builds.

Is there a way to clear these errors or its something that is just going to persist? Have tried new ROMs and such to fix but to no avail. I'm sure I'm missing something.

Have seen others posting elsewhere with same messages but have not seen a fix. I still get clear scans in the end but if this can be taken care of that would be great.

Thanks!

Darwin

Set:   Bull Fighter
Name:   bullfgtr

Issue:   Alternative Samplefolder 'alphamc07' doesn't exist

Missing Alternative Samplefolder will be added as sample-only set.

Set:   Booby Kids (Italian manufactured graphic hack - bootleg of Kid no Hore Hore Daisakusen (bootleg))
Name:   boobhack
ROM:   kid_prom.4e

Issue:   Possible wrong nodump definition found

A valid checksum for it within its parent/clone relationship was found though.
Insert found checksum instead of using the 'nodump'?

Set:   Champion Super 2 (V0.13)
Name:   chsuper2
ROM:   a.bin

Issue:   Can't merge set due to equal names for different ROM hashes

Press yes to remove parent/clone relationship or no to force split-merge mode.

Roman:
Well, actually you can't do anything about the messages (besides hiding them via the hide option) unless you change the MAME source code.


- Alternative Samplefolder will be added as sample-only set

Well, there are sets in MAME which use an alternative sample folder which isn't listed at all in the MAME -listxml output. For correctness and easy scanning, this set will be added (containing only the sample definitions).


- Possible wrong nodump definition found

Well, here you got an effect where equally named roms within a parent/clone relationship are once listed as a nodump and the other time as a valid rom with a hash. You can decided if you want to keep the nodump or want to use the same hash for it.


- Can't merge set due to equal names for different ROM hashes

There are cases where equally named roms within a parent/clone relationship are not identical (different hashes). So if you try to full merge these sets without adding subfolders to the archive, you will overwrite one of them. So you can decide if you want to be forced to splitmerge mode or remove parent/clone relationship for the set in question.

Again, these are all events coming from the MAME database. You as an enduser can't do anything about it....as a MAME developer you got pros and cons for each root cause of these events....So...live with it ;)

windar:
Thanks for the explanation. I will consider this a known issue and ignore it. Thanks for all your help and clrmamepro!

Roman:
Just to be crystal clear here: There is NO issue.
It's a normal behaviour handling some datfile/datasource inconsistent definitions.

Navigation

[0] Message Index