MAME Compiler 64 v2.0.197

[Vash]

Scrapple:

That means you don't have the source code, either at all or in the right place.   Make sure that you've selected the correct folder that houses the source code of the build you're compiling, and make sure that you're not just selecting the folder that says 'src'.  The parent folder of that one should have a makefile file in it, along with something else (I believe).   You want to select the parent folder of 'src'.


I just compiled MAME .120 in 64 bit, so the problem must stem from the .119 source code.  Oh well.  I'll live.

[Teknique]

thanks for your work on this Headkaze, its much appreciated!

Tek

[lettuce]

headkaze, i want to use SailorSat cabmame, but he hasnt complied it for dual core, i have download his diff files for cabmane:

0126_changeres.diff
0126_cleanstretch.diff
0126_defaults.diff
0126_emuspped.diff
0126_frogger.diff
0126_hiscore.diff
0126_redraw.diff
0126_resolution.diff
0126_soundsync.diff

Now it it just a case of using complier64 and ticking the dual core box and just patching each of these files in turn and then after ive patched all 9 diff files complie the whole lot??

Any help with this, im getting a message when patch some of these diff files say:

"Hunk#1 FAILED at 102." etc

Any help?

Any help with this please???

[lettuce]

Just applied patches 0.126u1.diff, 0.126u2.diff, 0.126u3.diff, 0.126u4.diff and Hi_0.126.diff. I noticed that i was getting messages like:

File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 74654
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

Numerous times, is this nomal? Do i have to apply each update or can i just apply 0.126u4 and none of the others?

Also once i applied all above patches and went to complie i got the message:

Compiling Mame64...
Using Parameters  -j3 ARCHOPTS="-march=pentium-m -msse3" MSVC_BUILD=1 PTR64=1
mingw32-make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.


What is happening here?

[headkaze]

When you get the "Skip this patch" message that means your applying a patch that has already been applied. I would try again with a fresh extract of the Mame source code.

BTW If you want to force a recompile, then tick the "Clean Compile" option and it will start from the beginning.

[u_rebelscum]

Any help with this, im getting a message when patch some of these diff files say:

"Hunk#1 FAILED at 102." etc

Any help?

The diff files aren't working because one or more of the following:

The diff file version doesn't match the source version you're changing.
The diff files are being applied in the wrong order.
The diff file doesn't have the correct patch options (-p0 vs -p1 is most common wrong option if patching by hand).


If every line in a diff is failings, I'd guess it's the last reason for that diff.  If only some lines fail, it's probably one of the first two.

