Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: Jefferson on January 24, 2010, 05:56:58 am
-
Why did I suspect this would happen? I had Mame 135 working great, but no saved hi scores. I wanted it bad, so I compiled my own MAME (despite not having used a command line in about 20 years) I dont know the first thing about command line stuff but I did it... BUT AT WHAT COST..?
I followed this guide...
http://mameworld.info/mrdo/compile.html (http://mameworld.info/mrdo/compile.html)
running hi_135.diff before compiling...
and was ecstatic when 'mspacman' and 'asteroid' saved my hi scores! Then I tried to run xmen vs SF. Black screen. same with all capcom fighters. and who knows how many others.... ugh
one thing that did seem weird was, in the guide, under the 'create Mame executable' section, it lists a series of files I was supposed to see... I was missing 'makemeta.exe'
please help!
-
Thanks so much to headkaze and to Mame Compiler!
http://www.headsoft.com.au/index.php?category=mame&page=mc64 (http://www.headsoft.com.au/index.php?category=mame&page=mc64)
I had compiled following Mr. Do's instructions, finding their mamedev linked files had changed, and thus instructions had to be... I had gotten it working though just by guessing and checking. It saved mspacman and galaga scores, but I noticed SFII would just go to black screen and quit. Same with all capcom fighters. and Burgertime. Ugh.
Then I walked thru the Mame Compiler program instructions from scratch, and caught a snag when I pointed to a brand new empty C/mingw. Then I pointed it to the c/mingw from my failed Mr Do compile (made additions per Headkazes instructions)... and it worked! All games enabled! Looking back I learned that my Mr. Do-instructed compile was going off of .128 source (thus my .135 werent all working apparently)
The weekend wasn't a total failure!