Let's be direct. If you have a gaming PC from 2020 or later, you should not daily-drive MAME 0.130. Modern MAME (0.250+) has better: input latency (via frame delay), widescreen bezels, save states for tricky games, and emulation for the Sega System 32.

But in niche retro applications—DIY bartops, Softmodded Xbox Originals (CoinOPS 2), Raspberry Pi 2 builds, or RetroArch on PS Vita—mame 0.130 romset is the final, functional frontier.

The most important feature (or challenge) of the 0.130 romset is that it uses the Split format.

Unlike modern full non-merged sets, a split set requires you to keep the Parent ROM and Child ROM (clone) in the same folder.

How it works:

Helpful Tip: If you download a single game (e.g., tmnt2.zip for Teenage Mutant Ninja Turtles - Turtles in Time), it will not run unless you also have the parent ROM (tmnt.zip) present in your roms folder.

MAME 0.130 uses 8.3 short filenames (due to DOS-era legacy) and strict CRC32 checksums.

Example entry from mame0130.xml (the official metadata):

<game name="1942" sourcefile="1942.c">
  <rom name="1942a.1b" size="4096" crc="e5c29ce6"/>
  <rom name="1942b.2b" size="4096" crc="8db8e903"/>
  ...
</game>

Critical: A ROM named 1942.zip that works in MAME 0.200 will not work in 0.130 unless it matches 0.130’s CRC32, size, and internal file names.

"MAME 0.130 romset" refers to a specific collection of ROM files matched to version 0.130 of MAME (Multiple Arcade Machine Emulator). Each MAME release has a defined internal database of supported arcade, console, and computer systems, plus a list of required ROM files (and their expected names, sizes, checksums, and arrangement). A "romset" for MAME 0.130 is the set of ROM images arranged and named to match exactly what that MAME version expects so games run correctly and are identified as complete or missing by the emulator.

Below are the main points you need to understand about MAME 0.130 romsets: what they contain, why matching the emulator version matters, how sets are structured, common file types, legal and practical considerations, and tips for working with and managing these sets.

To understand the legendary status of mame 0.130 romset, you must first understand the tectonic shift that occurred shortly after its release. For years, MAME ROMs were distributed in two primary formats: merged and split.

Version 0.129 and 0.130 were the last great bastions of a third, now-abandoned philosophy: Non-Merged sets. A non-merged MAME 0.130 ROMset is a miracle of convenience. In a non-merged set, every single game—from Pac-Man to the rarest Korean bootleg—contains all the necessary data to run entirely on its own. You do not need a separate parent ROM. You do not need a "bios" folder (in most cases). You simply drag the ZIP into your roms folder, and it works.

After version 0.131, the MAME dev team began aggressively optimizing storage space for dedicated full-set collectors. They moved toward a "merged-only" ideology for official distributions. Consequently, building a non-merged set for modern MAME is a logistical nightmare. This is why vintage collectors hoard the mame 0.130 romset like digital gold.

🕹️ The "Sweet Spot" of Emulation: Why MAME 0.130 Still Matters

If you’ve been in the arcade emulation scene for a while, you know the "ROM set chase" never really ends. While the latest version of MAME (Multiple Arcade Machine Emulator) is always the most accurate, there’s a reason you still see MAME 0.130 (released March 2009) mentioned so often. What is the 0.130 ROM set?

A MAME ROM set is a collection of data files dumped from original arcade game circuit boards. Because the emulator's code changes to become more accurate over time, the way it "reads" these files also changes. This means a ROM set from 2024 likely won't work on an emulator from 2009, and vice versa. Why 0.130?

The 0.130 release was a major milestone for several reasons: The "Mid-Range" King:

It hit a perfect balance between speed and accuracy. It’s light enough to run on older hardware (like original Raspberry Pi units, modded Wiis, or older Android phones) while still supporting a massive library of classic titles. Stable Drivers:

By 0.130, many of the "Golden Age" 80s and 90s drivers (think Capcom CPS1/CPS2, Neo Geo, and Konami classics) were already highly mature and near-perfectly emulated. Foundation for Mobile: Many popular mobile ports and RetroArch cores (like

, which actually uses 0.139, often sits right next to it in terms of performance) were built around this era of MAME's codebase. Quick Facts for the Curious: Release Date: March 9, 2009 [ Notable Updates: This version saw significant work on Sega System 1/2 and improvements to the Naomi and PGM hardware Compatibility:

If you are using an older device or a specific "lite" frontend, finding a "Reference Set" for 0.130 ensures you aren't fighting with modern

(large disk images) that your hardware can't handle anyway [ Pro-Tip for Newbies:

Always match your ROM set version to your emulator version! If you’re running a core labeled

, you want the 0.139 set. If you're on a legacy cabinet running 0.130, only a 0.130 set will guarantee that every game boots without "Missing Files" errors.

Are you still rocking a legacy MAME setup, or do you always stay on the bleeding edge? Let's discuss! adjust the tone to be more technical, or perhaps focus on a specific device like the Raspberry Pi?

MAME 0.130 ROM set is a specific snapshot of arcade emulation history, released in March 2009

. While nearly 15 years old, this particular version remains a popular "legacy" target for enthusiasts using low-power hardware, such as older Raspberry Pi models or handheld retro-consoles, which may not have the processing power to run the more accurate (and resource-heavy) modern versions of MAME. Historical Significance and Evolution The 0.130 Milestone

: This version represented a mature period in MAME development before significant architectural shifts—like the integration of MESS (Multi Emulator Super System)—complexified the core engine. Performance vs. Accuracy

