> Thanks BIOS-D, that image showing the difference between "non-merged / merged / > split" makes it very clear. > > So when CMP says; > 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. > > I assume this means that CMP can't do 'merged' so wants to know wether to do > 'non-merged' or 'split'. I would personally prefer 'split' because refering to the > picture 'non-merged' mode would increase the HDD space requirements for ROM storage > which should also be a factor for some people.
Re-word for effect: Yeah, that message means "Cannot merge sets because there is the same filename in the the parent as well as the same filename in the clone, but they have different (CRC32/SHA1) checksums. You cannot have this in a ZIP file."
So at that point you need to do either "non-merged" ("remove parent/clone relationship") or "split" ("split-merge") because the same filename with different checksums can't exist in the same ZIP file (without doing some sort of directory structure within the ZIP file).
As it says at the EasyEmu Guide for CLRMame Pro... "Non Merged Sets - Every rom file has all the roms it needs to run including sets. Split Sets - All rom files are split into clones that share the roms from a parent rom file. Merged Sets - All roms from sets are contained in one file."
---
"Remove parent/clone relationship" is almost a misnomer because the relationship will still exist as far as MAME's internal information goes. The first time I saw that message back in the early days of his program, I thought it implied farther-reaching effects.
*wonders if unmerge is a word... looks like it is, according to Merriam-Webster...*
Index 
Flat 
Re: I'm boycotting clrmpro.....
Reply
Re: I'm boycotting clrmpro.....
