Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Digesting games list  (Read 1099 times)

0 Members and 1 Guest are viewing this topic.

SavannahLion

  • Wiki Contributor
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5986
  • Last login:December 19, 2015, 02:28:15 am
Digesting games list
« on: January 06, 2009, 12:32:10 am »
Looking at the MAME options, I don't really see any way to say... list what games were added, dropped, earmarked for whatever reason. In other words, I would like to use Mame XXX to generate a list of working/non-working ROMS then compare it to the list of working/non-working ROMS from MAME xxx+y.

Is there an option to generate such a list? I see -listfull flag that generates a list, but the list is limited as it only tells me what was added or taken out. It doesn't necessarily seem to be the same kind of information about what is considered "working" vs "non-working" as what you would find in the Whatsnew file. -listxml goes into further detail on each ROM but still doesn't seem to indicate working or non-working status.

Am I doomed to generate a list and reference the whatsnew file on every single point release to keep track of the ROM changes?

u_rebelscum

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3633
  • Last login:April 21, 2010, 03:06:26 pm
  • You rebel scum
    • Mame:Analog+
Re: Digesting games list
« Reply #1 on: January 06, 2009, 05:45:53 pm »
I'd say "Yes, but..."  ;)

"Working" and "non-working" are near equivalents of listxml's driver status "good" and "preliminary", respectively.  I'm not sure which way status imperfect goes.  So you could use the listxml data to produce lists to compare, but the results might differ a little than what you'd get from the way you do it now.

Note that none of the above relate to playable or not-playable.  (You might know this already, but for others reading.)
Robin
Knowledge is Power