: Modern MAME versions prioritize cycle-accurate emulation, which demands high-end CPUs. Version 0.130 strikes a balance, offering compatibility with thousands of classic titles while remaining lean enough to run on hardware with limited specs. LaunchBox Community Forums Understanding the ROM Set Structure

A "ROM set" is more than just a folder of games; it is a precisely curated database of files that must match the emulator version's internal data exactly. File Dependency

: MAME 0.130 requires specific "Parent" and "BIOS" files to function. For example, a "Clone" (a regional or bootleg variant of a game) often relies on the code found in the "Parent" ROM to boot. Merging Options Non-Merged

: Every game ZIP contains all files needed to run, making it easy to pick and choose individual games but taking up more total disk space.

: Clones only contain their unique files and must be kept alongside the Parent ROM to function, saving space.

: Parent and all its Clones are combined into a single ZIP file. Maintenance and Utility To manage this specific set, users often employ tools like ClrMamePro Verification

: By using a version-specific "DAT file," these tools can scan a collection, rename files to match the 0.130 standard, and identify missing components like

(Compressed Hunks of Data) required for newer arcade games that used hard drives or laserdiscs.

: Because the arcade hardware for these games is physically degrading, the 0.130 ROM set acts as a digital archive, preserving the software state of late 20th-century gaming culture for future generations. convert a newer ROM set down to 0.130 using ClrMamePro?

If you are looking to make the MAME 0.130 ROM set more useful, the best feature you can implement is "Non-Merged Rebuilding."

The 0.130 set is a popular "legacy" version often used for lower-powered devices like older PCs, Raspberry Pis (using

), or older handhelds. However, full ROM sets are notoriously bloated with non-working files, clones, and BIOS files that make them hard to navigate. Most Useful Feature: Creating a "Just the Hits" Custom Set

Instead of keeping the entire 25GB+ set, you can use management tools to filter and export only the games you actually want to play. Non-Merged Conversion : By default, MAME ROMs often rely on "parent" files (e.g., needs files from the original ). Use a tool like ClrMAMEPro

to rebuild your set into a "Non-Merged" format. This makes every ZIP file 100% self-contained, allowing you to delete any game you don't like without breaking others. Filtering by Genre/Rating Arcade Database

to upload your 0.130 XML list and filter for "Working Only," "No Mahjong," or specific genres like "Shoot 'em up." You can then export a batch file to copy only those specific ROMs to a new "Best Of" folder. Remove Nag Screens

: Version 0.130 still had many "disclaimer" and "nag" screens. While this requires a custom-compiled MAME executable rather than a ROM set change, using a version with "Nag/Highscore" patches significantly improves the "pick-up-and-play" experience. GameEx - Forums Compatibility Context CHD Updates : Version 0.130u1 introduced a major change to the CHD v4 format

. If your 0.130 set includes hard drive images (CHDs), ensure they are compatible with the specific sub-version of MAME you are running to avoid black screens. Frontend Integration

: To make the set truly "useful," pair it with a modern frontend like

. These tools can automatically download high-quality box art and video previews so you aren't just looking at a list of cryptic filenames like LaunchBox Community Forums how to use ClrMAMEPro specifically to trim down this 0.130 set?

The MAME 0.130 ROM set!

MAME (Multiple Arcade Machine Emulator) is an emulator that allows you to play classic arcade games on your computer. The ROM set, version 0.130, is a collection of game data that includes the games' ROMs (Read-Only Memory) and other necessary files to run the games.

Here's a report on the MAME 0.130 ROM set:

ROM Set Details

Notable Features and Changes

Game List

Here is a list of some of the games included in the MAME 0.130 ROM set:

Known Issues and Bugs

System Requirements

Conclusion

The MAME 0.130 ROM set is a comprehensive collection of classic arcade games that can be played on your computer using the MAME emulator. With its vast library of games and improved emulation, it's a great resource for retro gaming enthusiasts. However, be aware of the potential issues and bugs, and make sure to check the system requirements to ensure smooth gameplay.

The MAME 0.130 ROMset refers to a specific collection of arcade game data files released on March 9, 2009 . Because MAME evolves to improve emulation accuracy, each version typically requires its own matching ROMset to ensure games boot correctly . Key Technical Details (v0.130) Release Date: March 9, 2009 .

CHD Format Change: A major update to the Compressed Hard Disk (CHD) format occurred immediately after v0.130 (specifically in v0.130u1), which rendered previous CHD differencing files invalid .

Notable Fixes: This version included palette bug fixes for GP World, sprite positioning for Zero Target, and new graphic ROMs for Head Panic (1999) . Available Versions & Documentation

Official binaries and source code for this specific version are archived for historical reference:

Official Source: MAME 0.130 (Source) on the Internet Archive . Official Binary (Windows 64-bit): MAME 0.130 (64-bit) . Official Binary (Windows 32-bit): MAME 0.130 (32-bit) .

Technical Changelog: Comprehensive details on driver changes and internal source modifications can be found on the MAMEDEV Wiki . ROMset Compatibility

Writing a review for a specific MAME romset like 0.130 requires looking at it through the lens of retro gaming history. This version, released in late 2008, occupies a very specific "sweet spot" for many enthusiasts.

Here is a review of the MAME 0.130 Romset, breaking down why it remains a popular choice today.

If you download a "merged" 0.130 set, each parent ZIP contains clones internally. MAME can read it, but you cannot delete parent without breaking clones.