Is this motherboard/cpu fast enough?

[bluevolume]

I'm moving forward with my MAME project, and I picked up a motherboard/cpu/memory combo off of Craigslist.  I'm starting to think that I might have made a mistake; didn't realize that the latest versions of MAME are so CPU hungry.

Here are the specs:
AMD x64 3000+ (1.8GHz)
1gb PC3200 RAM
MSI MSI RS482M4-ILD board
Integrated ATI x300 graphics (though I will probably replace this with an ArcadeVGA)

I loaded up a clean version of XP and ran through all of the performance tweaks that I know of.  My benchmark game is MK2, and no matter what configurations I try this game sits at 100% CPU all the time.  I know that means that MAME is throttling itself, this is not what I want to see in a project that I'm just starting.

Any ideas?  On paper does it sound like this board should be fast enough?  If I have to go with something else, I found a deal on a Pentium D 2.6ghz -- would that get me there?

Thanks!
Blue

[ahofle]

I loaded up a clean version of XP and ran through all of the performance tweaks that I know of.  My benchmark game is MK2, and no matter what configurations I try this game sits at 100% CPU all the time.  I know that means that MAME is throttling itself, this is not what I want to see in a project that I'm just starting.

I'm not sure why you are concerned with CPU utilization while MAME is running.  Are you planning on encoding video while you are running MAME?  Load up MK2 and press F10 to unthrottle and see how fast it goes.  That's all the matters on a MAME rig.  Your system should be fine for the vast majority of games IMO.

[torez]

Did you try updating the drivers or just use default ones that came with Windows XP?  Check mobo manufacturer's website for any updates, then go to ATI, etc.  Integrated video card is not the best choice, as it takes cpu cycles as well.  Make sure your ram has matching cass latency (CL, that would be either 2.5 or 3).

[bluevolume]

Did you try updating the drivers or just use default ones that came with Windows XP?  Check mobo manufacturer's website for any updates, then go to ATI, etc.  Integrated video card is not the best choice, as it takes cpu cycles as well.  Make sure your ram has matching cass latency (CL, that would be either 2.5 or 3).

I think I'm good with the drivers.  Hopefully the ArcadeVGA card will help, I'll be disabling the integrated video at that point.

[Neilyboy]

I would guess with those spec's if you are experiencing and hiccups in playback its more than likely due to the onboard video. Let us know how things roll after the ArcadeVGA installation. Im rather curious myself.

Neil

[TOK]

Somethings up there... My fastest machine is 2ghz and everything is fast except for stuff that is slow on all rigs. Mortal Kombat has been in MAME for numerous revisions. As a last resort, go back to like .99 or something. My bartop will run it full speed with .99 and its a P3/800mhz with whatever oddball RAM I had to throw in it... 384 meg via a 512 and 128.

[Malenko]

my MAME cab's PC is a lowly Dell Optiplex 210L P4 @ 2.8GHz with onboard video and a gig of RAM. UMK3 runs full speed with no hiccups, when you hit F11 does it say 53/53 ?

[bluevolume]

my MAME cab's PC is a lowly Dell Optiplex 210L P4 @ 2.8GHz with onboard video and a gig of RAM. UMK3 runs full speed with no hiccups, when you hit F11 does it say 53/53 ?

I tried MK3, and it says "0/10 100%", with it dipping down to 99-98% just a couple of times.  Hitting F10 puts it at about 114% average.  So I guess the processor does have a tiny bit of head room, just not much. 

I would think that the old 2.8 P4 would be faster if we are talking pure CPU emulation.  The AMD chip I have while newer is only running at 1.8GHz.  I've only really kept up with servers the last couple years, I'm not up to speed on desktop CPU setups anymore.

[xmenxmen]

Interesting....  On my Athlon 1800, I can run MKIII at full speed with no slowdown.  Only difference on mine is that I have a Radeon 7500 with s-video out at 800x600. 

BTW, what resolution are you running it at.  If it's high, try setting it low like 640x480.