[APP] MAME Compiler 64 v2.0.165

[bkenobi]

I think the error might have to do with the path. I was getting the same error with the instructions off logiqx's site until I included the c:\mingw\bin directory. I'm wondering if I should just add that to my windows path and try again?

[headkaze]

I think the error might have to do with the path. I was getting the same error with the instructions off logiqx's site until I included the c:\mingw\bin directory. I'm wondering if I should just add that to my windows path and try again?

You shouldn't need to do that using Mame Compiler. Have you got the latest version? It installs all the files needed to compile and automatically sets all the paths for you.

All you have to do is make sure you have the source code path set. Why are you using a "u" release? Try compiling 105 instead of 104u4. Any particular reason your using 104u4? If you have to use a "u" release are you applying the source updates correctly?

[bkenobi]

It's not the path. I think something must have changed between v0.104 and v0.105 (perhaps that's when MAME went to DX8?). I can compile 105, but I get errors on 104. I have been able to compile 104u6 with the MinGW stuff that Logiqx linked. I wasn't able to get things to work with the instructions from the MAME compiling board (mainly because the links were no good).

So, it looks like MAME Compiler can compile anything from MAME v0.105 up to current. Oh well, I was able to apply the patches with Your code anyway. That made things a little quicker. Any chance there's a 104 diff file to remove the nag screen?

[headkaze]

Why do you want 104 and not 105?

[bkenobi]

From what I've read, 104u6 is the last version that will support the WinGun driver. I know it's not supported under 125, but I haven't gone through and validated that 105 won't work. Either way, there's no patch for 105 that I've found either. The oldest hiscore patch I've seen is 108.

[headkaze]

You could probably apply the hiscore patch manually as diff files are human readable. Open up hi_108.diff in a text editor and it tells you the file and line positions of the code it changes. You can then go through and change it manually (a + at the start of a line means code is added and an ! is a line that is changed by the next line with a !).

You can also just try and apply hi_108.diff to 104u6 and see if it works. Hiscore patches can often work on multiple versions of Mame even if the source code changes because it can adjust to code moving around in the file as long as it doesn't differ too much. So you might be in luck.

[bkenobi]

That's one of the first things I did. I grabbed the 0.108 hiscore diff file and checked what it was changing. I looked at the source and realized that somewhere between 0.104 and 0.108 there was a somewhat significant change in how things were coded in this region of the code. In the end, all I really care about is having no nag screens and turning off the cross hairs, so I manually edited the code. It appears that the nag screens will not show after the first time you run MAME and if I use -nogame_info I'll be good to go. I haven't gotten a chance to try it yet, but it did compile last night.

Oh, in case Tempest is viewing this (or anyone else who wants to use the WinGun driver), the reason you can't use anything beyond 0.104u6 is that in the u7 release this was added:

Updated raw mouse support for Windows XP: [Derrick Renaud]
 * Reversed the RAWMOUSE device list. RAWMOUSE reports the last 
	installed mouse as the first device. I now place new mice at the 
	end.
 * Added clipping to RAWMOUSE support so the cursor does not leave 
	the game area in Windowed mode. Also fixed the non-RAWMOUSE 
	Windowed mode clipping I broke by my last changes.
 * You can now see the names of the mice attached by using -verbose.
 * Changed Lightgun functionality if using XP.  You no longer need 
	to use -lightgun or -dual_lightgun. Use -mouse and multiple (2+) 
	"HID-compliant mouse" lightguns will be detected. Lightgun 
	support in Win98/Me remains unchanged. -offscreen_reload can 
	still be used on Win98/Me/XP. See windows.txt for further info.

The important bit for WinGun users is the 4th bullet. Guncon2pc uses a HID-compliant mouse for each gun. WinGun doesn't AFAIK.

[headkaze]

I would make a post on BYOAC about this, there might be some other way to get the WinGun working in a newer version of Mame.

[bkenobi]

