Weird Mame32 problems

[Mr. Three]

It was running very well a few days ago. Suddenly poof, it's not only not working at all but actually freezing solid.

Mame32 seems to be freezing up regardless of which ROM is chosen, and the screen sort of stretches out. Total freeze too, no ctrl alt del, no F4, no ESC, I have to basically reset the machine! I have tried seemingly endless variations of settings including default, resetting the paths to roms, auditing everything, eliminating then reinstalling video drivers, reinstalling DirectX, but I don't know what else to do. It was working fine the other day.

Here's a pic, for what good it will do. Is there a simple solution to this? It is driving me crazy. I have been screwing around trying to get it to work for days now. 

Does anyone please know how to fix this? I can provide any details that may help here!

[SGT]

You need to determine whether it is mame32 or some other factor like hardware/other software causing the lockup.  I would create an empty folder and put a newly downloaded version of mame32 into it and copy 1 rom file over to this new install.  If the problem still occurs with a brand new fresh install, it is probably not mame32 causing the lock up.  Your video card or other hardware could be flaking out on you or you might have malware or etc....   Have you installed any new software recently?

[Mr. Three]

I absolutely did that! Still crashed. 

It is definitely maybe Mame32.  Maybe not. Oh hell I don't know. 

[SGT]

I am saying that if it still crashes with a brand new installation, it may NOT be Mame32.  That is as long as you didn't copy any config or other files from the old install and especially if you have already ran that version successfully.    It could be your video card flaking out with what Mame is asking it to do or it could be your memory or etc...   I would go back to a XP restore point that was created before the crashing started occurring to help rule out other software running in the background that might be conflicting with mame32.

[Mr. Three]

I'm confused. There's nothing to install with Mame32. The program can reside anywhere, correct? I had a copy in a folder on the desktop and another on a jump drive. Both exhibit the same behavior.

How do I eliminate config files or reset the program to defaults? No other software has been installed on this old machine.

[Mr. Three]

Here's some detailed info, if it helps! 


It stopped working after a simple restart. For some reason the computer started asking for sound drivers, which I cancelled, and the sound dropped out. When I restarted again, the sound was restored but Mame32 began locking up the exact same way every time it was started. I tried reinstalling the sound drivers again, as well as the video drivers, and removing all but one ROM file which has been my test ROM all along, but still nothing. The screen seems to be switching resolutions but freaking out before the ROM even loads. I don't get so much as the "hit button to continue" point, just the oddly stretched pointer on a black field of freeze.

Grrr, it was working prefectly and the table if bully built, now the software goes kooky on me. I admit I am a little new to emulation, so I don't know how to remedy this situation.

Maybe I should try an earlier version of the software? Regular MAME doesn't work because my video adapter is only 24bit and MAME insists on 32bit, but MAME32 worked fine for weeks. It would even run through MaLa, which I learned about here and still need to configure but currently don't run.

The machine is a 677MhzP3, 128Mb Ram, W98se

[SGT]

If this version of mame32 used to work fine, and you've tried a fresh install of this version with no change to the settings and it still crashes, then why would you think its mame32's fault?  I stand by my statement that either your hardware is causing the problem or some other software including Windows.  That's why I suggested going to an earlier restore point.  Obviously with Win98 you can't do that.

If the mame32 settings on the thumb drive are pointing to the drive C intallation, then that is not a fresh install and could be picking up some of the config files.

[Mr. Three]

I absolutely did that! Still crashed. 

It is definitely maybe Mame32.  Maybe not. Oh hell I don't know. 

I'll run system restore.

[SGT]

Dude I wasn't suggesting you run a system restore.  I was talking about Windows XP restore points which is totally different.  At the time I didn't know you had Win98.  You may have hardware problems (video card maybe) that a total system restore won't fix.

[Mr. Three]

Dude I wasn't suggesting you run a system restore.  I was talking about Windows XP restore points which is totally different.  At the time I didn't know you had Win98.  You may have hardware problems (video card maybe) that a total system restore won't fix.

All attempts at Restore failed just now anyway.

But understand, I thought it was a Mama32 issue because of the resolution switch and hang, and there are many settings that I as yet do not know the intricacies of in the program options. I realize I could be wrong. I am trying to provide as many details as possible here.

The video card is integrated into this motherboard, which came from a Dell L667r. There is a Creative sound card installed, but no other components. I can download a RAM checker utility or something but I don't really think that's the issue. I think it's some kind of driver conflict. Removing and reinstalling them all hasn't helped as yet. I may try that entire process again.

[ahofle]

It stopped working after a simple restart. For some reason the computer started asking for sound drivers, which I cancelled, and the sound dropped out. When I restarted again, the sound was restored but Mame32 began locking up the exact same way every time it was started.

Sounds to me like a hardware issue with your sound card.  Have you tried removing/replacing it?

[Mr. Three]

No, but I will try that immediately.

[Mr. Three]

And there it is. 

I assumed that uninstalling the drivers would be enough.    Yanking the card has resulted in a functioning Mame32 again, in total silence of course. Hey, at least it is working, and I know it has worked in the past, so getting it to work again in the future should be no problem, right?

Thanks for all your help guys! As a new guy around here, I have to ask - did I post everything correctly and follow forum rules and all that?

[ahofle]

Good deal.  Yeah, should work fine if you get a functional soundcard.  Does your motherboard have on-board sound that you can enable?  If not, just get any cheap soundcard -- should be fine for MAME.

And I'd say you followed the forum rules perfectly.