> > When creating a new dat file from a new mame release, I get a general set of
> > messages, "duplicate ROM, 2nd entry ignored" and such. I understand most of
> > them, but one particular message always makes me wonder:
> >
> > Set: 'xxx'
> > includes at least one 'nodump' ROM, but ClrMamePro
> > found valid checksums for it within its parent/clone relationship.
> > Should ClrMamePro use the found checksum instead of the 'nodump'?
> >
> > Can anyone please explain this one?
>
>
> It means that a rom with the same name within a parent/clone relationship was
> once listed with a valid checksum and the other time it was set to "flags
> nodump".
>
> Example:
> Parentset got a rom: rom ( name bla crc 12345678 ...)
> cloneset got a rom: rom ( name bla flags nodump ...)
>
> so when fullmerging the set you might run into a problem. You may replace the
> correct rom with a possible dummy nodump one. ClrMamePro's datread will set the
> flags nodump one to the checksum of the valid one.
>
I think I understand what you explained. With that info the, what's the best way to answer the "Should ClrMamePro use the found checksum instead of the 'nodump'?" question then? Guessing, "yes" if I use split or non-merged sets, and "no" if I use merged sets?

Joe