MAME readconfig and noreadconfig explained for Android troubleshooting
`readconfig` allows MAME to load its normal configuration files; `noreadconfig` starts without reading them. Use `-noreadconfig` for one controlled launch to ask whether an INI-layer setting causes the failure, then compare showconfig output. Do not delete configuration files or assume the Android wrapper stopped injecting arguments.
Do this in order
- 01
Record the wrapper settings and capture the normal effective configuration.
- 02
Back up INI and CFG directories without moving or editing them.
- 03
Launch the same authorized machine once with `-noreadconfig` and otherwise identical arguments.
- 04
Compare the first error, paths, renderer, sound, and input behavior with the normal launch.
- 05
If the failure disappears, re-enable configuration and inspect precedence one file at a time.
- 06
If it remains, move to wrapper arguments, content audit, or platform logs; restore no files because none were deleted.
Decision and diagnostic table
| Result | Meaning | Next boundary |
|---|---|---|
| Only normal launch fails | Loaded configuration contributes | Inspect INI precedence |
| Both launches fail identically | Cause is outside loaded INI | Wrapper, media, OS log |
| Paths differ | INI supplies search paths | Compare showconfig |
| Option unavailable | Wrapper filters upstream switch | Use package diagnostics |
A clean launch is an experiment
`-noreadconfig` changes one input layer and preserves the original files. That makes it safer and more informative than resetting an entire app.
Wrapper arguments can still win
An Android frontend can append command-line values even when MAME skips INI files. Record those arguments before attributing the result to upstream defaults.
Test only with games and firmware you created, dumped lawfully, or received under permission covering your use. Emulator settings and technical compatibility never grant rights to ROM, BIOS, CHD, artwork, music, or other media.