Identical named but different hash-valued roms are in MAME since its beginning.
If such a thing occurs within a parent/clone relationship, clrmamepro tells you while parsing the datfile/mame.exe.

You go the option to either: split up parent/clone relationship for the sets in question, or force clrmamepro to work in split mode.

Again..this is nothing new...it's a common MAME behaviour.


Roman Scherzer