MAME problem

[ddockery]

I recently built a new PC. Ever since then, and time I try to start a game in MAME it just shuts down. I'm using MAME32. I get no error or anything, it just closes. I tried shutting down sound, direc3D, input devices, you name it, and it doesn't matter. It happens on all games. I'm running XP w/ SP2 and all updates. If anyone has any suggestions please let me know.

Thanks,
Drew

[Daniel Thomas]

Which version of MAME are you using? I've noticed that the latest version doesn't work properly. I think it's version .86. If that's the version you have, then it's definitely the emulator. Just hunt around for a slightly older version, like .84. Whatever bug is going around will be fixed soon.

[Sylentwulf]

Get rid of mame32 and try something like mamewah might help too.

[Daniel Thomas]

Maybe someone should sort out the differences between all these versions of MAME. I see a lot of them at Zophar, but I couldn't really tell heads or tails from any of them. Which version works best for you?

[Flack]

We set up a MAME cabinet last night using GLaunch as the front end and good ol' MAME (0.86) and it worked okay. On my laptop, I think I'm runing Mame32, 0.74. I never saw the point in updating MAME every 10 seconds. The games I play all work great. I doubt there's much they're gonna do to improve how ExciteBike runs anytime soon.

[Sylentwulf]

There's only one mame. All the rest are different front ends.
Basically, it's like putting skins on winamp, or modifying your desktop theme, it's the same program just looks different.

MAME32 is a bit different because it is run a bit differently through windows, and takes up more CPU and system resources. I run Mamewah on my arcade cab, and while I haven't gotten any of the skins to work right yet, I'm pretty damn satisfied with it.

[kingpong]

There are many different versions of MAME, if you include builds based on the regular source but with compiler optimizations for different processors. Any builds that introduce driver or functionality changes deserve to be ignored though.

Personally I haven't used anything but MAME32 in many years, barring a brief fling with SmoothMAME32. Front ends are such a cheesy kludge for any emulator... Using one application to launch another is just too inelegant for me. Even though the end result with MAME32 is effectively the same thing happening, for some reason it sits better with me to be using a single, integrated application.

This shutdown problem with MAME32 may be related to the recently reworked multi-session behavior, which was intended to reduce memory usage. Some people don't have any problems, others get one game to run then it crashes on a second game, while others can't get anything to run. I haven't had any problems up through .86u2, but I haven't seen an Athlon XP optimized .86u3 build posted yet to try that. But just in case the multi-session stuff isn't the problem though, clear out all the .nv, .ini, .cfg, etc. files since many of them were recently rendered invalid, and try again.

[Sylentwulf]

Well, yes, using mame on a PC without a controller, mame32 works great, but if you're using a controller or a mame cab, it's all but useless.

[ddockery]

kingpong, thanks for a good suggestion, but none of that seemed to help either. I'll have to hunt down when the multi-session stuff was added and try the last version before that in case that is my problem.

[kingpong]

Well, yes, using mame on a PC without a controller, mame32 works great, but if you're using a controller or a mame cab, it's all but useless.

I've never had any problems using controllers with MAME32 - at least nothing outside problems with the MAME core. Typically I use a USB PSX->PC adapter and never have any problems. I don't know if the recent controller changes help or not, but my only issue has been that the ctrlr.ini files or whatever would not recognize more than 10 buttons, while the internal configuration would recognize more. There's also a core bug with button 11 (I believe) resetting itself, and there's a bug with driver level (as opposed to game level) settings being ignored, but I can't think of any MAME32 specific controller issues.

But controller issues aside, I can see where with the relatively low resolution in a cab the MAME32 front end may be less than ideal. I used to go out to a TV, first with composite, then S-Video, then component, and at 640x480 it wasn't the best. At 800x600 on my projector though I have no complaints.

[Sylentwulf]

I meant without a keyboard and real mouse. It runs fine once you get into the game (besides needing a slightly faster computer) but using the frontend aspect of it isn't the easiest thing without a keyboard/standard mouse sometimes, and it LOOKS like a computer program.

[ddockery]

Alright, this just got REALLY weird. I downloaded the latest commnad-line version, and installed EasyMAME for a frontend. Nothing ran this way either. The commad box flashed up and then closed. SO I went into command line mode and tried it, and no matter what game I try, it lists EVERY rom as not found. I even tried unzipping one of them to be sure that wasn't the problem. Then I went back ito MAME32 and it's doing the same thing. These roms all check out fine under clrMAME. Any idea what the heck is going on?? Anyone?

[ddockery]

Through a LOT of copying stuff around, I have it down to my roms folder causing my problems. If I copy everything in my MAME directory EXCEPT the roms folder, create a new roms folder, and copy a file to it, that game runs fine. Any suggestions as to what may be the problem? clrMAMEpro give it the all clear.

[Sylentwulf]

Open the mame.ini file and make sure your rom path is correct?

[ddockery]

I had already wiped out all of my .ini files with no luck. I have everythiing working again, btu I still have no idea HOW. I ended up moving everything to another directory and it worked. The I moved it back and it still works. Nothing changed. Go figure.