[headkaze]

Just a point on Brians post, for those of you who get a little faint when using command line. You can actually download a GUI version of 7Zip off the net which allows you to right click on the file and extract it.

http://www.7-zip.org/

[headkaze]

Minor update. I mainly added a timer so I can see if the Dual Core option actually compiled Mame faster on my machine. I don't have a Dual Core but I do have HT, so it may just be a multi-threading option.

I'll post the results here.

EDIT: Interesting using the "Dual Core" setting reduced my compile time by 7 minutes. That's a notable difference, and I don't even have a dual core processor. I'm guessing the Hyper Threading helps though.

[headkaze]

Brian Hoffman, on Oct 1 2007, 09:57 AM, said:

Mame32 uses additional compnents... So NO..Sorry

I reakon you could use this okay to compile Mame32. All you have to do is copy over the original Mame source with the Mame32 stuff.

The patches might not work though.

[SpyDIRmaN]

I've followed the above instructions.
Used mame 119 source
applied (in order) u1.diff, u2.diff, hi_u2.diff
Set the the compile options to P4 / Dual Core
and compiled.

I think i've done this right, but what I'm left with is a number of strange .exe files in addition to the mamep4.exe
I'm fairly new to command line mame, but the binary version of 118, that I had been using, doesn't contain most of these .exe files, and has a number of other files that are not present in the folder (post compiling).

I figured it was safe to assume that anything in the mame-compiler/mame/ folder that wasn't the original source files, was the finished result. Is this all I need? or should I dump these into the old mame folder?

Oh, and if the "optimize for p4, dual core, etc" feature is only to speed up the compiling process, then why add the P4 bit to the end of the mame.exe? (ie.mamep4.exe) I'd thought it was a change in the mame source to speed up mame once compiled (based on cpu)..

Anyways, sorry if none of this makes sense. it's 1:30am and I really should be sleeping instead of mucking with mame. but what can i say... I'm addicted

[headkaze]

SpyDIRmaN, on Oct 5 2007, 01:32 AM, said:

I've followed the above instructions.
Used mame 119 source
applied (in order) u1.diff, u2.diff, hi_u2.diff
Set the the compile options to P4 / Dual Core
and compiled.

I think i've done this right, but what I'm left with is a number of strange .exe files in addition to the mamep4.exe
I'm fairly new to command line mame, but the binary version of 118, that I had been using, doesn't contain most of these .exe files, and has a number of other files that are not present in the folder (post compiling).

I figured it was safe to assume that anything in the mame-compiler/mame/ folder that wasn't the original source files, was the finished result. Is this all I need? or should I dump these into the old mame folder?

Oh, and if the "optimize for p4, dual core, etc" feature is only to speed up the compiling process, then why add the P4 bit to the end of the mame.exe? (ie.mamep4.exe) I'd thought it was a change in the mame source to speed up mame once compiled (based on cpu)..

Anyways, sorry if none of this makes sense. it's 1:30am and I really should be sleeping instead of mucking with mame. but what can i say... I'm addicted

Those other exe's are just programs that relate to Mame and arn't needed. Like chdman is a chd manager, ledutil is a program for lighting the caps lock/scroll lock LED's for some games. There are others programs for various Mame related tasks so these can be safely ignored. All your after is mamep4.exe.

The Compile Options are not just for speeding up the compile process. The Dual Core and Quad Core options are only for speeding up compiling on those processors but the "Optimize for" optimize the compiled binary for a particular processor. So if you compile using the Pentium 4 optimization, the compiled binary (mamep4.exe) is optimized to run on a Pentium 4 processor.

[SpyDIRmaN]

headkaze, on Oct 5 2007, 01:46 AM, said:

Those other exe's are just programs that relate to Mame and arn't needed. Like chdman is a chd manager, ledutil is a program for lighting the caps lock/scroll lock LED's for some games. There are others programs for various Mame related tasks so these can be safely ignored. All your after is mamep4.exe.

The Compile Options are not just for speeding up the compile process. The Dual Core and Quad Core options are only for speeding up compiling on those processors but the "Optimize for" optimize the compiled binary for a particular processor. So if you compile using the Pentium 4 optimization, the compiled binary (mamep4.exe) is optimized to run on a Pentium 4 processor.

Just a couple of quick questions... I have an athalon64 system running 32bit windows xp pro. Do you know if the athalon64 optimizations only work in a 64bit enviornment or would my cpu be helped by these anyway?

The other question I have is about the hiscore.dat. I've downlaoded the latest and poped it into the mame directory however I've noticed in the mame.ini that there is a listing for hiscore_directory just below the cheat-file listing and it just says "hi"... do I need to change or remove this. I don't appear to have any directory named "hi" in my mame folder.

[bkenobi]

