Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: Drakin on August 21, 2009, 07:23:27 pm

Title: compiling mame problem
Post by: Drakin on August 21, 2009, 07:23:27 pm

Hello, I've been compiling mame and have developed a problem...I went from 132 and updated all of the U updates with no problems. I then went from 132u4 to 133 and now the games come up with the nag screens. I have no idea what is up and am hopeing that somebody has run into this before.

I know that if you compile you should get rid of the nags....and they were gone with mame132 but now there back.

Thanks for any suggestions.

Drakin

Title: Re: compiling mame problem
Post by: FrizzleFried on August 21, 2009, 07:25:06 pm

Each time you compile you must compile the Highscore.diff file for that version in as well or you will get your nag screen back.

Go get the .133 highscore.diff file and add it before compiling .133...

Title: Re: compiling mame problem
Post by: Drakin on August 21, 2009, 07:39:00 pm

Ahhh...makes sence....is there a .133 highscore.diff available? all I can find is 132 version....I may have jumped the gun a bit huh?

Title: Re: compiling mame problem
Post by: FrizzleFried on August 21, 2009, 07:42:30 pm

First page of the HS thread has them all... the latest being .133u3.  Make sure to get the .133 only if you're going to stick with .133.

Title: Re: compiling mame problem
Post by: Drakin on August 21, 2009, 07:50:51 pm

Thanks for the fast replies FrizzleFried...I had forgot about this thread :http://forum.arcadecontrols.com/index.php?topic=64298.0 (http://forum.arcadecontrols.com/index.php?topic=64298.0).

I think I need to follow it and use the updates posted there...you agree?

Title: Re: compiling mame problem
Post by: FrizzleFried on August 21, 2009, 07:56:49 pm

Correct... the .133-.133u2 version...

Title: Re: compiling mame problem
Post by: Drakin on August 24, 2009, 04:12:18 pm

Got the problem fixed....what I think happened is that my compiling files (environment) had got corrupted and thus corrupted my final mame.exe. What I had to do was completely delete all the files and start over....now everything works like it should.. Thanks for all your help.

 :cheers: