MAMEUI64.140u1 Compile assitance

[Draco1962]

I compiled mameui640.140u2 again from scratch with the u1 and u2 diffs in addtion to the hi-score txt for .140 and continue to get the same error message each time a game appears in attract mode or loading from MAME directly or through GameEx. I can play the games, it's just distracting to get the error messages.

cquealy - what settings did you use in the compiler and what diffs did you apply to patch?

[IMBerzerk]

Glad you got it working

You need a 'hi' folder and hiscore.dat file in the root of your MAME folder. Check here for more info http://forum.arcadecontrols.com/index.php?topic=64298.0

You also need 'highscore.dat' in the main MAME (mameui) folder. Also... and often forgotten... create an nvram folder in the main root of mame, and pull down the core of the nvarm files from here. That folder is very important to saving the high scores for some games, it allows the game to auto create the nvram if it uses one. Nvram is what some of the original cabinets used back in the day to store the high scores once it was shutdown for the night. Keep in mind that MAME emulates the action of the original cabinet, so if the nvram file is not there, and it requires one, it will never save the high scores.

On a side note... always save those two folders (hi and nvram) to a back-up drive. As you update MAME, you can carry them forward, literally archiving your best hi scores for YEARS... I know this because I've been doing it with my Berzerk cabinet for 10 years now. It makes for great conversation for friends that still see their best scores on display so many years later.

All the best,

IMB

[IMBerzerk]

I compiled mameui640.140u2 again from scratch with the u1 and u2 diffs in addtion to the hi-score txt for .140 and continue to get the same error message each time a game appears in attract mode or loading from MAME directly or through GameEx. I can play the games, it's just distracting to get the error messages.

cquealy - what settings did you use in the compiler and what diffs did you apply to patch?

Draco, drop back to the original 140 version, recompile with the hi_diff and see if you get the same error. Chances are updating to the u2 patch created compatibility issues with your rom set.

Everytime there is a xxxux update, the core of the roms change, because they might have changed a driver ... not all of the roms change, it depends on what was done in the update. You might have to find the newest roms or update your set with the latest dat file and clrmamepro.

Personally, I find it's simply not worth updating Mame until I read something has changed in the 'whatsnew' file that effect some of my games in a real positive way. Somtimes I update, and the update makes the games worse.. like Stratovox... the digital voice has been screwed for 2+ versions now.

I hope that helps a little...

IMB

[Draco1962]

Draco, drop back to the original 140 version, recompile with the hi_diff and see if you get the same error. Chances are updating to the u2 patch created compatibility issues with your rom set.

Everytime there is a xxxux update, the core of the roms change, because they might have changed a driver ... not all of the roms change, it depends on what was done in the update. You might have to find the newest roms or update your set with the latest dat file and clrmamepro.

Personally, I find it's simply not worth updating Mame until I read something has changed in the 'whatsnew' file that effect some of my games in a real positive way. Somtimes I update, and the update makes the games worse.. like Stratovox... the digital voice has been screwed for 2+ versions now.

I hope that helps a little...

IMB

Thanks! Will give that a try. I had considered something along those lines (compile one of the diffs each time to see which one "breaks" the process). Likely will just apply the hi-score diff and be done with it.

[Draco1962]

Well, I gave it a try but for some reason the .140.u2 hi-score diff patch kept failing during the Apply process. I then decided to try to install the 140.u2 version of mameui64 and ran into the same errors as I did with the previous compiled version. At that point, I decided to totally reinstall .140.u1 and no problems. When I have more time I will attempt the same with .140.u2 (without the .140.u2 hi-score diff) to see if it is the .140.u2 version or maybe try patching/compiling .u1 instead..

[cquealy]

I applied all diffs & now I'm getting the same errors with the snaps. I'll try to go back to 140 too.

[headkaze]

According to the hiscore patch thread MKChamp just re-uploaded the 140u2 patch so I would give that a try.

[Draco1962]

According to the hiscore patch thread MKChamp just re-uploaded the 140u2 patch so I would give that a try.

Sounds like I may not have been the only one impacted by errors - thanks HK! Will probably give it another go, right after I frag my roms with Clrmamepro!

[Draco1962]

Well, it has been a good day - successful clrmampro update and successful MAMEUI .140u2 compile with the corrected hi_136u2.txt file did the trick! will see if it is creating the hi scores soon but at least there are no issues with error messages, etc. So far nag screens are removed and all looking good! Go ahead and FINALLY mark this as resolved! Thanks to all that helped!

EDIT: Looks like the scores are saving as well! YAY!

[cquealy]

I have never used clrmamepro before but figure I should give it a go. Any suggestions for a good tutorial?

[Draco1962]

I followed the instructions from the site here. You can download the latest copy and dat files from http://mamedev.emulab.it/clrmamepro/ . There are also a few threads here in the forums.

[fRequEnCy]

Well, it has been a good day - successful clrmampro update and successful MAMEUI .140u2 compile with the corrected hi_136u2.txt file did the trick! will see if it is creating the hi scores soon but at least there are no issues with error messages, etc. So far nag screens are removed and all looking good! Go ahead and FINALLY mark this as resolved! Thanks to all that helped!

EDIT: Looks like the scores are saving as well! YAY!

Yay again! It's about time it's finally working. Glad you got it figured out.

[cquealy]

I know this is going to sound stupid, but as it's my first time compiling MAME, do I have to do do the whole compile process again or is there a way to apply just updates/patches (like the updated hiscore diff) to my current created MAMEUI?

[Draco1962]

If compiling using HK's compiler, you will need to delete the source files and download them again (or unzip the original to the paths indicated in the instructions) and compile again applying whatever diffs you wish to include first. Once the mameui.exe file is created, it cannot be updated again.

[cquealy]

Thanks. Do you think it was the clrmamepro or the change in hiscore diff (did you use 136u2 or 140u2) that solved the problem? Or a combination of both. I'm feeling okay with doing another compile but the clrmamepro is scaring me!

Also, did you have to go reconfig all your games again?

Thanks again!!!

[Draco1962]

I believe the issue was with the 140u2 highscore diff as that was what was failing to apply. I also applied the 140u1 and 140u2 diff files this time without a problem. I would try compiling again first. If you find any issues with your roms, make backups of them and try clrmamepro. I have not had to reconfigure any of my games but, as always, never hurts to make backups before making any changes.

[Draco1962]

Thanks. Do you think it was the clrmamepro or the change in hiscore diff (did you use 136u2 or 140u2) that solved the problem? Or a combination of both. I'm feeling okay with doing another compile but the clrmamepro is scaring me!

Also, did you have to go reconfig all your games again?

Thanks again!!!

Let me know how you do with the recompile. Also, pretty tight cab! Share some more pics!

[cquealy]

I got greedy and tried the 140u3 update too and amd still getting the errors. I'm going to try and with just the u1 & u2.

Thanks on the cab. Just a standard Slikstik Quad unit but I have added two Actlabs lightguns & recently found a better way to mount my momo steering wheel. I took an old keyboard tray arm and mounted it just above the keyboard slide out tray. The arm can slide all the way left and then be turned to the side out of the way. Just ordering a usb wall plate so that I can have plug and play access on the side on the cab for the usb connection instead of having to open the coin door.