MAME Compiler 64 v2.0.197

[headkaze]

Yup I do.

Perhaps rename your "Mame 130" folder so it's "Mame130" (without the space) and then point MC64 to the new directory.

[gargoyle67]

Thanks headkaze, I've changed a few things about and it's compiling now so fingers crossed

[gargoyle67]

Ok it runs for a good while then throws up errors:

src/osd/windows/video.c:237:error:redifinition of 'osd_update_hi'

src/osd/windows/video.c:216:error: previous difinition of 'osd_update_hi' was here mingw32-make:***[obj/window/video.o] error 1

I'm just trying to compile on my cab's machine to see how C64 get's on with winxp

[gargoyle67]

Success ! Thanks headkaze
Just a quick question regarding optimization, I'm runing on an AMD 64 dual core machine running winxp 32bit, what options should I have selected ?
AMD 64 from the dropdown selector and 64bit proccessor + duel core in the tick boxes ?

(I take it I was missing some ms lib file on my vista machine when I was trying to compile on that ?)

[headkaze]

Thanks headkaze, I've changed a few things about and it's compiling now so fingers crossed

Care to share what you did so it can benefit others?

(I take it I was missing some ms lib file on my vista machine when I was trying to compile on that ?)

I have no idea. Others have tested it on Vista and it works okay for them. If you can shed any light on why it didn't work let me know.

[gargoyle67]

Not sure why it wouldn't compile on my vista machine , Only that it came up with the listed errors.
I got it to compile on windows XP Pro without any hassle 1st try, Any answers to my optimize question's ?
Thanks Again

[aevans0001]

Ok I think I know my own answer but can someone please help.... Ok i copiled a version of Mame .128, I would like to upgrade to the newest version.  How do I do it, Do I have to start over and get the new source and diffs and then use the compiler to add the high score and bezel? Or can i just add in the upgrade?

[Dazz]

This should really be a sticky thread... one of the most helpful apps around.

BTW - what does this error/warning mean?  dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

[rooter]

Mame Compiler 64 Homepage

FYI, that link is incorrect.  The correct link is http://headsoft.com.au/index.php?category=mame&page=mc64

[headkaze]

Mame Compiler 64 Homepage

FYI, that link is incorrect.  The correct link is http://headsoft.com.au/index.php?category=mame&page=mc64

Thanks for reporting that I've corrected it now

[rooter]

Add me to the list of not working....

I double checked and even tried re-downloading the files.  There is definitely a problem with 0128 at least on my puter...  I couldn't add any diff file patches and I am certain I followed the instructions correctly.

applying diff patch...
error applying patch.
PatchDiff(): The system cannot find the file path specified.

Any ideas?

When you install Mame Compiler it loads certain files into the MinGW folder.  You probably cleared the content of this folder.  To resolve just re-install Mame Compiler.

I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?

[headkaze]

I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?

The MinGW folder should be defaulted to C:\MinGW. Check inside C:\MinGW\bin there is a file called patch.exe.

Then check that the patch file your trying to apply exists as well.

Also what Windows version are you using?

[rooter]

I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?

The MinGW folder should be defaulted to C:\MinGW. Check inside C:\MinGW\bin there is a file called patch.exe.

Then check that the patch file your trying to apply exists as well.

Also what Windows version are you using?

Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!

[headkaze]

Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!

Yeah I don't recommend moving the MinGW folder. Sometimes you have to hit "go" a few times when compiling a 64-bit version. After it's created the Mame exe you don't need to hit go anymore.

[rooter]

Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!

Yeah I don't recommend moving the MinGW folder. Sometimes you have to hit "go" a few times when compiling a 64-bit version. After it's created the Mame exe you don't need to hit go anymore.

It worked!  Took 19 minutes.  Thanks!
Finally I can track my high scores.  I'm never updating again!

[alui]

Could someone point me to a place where I can download mame and mameui source for older releases?  The particular version I''m interested in is 0.122.  I can find the source at the official mame site.  However, it doesn't have the update sources, and I have no idea where to locate the source for mameui. 

Thanks

[Dazz]

New compile of 132u5 with 64 bit & dual core

dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

Would this warning have anything to do with why I can't get MAME to see my mouse devices or joysticks?

[headkaze]

New compile of 132u5 with 64 bit & dual core

dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

Would this warning have anything to do with why I can't get MAME to see my mouse devices or joysticks?

The warning is normal and should not cause any problems.

[zmartin34]

Can someone verify that this is correct before I waste a bunch of time please? I am trying to compile a 64-bit version of cabmame using .132 source and .129 cabmame diff files. I have heard that these diff files still work with .132 source but not sure if they are 64-bit compatible or not.

I keep running into errors with the 0129 changeres diff. Hunks failing (2 of 5). I'm working on a 32-bit machine right now though; not sure if this would be causing it or if I've got the wrong pieces to the puzzle.

Thanks for any help.

[headkaze]

The source code does not change between 32 and 64 bit so applying the patches does not make a difference.

So my guess is you have applied the wrong patch or in the wrong order. If you have any more problems with diff's perhaps try the hiscore diff pinned topic.

[zmartin34]

Will do, I did several searches and was not able to find anything on cabmame diff order.

[zmartin34]

opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?

[headkaze]

opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?

You need to set it to "Intel Core2" in the dropdown list and have "64-bit Processor" and "Dual Core" ticked. How can you tell if it's compiled for 64-bit? The name of the exe will be vmame.exe.

[zmartin34]

opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?

You need to set it to "Intel Core2" in the dropdown list and have "64-bit Processor" and "Dual Core" ticked. How can you tell if it's compiled for 64-bit? The name of the exe will be vmame.exe.

OK I was thinking Core2 was Duo line. Will do, thanks!

[markronz]

I am trying to use this tool to compile the latest Mame 133 but am having some problems.   It seems to lock up in the middle of the compile.  I even let it run over night and it still did not finish. 

I downloaded the hi_133.diff patch, and the latest source code for mame 133.  There are no other intermediate diff patches right now either for 133.   

When I compile it, I choose to optimize for "Pentium 4 (+SSE3)", and I tick Dual Core (since I have a pentium D dual core processor), and I tick mameui.

I followed along the guide posted on the Compiler Home page.  The guide references all 126 stuff, so I just replaced 133 stuff and did the same steps.

I've tried doing it without the optimization part and that didn't help either.  I've tried the "Disable Warnings as Error" option and that does not help either.   I look at the status window of the compiler and there doesnt appear to be any errors I can see.  It just locks up in the middle is all.

Anyone have any ideas what I can do to make this work?  Let me know if you need any more info!

Thanks!

[headkaze]

You should have it set to optimize for "Intel Core2".

[markronz]

Just have two questions...

1.  A Pentium D is considered an "Intel Core2"?

2.  Do I need to compile this on the machine I plan on using it for?   I use my own personal computer that I typically use to compile things, and it's not the computer that has the actual Pentium D in it.  Just wondering if it's ok if I use a different pc to compile or if it has to actually be my mame pc...

Thanks!

[headkaze]

1. It seems that the Pentium D is infact the predecessor to the Intel Core 2 line of chips, but the question is what instructions sets do they use? According to Wikipedia the difference is in cache and power consumption. So without someone with more knowledge on the subject I can't say for sure if it will work or not. How about giving it a try and letting us know?

2. You need a 64-bit OS and CPU to compile a 64-bit version but as for different CPU's with the same bitness again I can't say for sure. There is such a thing as "cross-compiling" which allows you to do that but I really don't know if the compilers used in MC can do that. In my experience you can't as it compiles tools on the fly and executes them, so these tools will fail if the CPU does not support the instruction set. I do know you can compile a 32 bit version of Mame on a 64-bit OS/CPU and it works fine, but not a 64-bit version of Mame on a 32-bit OS/CPU.

Best thing to do is give it a try and share your experience with us.

[markronz]

Well, the machine I am using is 32bit and also is dual core, but it is Athlon.  My mame machine is a Pentium as I mentioned before.  So I'm not sure what that would mean.  I did give it a shot though...  I picked Intel Core 2 and ticked dual core and mameui