you have to create the "hi" directory and add in the hiscore.dat file to it as I recall. I haven't actually used the hiscore data with vanilla mame before (or any other version for that matter), but that's the way it's supposed to work.

[Brian Hoffman]

bkenobi, on Oct 5 2007, 02:47 PM, said:

you have to create the "hi" directory and add in the hiscore.dat file to it as I recall. I haven't actually used the hiscore data with vanilla mame before (or any other version for that matter), but that's the way it's supposed to work.

The "HI" folder is created in the MAME folder. The HISCORE.dat is placed in the MAME folder.
The highscore.dat does NOT go into HI folder

[bkenobi]

So the HI folder contains the files listing the high scores so MAME can grab them each launch and save them on close? I haven't used it, but that would be my next guess. Am I getting close

[Brian Hoffman]

bkenobi, on Oct 5 2007, 06:32 PM, said:

So the HI folder contains the files listing the high scores so MAME can grab them each launch and save them on close? I haven't used it, but that would be my next guess. Am I getting close

Yes... the given name is the name of the rom followed by the .HI extension

Eg. galaga.hi

[headkaze]

SpyDIRmaN, on Oct 5 2007, 04:19 PM, said:

Just a couple of quick questions... I have an athalon64 system running 32bit windows xp pro. Do you know if the athalon64 optimizations only work in a 64bit enviornment or would my cpu be helped by these anyway?

You know that is a good question, I'm not sure if you need 64-bit Windows to take advantage of a 64-bit processor. I guess you could just try compiling Mame with Athlon 64 and 64-bit proccessor options and see if you can see any better performance on some of the slower games.

[Brian Hoffman]

headkaze, on Oct 6 2007, 05:14 AM, said:

You know that is a good question, I'm not sure if you need 64-bit Windows to take advantage of a 64-bit processor. I guess you could just try compiling Mame with Athlon 64 and 64-bit proccessor options and see if you can see any better performance on some of the slower games.

Well one of my systems is an amd64 and I use xp 32bit... performance increase is not anything to write home about.
However on 64 bit windows there has been alot of improvments and with multithreaded cpus..
The U3 build of 119 has much better support for these new chipsets..
Check this out
http://aarongiles.com/?p=217

[iano]

Hi folks. I need a little help with this. I've downloaded the source for mame 0.109 , extracted it and placed the src folder in the mame folder. I've set the paths to the source folder and diff file. I then clicked the patch button and i think that it seemed to work ok. But when i click the compile button here's what i get in the text box:

Object Folder...
Compiling Mame...
Using Parameters P4=1
mkdir.exe obj
mkdir.exe obj/mamep4
mkdir.exe obj/mamep4/cpu
mkdir.exe obj/mamep4/cpu/adsp2100
mkdir.exe obj/mamep4/cpu/alph8201
mkdir.exe obj/mamep4/cpu/arm
mkdir.exe obj/mamep4/cpu/arm7
mkdir.exe obj/mamep4/cpu/asap
mkdir.exe obj/mamep4/cpu/ccpu
mkdir.exe obj/mamep4/cpu/dsp32
mkdir.exe obj/mamep4/cpu/dsp56k
mkdir.exe obj/mamep4/cpu/e132xs
mkdir.exe obj/mamep4/cpu/g65816
mkdir.exe obj/mamep4/cpu/h6280
mkdir.exe obj/mamep4/cpu/h83002
mkdir.exe obj/mamep4/cpu/hd6309
mkdir.exe obj/mamep4/cpu/i386
mkdir.exe obj/mamep4/cpu/i8039
mkdir.exe obj/mamep4/cpu/i8051
mkdir.exe obj/mamep4/cpu/i8085
mkdir.exe obj/mamep4/cpu/i86
mkdir.exe obj/mamep4/cpu/i8x41
mkdir.exe obj/mamep4/cpu/i960
mkdir.exe obj/mamep4/cpu/jaguar
mkdir.exe obj/mamep4/cpu/konami
mkdir.exe obj/mamep4/cpu/m37710
mkdir.exe obj/mamep4/cpu/m6502
mkdir.exe obj/mamep4/cpu/m6800
mkdir.exe obj/mamep4/cpu/m68000
mkdir.exe obj/mamep4/cpu/m6805
mkdir.exe obj/mamep4/cpu/m6809
mkdir.exe obj/mamep4/cpu/mc68hc11
mkdir.exe obj/mamep4/cpu/mips
mkdir.exe obj/mamep4/cpu/nec
mkdir.exe obj/mamep4/cpu/pic16c5x
mkdir.exe obj/mamep4/cpu/powerpc
mkdir.exe obj/mamep4/cpu/r3000
mkdir.exe obj/mamep4/cpu/rsp
mkdir.exe obj/mamep4/cpu/s2650
mkdir.exe obj/mamep4/cpu/se3208
mkdir.exe obj/mamep4/cpu/sh2
mkdir.exe obj/mamep4/cpu/sharc
mkdir.exe obj/mamep4/cpu/spc700
mkdir.exe obj/mamep4/cpu/t11
mkdir.exe obj/mamep4/cpu/tms32010
mkdir.exe obj/mamep4/cpu/tms32025
mkdir.exe obj/mamep4/cpu/tms32031
mkdir.exe obj/mamep4/cpu/tms32051
mkdir.exe obj/mamep4/cpu/tms34010
mkdir.exe obj/mamep4/cpu/tms9900
mkdir.exe obj/mamep4/cpu/upd7810
mkdir.exe obj/mamep4/cpu/v60
mkdir.exe obj/mamep4/cpu/v810
mkdir.exe obj/mamep4/cpu/z180
mkdir.exe obj/mamep4/cpu/z80
mkdir.exe obj/mamep4/cpu/z8000
mkdir.exe obj/mamep4/debug
mkdir.exe obj/mamep4/drivers
mkdir.exe obj/mamep4/expat
mkdir.exe obj/mamep4/layout
mkdir.exe obj/mamep4/machine
mkdir.exe obj/mamep4/sndhrdw
mkdir.exe obj/mamep4/sound
mkdir.exe obj/mamep4/vidhrdw
mkdir.exe obj/mamep4/windows
mkdir.exe obj/mamep4/zlib
Compiling src/audit.c...
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
mingw32-make: *** [obj/mamep4/audit.o] Error 1
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.

