Launch a MAME software-list item on Android without guessing media slots
Use the exact MAME build to identify a system and software-list short name, audit that authorized item, then launch it as `mame system software` when the build can select the correct part automatically. If it cannot, run `mame system -listmedia` and use the reported media switch. An Android wrapper must expose software lists, the hash directory, and either the relevant UI or arguments; an arcade-only core may not.
Do this in order
- 01
Record the Android wrapper and embedded MAME version, then prove that its hash directory and software-list UI are present.
- 02
Use that build's system selector or `-listfull` to record the emulated system short name.
- 03
Use the software selector or `-listsoftware system` to record the software list, item short name, parts, and support status.
- 04
Audit only your authorized item with the build's software verification workflow before changing mount arguments.
- 05
Try `mame system software`; if selection is ambiguous, run `mame system -listmedia` and use only a switch the build reports.
- 06
Cold-launch again through the Android wrapper and record system, item, part, media switch, audit result, and any wrapper limitation.
Decision and diagnostic table
| Evidence | Answers | Does not prove |
|---|---|---|
| `-listsoftware system` | Known item and list | Files are present |
| `-verifysoftware` | Expected media matches | Android wrapper can launch it |
| `system -listmedia` | Available mount switches | Automatic part choice |
| Successful cold launch | This exact stack works | Other MAME generations work |
A software item is not an arcade machine
MAME software lists describe media mounted into an emulated host. The system, list, item, and part are separate identities, so an archive filename alone is not a launch contract.
Ask the build which slot exists
`-listmedia` reports the image devices exposed by the chosen system. This avoids copying a cartridge, floppy, or CD switch from another machine or MAME generation.
Android is an additional boundary
A standalone desktop command can be technically correct while an Android frontend hides arguments or ships without matching hash data. Document that limitation instead of treating an unsupported wrapper as missing game data.
Use only game, firmware, artwork, music, and media files you created, dumped lawfully, or received under permission covering your use. Emulator compatibility never grants content rights; do not use unauthorized ROM, BIOS, CHD, artwork, music, or download mirrors.