Stripped Mame EXE for Golden Tee

[Wade]

Now that I have my new Atomic FE Layout ready, I'd like to add a few games to my machine.  Some will be Daphne with a couple of laserdisc games (need to order the DVD first), and others will be Golden Tee 2k and Classic (2001).

I can have a different EXE used for just these games, because I'm using an older version of Mame for my other games.

The problem is, the newer MAME exes that run Golden Tee are HUGE and bloated.  I tried .99 and it ran for minutes and never finished loading the game!  I had to abort it.  Maybe I need more RAM in my machine.

Anyway, I thought I'd check if anyone has a custom build of .96-.99 that has only the Golden Tee games in it, since that is all I plan to run from that version.

Thanks!
Wade

[Minwah]

I take it you have skip_validitychecks 1 set?

[Wade]

Yeah, I tried that.  I may try adding more RAM.

Wade

[Howard_Casto]

For the record removing stuff from mame won't really fix anything.  It's the mame processor cores that are making things slower and it isn't possible to remove any that would cause any noticable speed increase. 

[Wade]

My speed problems with mamewin99 don't seem to be directly processor related, but  RAM and exe size related.  Maybe it is something else entirely?  I should try mamewin96, just in case.

Are you saying that even a much smaller, GT-only version of Mame would be just as slow to load?  I just want to make sure you are understanding the problem.  I don't know MAME's architecture, but I assume that removing most of the drivers would cut down on its size dramatically.  On my machine anyway, the smaller MAME versions load FAR quicker, but maybe I'm barking up the wrong tree.

Wade

[youki]

Hi wade,

Just do a test, try to run a small game like pacman using mame 0.99 , a check the loading time.

I don't know GT  , i suppose it use more memorythe a "pacman" , and it could be your problem. Recent mame.exe consume huge memory just by itself without game. (about 40mb, i'd say i remember what i saw when i tested) at this memory you have to add the memory used by the game. Few Kilo for a pacman , and hundreds of mega byte for others.  So if you have not enought memory , your processor will begin to swap memory to disk... and your loading time will slowdown terribly.
Do you hear you hard drive ? the sound is typical when it is swapping.

So by reducing the size of the mame exe  , removing all drivers except GT, you could save may be (it is just a guess) 35 Mega byte of your memory.  And it could effectivly speed up your loading!

With Atomic, you can a in the .CFG file , this line :
LOADSLEEP=2000

It could improve loading speed in your case , but no sure at all.

[Buddabing]

Hello,

You can drastically reduce the size of your executable using a tiny compile.

You'll need the compiling tools from mame.net.

Edit your makefile so that TINY=1 is not commented out. Also set optimization to your specific processor type.

I took the liberty of creating a tiny.mak for you. I've attached a file called tiny.txt, rename it to tiny.mak and put it into the src subdirectory.

When I compiled the program it was only 1.7 megabytes in size.

Regards,
Buddabing

[Wade]

Thanks for the tips.  Budda, I haven't done a Windows build yet, so I will have to go through that process before I can make custom Windows builds.

Wade

[TalkingOctopus]

What are your computer's specs?  I doubt adding ram will help much at all.

[Wade]

I have a lot of idea here to try.

The system only has 128M, processor is AMD XP 1700+, Win2K.

Wade

[wakerlet]

I have a lot of idea here to try.

The system only has 128M, processor is AMD XP 1700+, Win2K.

Wade

OMG, you must add more RAM.

[zaphod]

Second that about RAM.  Get 512 in there at least.  You're crippling that poor AMD chip.

[TOK]

I concur with adding more RAM. Its cheap, and you already have a solid spec machine.
I'm doing something similar to what you're doing. My cabinet is based on a .84 ROM set. I have .99 on there, but in a totally separate folder and only run two games with it, Golden Tee 3D and Robotron. I took the icon from the PC version of Golden Tee and made a shortcut to it on my cabs desktop. I've just been running the new version of Robotron (slowed down version) from the Command line.