Any ideas would be appreciated.

[Brian Hoffman]

Mame has recently changed its version of compilier. Tho Im not sure it would cause this error.
Have you tried compiling a new version?

[iano]

Brian Hoffman, on Oct 6 2007, 09:25 PM, said:

Mame has recently changed its version of compilier. Tho Im not sure it would cause this error.
Have you tried compiling a new version?

No Brian i haven't tried compiling a recent version of mame. The reason being that the space the romset takes up of recent versions is a lot bigger and the version i'm using (0.109) plays all the games i like.

[Brian Hoffman]

iano, on Oct 6 2007, 09:17 PM, said:

No Brian i haven't tried compiling a recent version of mame. The reason being that the space the romset takes up of recent versions is a lot bigger and the version i'm using (0.109) plays all the games i like.

Really... I dont use many CHD's but the ROMset is 15 gig. That cannot be too big a diffrence.
Im mean its not that old...
I will look at it. and pm you.
Are you trying to add hiscore and get rid of nags?


**EDIT**
I get that too. I just think its the new compilier.

[iano]

Brian Hoffman, on Oct 6 2007, 11:17 PM, said:

Really... I dont use many CHD's but the ROMset is 15 gig. That cannot be too big a diffrence.
Im mean its not that old...
I will look at it. and pm you.
Are you trying to add hiscore and get rid of nags?

Hi Brian. Thanks. I'm just really trying to add the hiscore and get rid nags but i'd like to learn how to apply the patches for myself as well.

Thanks for your help.

[headkaze]

Quote

If you download these tools now, you should still be able to build MAME, but you will need to disable -Werror with any version of MAME prior to 0.118u5 (which is not yet released), since there are some new warnings which need to be dealt with (really, not that many).

I'm about to release a version of Mame Compiler that fixes this.

EDIT: Done and uploaded. Use the "Disable WError (<0.118u5)" option.

[iano]

headkaze, on Oct 7 2007, 07:15 AM, said:

I'm about to release a version of Mame Compiler that fixes this.

EDIT: Done and uploaded. Use the "Disable WError (<0.118u5)" option.

Thanks HK! I just downloaded version 0.3 but when i try to compile i get this error message:

*POST EDITED TO REMOVE STUPIDITY*

It seemed to compile fine although i did get an error in the textbox along the way. I'm hoping it's nothing serious (it didn't stop it from compiling anyway).

Compiling src/mame.c...
src/mame.c: In function 'fatalerror_exitcode':
src/mame.c:786: warning: 'noreturn' function does return
src/mame.c: In function 'fatalerror':
src/mame.c:772: warning: 'noreturn' function does return
Compiling src/mamecore.c...


Cheers,
ian.

[headkaze]

iano, on Oct 7 2007, 08:10 PM, said:

It seemed to compile fine although i did get an error in the textbox along the way. I'm hoping it's nothing serious (it didn't stop it from compiling anyway).

Yep those should be perfectly fine. I tested compiling Mame 109 and I didn't get any warnings but I didn't apply any of the diff's. I'm pretty sure those warnings are from the diff's.

Those are just warnings not errors so it should be fine. The "Disable WError" really just disables the warnings that stop compiling. This is because were using a newer version of GCC.