MAME Compiler 64 v2.0.197

[200X]

I got one error

make *** [......blah..blah.../drivers/snesb.o] Error 1

But then it finished. So is that bad?

OK, Started over again and the same thing happened but it was a different file this time: uismall.fh

What's the problem?

I compiled mine on another computer and it worked.

But when I try to start a game by double-clicking it, it crashes. If I right-click and choose play (whatever game), then it works. But through Maximus, it won't work. I have basically tried all the same settings as the old version. What could be the problem?

[Harakiri]

I compiled MAMEUI and i was experiencing random crashes then i tried this setup:

http://forum.arcadecontrols.com/index.php?topic=84933.msg1067238#msg1067238

It works flawlessly.

[raungst]

I got one error

make *** [......blah..blah.../drivers/snesb.o] Error 1

But then it finished. So is that bad?

I'm having a similar issue. Though mine is:

make: *** [obj/windows/mame/mame/drivers/megadriv.o] Error 1

I'll try on a different computer tonight.

[Yoeddy1]

This running ok with .137?  Just checking to see if anyone has used it yet with the new release.

[FrizzleFried]

I got one error

make *** [......blah..blah.../drivers/snesb.o] Error 1

But then it finished. So is that bad?

I'm having a similar issue. Though mine is:

make: *** [obj/windows/mame/mame/drivers/megadriv.o] Error 1

I'll try on a different computer tonight.

I got a similar error... 18 minutes and 48 seconds in to a regular MAME 32-bit compile.

make: ***[obj/windows/mame/mame/video/cheekyms.o]Error 1

EDIT: I am trying a 64bit compile on a Core2Duo rig now (different computer)...I'll report back.

Welp,  the 64 bit compile on the Core2Duo rig compiled fine,  but the 32 bit compile on the AMD Opteron (AMD32) failed with the above error.  Same procedure executed.  Frankly,  I don't really care as I was primarily looking to upgrade the Horizontal MAME (64-bit)...

[Havok]

Just compiled Mame64 on a Core 2 Duo running Windows 7 - works fine, took 11 minutes...

[cmoses]

Trying to compile and got the following error

make: *** [obj/windows/mame/emu/uismall.fh] Error 1073741819

Any ideas?  Just a standard compile no options checked.

[dwight01]

I too am seeing similar errors and have tried compiling 0.137 using mame compiler 64 v1.18 on a Windows 7 Core i& machne and a core2duo.  The 64 bit version compiles without a hitch and works fine.  I managed to get a 32 bit version compiled once, but anytime I tried to run a game it would fail with an error about accessing memory segment FFFFFFFFFFF (a bunch of Fs).

Now when I try to compile a 32 bit version on the core2duo I get an error about PNG2DBC (thats not the right name, but its close) failing and whether I want to send the error to Microsoft.  Otherwise, on either machine, and with disabling warnings displayed as errors, I keep getting those error 1 messages.  I have also tried uninstalling and reinstalling mame compiler 64, no difference.  Finally I tried downloading the 32bit minGW package from mamedev.org/tools, but now if I try to compile it fails almost immediately with the first mkdir command.

Any thoughts?

[bent98]

I have same exact problem as swight01 on with my i7 win 64 bit install with 32 bit mame compile. I am glad Im not going crazy

[Havok]

Has anyone tried compiling the old fashioned way? Is this a problem with the compiler software, or Mame?

(I'd do it but I'm feeling lazy since I have my 64bit goodness working fine)

[headkaze]

Are people compiling using the "Auto Detect" option? It's equivalent to the "ARCHOPTS=-march=native" option.

The problems people are having extend to compiling "the old fashioned way". If people searched on Google with the errors they are getting they would find threads like this

[dwight01]

I have tried specifying "Intel core 2" as well as using "Autodetect", also tried "dual core" compile options, tried no compile options, have tried "Clean compile" and "Disable warnings with errors" with the same results. 

I have also tried installing a fresh install on a core2duo laptop that has never had MINGW or anything mame related installed on it, with the same result - for me, compiling dies around the "Archiving" phase with an error on png2bdc.exe "png2bdc.exe has encountered a problem and needs to close.  We are sorry for the inconvenience".  The last message was "Archiving obj/windows/mame/libcpu.a...", and the last compiling message (before the archiving messages) was "Compiling src/emu/cpu/tms57002/57002dsm.c..." (the stop point seems fairly consistent).

