> 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...