Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bollwerk]

It seems like it should be possible to create a set of only working ROMs and exclude non-working or preliminary ones, using %D, but I'm guessing that you need a DAT file that contains the <driver status> tags for each game, as %D=working on my "MAME 139u4.dat" file does not seem to work.

If my assumption is accurate, where can I get (or create) a DAT file with this info? I've googled high and low and am unable to answer this.

Thanks.

[Roman]

hmm...I will have a look at it...actually yes, a %D=good should select sets with this driver status flag in the xml...doesn't work...maybe the syntax was different...I will check later at home.

[Roman]

Hmm...here at home with MAME .189 %D=good works fine.

Well, it enables sets which have driverstatus good....whatever this means ;-) Most likely this does not necessarily mean they are 100% fully emulated and 100% working....but since there is no other useable flag you're coming close to your goal...

Of course you need to keep devices/biossets and maybe parents/clones enabled for your selection to get valid set selections...

[bollwerk]

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.

[Roman]

;-)