Patching MAME breaks my ROMS

[wol-nz]

Unsure if this has been discussed - couldn't see it in the first pages.

I'm running MaLa FE v1.7.4.0 and trying to get a patched no-nag MAME version to run all 65 ROMS i have.
I have easily compiled about 10 version of source code MAME and .diff patches from MKchamps and Mr Do's instructions the MAME executable finishes with no errors.

When i try to use my new shiny compiled executable some ROMs break. Mostly Metal slug and streetfighters.
It attempted to load - the screen flickers and returns to the FE after about 2 seconds.

Although all games work with non-compiled MAME - it really peeves me that the nag screen shows.
The most successful complied version was 0.115 - but still not perfect.

Am i missing something else here.
Thanks for helping

[krick]

Every version of MAME supports more (and different) ROMs than the version before.

What version is your working "non-compiled MAME"?

Just run MAME from the command line without any parameters and it should tell you.

Once you know that, grab the source for that version, add your patches, and re-compile.

[wol-nz]

MAME v0.117 (Jul 10 2007) this is where all my ROMs are working (with nag)
I'll give the .117 source code a compile with the .117.diff file and see what happens.

Thanks for the advice - don't know how others keep updated as it must be a full time job staying up-to-date
I'll let you know

[krick]

Depending on how powerful your hardware is, you might not want to stay up to date.  Newer versions of MAME tend to have higher hardware requirements due to improvements in emulation accuracy.  Better emulation usually requires more power.  Case in point, the discrete audio in games like Asteroids, Phoenix, and Donkey Kong.

As for how people do it, most people use CLRMAMEPRO to manage their MAME ROM collection.
It's very powerful, and it's not the easiest piece of software to use, but once you understand how it works, it's not bad.

As for getting the ROMs, they either download ROM update packs off of [redacted].

[wol-nz]

thanks for that -
Seems i have hit a stumbling block on compiling v.117 it seems to crash in the same point.

Compiling src/mame/drivers/gyruss.c...
Compiling src/mame/audio/gyruss.c...
Compiling src/mame/video/gyruss.c...
cc1.exe: warnings being treated as errors
src/mame/video/gticlub.c: In function 'render_polygons':
src/mame/video/gticlub.c:431: error: 'v[0].z' may be used uninitialized in this
function
src/mame/video/gticlub.c:622: note: 'v[0].z' was declared here
src/mame/video/gticlub.c:432: error: 'v[1].z' may be used uninitialized in this
function
src/mame/video/gticlub.c:622: note: 'v[1].z' was declared here
src/mame/video/gticlub.c:433: error: 'v[2].z' may be used uninitialized in this
function
src/mame/video/gticlub.c:622: note: 'v[2].z' was declared here
src/mame/video/gticlub.c:433: error: 'v[3].z' may be used uninitialized in this
function
src/mame/video/gticlub.c:622: note: 'v[3].z' was declared here
make: *** [obj/windows/mame/mame/video/gticlub.o] Error 1
make: *** Waiting for unfinished jobs....

C:\mamesrc>

SO.. i tried .118 and .119 (crashes in different points but same outcome - unfinished)
I don't suppose you've encounter this error.
Maybe a case of downloading and setting up the compiling environment again?

[krick]

Different versions of MAME may have different compiling environments, unfortunately.  You have to make sure you have the right stuff.

I *think* this is what you need to compile 0.117...

http://mamedev.org/tools/previous-20070617.html


Here's more info with links to older compiler tools...

http://www.mameworld.info/ubbthreads/showflat.php?Number=207730

[Gray_Area]

I *think* this is what you need...

He needs to do a lot of reading before playing.

[wol-nz]

Thanks krick - I had no idea there were different compiling environments.

Geez! -- Gray_Area - for I not know the answer if the question is unknown