[zaphod]

Wade, I just pulled down Mame .96 and ran GT2k and 3D at 60fps (good enough) on an XP1800+ with 512RAM.  It took maybe 5 seconds to start up, if that.  Sounds like your only issue is the memory.  Don't waste your time trying to get a custom build if you only intend to play these few games.

[SirPeale]

Thanks for the tips.  Budda, I haven't done a Windows build yet, so I will have to go through that process before I can make custom Windows builds.

Is this a DOS build?  You have the latest DOS source?  If not, that's the reason it's taking so long to run.  Some options were only added recently.

[Howard_Casto]

For the record, afaik a tiny complie won't save you any memory.  When the tiny version is ran, it decompresses itself into memory, so in effect a tiny compile might cost you resources.

Btw you do know that the minimum system requirements for 2k are 128 megs right?  In case you don't know the windows code, you take the min sys req they post on the box and double it.  That will truly be the lowest amount of ram you can get the os to run on and actually run something other than word or mspaint. 

In this day and age, I won't even consider xp on a system unless it has 512 megs. 

[Buddabing]

For the record, afaik a tiny complie won't save you any memory.

[TalkingOctopus]

Ok...like everyone else said, ADD MORE RAM!  I use an athlonxp 1800 w/ 512 MB of ram as my primary computer.  2000/XP are painfully slow with 128 MB.  Upgrade now!

[Wade]

Okay guys, there is a lot here to respond to.  This is a very interesting thread, on several levels.

First, I will try adding RAM.  I think I have some more spare chips laying around.  Again, this is why I asked for a stripped MAME version.  I figured RAM was probably an issue, because of the FAT footprint of Windows (GT ran just fine when I run it on the same machine, in DOS!)

FWIW, this is the only problem I have with 128M and Win2K.  Atomic, and all my other MAME stuff runs perfectly with no delays.

If I can't find more RAM chips or it doesn't fix the problem, I will try a tiny Mame build.  Or, I may just do the tiny build anyway!

Peale, I'm not sure what you are asking about DOS.  I am not running a DOS build in this Windows setup.  I was trying to run 0.99 Win Mame.  I have run the 0.96 DOS version with GT, in DOS, and it worked great.

Howard, I agree I wouldn't normally try to run WinXP on a system with less than 512k either.  In this case, this isn't a general purpose computer, this is used only for MAME, and if it runs fine with XXX RAM then that is all that matters to me.  (As I said, everything runs fine except this Mamewin99 version and GT).  I don't care about performance for any other apps.

[Wade]

Budda,

   I did a 0.92 build for windows, and it worked.  I tried your tiny.mak file, and set the target=tiny, but it stops pretty quickly with this error screen.

Wade

[Buddabing]

Budda,

[Wade]

Oh, for some reason I was thinking GT was added in 0.92... I had downloaded 0.96 a couple of days ago, was that the first version with GT?

*** EDIT: Apparently it WAS 0.96, as it is doing the tiny build now.

Thanks for the help Budda, I will try this EXE tonight and see if it runs.

I get the following error when I try to run it:

