1
clrmame Discussion / Re: Using %D (driver status) to filter only working ROMs - is this possible?
« on: 19 September 2017, 01:06 »
Figured it out. The problem, as I suspected, was that the DAT file I was using lacked the XML tags for driver status. To resolve this I did the following:
1) Download the mame64.exe for 0.139 (matching the set lb-mame2010 is based on)
2) Run "mame64.exe -listxml > mame139.xml" which creates an XML file with ALL tags possible
3) Download and use RomLister to create a new XML file with only playable games (and excluding some game categories I didn't want)
4) Use the new XML file as a profile for clrmamepro (I think I had to rename with .dat instead of .xml)
5) Rebuild, then scan with Set Information option "%D=good"
The result, as far as I can tell, is a set of only good, working ROMs.
1) Download the mame64.exe for 0.139 (matching the set lb-mame2010 is based on)
2) Run "mame64.exe -listxml > mame139.xml" which creates an XML file with ALL tags possible
3) Download and use RomLister to create a new XML file with only playable games (and excluding some game categories I didn't want)
4) Use the new XML file as a profile for clrmamepro (I think I had to rename with .dat instead of .xml)
5) Rebuild, then scan with Set Information option "%D=good"
The result, as far as I can tell, is a set of only good, working ROMs.