EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - bollwerk

Pages: [1]
1
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.

2
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.

Pages: [1]

Page created in 0.13 seconds with 20 queries.

anything
anything