The png2bdc.exe file lives under "C:\MinGW\sources\mame0137\obj\windows\mame\build" - It's not part of the source file package, so I think that means it is created during compiling?  I have also unzipped the updated png2bdc.exe and mamecompiler64.exe (after copying to specified locations) - If I double click the updated png2bdc.exe it tells me it is not a valid win32 file (is this update only meant for 64bit OSs?) - same png2bdc.exe error unfortuantely.  If I hit "GO" again immediately (so clean compile is NOT selected", png2bdc.exe crashes almost immediately.

My compile options were "Using Parameters OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=core2".  I have attached the entire log from the mame compiler  "Output" window to this message in case that will be helpful.  This is a 32 bit machine I am compiling on.

[headkaze]

The issue with png2bdc.exe is not a problem with the MC64 it's an issue in MAME. Hopefully they will have it sorted soon.

I thought I posted a 32-bit version of png2bdc.exe but perhaps I didn't? Try the one attached.

[bent98]

file is corrupt

[Havok]

file is corrupt

I also can't open the attached zip...

[dwight01]

I had no trouble with the zip, applied it and was able to complie mame.exe - unfortunately, the exe won't run any roms.  It starts up fine and shows the list of roms, but as soon as I launch one of the roms it dies with an unable to access memory region FFFFFFFFFF error, and a dump of some register values by the looks of it.  This is also mentioned in other forums as a current symptom of the current mame 137 source.

Interestingly, the same mame.exe (compiled for 32 bit) will work fine on a 64 bit OS (on my i7), it just won't run on any 32 bit machine.

Just have to wait for a new mame source, or a new mingw-mame package.

[Encryptor]

I'm not compiling at this time but I was able to download the zip and open it.

Encryptor

[Havok]

Weird - I get an expected end of archive error when attempting to open it on two different computers, and with IE\Firefox\Chrome.

(They are both Windows 7 machines however)

[Huggybaby]

The file downloads fine for me. Here's a mirror: http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip

[headkaze]

Weird - I get an expected end of archive error when attempting to open it on two different computers, and with IE\Firefox\Chrome.

(They are both Windows 7 machines however)

I can't download it in Firefox either.. corrupt archive.. XP 64 machine... just tried uploading again and same problem. Wierd!

[Havok]

The file downloads fine for me. Here's a mirror: http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip

That one works for me...

[cmoses]

Okay managed to get the 32-bit version compiling by doing the following..

1. Download png2bdc.zip and extract png2bdc.exe to Mamexxxx\obj\windows\mame\build
2. Open Mamexxxx\src\build\build.mak and edit the following (Add '#' to the beginning of the last line shown below)

Code: [Select]

#-------------------------------------------------
# png2bdc
#-------------------------------------------------

PNG2BDCOBJS = \
$(BUILDOBJ)/png2bdc.o \

$(PNG2BDC): $(PNG2BDCOBJS) $(LIBUTIL) $(LIBOCORE) $(ZLIB)
@echo Linking $@...
# $(LD) $(LDFLAGS) $^ $(LIBS) -o $@

Headkaze,

I had previously sucessfully compiled a few versions of 32 bit MAME around the time I was first setting up my cabinet.  I wanted to update and take advantage of the new versions features so I have been trying to compile a 32 bit version of 137 with Mame Compiler 64 v1.18.  I had been unsuccessful, getting various errors during the process.  I went back through the posts to reread and see if I missed anything.  I found the post above and downloaded the png2bdc file.  I was easily able to edit the build.mak file in step #2, but was not able to find the location specified in step #1.  I checked a previously compiled version and saw that the directory was there but it was not in the newly unzipped source.  I concluded that this directory 'Mamexxxx\obj\windows\mame\build' is created during the compile process.  I launched Mame Compiler, did my updates and then started the compile.  I watched for the directroy to be created and once it was I copied the png2bdc.exe file in there while the program was compiling.

The program compiled for the first time and seemd to be sucessful but when I try to run any ROMS I get the same error as Dwight01 mentioned in a post above.  I get an unable to access memory region FFFFFFFFFF error.

I am not sure that this is the proper way to do this but it worked for me.  Can you verify that this is correct or is there another way?

Thanks

[headkaze]

Wait for the next release of MAME the 32-bit compiled version seems to have some bug.

[cmoses]

Wait for the next release of MAME the 32-bit compiled version seems to have some bug.

Do you mean the next full version (0138) or the next update (0137U1)?  I see they have released a update for 0137.

[R0UNDEYEZ]