"src/drivers/itech32.c: gt3d uses non-present CPU
src/drivers/itech32.c: gt3d cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3d uses non-present CPU
src/drivers/itech32.c: gt3dl192 uses non-present CPU
src/drivers/itech32.c: gt3dl192 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dl192 uses non-present CPU
src/drivers/itech32.c: gt3dl191 uses non-present CPU
src/drivers/itech32.c: gt3dl191 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dl191 uses non-present CPU
src/drivers/itech32.c: gt3ds192 uses non-present CPU
src/drivers/itech32.c: gt3ds192 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3ds192 uses non-present CPU
src/drivers/itech32.c: gt3dv18 uses non-present CPU
src/drivers/itech32.c: gt3dv18 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dv18 uses non-present CPU
src/drivers/itech32.c: gt3dv17 uses non-present CPU
src/drivers/itech32.c: gt3dv17 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dv17 uses non-present CPU
src/drivers/itech32.c: gt3dv16 uses non-present CPU
src/drivers/itech32.c: gt3dv16 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dv16 uses non-present CPU
src/drivers/itech32.c: gt3dv15 uses non-present CPU
src/drivers/itech32.c: gt3dv15 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dv15 uses non-present CPU
src/drivers/itech32.c: gt3dv14 uses non-present CPU
src/drivers/itech32.c: gt3dv14 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dv14 uses non-present CPU
src/drivers/itech32.c: gt3dt231 uses non-present CPU
src/drivers/itech32.c: gt3dt231 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dt231 uses non-present CPU
src/drivers/itech32.c: gt3dt211 uses non-present CPU
src/drivers/itech32.c: gt3dt211 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3dt211 uses non-present CPU
src/drivers/itech32.c: gt97 uses non-present CPU
src/drivers/itech32.c: gt97 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97 uses non-present CPU
src/drivers/itech32.c: gt97v122 uses non-present CPU
src/drivers/itech32.c: gt97v122 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97v122 uses non-present CPU
src/drivers/itech32.c: gt97v121 uses non-present CPU
src/drivers/itech32.c: gt97v121 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97v121 uses non-present CPU
src/drivers/itech32.c: gt97s121 uses non-present CPU
src/drivers/itech32.c: gt97s121 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97s121 uses non-present CPU
src/drivers/itech32.c: gt97v120 uses non-present CPU
src/drivers/itech32.c: gt97v120 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97v120 uses non-present CPU
src/drivers/itech32.c: gt97t240 uses non-present CPU
src/drivers/itech32.c: gt97t240 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt97t240 uses non-present CPU
src/drivers/itech32.c: gt98 uses non-present CPU
src/drivers/itech32.c: gt98 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt98 uses non-present CPU
src/drivers/itech32.c: gt98v100 uses non-present CPU
src/drivers/itech32.c: gt98v100 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt98v100 uses non-present CPU
src/drivers/itech32.c: gt98s100 uses non-present CPU
src/drivers/itech32.c: gt98s100 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt98s100 uses non-present CPU
src/drivers/itech32.c: gt98t303 uses non-present CPU
src/drivers/itech32.c: gt98t303 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt98t303 uses non-present CPU
src/drivers/itech32.c: gt99 uses non-present CPU
src/drivers/itech32.c: gt99 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt99 uses non-present CPU
src/drivers/itech32.c: gt99s100 uses non-present CPU
src/drivers/itech32.c: gt99s100 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt99s100 uses non-present CPU
src/drivers/itech32.c: gt99t400 uses non-present CPU
src/drivers/itech32.c: gt99t400 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt99t400 uses non-present CPU
src/drivers/itech32.c: gt2k uses non-present CPU
src/drivers/itech32.c: gt2k cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt2k uses non-present CPU
src/drivers/itech32.c: gt2ks100 uses non-present CPU
src/drivers/itech32.c: gt2ks100 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt2ks100 uses non-present CPU
src/drivers/itech32.c: gt2kt500 uses non-present CPU
src/drivers/itech32.c: gt2kt500 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt2kt500 uses non-present CPU
src/drivers/itech32.c: gtclassc uses non-present CPU
src/drivers/itech32.c: gtclassc cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gtclassc uses non-present CPU
src/drivers/itech32.c: gtclassp uses non-present CPU
src/drivers/itech32.c: gtclassp cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gtclassp uses non-present CPU
src/drivers/itech32.c: gtcls100 uses non-present CPU
src/drivers/itech32.c: gtcls100 cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gtcls100 uses non-present CPU
src/drivers/itech8.c: gpgolf uses non-present CPU
src/drivers/itech8.c: gpgolf uses non-present CPU
src/drivers/itech8.c: gtg2 uses non-present CPU
src/drivers/itech8.c: gtg2 uses non-present CPU"

Thanks,
Wade

[Buddabing]

You were right, GT was added in 0.92.