Hmmm, I can get the guns to track in MAME (which didn't work last time I tried the WinGun drivers), but I can't get the trigger to respond. The screen flashes (as it should), but no bullet hits can be seen. I'm starting to think this is actually a 117 issue where the new control system doesn't like the driver remapping the buttons or something. I'm not quite sure. It detects the button press in MAME when I'm setting things up, but it doesn't accept the location when I'm trying to test it out. Weird.

I guess this isn't a MAME Compiler question any more, so perhaps I should open a new topic if I decide to continue discussing this here.

Thanks for the suggestions HK!

[bkenobi]

Just a final note on the Gun stuff. I compiled 0.117 with the hiscore patch and it works fine with WinGun and Guncon2pc with dual lightguns. I think this is the last version that will work with WinGun due to the way the RAW input system (incorporated in 0.117u1) works. It will recognize the gun position, but it will not accept the trigger buttons.

[TalkingBull]

I am having some difficulty getting this to work. I haven't used a compiler before but I followed the instructions and came to two problems. First, I didn't have a mameui.mak file or a winui folder to copy anywhere. I am using the latest MAME files etc... from the links on the initial post. When I tried to compile it without that stuff, I get:

In file included from src/emu/cpu/m68000/m68kcpu.h:32,

from src/mame/machine/fddebug.c:111:

src/emu/cpu/m68000/m68k.h:32:22: error: m68kconf.h: No such file or directory

mingw32-make: *** [obj/windows/mame/mame/machine/fddebug.o] Error 1

mingw32-make: *** Waiting for unfinished jobs....

Not sure what to do...

[headkaze]

I found this message on the MameWorld forums that might help you.

Create an empty file called m68kconf.h in src/emu/cpu/m68000. The -E flag for patch causes it to delete empty files, but in this particular case the file should have been left present but empty because it hasn't been removed from the includes yet.

[wasko]

I am compiling Mame ver 128 and I am pretty sure I have done everything correctly and followed the steps in the post but I keep getting these errors when patching the diff files.

I am getting these types of errors throughout:

--------------------------

File to patch:

Skip this patch? [y]

Skipping patch.

1 out of 1 hunk ignored

can't find file to patch at input line 23003

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--------------------------

|diff -Nru src-old/version.c src/version.c

|--- src-old/version.c 2008-10-16 01:59:25.000000000 -0700

|+++ src/version.c 2008-10-23 02:15:58.000000000 -0700

--------------------------

File to patch:

Skip this patch? [y]

Skipping patch.

1 out of 1 hunk ignored

[wubble]

Just compiled MAME 0.129 without a hitch. Ran first time. Great program and instructions, thanks.

(AMD64 dual core 3800+, XP 64 bit, no mameui)

[bkenobi]

Congrats! You now have more experience with MAME than 90% of it's users (cause they never compile MAME themselves).

[iano]

I'm trying to compile MAME0.129 with MKChamps diff file but i keep getting the same error. I've no doubt that i'm doing something wrong because other people have compiled MAME0.129 without a hitch. Any help would be appreciated.

src/emu/sound/ay8910.c: 751: internal compiler error: in assign_386_stack_local, at config/i386/i386.c: 13482

Please submit a full bug report, with preprocessed source if appropriate.

see<URL: http://www.mingw.org/bugs.shtml> for instructions

mingw32-make: ***[obj/windows/mame/emu/sound/ay8910.o] error 1

Thanks,

ian.

[bkenobi]

Well, the error report tells you the file and line where the error occurs. If you are a programmer, you could review the source to see what's wrong with it and fix it. But, I would recommend deleting the source and repeating your patching process. Something obviously went wrong with the patching, so that's the easiest thing to try. If that doesn't fix it, we can go from there.

[iano]

Well, the error report tells you the file and line where the error occurs. If you are a programmer, you could review the source to see what's wrong with it and fix it. But, I would recommend deleting the source and repeating your patching process. Something obviously went wrong with the patching, so that's the easiest thing to try. If that doesn't fix it, we can go from there.

I've already tried deleting the source and repatching/recompiling - the result is the same. I do have a few queries though. 1) There's a batch file called make_mame64 located in c:\MinGW\source\Mame0128\ - am i suppose to move this file into my Mame0129 source folder before compiling ? 2) There are a couple of diff files called snd_0111u3 and snd_0121 in the patch folder - what are these for ?

Thanks,

ian.

[bkenobi]

You really just need to follow the procedure that HK listed on the first page. The only thing that might be different is related to the 64-bit compiling options. I haven't compiled for 64-bit but I know several people have. Try compiling for 32-bit using the standard procedure. Maybe the problem is related to 64-bit? Also, I would try adding patches 1 at a time to see where the error is (add patch, compile, add patch, compile, etc.).

[iano]

You really just need to follow the procedure that HK listed on the first page. The only thing that might be different is related to the 64-bit compiling options. I haven't compiled for 64-bit but I know several people have. Try compiling for 32-bit using the standard procedure. Maybe the problem is related to 64-bit? Also, I would try adding patches 1 at a time to see where the error is (add patch, compile, add patch, compile, etc.).

I've tried compiling again (using HK's instructions on the first page) with the same resulting error as before.

[Adultery]

Probably a stupid question, but...

If I'm using my quad core CPU to compile but running on a single core AMD processor in the cab, do I check the Quad Core ticker under 'Compile Options'? Is that an option just for the building process, or is that an option for the final product?

[headkaze]

Probably a stupid question, but...

If I'm using my quad core CPU to compile but running on a single core AMD processor in the cab, do I check the Quad Core ticker under 'Compile Options'? Is that an option just for the building process, or is that an option for the final product?

The "Dual Core" and "Quad Core" options only speed up the compiler by using mutiple threads during complie time. Only the combo box under "Optimize For" will optimize the binary. "64-bit Processor" will compile the binary for a 64-bit CPU/OS so that could be considered an optimization setting as well.

BTW It's nice to see you Adultery!

[Adultery]

Glad to be back.

Just compiled MAME 0.129 without a hitch. Thanks again for a sweet program, and I will use that option next time I compile MAME.

[stephenp1983]

Glad to be back.

Just compiled MAME 0.129 without a hitch. Thanks again for a sweet program, and I will use that option next time I compile MAME.

Quick question. If I just want to use .129 mame, and not another of the u1 or whatever versions, I assume I can just skip those steps in the process?

[Tempest]

That's correct.