Home Page Forums MAME Non-Windows MAME Support M+GUI 1.5.0 20100305 (Win/Linux/Mac/src)

neogeo.zip is in the ROMs folder!
Very strange... No NeoGeo games shows up.
I'm running M.A.M.E. v0.143u2 64bit and mamepgui 1.5.0

SOLVED!
I found a new version of "neogeo.zip" and now it works!

For anyone on OS X who has M+GUI crashing after updating MAME:

Open a Terminal prompt, navigate to your MAME folder and type ./mame64 -cc (./mame -cc if you're on 32-bit OS X obviously) to update your mame.ini. Your existing settings will stay the way they are.

When doing this, you will see one of the weirdest error messages in the world:
"Illegal integer value for numprocessors: "auto"; reverting to auto"
Incidentally, this error message is apparently part of the reason why M+GUI crashes while populating the gamelist:
http://www.mameworld.info/ubbthread...ded&sb=5&o=&fpart=1&vc=1

In the Finder, click Go, Go to folder, type ~/.mamepgui and press return. Delete the cache folder and mamepgui.ini.
Move your mame.ini out of your mame folder.
Start M+GUI and point it to your mame binary as prompted. Once it's done populating the game list, quit.
Put back mame.ini and start M+GUI.

This way, if you had everything set in mame.ini already, you only have to set up the GUI part of M+GUI again.

isn't it enough to open mame.ini and change "numprocessor" from auto to 1?

:lightbulb: It might be possible to get around this issue entirely by opening mame.ini and setting the numprocessors value to the number of CPU cores you have.

Yep eta...took me about 33 seconds to write that post.

Yes it really works.. I compiled 143u4 just now and M+GUI doesn't crash anymore.

Hi, I have a question;

is it possible to change the font color of the games?

I followed the instructions after MAMEPGUI crashed after an update but it does not work. It still crashes.

I removed all from .mamepgui, the prefs in the prefs folder, removed the mame.ini and tried the ./mame64 -cc but nothing helped. Still crashes.

By the way - any hopes that the great MAMEPGUI will be updated in future?

For this particular crash, all you need to do is set the numprocessors value in mame.ini so that it matches your number of CPU cores.
If that doesn't work, maybe you have some other issue.