Mame Compiler 100% Automated

[Rain]

^^ I don't have my ROMS available to test this out. You don't have to add your own high score patch to the system, just check the box. Lemme see what my other tester concludes.

[zero dreams]

I have no idea why this is displayed this way, but I don't even have a box. I've downloaded QuickMame twice. I've also clicked everywhere surrounding this box. ???

[Rain]

it looks that on your pc because your font dpi must be greater than 100%

[bb_neo]

Ok will wait your tests. Yeah I understood that the hiscore file gets fetched automatically. I did not add anything in the Source patches tab. If the function of the Disable Warning box removes the nag screens then this is not working. I complied 2 time but still no joy.

@ zero dreams: No display error on my side. As rain said, this is clearly something to do with higher dpi settings in Windows7.

[zero dreams]

Ok will wait your tests. Yeah I understood that the hiscore file gets fetched automatically. I did not add anything in the Source patches tab. If the function of the Disable Warning box removes the nag screens then this is not working. I complied 2 time but still no joy.

@ zero dreams: No display error on my side. As rain said, this is clearly something to do with higher dpi settings in Windows7.

I'll change my dpi back to see if I can compile without using the hi_147.diff patch and only using QuickMame from start to finish.

I have no idea what went right but it seems to actually work after the first play. First play = Loading & Nag. Restart Mame. Second play (same game) = only Loading. Idk what's going right but I'm going to do some more testing & compiling. Thanks!!

[Rain]

I am currently looking @ a bug with the current high score patch; because reading the QuickMame logs I can clearly see that it is compiling in the high score patch - so it might be an error with the high score patch itself.

[zero dreams]

I changed my dpi back to 100% and the window appeared exactly as it should, with the exception that "Enable Direct Input" appears as "Enale DirectInput". I'm gonna test without any Source Patches. Also, whenever Build MameUI is checked it will not compile. Leaving that box unchecked is the only way I have been able to start the compiling process. I'll do some more testing and post back with more info.

On another note, will QuickMame compile other versions? I have read most of this entire thread, but it seems during the evolution some things changed. Just curious.

Edit: Only using QuickMame it compiled with direct input, no-nag, high scores successfully

[Pyramid_Head]

Thanks a lot for reviving this Rain, giving it a shot now!!

[Pyramid_Head]

Getting this error in the terminal

Parameters = OSD=windows TARGETOS=win32 -j5 ARCHOPTS=-march=native PTR64=1

CompileMame: The system cannot find the file specified

does the same for core 2 etc..

[Thooperman]

Hi Rain,

Just thought I'd post my results with having a go at QuickMame 2.1.0.8

I used a 32bit compile for a Core2 processor with Dual Core Ticked.

I first compiled MAME with Enable Direct Input, Enable Hi Score, Disable Warnings, Clean compile and Base build ticked and all worked well except for the Hi Score/Nag/White Box which is mentioned above.

I decided to try again, only this time I only ticked Enable Direct Input, Clean Compile and Base Build then I downloaded the Hi Score/No Nag/No White Box diff from http://forum.arcadecontrols.com/index.php/topic,64298.0.html and added that diff into the source patch area. This compile worked like a charm with everything working the way I hoped!

Thanks so much for this program, it's so simple to use. I've used other compilers and I've done manual compiles both of which has given me mixed results, sometimes I got it working, sometimes not so much. The failed compiles were probably my fault entirely, but with this program, there's not much for me to think about to get it going.

The only suggestion I have to the program is to automatically add the folder named "hi". It's not a big deal to do manually, but someone might not realise it has to be done or forget and have trouble with hi scores not working.

I hope this helps and Thanks again.

[Rain]

I can now confirm that the automated high score patch is not working on Windows 7 builds. However, it does work on Windows 8; proof positive that Windows 8 rocks! I will see what I can do for you Windows 7 users.. Thanks guys!

[Pyramid_Head]

I'm still not sure about my error though.

[Rain]

I'm still not sure about my error though.

Your error, QuickMame is complaining that it cannot find make.exe.. Do you only have one check box checked (either 32 bit, or 64 bit) because having both checked or none will also result in this error? Failing that open up your MinGW folder and verify that the make.exe is located in the /bin folder. Thanks hunk!

[Pyramid_Head]

64 bit is checked. However, the MinGW folder is completely empty lol. I get this when trying to reinstall the MinGW folder.

---------------------------

Error Extracting

---------------------------

There's been a problem extracting that zip file. Could not find a part of the path 'C:\Users\Hunk\AppData\Roaming\QuickMame\MinGW\mingw.zip'.

---------------------------

OK

---------------------------

[Rain]

64 bit is checked. However, the MinGW folder is completely empty lol. I get this when trying to reinstall the MinGW folder.

delete the mingw folder manually, then try to reinstall mingw.

[Pyramid_Head]

Doing that now. Will report back

[zero dreams]

I can now confirm that the automated high score patch is not working on Windows 7 builds. However, it does work on Windows 8; proof positive that Windows 8 rocks! I will see what I can do for you Windows 7 users.. Thanks guys!

Hmm...that's strange because the one I compiled shows me a high score screen on many of my games as well as removing the nag screen after first play.

[Rain]

Okay guys, I think I solved a little mystery here - it would seem after MAME is compiled you should then -cc your Mame executable and make sure these lines are all set to 0 in your Mame.ini file. I recompiled on Windows 7 -cc my install and changed the lines to 0 and then the no nag patch worked. Let me know how it goes for you all.

#

# CORE MKChamp OPTIONS

#

disable_hiscore_patch 0

disable_nagscreen_patch 0

disable_loading_patch 0

I will probably build an update that handles this automatically. I am also thinking about adding in native Cave support; but not sure about that ATM, priority #1 is to fix up these loose little annoyances. I miss programming stuff like this

[Pyramid_Head]

Cave support would be sweet! Though imo that should probably be discussed in the gold section lol. Btw I got the same error man not sure what is going on

[zero dreams]

Sorry if I'm clogging but just wanted to give good feedback...

I used QuickMame, -cc my install, added the "hi" folder, changed skip_gameinfo to "1" and confirm_quit to "1"

The above lines were already changed to "0"

[Rain]

Sorry if I'm clogging but just wanted to give good feedback...

I used QuickMame, -cc my install, added the "hi" folder, changed skip_gameinfo to "1" and confirm_quit to "1"

The above lines were already changed to "0"

Your not cloggin' at all, I like getting feedback. So, after doing that I am assuming the auto patch worked? If so, I will include that data you provided in the next build.

[zero dreams]

It worked for me as I deleted the diff, then compiled, and BAM!!

[Rain]

It worked for me as I deleted the diff, then compiled, and BAM!!

What do you mean, deleted the diff?

[zero dreams]

The diff I downloaded from here and tried to use as a source patch.

[Rain]

Updated application, download here: http://www.hyperspin-fe.com/forum/downloads.php?do=file&id=5280