It seemed to get a lot further but it's been running for 16 minutes now and hasnt finished.   Here is an exerpt from the end of the compiler...

Compiling src/osd/windows/output.c...
Compiling src/osd/windows/sound.c...
Compiling src/osd/windows/video.c...
src/osd/windows/video.c:237: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c:258: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c:279: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
mingw32-make: *** [obj/winui/mame/osd/windows/video.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....


Any ideas on what to do now?

[headkaze]

That looks more like a problem with how you've setup the files to compile not the settings in MC64. I would start from scratch and follow the instructions. If your still having problems try compiling vanilla Mame (no MameUI) as well as no patches and see if you can get that to work. Most probably just a simple mistake your making.

[u_rebelscum]

1. No.  "Pentium D"s are two pentium 4s on one chip.  The brands "Core", "Core 2", and "Core i7" are very different then P4s.  I blame Intel for the confusing brand names: dual core = any CPU chip with two CPU cores on it; Core 2 = a specific CPU brand that comes in single, dual and quad models.  So the setup is correct as you mentioned.

2. As headkase said, to compile or run the 64bit version, you need a 64 bit OS.  But besides that, you can compile for any CPU with any CPU.  IOW, compiling a 32 bit mame to be run on a P4 from an athlon is fine, but compiling a 64 bit mame from a 32 bit OS is a no-no.

[headkaze]

I've confused myself with Dual Core and Core 2 before. So Pentium D is just a P4 then, so in that case I would just be careful using "Pentium 4 (+SSE3)" as you may need to select "Pentium 4 (-SSE3)" instead.

[garnerb350]

Headkaze...I need to pick your brain on this one...

Can your Compiler compile Misfitmame? I was talking to MKChamp asking if the "no nag/hi-score diff" would work...

MKChamp...

Sorry if this question is stupid...but I just got Misfitmame (still has the new car scent)...Can this be done also on Misfitmame? 

(I just got it yesterday...playing D2K...other games eventually)

When i first played it, i forgot all about the nag screen...

It *should*...I've never tried it. Easy to do, though. I believe the last time misfitmame was updated was for 127...so...
1) Get the mame source for 127
2) Get the misfitmame source for 127

3) Apply misfitmame source to core mame source
4) Download the hi_127a.txt and patch away!

Let me know if it worked...

I used your compiler on my MameUI v.129...and it worked....Now I am tinkering with this misfit mame...and I feel like i am back at step one trying to figure this mess out....

[FrizzleFried]

Welp,   went from .132u2 to 133u2 last night and got an error...something to do with "SPEAKER"... I couldn't capture the error as it was on my arcade cab not my wired PC...

I was attempting to compile a 64 bit version...

...when I backed off to .133 it compiled perfectly (with HS support).   I've not tried .133u1 yet,  but .133u2 crashed with the same error,  about 8 minutes 30-40 seconds in...

...any ideas?

[FrizzleFried]

Found reference to this issue at MAMEWORLD. 

http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=199408&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1

[headkaze]

Found reference to this issue at MAMEWORLD. 

http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=199408&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1

The equivalent to that is to turn on the "Disable Warnings as Error" option.

[FrizzleFried]

Well... I waited for .133u3 to come out and now that it did,  I get a different error only 4 minutes in to the process both with DISABLE WARNINGS on and off.  I think it may be a HS.diff issue though... not 100% sure.

[MKChamp]

Well... I waited for .133u3 to come out and now that it did,  I get a different error only 4 minutes in to the process both with DISABLE WARNINGS on and off.  I think it may be a HS.diff issue though... not 100% sure.

Yep...grab the one for 133u3...

[FrizzleFried]

I can confirm the problem is with the HS.diff not the u3 release. 

I compiled with the HS.diff = crash at about 4:30 in to the compile.

I compiled without the HS.diff = finished compiling ... good to go.

I re-comppiled with the HD.diff (the latest .133 version) = crash at about 4:30 in to the compile.

At least with my rig...

[FrizzleFried]

Damn... I see that a new HS file was added today.  There ya go! 

I wish the post would show as updated today in the menu without having to look in to the post...