Do you mean the next full version (0138) or the next update (0137U1)?  I see they have released a update for 0137.

I was never able to get it to compile with headkazes compiler program for this release. (no disrespect at all headkaze, i've used it 3 times for prior releases with absolutely no problems at all)

what i did was download the source,the high score diff offered here: http://forum.arcadecontrols.com/index.php?topic=64298.0  and got the updated toolset mentioned on the mame site when you get the source. then i followed the directions here: http://mrdo.mameworld.info/compile.html
its slightly different than the pictures because of the new tool set but essentially the same process. I can't code and the idea of compiling myself from the command line really made me nervous, but it really isnt that hard if you  follow the directions.plus it feels awesome when you finish and it works haha
hope that helps you out.

[cmoses]

Roundeyez,

I followed your post, got the hi score diff, got the updated toolset and the Mame updates then followed the directions on Mr Do's site.  Everything went pretty smooth until I got to the last step.  When I typed 'MakeMame' I got an error stating that it didn't recognize the command 'mingw32-make'.  I looked at the .bat file and realized that the last line needed to be edited.  The line was

mingw32-make

I edited to just

make

and it ran correctly.  I tested the compiled version and it runs fine.

[R0UNDEYEZ]

I'm glad it worked for you. 
Yeah ,the command change threw me off as well, sorry I forgot to mention that.

[RetroBorg]

Other than adding hiscore support, what other things are people compiling into mame?

[headkaze]

Can anyone confirm if MC64 works with the latest version of MAME? Just seem to be alot of people reporting it failing and I haven't had time to test the latest version.

[atomikbohm]

I seem to be having trouble compiling the 32 bit version of 137.  I've tried on my i7 (64bit vista) system as well as a AMD Athlon XP (32 bit Win XP) system.  The 32 bit version complied on my i7 system works just fine in my 64 bit vista but when I try to load a rom on the 32bit system it crashes right after selecting a ROM to load. 

Core I7 920
6Gb RAM
Nvidia Geforce 9600

AMD Athlon XP 2100+
768 MB RAM
Geforce FX 5500 OC

I was compiling MAME 0.137 only the hiscore Diff. No 'u' updates.

[headkaze]

Mame Compiler 64 v1.19 Released

- Added "Optimize for: None" option (should solve png2bdc.exe crash issue)

For those who were having problems compiling a 32-bit verson of MAME the official solution from MameDev is to compile with no optimization (ie. Set "Optimize for: None" in Mame Compiler).

[Huggybaby]

Thanks headkaze.

[Yoeddy1]

Just compiled .138...worked great!

[Don]

EDIT: nevermind, have it working perfectly now thanks, great app!

Just one thing, when chosing what processor to optimise for, is there one i should choose for a Pentium III (996MHz)?

[lettuce]

Is this error message anything i should be worried about?:

MameUI.mak:40: warning: overriding commands for target `mameui64.exe'
makefile:684: warning: ignoring old commands for target `mameui64.exe'

[headkaze]

Is this error message anything i should be worried about?:

MameUI.mak:40: warning: overriding commands for target `mameui64.exe'
makefile:684: warning: ignoring old commands for target `mameui64.exe'

Nope. It just means it's using the MameUI makefile instead of the default one.

[jimmy2x2x]

Im trying to compile mameui 0.138.1.0

I have followed the instructions, patched in the correct order (u1.diff then hiscore.txt)
ticked the Mame UI check box and optimize for none option
it compiles with the warnings from the last post, took 20 mins for me
the .exe is 38,626kb
it runs the gui just fine, and allows me to audit games, change default options etc
but crashes when I try to run any game

EDIT:

Changed my compile options to optimize for Intel Core2
ticked:
64 bit processor
dual core
mame ui
disable warnings as error

This compiled version seems to run fine

EDIT2:

optimize for Pentium M, Intel core
ticked:
mame ui
disable warnings as error

This version crashes on game launch

Any suggestions please?

Many thanks

[headkaze]

If it crashes when you compile using the "Pentium M" optimization setting, then don't use it

[jimmy2x2x]

The issue was I wanted to build on my (much) faster pc, and there isn't any combination of switches that would produce a stable build suitable for a pentium class machine.

The only way to build a stable version was to compile on the target machine.

Did the job tho! Thanks

[Generic Eric]

Finished!
3 Hours 11 Minutes and 44 Seconds Elapsed.

Awesome!  I tried w/o the compiler first, but I was missing something.  I took about 5 minutes to set everything up.  What a gem!