I'll look at the error tonight, in the meantime please try compiling 0.99.

[Wade]

Okay, I'll give 99 a try tonight.  I'll have to set up the compile utils on my home machine.

I was really surprised how easy it is to compile the Windows versions (or is it, the later versions?)  Last time I compiled it was 0.36, and it took a LOT of downloads and config to make it all work.

Thanks,
Wade

[SirPeale]

Peale, I'm not sure what you are asking about DOS.  I am not running a DOS build in this Windows setup.  I was trying to run 0.99 Win Mame.  I have run the 0.96 DOS version with GT, in DOS, and it worked great.

You had mentioned:

Budda, I haven't done a Windows build yet, so I will have to go through that process before I can make custom Windows builds.

So I assumed that you were working with a DOS build.

Up until quite recently (I think .97 or .98) the DOS version didn't support skip_validitychecks.

[Wade]

Budda,

   Same types of error messages when running 99 also.

   More bad news.  I tried a dozen other RAM chips, and they are either the wrong type, smaller than what was in there already, or are unreliable.  I DO however have 192M instead of 128M (I know, big deal).

   When running with a larger but faulty chip, it did load okay, however the sound stuttered frequently.  Never did this in DOS, or in any other games. :/

Wade

[u_rebelscum]

I get the following error when I try to run it:

"src/drivers/itech32.c: gt3d uses non-present CPU
src/drivers/itech32.c: gt3d cpu #0 uses wrong data width memory handlers! (width = 8, memory = 000c0005)
src/drivers/itech32.c: gt3d uses non-present CPU
src/drivers/itech32.c: gt3dl192 uses non-present CPU
[snip]

I've never used tiny, but I think you aren't including the CPU GT uses in the tiny compile.  Look around to info on adding CPUs to the compile.

[Buddabing]

Correct, the tiny.mak was missing two cores that I know of.

I've attached a new tiny.txt, rename it to tiny.mak and recompile.

I'm unfortunately unable to actually run the game since I don't have it. All I can do is compile it.

[Wade]

Sweet, I'll try it again.

[Buddabing]

I went ahead and added in all other cpu cores. The result is an executable that is 6+ megabytes. Not that great. I'm sure it can be whittled down some, but I just don't  have the time.

I compiled the tiny executable and ran gt3d successfully.

I've attached tiny.txt (rename to tiny.mak and do make clean followed by make)

[Wade]

Thanks Buddabing.  At the moment, I'm having so many problems with my Windows setup, that this GT issue is on the backburner.  The chances are VERY high that I'm going to switch back to DOS anyway.  I have had nothing but problems with MAME and Windows.  All this work just to use a fancier FrontEnd, I've just about decided it isn't worth the hassle.

My DOS setup was perfect in performance, convenience, and video modes, except for the bland Frontend.

Wade

[Buddabing]

Thanks Buddabing.

[Wade]

Yeah, I will have to give it a try.

Wade

[Lilwolf]

btw, if you don't care about disk storage space.

use plain jane mame but un-upx it.   So the executable is about 30mg.

With this, and windows... Windows will only load the part of mame that it uses.  Otherwise (as mentioned before) it loads the whole EXE into memory, then brings out the parts you want/need.

Anyway, if you have diskspace, but low memory... Just uncompress the EXE file and you will as good as you can get.

[Wade]

Thanks for the tip.  I wasn't aware it would work that way!  RAM is at much more of a premium on my system than disk space.

Wade

[SirPeale]

Thanks Buddabing.  At the moment, I'm having so many problems with my Windows setup, that this GT issue is on the backburner.  The chances are VERY high that I'm going to switch back to DOS anyway.  I have had nothing but problems with MAME and Windows.  All this work just to use a fancier FrontEnd, I've just about decided it isn't worth the hassle.

My DOS setup was perfect in performance, convenience, and video modes, except for the bland Frontend.

Wade

IIRC Kymaera supports DOS now. You should try that.

There's even support for arcade monitors, but at the moment it's not working.