The only way to find out, which roms are supported and which are not, you need to get yourself familiar with rom management. If you want to use a game from the, let's say, mame2013 core (0.159 Rom Set), it won't work, BUT there might be a version of the Game which IS working with one of the older cores. That basically means xyou can run (almost) all games included in the above mentioned sets. We are using the mame2003 (0.78 Rom Set) and the imame4all (0.37b5 Rom Set) cores for our MAME integreation. Hi assumptions are right (more or less), but the important thing to know is, that MAME is backwards compatible (somehow), but not upwards compatible. So why on earth would a small version change in MAME cause so much destruction with compatibility? Why isn’t MAME backwards compatible? So with Frogger (at least the version I have), there are 9 files, so I assume those each represent each chips? And when it comes to BIOS, I assume that would be very loosely similar to a gaming system. With MAME ROMs, I gathered that the ZIP files contain the digital images of the chipset found in the cabinet. The emulator itself isn’t a digital image of the system, but rather just as an interpreter. I want to downsize and replace the laptop with a raspberry pi, but now finding the games I have no longer work with the mame version on recalbox (which I still cant figure out how to do)Ĭorrect me if I’m wrong, but from working with nearly every other emulator, the ROM is the digital image of the cartridge (or whatever media the game was on). No rush on this, but could someone please explain in more Lameman’s terms why MAME ROMs are so closely tied to the version of MAME? I built a custom cabinet using MAME and Windows and loaded it up with games I want.

Gauntlet legends mame 0.37b5 rom