MAME 2003-Plus isn't just any emulator. It is a "retro-active" fork of the official MAME code from, you guessed it, 2003. But "Plus" is the magic word. The original 2003 version of MAME was famous for its speed and low system requirements—it could run on anything from a PC to a Raspberry Pi. However, it was missing thousands of games that were later dumped and preserved.
The MAME 2003-Plus team took that rock-solid 0.78 (circa 2003) codebase and backported support for newer games, fixed old bugs, and added features like save states, cheats, and better input lag. The result? A lean, mean, arcade machine that runs on low-powered devices (RetroPie, classic consoles, handhelds) while supporting a massive library of games.
But there was a catch: MAME 2003-Plus expects ROMs to be organized in a very specific, very old way. It doesn't understand the "merged" or "split" sets that modern MAME versions use. It wants a Full Non-Merged set. mame 2003-plus reference: full non-merged romsets
To understand the ROMset, you must first understand the emulator.
Once you have your "MAME 2003-Plus Reference Full Non-Merged" folder (let's call it mame2003-plus-roms), here is how to operationalize it. MAME 2003-Plus isn't just any emulator
Even with a Full Non-Merged set, you still need to place BIOS files (e.g., neogeo.zip, pgm.zip, qsound.zip, decocass.zip) in your ROMs folder. Non-merged ROMs will contain device ROMs for most systems, but certain arcade platforms require the BIOS ZIP alongside the game.
Best practice: Keep a copy of the MAME 2003-Plus BIOS collection (non-merged BIOS set) in your /roms/ directory. The original 2003 version of MAME was famous
In a Full Non-Merged set, you will see mslug.zip (Metal Slug 1) and mslug2.zip (Metal Slug 2) and mslug2t.zip (MS2 Turbo).