(Disclaimer: I've never used this app; I patch by hand or batch.)

[MKChamp]

Just applied patches 0.126u1.diff, 0.126u2.diff, 0.126u3.diff, 0.126u4.diff and Hi_0.126.diff. I noticed that i was getting messages like:

...What is happening here?

Also, you are using the hi_126u4 diff and not the hi_126 diff, right?

[lettuce]

^^Yeah, so i need to apply all 'u' updates 1-4 then?

[lettuce]

No luck, still getting this:

Applyinh Diff Patch...
cant find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
-------------------
|diff -Nru src-old/emu/cheat.c src/emu/cheat.c
|--src-old/emu/cheact.c      2008-07-06 11:49:27.00000000-0700
|+++src/emucheat.c           2008-97-12 13:18:25.00000000-0700
--------
File to patch:
Skip this patch?[y]
Slipped patch.
57 out of 57 hunks ignored
cant find file to patch at input line 684
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

etc etc etc

[lettuce]

Edit, sorted it out now, had the mame source exe file in the MinGW folder and not the source zip 

[MillmoorRon]

I compiled MAME (& MAMEUI) using MAME Compiler 64 with diff files u1 to u4 (applied in sequence) and the u4 high score diff file.

Compilation was successful and the games run OK, however the high score support is a bit flaky - it only works about 50% of the time.

Is this a common thing or did I maybe do something wrong?

[Jdurg]

It depends on whether or not there is hiscore support for your game in the hiscore.dat file that you have.  Not all games have hiscore support in there.

[MillmoorRon]

Sorry, I wasn't very clear.

On games that DO support the high score dat it randomly works!

eg Asteroids: sometimes it shows my previous scores, other times it doesn't.

[headkaze]

I've updated the first post to include detailed instructions on how to compile Mame/MameUI. It also includes details of how to apply diff's. Should help a few new timers out there

[MillmoorRon]

That's exactly how I did it.

Tried again (re-downloading all the files from your links) to be sure and also on a different machine at work but I still get the same intermittent effect.

Any suggestions?

[Jdurg]

That's exactly how I did it.

Tried again (re-downloading all the files from your links) to be sure and also on a different machine at work but I still get the same intermittent effect.

Any suggestions?

Are you perchance using cheats?  If any cheat is enabled, ANY of them, the high score will NOT save it at all for that session.

[MillmoorRon]

Not using any cheats at all.

It DOES save the high scores but it doesn't always read them back again when the game starts up!

If I restart the game a few times eventually it picks them up.

[bent98]

Head

Does 1.16 work with Mame 127?

I am getting an error applying a .diff made for 127.

[headkaze]

Head

Does 1.16 work with Mame 127?

I am getting an error applying a .diff made for 127.

Just successfully applied hi_127.diff and compiled both a 32 and 64 bit version of Mame 127. So must be some issue your having with that patch.

[retrometro]

Summary:  64bit compile with hi_126 exe works except hi scores aren't being read

I've been using a 32bit compile with only the hi_126 diff patch and it's been successfully reading and writing scores.  Just for full info, I'm using blockout.  As you'd expect, running without a hi_126 patch copy of mame, the default high score shows up upon game start.  Switching back to the hi_126 patched mame.exe and everything is fine again.  The time stamps on blockout.hi match when you leave the game so you know the file is being written to.

I've since used the tool to compile a 64bit version with only the hi_126 diff again and the compile completes without error and the resulting vmame.exe runs fine.  Another validation that it's 64bit is that for most games, the game percentage and fps are faster.

However, when I load blockout (as an example, other games also break this way), the default high scores show up as if it was a vanilla / downloaded copy of 64bit mame.  Just in case someone asks, before a compile, I not only delete the obj directory, but everything under mamesrc and I copy everything from the source download zip all over again just to be sure and then hi_126 diff patch again.  I've tried checking only the 64bit checkbox with and without the "optimize for" drop down list box for core2duo.  I've tried those combinations with and without the dual processor checkbox.  I've also tried checking clean compile but to no avail. 

As a control between these 64bit compile runs, I run a 32bit compile (I have all checkboxes turned off) with the hi_126 patch again just to make sure it cranks out a mame.exe that loads the high scores fine for blockout.

What would be very helpful would be if:

1)  Someone can verify that there's no difference between hi score data saved to __.hi files for 32bit or 64bit versions of mame.  That is, the 32bit "created" copy of a ___.hi file can be read/written to from a 64bit mame.exe.

2)  Can someone send me a hi_126 or hi_127 64bit compile of mame so I can test.  (headkaze?)

Thanks!


----
also posted this question to the hiscore_diff thread at:
http://forum.arcadecontrols.com/index.php?topic=64298.msg874466#msg874466

[lettuce]

Yeah ive had problems with my comnplied 64bit version not keep high scores also

[retrometro]

Yeah ive had problems with my comnplied 64bit version not keep high scores also

Man, I hope this isn't the case.  I can't imagine why the same source wouldn't compile the right way for an application level feature like this.  The only reason I can think of is maybe because of how this hack works.  Since it's reading and writing to specific memory locations, maybe the memory location addresses are different in 64bit.

Just successfully applied hi_127.diff and compiled both a 32 and 64 bit version of Mame 127...

Simple question to headkaze then...  does your 64bit compile of 126 or 127 keep hi scores?

[retrometro]

Update...

It turns out Lettuce had the same problem and found that when he used SailorSat's hiscore patch, 64bit compile worked fine.  So it looks like MKChamp's hiscore plus no-nag patch may need some looking at. 

I tried the same thing using HeadKaze's compiler tool and also got it working with all the checkboxes I need turned on:  64bit, core2duo, dual core.

http://forum.arcadecontrols.com/index.php?topic=64298.msg874592#msg874592

[retrometro]

MKChamp's fixed the 127_diff and 64bit mame is happy w/ high scores again.

[headkaze]

I was going to mention that we need MKChamp to check this out, but looks like he's fixed it already 

[MKChamp]

Don't mean to cross post...but since this thread and the hiscore thread should probably get married....here's a copy/paste.
(For those reading that have no idea what I am talking about, you can probably just ignore this)

