Meet the SNID-R-CADE

[Sniderman]

Hey gang,

OK, I have MAME running on my "primary" computer here at home. Works Hunky-dorey with no problems. Here are the stats on that system:

Compaq running Windows XP
AMD Sempron Processor
1.81 GHz
448 MB of RAM

Now then, I inherited an older system that I had planned to use for a MAME system. All of the comp's stats looked to hit the minimums needed for MAME emulation, but all of the games are running at half-speed (take the normal framerate, devide in half, that's where it sits) with the typical "skippy choppy" sound associated with an overtaxed processor. The games I'm running are older releases (Pac-Man, Donkey Kong) so I'm not trying to run Virtua Fighter or anything... Here are the older computer's stats:

Dell running Windows 98
Pentium III processor
730-ish MHz (best as I can tell when running a clocking program...)
128 MB of RAM

Now, I realize that "MAME minimum requirements" are a tough set to nail down as all ROMs run at different speeds, all computers are different, how do you have frame skipping/other MAME settings set, etc. But according to what little I've researched, a Pentium III processor is more than enough to run MAME. The computer was stripped down to it's base, so Windows and MAME are the ONLY programs on it, so there are no hidden programs, spyware, malware, etc.

Ergo, what could be causing the slowdown? Would increasing the RAM help speed things up? Or is a Pentium III just not gonna cut it here? Any quick fixes to get this up to speed would be grand. And increasing the Frameskip to 11 ain't exactly an option...

Thanks gang!

[Gapporin]

I don't know if this is a viable option for you or not, but if all you want to run are the "classics", you might want to downgrade to an earlier version of MAME (say around .70). With every new release, speed gets sacrificed in order to include more games/more accurate emulation/etc., and this affects all games. A version released around 2-3 years ago might have a general speed increase across the board more than the latest version of MAME would. And as far as the "classics" go, I don't think there's been any drastic changes done to them for awhile now (though I could be wrong).

[NE146]

That RAM is pretty friggin small so that's what I'd upgrade if you could. But aside from that, the computer should be fine for the most part.

Barring that, I dont know if you've done this, but the first thing I would do with that computer is friggin wipe it out completely and install the OS from scratch right off the bat. Especially if you're looking at making it just a Mame machine.. wiping it out completely and having a fresh OS with nothing on there would probably make a difference.

[jb143]

I have mame running fine on a 233MHZ machine. The only difference is the games you can run. My main mame computer is only slightly faster than yours (933MHz) and it runs all but a few of the more demanding games perfectly. I also maxed out the ram and installed a better graphics card so that might help a little.

Are you using the windows or colsole version of Mame? I think the windows version is more of a system hog. The console version has a built in GIU now. I know the command prompt was a turn off for a lot of people.

[InsaneDavid]

You may want to use an older version of MAME. On my desktop (900MHz) I can't run the latest builds at all so I normally run v0.76. Heck, my Pole Position MAME conversion has a 350MHz PII, 128MB RAM in it and it runs fine - of course it's running MAME v0.56.

[Sniderman]

Thanks gang. I'll grab an extra RAM stick on the way home (system only has space for two) and I'll bump it up by at least two times if not more. If that doesn't work, I'll use an earlier MAME build (currently running the most recent build with a Windows GUI). We'll see what happens then.

[NE146]

Thanks gang. I'll grab an extra RAM stick on the way home (system only has space for two) and I'll bump it up by at least two times if not more. If that doesn't work, I'll use an earlier MAME build (currently running the most recent build with a Windows GUI). We'll see what happens then.

What will happen then is you wipe that thing out and start it fresh if you haven't already

[Sniderman]

What will happen then is you wipe that thing out and start it fresh if you haven't already

Dagnabbit, I told ya it's got nothing but Windows and MAME on it. It was stripped to the bone, then a fresh version of Win98 was installed. Nothing else lurks on the hard drive. Clean as a whistle.

Anyway, I popped the sole memory stick out and was chagrinned to find it was SDRAM. You don't just walk into Best Buy and pick it up. Sure, Circuit City had one 258 MB stick - for $79.99. Ended up at a local computer thrift/salvage/"repair" shop and told 'em I was looking for a chunk of SDRAM. Guy tossed me a 128 MB stick for no charge. "Can't use 'em myself, and a new one's gonna cost you a mint. Just take this used one. If it works, it's yours. If not, no sweat."

Nice guy.

Anyway, got home and installed it. Works fine. I'm now at 258 MB....And MAME is only slightly faster. I'll try an older version now and see if that helps at all. If not, I guess I'll try getting more SDRAM off ebay or something. Kind of at a loss here...

[NE146]

ok then.. I guess the question needs to be asked, what version of mame are you running. Any of the "custom" builds of Mame32, etc.? Sometimes the differences in versions can be pretty huge

[Sniderman]

Well I *was* (operative word) running MAME32. Windows based and menu-driven. Very easy to use, but that was what was bogging me down. I took InsaneDavid's suggestion and downgraded to .076. Took me a while to remember how to use the MS-DOS prompt, but once I got going, I had MAME working. SUCCESS! The games I have are running fast with full sound and no slow down.

However, I need a simple front-end program as typing in everything is for the birds. But I'm afraid of bogging everything down again.

So, on the plus side, I seem to have it working. On the minus side, I miss the point and click simplicity...

[InsaneDavid]

