When I first tried to do it, there were a few rom names that changed from 0.141 to 0.145, those gave compile errors, so I first commented those out until it compiled correctly, then I d/l 0.141's source and searched the driver's. Some people just have OSD, and want to see the "Romlist complete." even if it is just a lie.Ī side note to anyone that tries my overly simplistic instructions: I think it would also be nice if you are using MAMEUI, though I don't, and therefore haven't tried it.Ī side note is that it saves A LOT of space, not only in roms, but all the.
MAME HYPERSPIN NO MATCHING GAMES DRIVERS
As far as I'm concerned my list of 2800 or so is "it", I'll lock down the frontend list with it, fix all the display names, find the missing support files for just those, and "upgrade" by compiling only that list from now on, I'll see emulation improve on those drivers as the devs fix things, and be able to scan for "missing" files that should only include fixes to "No good dump known". lst for 0.145, and aside from the occasional rom name change, be able to have hlsl functions AND not have a giant missing list of roms to go along with it. For instance, you can take your old 0.131 list of roms (dir c:\mame\roms\*.zip /b >mame.lst (then remove the ".zip" off lines in the file)) and simply use that as the.
MAME HYPERSPIN NO MATCHING GAMES UPDATE
lst it is a lot less complicated to stick with your current romset, and just update the code that runs just those. I somewhat agree, but now that the build process uses a. (The only downside is that because it has the best or US version of the rom and not necessarily the parent, you need to "rebuild" your roms to Split.) The exclude list is about 15,000 lines long, and it compiles a version of MAME that thinks 0.145 only has about 2700 roms in it. It's nice because if you're not interested in new roms (your lists are perfect and just the way you like), you can use your custom mame.lst from before and just compile the old list on the new source (taking advantage of Robotron fixes). It works fine, but takes a long time (SED is slow), and can be used with current 0.145, and because I am using an exclude list rather than a keep list, new releases of MAME can have the same exclude list ran against them, and "new" roms will be left alone and compiled by default, and any more pinball-screens and fruit machines in the new releases can be added to the exclude list when needed. I am in the process of making a list that when ran with a batch file, will comment out any driver in that list from the existing mame.lst.
0 kommentar(er)