Ok...instead of creating and maintaining separate diffs...I incorporated the ability to turn on/off portions of the patch via the mame.ini file. By default, the patches are enabled. To disable a portion of the patch add the appropiate line to your mame.ini file. Let me know how it works for you guys....

disable_hiscore_patch   1   <- To disable highscore support. Set to 0 or omit it entirely from ini file to enable.
disable_crosshair_patch   1  <- To disable crosshairs off by default. Set to 0 or omit it entirely from ini file to enable.
disable_nagscreen_patch   1  <- To disable removal of nagscreens /white box. Set to 0 or omit it entirely from ini file to enable.
disable_loading_patch   1      <- To disable suppresssion of loading/decypting/etc messages. Set to 0 or omit it entirely from ini file to enable.

Uploaded hi_127a.txt with this in it. If this works out, it'll be in all the future diffs.

[MillmoorRon]

hi_127 works OK in 32bit too!

[Turnarcades]

I've got a problem compiling MAME 0.103. I've just found this thread so I've posted the error log here already:

http://forum.arcadecontrols.com/index.php?topic=84130.msg880605#msg880605

Can anyone help?

[Twin-X]

mkdir.exe -p obj/windows/vmame/tools
Compiling src/osd/windows/vconv.c...
process_begin: CreateProcess(C:\MinGW\psdk\bin\amd64\cl.exe, cl.exe /nologo /O1 -D_CRT_SECURE_NO_DEPRECATE -c src/osd/windows/vconv.c /Foobj/windows/vmame/osd/windows/vconv.o, ...) failed.
Finished!
0 Hours 0 Minutes and 5 Seconds Elapsed.
make (e=216): Error 216
mingw32-make: *** [obj/windows/vmame/osd/windows/vconv.o] Error 216

Well i need some help here. I am trying to compile a 64bit processor core2 dcore marked version. (i read that these options are needed for my e8400 processor)

However i apply 127a diff patch and then click compile and i get above error?

*fixed.

To compile 64bit you need to do this on your 64bit os

[lettuce]

Cant seem to complie 127u1 or 127u2 updates which this for some reason get the error message:

mingw32-make: *** [obj/windows/vmame/emu/cpu/drcbex64.o] Error 2
mingw32-make: *** Waiting for unfinished jobs....

[retrometro]

Cant seem to complie 127u1 or 127u2 updates which this for some reason get the error message:

mingw32-make: *** [obj/windows/vmame/emu/cpu/drcbex64.o] Error 2
mingw32-make: *** Waiting for unfinished jobs....

Before retrying, did you at least delete the obj dir or everything in the mamesrc dir first?

[headkaze]

Before retrying, did you at least delete the obj dir or everything in the mamesrc dir first?

If you select the "Clean Compile" option before starting it will delete the obj dir for you.

[cmoses]

Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 

[cmoses]

Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 

Anyone know the answer?  Once complied, what do I need to do?

[massive88]

Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 

Anyone know the answer?  Once complied, what do I need to do?

All you really need for your average Mame-ing, is the Mame.exe

Put it in whatever folder you choose, it does not require any pre-existing install or anything of the sort.  When you first run it, it will create folders that its missing and so on.

[encom]

I have a question please.

Can this ap be used to create an updated version of Dos MAME? Currently I'm running DMAME v96 , and have been for a few years , but I'd like to upgrade and try out some of the newer additions to MAME.

[Havok]

Hey headkaze - finally took the plunge and tried your app out on my test rig. Nice job.

I still won't forget my manual compiling roots, though.

 

[headkaze]

Hey headkaze - finally took the plunge and tried your app out on my test rig. Nice job.

I still won't forget my manual compiling roots, though.

 

I agree it's definately handy to have the skill to manually compile. I think Mr Do should update his site for instructions on compiling the 64-bit version as I think you can do that now with Visual Studio 2008 Express.

[Martijn]

i tried it some times now, still getting errors

can someone compile me a mame0127 u3 and high score patch

optimised for windows xp 32bit and core2duo e8500

please.... 

[FhM]

I cant seem to find it in this thread again but can you tell me if the following is true:

The optimise dropdown is for the processor optimistations and the cpu entries underneath that are tick boxes just relate to how the compiler is setup eg there is no optimisation for quad core but you can take advantage of it while compiling?