From you explanation, I gather there are various levels in softwarelist support. Candidates for software list inclusion could be categorized as follows:
- Not listed in a .xml file of the hash folder.
- Listed in a commented-out area of a .xml file in the hash folder.
- Listed in the main body of a .xml file in the hash folder, but not wired into MAME.
- Listed in the main body of a .xml file in the hash folder, and wired into MAME, but has the supported="no" tag.
- Listed in the main body of a .xml file in the hash folder, and wired into MAME, and does not have the supported="no" tag.
And of course, some may be nodumps or baddumps.
The reason that categories 2 and 3 exist is to provide partial documentation for eventual inclusion as categories 4 or 5.
And any candidate could be loaded by name from either the command line or internal GUI when in category 5. If the candidate was in the other categories, it might be able to be loaded by full path\filename, provided that it's structure was compatible with the default wiring of that particular driver in MAME. And only categories 4 and 5 will produce output with the -listsoftware command.
Is that about it?
My original assumption was that MAME -listsoftware produced the de-commented contents of the various .xml files in the hash folder. That is, categories 3, 4, and 5 as listed above.
Thank you for clearing that up.
Edited by mw (06/02/15 09:12 PM)
|
Index 
Flat 
Re: MAME 0.162 -listsoftware
Reply
