MAME software-list and media verification / 2026-08-09

Use MAME verifysoftware for software lists instead of verifyroms

Choose the correct MAME audit for software-list media and keep its item, part, machine, BIOS, and file identities separate from arcade sets.

11 minute audit guideOfficial MAME 0.289 command semantics; Android ports may hide commands or ship a different hash directory

Use MAME verifysoftware for software lists instead of verifyroms

Use `-verifyroms` for machine ROM sets and `-verifysoftware` for software available to a selected system; use `-verifysoftlist` when you need to constrain the audit to one software-list name. Record the exact MAME build, system shortname, software-list name, item shortname, and reported missing or incorrect media. Do not rename a file or add a generic BIOS pack to turn one audit type into another.

Do this in order

  1. 01

    Record the Android port, exact upstream MAME revision, system shortname, software-list name, item shortname, and lawful source receipt.

  2. 02

    Use the build's software menu, `-listsoftware`, or `-getsoftlist` output to prove that the item belongs to the selected list and machine.

  3. 03

    Run `-verifysoftware` for the selected system, or `-verifysoftlist` for the exact list, and preserve the complete first result without editing filenames.

  4. 04

    Classify each line as an item ROM, disk, multipart medium, parent/clone item, machine ROM, BIOS/device dependency, or a best-available/redump status.

  5. 05

    Correct only the named path, item, part, or lawful source mismatch, then repeat the same audit before attempting to launch the software item.

  6. 06

    Record launch syntax, mounted part, boot result, controls, save path, and relaunch separately; a clean audit does not grant rights or prove every runtime path.

Decision and diagnostic table

TaskCorrect toolIdentity to preserve
Audit arcade or machine set`-verifyroms`Machine shortname and dependencies
Audit software for one system`system -verifysoftware`System, list, item, and part
Audit one software list`-verifysoftlist listname`List name without `.xml`
Inspect list definition`-getsoftlist` / list outputBuild-specific XML and hashes

Machine sets and software items are different namespaces

An arcade machine shortname identifies an emulated system and its ROM requirements. A software-list item identifies media used by a compatible emulated system, and one item can contain multiple parts. Keep system, list, item, and part in the receipt so a short filename cannot collapse those layers.

Best available is not the same as good

MAME may document imperfect dumps or media needing redump as the best known evidence. Preserve that exact status instead of treating every non-fatal result as a verified good file or searching for an unreviewed replacement.

Audit and permission answer different questions

A software-list hash describes expected technical identity for one MAME build. It does not tell you whether copying, downloading, or redistributing that software is permitted. Keep the lawful source receipt beside, not inside, the technical audit.

First-party sources

Related guides