MAMEDEV Forum

I'd like this confirmed before I post a bug report. I'm running vanilla 0.276 on Void Linux (x86-64).

1. Open MAME, then click RMB on any game in the list that you can usually run.

2. Select "Input Device Options", then select anything in the new window and change something.

3. Save your changes and go back to the ROM list. Double click the entry you just edited to run the game.

Here at this point the game ROMs are gone and MAME exits. It has been happening for a number of releases now but only recently I got access to 0.276 for my distro, then I tried to create my account here and 0.277 was released in the meantime, so please bear with me...

Maybe I should add that my CPU is older than x86-64-v2 but according to the notes in the front page only *Windows* binaries have this requirement.

Make your roms read-only. I can't see how MAME could kill your roms in any case.

EDIT: There's also this: https://github.com/mamedev/mame/issues/13233
where the paths are changed, making it seem that your roms aren't there any more.

Robert wrote: ↑Fri May 09, 2025 8:17 am There's also this: https://github.com/mamedev/mame/issues/13233
where the paths are changed, making it seem that your roms aren't there any more.

Indeed, that was it. Glad to see at least it isn't happening only to me. Thanks.