However, I need a simple front-end program as typing in everything is for the birds. But I'm afraid of bogging everything down again.

GameLauncher is what I use on my desktop system. It takes a little while to get used to how it works and to get it set up how you like but after that adding / removing games is as easy as adding / removing roms to your MAME roms folder and running a mamescan.exe file that comes with GameLauncher.

Just for the record I've been able to run versions of MAME32 up to v0.95 for the MAME League competitions here without any problems. Of course most of those were classic era games. I can run pretty much everything I want to play under standard command line MAME v0.76 including sprite intensive shooters.

[jb143]

The newest windows console(not DOS but it looks like it) release of MAME has a built in GUI...so you don't need to use the command prompt. Just double click MAME and it shows a list of your games.

Also...you shouldn't have to "dumb down" your version of mame. I'm pretty sure that the console versions are updated much more frequently.

[NE146]

Well I *was* (operative word) running MAME32. Windows based and menu-driven. Very easy to use, but that was what was bogging me down. I took InsaneDavid's suggestion and downgraded to .076. Took me a while to remember how to use the MS-DOS prompt, but once I got going, I had MAME working. SUCCESS! The games I have are running fast with full sound and no slow down.

However, I need a simple front-end program as typing in everything is for the birds. But I'm afraid of bogging everything down again.

So, on the plus side, I seem to have it working. On the minus side, I miss the point and click simplicity...

Well again you *might* still be able to use Mame32 so that's why I was wondering what version you were running. Did you ever figure that out?

In my experience there was very often a pretty large difference in performance w/ mame32 depending on what build it was. Some ran pretty slow and the games suffered, while others launched games lightning quick and played them fine. Did you have the latest and greatest mame32 (I forget which it is.. either 0.124u1, or 0.124u2, or 0.124u3.. who the heck knows. But you really are steppng back in time with .076

But I guess if you're happy you're happy

[Sniderman]

Well again you *might* still be able to use Mame32 so that's why I was wondering what version you were running. Did you ever figure that out?

You know, I never checked to see the version running underneath MAME 32, so I have no idea...

In my experience there was very often a pretty large difference in performance w/ mame32 depending on what build it was. Some ran pretty slow and the games suffered, while others launched games lightning quick and played them fine. Did you have the latest and greatest mame32 (I forget which it is.. either 0.124u1, or 0.124u2, or 0.124u3.. who the heck knows. But you really are steppng back in time with .076

True, but at least I know that 1:1 speed is possible with the hardware I have. Now it's a matter of coming forward until I find the set-up I like with the bells and whistles I prefer. So somewhere between .076 and MAME 32 lies perfection.

[NE146]

You know, I never checked to see the version running underneath MAME 32, so I have no idea...

Just launch it, then look at the title bar.



Only reason I'm pushing this is most of the classics run absolutely fine in mame32 on on my 600 mhz Dell pc w/ XP on it. Yes 1:1 speed with no hiccups. Granted it has about 4x the ram, but still.

[rxd]

Not sure if you ever fixed this problem you're having but if you didn't I had this exact same problem and it took me quite a while to figure out what the issue was. I'm around 90% sure your issue is the same one I had, and it's that MAME, MAME32, etc., default to using Direct3D. Using that on a computer without a good video accelerator is just going to kill performance, no matter how much ram you have, even if you have a decent cpu. Change the video setting from Direct3D to DirectDraw and I'm virtually certain your problem will disappear...

[Sniderman]

Well, the problem is 95% gone by now. Turns out that any of the recent releases of MAME with the built-in GUI would sap my resources to a crawl. But when running .76 in DOS with an outside front-end, works quick as a charm. I have 512K coming in the mail, and we'll see if that bit of memory bump will allow me to use one of the newer MAMEs without losing any speed. But I've got it working well now, so if it doesn't work, at least I'm where I wanted to be anyway.

My newest hiccup is that I cannot get a controller to work through either of the USB ports. The controller's got power (little light on it lights up), but the drivers are missing, misdirected, corrupted, or something. I really haven't had time to troubleshoot, but I'm getting device errors when I try to install and/or initialize 'em.

[Flack]

DOS doesn't see USB devices natively. What controller are you running? There are probably drivers out there for it.

[InsaneDavid]

DOS doesn't see USB devices natively. What controller are you running? There are probably drivers out there for it.

Yeah, there's no reason to run DMAME. Once DOS MAME became a separate special build and eventually was discontinued (if I remember right) there was no reason to use it if you hardware was of decent spec. Regular old Windows command line MAME (pre built in GUI) will support all your USB devices. My MAME v0.76 setup uses regular command line MAME along with GameLauncher and I use a PS Family to USB converter with it, no problems at all.

I have to run DMAME on the Pole Position cabinet since the computer is much slower and everything with the exception of video is on the motherboard. That and I like being able to just throw the power switch without shutting anything down, since there are no extra external controls outside the wheel, shifter and pedal to do such with.

[Sniderman]

Well, if I run MAME through MAME32 (Or later MAMEUI), I have to frameskip to 6/10 to get a 100% run. My current way runs 10/10 allatime.

Regardless, I'm now working through the infamous "NTKERN.VXD" error to try to get the computer to recoginise the USB port. And that's just one error. The other error I get when I try to setup mew hardware tells me the device manager is full and I must remove somethin' before I bring in something. So conflicts ahoy!