MAMEDEV Forum

Hi!

I'm at Linux (at a Debian stable based x64 distribution. XFCE desktop).

At first I tried the repository version (0.251), then I uninstalled it and I compiled locally the official sources (0.278), but it affected from the same problem.

Though i can play several (already audited) ROMs (from "Working" category), when I'm trying again them, at a later time, It drops several "NOT FOUND" messages instead and fails to run them.

Any thoughts?
TIA!!!

Could it be this ?
https://forum.mamedev.org/viewtopic.php?t=1059

It may be, although at my case, MAME doesn't hurt or alters any of the ROMs.
(I checked the hash signatures).
It just somehow gets confused.

I also noticed a couple of other faulty symptoms:

At he locally compiled version, the "Cheat" option is missing.
(At the repo version, works flawlessly).

Finally, although I compiled the sources without debugging symbols, the "file" command says that the binary is not-stripped.
OK, it's very easy to issue the strip command, but it's an indication, of a problematic compilation.

In the post I linked to, it turns out the actual roms are not hurt or altered either.

If you read the second post in that thread, you will notice that a reference is made to this bug report :

https://github.com/mamedev/mame/issues/13233

where mame somehow (on it's own) changes the paths (in the ini files) to invalid locations, making it seem (to mame) that your roms aren't there any more. (because it cant find them in the now invalid ini location).

Oh GREAT!!!
Changing a single setting and you have to enter over and over again the rompath???
Obviously a no-go.

Since this is the worst but not the only bug that infests current releases, I'm thinking to try mame at the Windows instead.

THANKS for your help!!!