Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All Threads*Show in Threaded Mode


SubjectBad MameDiff Dat??? new Reply to this message
Posted bys4turn3
Posted on07/24/08 08:28 AM



Hi Roman, question? I’ve noticed a possible problem with Logiqx’s mamediff, where I’m generating a fully-merged mame supplement. In this case I have a generated dat with a set with two roms with the same name with different crc’s and hashes… I’ve just reported this to Logiqx’s forum, so he hasn’t had time to respond yet.

My question for you is I can load this dat into CMP and do a full scan—every thing shows as good, but when I inspect the zip it of course only has one of the roms with that name—the last one. Is this expected behavior or would you expect CMP to complain about the dat? There's not really a parent-clone relationship anymore...

Thanks for your comments. I’m using your latest version.

Reference: http://forum.logiqx.com/viewtopic.php?t=474





SubjectRe: Bad MameDiff Dat??? new Reply to this message
Posted byRoman
Posted on07/24/08 08:45 AM



When you got 2 sets within a parent/clone relationship where you got roms with the same names but different hashes, clrmamepro will remove the parentclone relationship automatically. This prevents you from data loss if you would full-merge such sets.


Roman Scherzer



SubjectRe: Bad MameDiff Dat??? new Reply to this message
Posted bys4turn3
Posted on07/24/08 09:17 AM



> When you got 2 sets within a parent/clone relationship where you got roms with
> the same names but different hashes, clrmamepro will remove the parentclone
> relationship automatically. This prevents you from data loss if you would
> full-merge such sets.
>
>
> Roman Scherzer
>

Yes, I've seen that and that seems to quite work well. What I'm seeing now is a dat like the following...

game (
name kof97
description "The King of Fighters '97 (Set 1) [n.b. includes clones]"
year 1997
manufacturer "SNK"
sourcefile neodrvr.c
...cut....
rom ( name 232-p2.bin size 4194304 crc ee4a2db4 sha1 c790bdb9b255788df9c99aacf3861ee380eb2df4 )
rom ( name 232-p2.bin size 4194304 crc 90723643 sha1 62d95957ae51732de30af903dc8f07f5556d15f5 )
...cut...

mamediff already did the merge so the parent/clone information isn't available anymore...




SubjectRe: Bad MameDiff Dat??? new Reply to this message
Posted byRoman
Posted on07/24/08 09:29 AM



Blame Mike (Logiqx) ;)

clrmamepro would take the last one.....in MAME you usually have a lot of identical roms listed several times (that's based on how the xml is being generated). However I should add a warning if double entries with different hashes are listed.


Roman Scherzer



SubjectRe: Bad MameDiff Dat??? new Reply to this message
Posted bys4turn3
Posted on07/24/08 09:47 AM



> Blame Mike (Logiqx) ;)
>
> clrmamepro would take the last one.....in MAME you usually have a lot of
> identical roms listed several times (that's based on how the xml is being
> generated). However I should add a warning if double entries with different
> hashes are listed.
>
>
> Roman Scherzer
>

That would be great. Thanks for your time.




SubjectRe: Bad MameDiff Dat??? Reply to this message
Posted byRoman
Posted on07/24/08 09:54 AM



in fact I think clrmamepro currently takes the first one ;O)


Roman Scherzer



SubjectRe: Bad MameDiff Dat??? new Reply to this message
Posted bys4turn3
Posted on07/24/08 11:55 AM



> in fact I think clrmamepro currently takes the first one ;O)
>
>
> Roman Scherzer
>

Thanks Roman




View All Threads*Show in Threaded Mode