Updating old mame roms

Posted by / 03-Apr-2020 04:26

I'm not using Pi but most of my ROMS seems to be working fine, just wondering if they will crash at some point.

I have also noticed that my Hyperspin Databases are all out of whack not recognizing most of my MAME games yet they still work through Hyperspin, weird.

In our example, the file would contain: In this example only one single file is removed.

When you take into consideration that some games have lots of different versions (for example, Pac-Man, Galaxian or Asteroids), we have reduced the number of files from 3290 down to around 1870 the number of games MAME supports (for version 0.59).

Continuing with our example, we can say that the two 1941 sets must be named 1941(World) and 1941(Japan).

In the Split / Not Merged mode, there is an independent file for each ROM set, each containing all the required ROMs for the set.

By examining the table it can be seen that the last 8 ROMs are identical for both sets.This will produce two text files (quite big) with the information of the full ROM set of each MAME version, that mamediff will later use to create the dat file.We must copy these two text files to the mamediff folder.Storing the ROMs in Not Merged means that there will be unnecessary duplication of information, which just wastes storage space.MAME can solve this problem by erasing the duplicated ROMs from each of the clone sets and storing them only in the main set There is one final method: Not Split.

updating old mame roms-56updating old mame roms-25updating old mame roms-72

If there was an independent file for each set, for MAME version 0.59 there would be a total of 3290 files (the number of sets for v0.59).

One thought on “updating old mame roms”