When I do a -verifyroms on a clone that isn't present, the output says that roms are missing from the parent.
Here's an example:
C:\MAME>vmame64 -verifyroms sboblboa sboblboa: 1c.bin (32768 bytes) - NOT FOUND (shared with parent) sboblboa: 1a.bin (32768 bytes) - NOT FOUND (shared with parent) sboblboa: 1b.bin (32768 bytes) - NOT FOUND (shared with parent) romset sboblboa [bublbobl] is bad 1 romsets found, 0 were OK.
C:\MAME>vmame64 -verifyroms bublbobl bublbobl: pal16l8.bin (1 bytes) - NOT FOUND - NO GOOD DUMP KNOWN bublbobl: pal16l8.bin (1 bytes) - NOT FOUND - NO GOOD DUMP KNOWN bublbobl: pal16r4.bin (1 bytes) - NOT FOUND - NO GOOD DUMP KNOWN romset bublbobl is best available 1 romsets found, 1 were OK.
1a.bin, 1b.bin and 1c.bin are from sboblboa and not the parent bublbobl. This happens for every missing clone on my system, and it's screwing up my audit.
Is -verifyroms broken in 141u3?
EDIT: Also happens with MinGW compiled mame64, BTW.
Those guys at Narcotics Anonymous are assholes, I told them I have a 3 litre a day Coke habit and they kicked me out!
Edited by msbhvn (03/01/11 08:14 PM)
|