MAME ROM, CHD, and sample files explained
ROM files hold fixed device data, CHDs represent disk or other mass-storage media, and samples are optional recorded sounds used by certain emulated systems. They have different paths, validation methods, and dependencies; read the exact audit or runtime message before replacing anything.
Do this in order
- 01
Record the exact MAME revision and machine short name.
- 02
Run the machine's ROM audit and copy every named missing or incorrect item.
- 03
Classify each item as ROM/device data, disk media, or a runtime sample requirement.
- 04
For CHDs, inspect the expected machine folder and parent relationship; do not ZIP the CHD.
- 05
For samples, confirm the machine actually uses them and inspect the configured sample path.
- 06
Return only to your authorized source or own dump, then rerun the same audit and launch test.
Decision and diagnostic table
| Asset | Role | Primary evidence |
|---|---|---|
| ROM | Fixed program, graphics, firmware, or device data | MAME ROM audit and expected hash |
| CHD | Compressed disk or other mass-storage image | CHD header plus MAME dependency |
| Sample | Recorded sound used by specific drivers | Runtime message and sample path |
| Artwork | Optional presentation layout | Layout/artwork path, not ROM audit |
Missing does not name a legal source
An audit identifies a technical dependency, not permission to fetch it. Keep provenance separate from compatibility.
Each class has a different repair
A CHD folder change cannot repair a bad ROM hash, and a sample archive cannot replace unemulated sound hardware. Act on the exact class named by the target build.
MAME's file labels and hashes do not grant distribution rights. Obtain ROM, disk, sample, artwork, and firmware data only from your own authorized sources.