many thanks to MAME dropping the TESTDRIVER system.
- Made changes from MAMEinfo (including MAME32 changes)
- Made QMAME changes (except for the knocker stuff, which needs VC++)
Thanks for adding the QMAME stuff. Regarding MAMEinfo - Did the Cinematronics sound fixes get added?
Now the big question - This may not be the right place to post this, but I'll start here anyway.
I used to use TESTDRIVER as a crude filter system, as follows:
I have a text file: Removedgames.txt (updated each revision to only include games still in MAME). It contains the ROM names of 1257 (mostly Mahjong, etc.) games that I didn't want to see/didn't want my kids to know about.
I would run a WordPerfect Macro (only way I could find to make it work), which read the rom name, searched in driver.c, found the same name, verified it found the correct name (i.e. if searching for spool3, that it found spool3, not spool3a (which contains spool3), and then searched backward to find DRIVER and changed it to TESTDRIVER. I would then compile MAME with the revised Driver.c file and end up with a version that looked like these 1257 games didn't even exist. Useful for running ClrMAME pro for rom searches, etc., since I didn't have these roms.
I assume this method will no longer work. And I suppose what I need is a program that will read my list, search driver.c and remove the DRIVER line containing the ROM.
Anyone want to write something like this? Or are there better options that I'm not seeing??? Or have I got the whole idea wrong?
Would there be a way to write no-name MAME with an option to treat TESTDRIVERS the way previous MAME versions did; or do ClrMAMEpro and frontends build -listinfo before checking this?
Thanks in advance!!!
UPDATE: The removedgames.txt format is one game per line, alphabetical, so I can add new unwanted games to the bottom of the list, and then use the sort function in Word to realphabetize.