hiscore diff (with no nag/white box removal)

[bclinton]

Thanks guys for getting it sorted out. I've uploaded the latest patch and will use that going forward!

Alright.  Total newbie here, so be prepared.  I'm using .154.

I've followed the instructions on the first page of this post to the letter (as far as I'm aware).  I used Mr Do's instructions to compile MAME (I'm such a newb that I don't even know what compiling means, I just followed the instructions) and I downloaded the correct diff file and again followed the instructions to the letter (as far as I'm aware - I think you're getting some idea of my competency level here).

The Mame executable runs just fine, but I'm still getting the nagscreen/loading screen and I'm not sure what to do from here.  Bearing in mind I'm not going to understand a heap of technical terminology, does anyone know what I can do from here?  Have I even given you enough info to know what my problem is?

I'm using Windows 7, 64 Bit if that matters.

Thanks in advance and apologies for my idiocy.

Not trying to change you game plan but I struggled with this too until I found mameuifx. It is already modified to support hi scores and remove nag screens. Take a look at it if you hit a wall...

[Skeeball_Fanatic]

Thanks guys for getting it sorted out. I've uploaded the latest patch and will use that going forward!

Alright.  Total newbie here, so be prepared.  I'm using .154.

I've followed the instructions on the first page of this post to the letter (as far as I'm aware).  I used Mr Do's instructions to compile MAME (I'm such a newb that I don't even know what compiling means, I just followed the instructions) and I downloaded the correct diff file and again followed the instructions to the letter (as far as I'm aware - I think you're getting some idea of my competency level here).

The Mame executable runs just fine, but I'm still getting the nagscreen/loading screen and I'm not sure what to do from here.  Bearing in mind I'm not going to understand a heap of technical terminology, does anyone know what I can do from here?  Have I even given you enough info to know what my problem is?

I'm using Windows 7, 64 Bit if that matters.

Thanks in advance and apologies for my idiocy.

Not trying to change you game plan but I struggled with this too until I found mameuifx. It is already modified to support hi scores and remove nag screens. Take a look at it if you hit a wall...

Thanks dude, I will look now.

[Jakobud]

Are there any known patches for adding in the good old "skip startup frames" feature?

[darthcommanderman]

Hi,

Could someone please help with compiling mame 154s? I'm running XP SP3 (32-bit) and 32-bit mingw (ming-mame-w32-20140905.exe).

I followed Mr.Do's steps and patched the hi_154.diff. It runs a long time and then the error below occurs. I observed that the path advice was incorrect in Mr.Do's steps as make.exe was found in c:\mingw\bin, where c:\mingw\mingw64-w32\bin is an empty folder. I'm pretty sure my path correction is correct since make is not found and errors out quickly otherwise.

Update: I have now tried starting over without any diffs and the same error occurs.

Update 2: I observed that Mr.Do's screenshot showed "make -j5" where makemame.bat calls "make -j3". I tried changing this and the error received was only slightly different (these 2 lines: makefile:909: recipe for target 'obj/windows/mame/video/model1.o' failed
make: *** [obj/windows/mame/video/model1.o] Error 1L

--COMPILE ERRORS (save me!!!):
Compiling src/mame/drivers/model2.c...
src/mame/video/model1.c: In function 'void draw_quads(model1_state*, bitmap_rgb3
2&, const rectangle&)':
src/mame/video/model1.c:307:17: error: array subscript is above array bounds [-W
error=array-bounds]
    while(p[ps2+1].y == cury)
                 ^
src/mame/video/model1.c:319:17: error: array subscript is below array bounds [-W
error=array-bounds]
    while(p[ps1-1].y == cury)
                 ^
src/mame/video/model1.c:319:17: error: array subscript is below array bounds [-W
error=array-bounds]
src/mame/video/model1.c:329:17: error: array subscript is above array bounds [-W
error=array-bounds]
    while(p[ps2+1].y == cury)
                 ^
src/mame/video/model1.c:329:17: error: array subscript is above array bounds [-W
error=array-bounds]
src/mame/video/model1.c:305:17: error: array subscript is below array bounds [-W
error=array-bounds]
    while(p[ps1-1].y == cury)
                 ^
Compiling src/mame/video/model2.c...
cc1plus.exe: all warnings being treated as errors
makefile:909: recipe for target 'obj/windows64/mame/video/model1.o' failed
make: *** [obj/windows64/mame/video/model1.o] Error 1
make: *** Waiting for unfinished jobs....



I found this on a random google search but i think it is for a different symptom (and on linux!)

Troubleshoot

Q: When compiling I get error ompiling src/emu/video/9927tms9927.c... cc1plus: warnings being treated as errors src/emu/video/tms9927.c: In function 'void generic_access(const device_config*, offs_t)': src/emu/video/tms9927.c:142: error: array subscript is above array bounds. What should I do?

A: Edit the makefile and uncomment and edit the line

OPTIMIZE=0

Retrieved from "http://www.mohid.com/wiki/index.php?title=Mame"
Category: Linux


Any help is graciously appreciated!!!
D.

 

[krick]

Start over and make sure you are using the correct build tools from mamedev.org for 0.154:

http://www.mamedev.org/tools/previous-20121207.html

I'd follow the instructions on that page instead of the ones on Mr. Do's page.  I'm not sure his are updated with any frequency.

As an aside, the -j parameter to make controls how many threads are used to build.  -j3 means use 3 threads, -j5 means use 5 threads.  If you have a multi-core and/or hyperthreading CPU, it can dramatically decrease the build time.  Usually, the best number is one more than the number of cores you have.  If you have multi-core and hyperthreading, then I think you use the (cores x 2) + 1  However, some people have issues during the linking stage of the build.  Usually, these are fixed by running the make command again.  If you're experiencing issues compiling, just run "make" without the -j parameter.

[darthcommanderman]

I've been able to reproduce that same error on another XP/32 machine. I was able to compile first try on Vista/64 into mame64.exe. So I guess i'm out of luck for the moment. Someone has suggested looking into patching mingw so I may look into that.

When i used your older version of the build tool against a fresh download of 154s, I received a 'file not found' error near the end. I have no AV on the XP Home SP3 machine was underpatched so i patched it and still nada. I'll update if i continue the thrust or just bail out and download one of the binaries mentioned in this thread.

Thanks so much for your posting!!!

UPDATE: I realized after reading this that I can probably just compile 32-bit mame using the 64 bit machine so long as i set the 32-bit mingw directories in the path. I think i'm finally over it and I'll just use MAMEUIFX.

[abelenki]

hi_154.diff doesn't work with 0.155 source tree, many warnings and errors.

[MKChamp]

hi_154.diff doesn't work with 0.155 source tree, many warnings and errors.

Looking at it now...

EDIT....Uploaded and ready to roll!

[lamprey]

hi_154.diff doesn't work with 0.155 source tree, many warnings and errors.

Looking at it now...

EDIT....Uploaded and ready to roll!

Sweet, thanks a ton!

[abelenki]

EDIT....Uploaded and ready to roll!

many thanks!!

[Andypc]

I am getting a compile error with 0.155

Make.exe: *** [obj/windows64/emu/cpu/h8/h8.inc] Error 2

[Skinnysloth]

I'm having an issue with the video settings not being saved.  I go into mame and set it to display my bezel.  If I quit and restart mame, the bezel is displayed.  If I quit again and restart, the bezel no longer shows up.  I have to go back into the menu setting to set the bezel again.

This was not happening with the mame 0.154 compiled with just the hiscore diff.  It doesn't happen with the precompiled 0.155b from the officical mame site.  It happens with the mame 0.155 compiled with just the hicore diff.

I'm not sure if this is an issue with the hiscore diff, or the 0.155 source.

[Skinnysloth]

Ok, so I complied the 0.155 source without the 0.155 hiscore diff and my video options are being saved.  It looks like there's something in the 0.155 hiscore diff preventing the video settings from being save or it's resetting it.

[lamprey]

Ok, so I complied the 0.155 source without the 0.155 hiscore diff and my video options are being saved.  It looks like there's something in the 0.155 hiscore diff preventing the video settings from being save or it's resetting it.

Confirmed.

[MKChamp]

Ok, so I complied the 0.155 source without the 0.155 hiscore diff and my video options are being saved.  It looks like there's something in the 0.155 hiscore diff preventing the video settings from being save or it's resetting it.

Confirmed.

I uploaded a new version that I believe will correct this(download from the usual spot...). Can someone compile and test and let me know?
Thanks!

[Skinnysloth]

I uploaded a new version that I believe will correct this(download from the usual spot...). Can someone compile and test and let me know?
Thanks!

Just compiled with the new 0.155 diff and video options are now being saved.  Thanks for the fix. 

[phulshof]

I'm obviously doing something wrong, but I'm not getting anywhere with the 0.155 patch. It probably doesn't help that I'm doing this under Linux.
For starters, it doesn't appear to be able to find the files:

-----

patch < hi_155_2.diff
(Stripping trailing CRs from patch; use --binary to disable.)
can't find file to patch at input line 12
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -Nru old/emu/emu.mak src/emu/emu.mak
|+++ src/emu/emu.mak    2014-10-21 15:13:00.000000000 -0500
|
| # emulator core objects
| #-------------------------------------------------
| EMUOBJS = \
|       $(EMUOBJ)/emupal.o \
|       $(EMUOBJ)/hash.o \
|       $(EMUOBJ)/image.o \
|       $(EMUOBJ)/input.o \
|--- old/emu/emuopts.c  2014-09-23 00:48:10.000000000 -0500
--------------------------
File to patch:

---

which is interesting, because the file's right there:

-----

ls src/emu/emu.mak
src/emu/emu.mak

-----

so I figure I'll help it a little:

-----

File to patch: src/emu/emu.mak
patching file src/emu/emu.mak
Hunk #1 FAILED at 52 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file src/emu/emu.mak.rej

-----

Any thoughts?

[MKChamp]

Try patch -p0 -E <hi_155_2.diff

[phulshof]

Try patch -p0 -E <hi_155_2.diff

That takes care of one error; we're on the right track.

patch -p0 -E < hi_155_2.diff
(Stripping trailing CRs from patch; use --binary to disable.)
patching file src/emu/emu.mak
Hunk #1 FAILED at 52 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file src/emu/emu.mak.rej
(Stripping trailing CRs from patch; use --binary to disable.)
can't find file to patch at input line 25
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|
|--- old/emu/emuopts.h  2014-06-06 12:11:32.000000000 -0500
--------------------------
File to patch:

[phulshof]

There appears to be a bit of discrepancy between the code too; perhaps I need a different code base? I'm currently using mame0155s.zip  from http://www.mamedev.org/release.html

From the patch:

diff -Nru old/emu/emu.mak src/emu/emu.mak
+++ src/emu/emu.mak   2014-10-21 15:13:00.000000000 -0500
 
 # emulator core objects
 #-------------------------------------------------
 EMUOBJS = \
    $(EMUOBJ)/emupal.o \
    $(EMUOBJ)/hash.o \
    $(EMUOBJ)/image.o \
    $(EMUOBJ)/input.o \

From the file:

#-------------------------------------------------
# emulator core objects
#-------------------------------------------------

EMUOBJS = \
   $(EMUOBJ)/hashfile.o \
   $(EMUOBJ)/addrmap.o \
   $(EMUOBJ)/attotime.o \
   $(EMUOBJ)/audit.o \
   $(EMUOBJ)/cheat.o \
   $(EMUOBJ)/clifront.o \
   $(EMUOBJ)/config.o \
   $(EMUOBJ)/crsshair.o \
   $(EMUOBJ)/debugger.o \
   $(EMUOBJ)/devdelegate.o \
   $(EMUOBJ)/devcb.o \
   $(EMUOBJ)/devcpu.o \
   $(EMUOBJ)/devfind.o \
   $(EMUOBJ)/device.o \
   $(EMUOBJ)/didisasm.o \
   $(EMUOBJ)/diexec.o \
   $(EMUOBJ)/digfx.o \
   $(EMUOBJ)/diimage.o \
   $(EMUOBJ)/dimemory.o \
   $(EMUOBJ)/dinetwork.o \
   $(EMUOBJ)/dinvram.o \
   $(EMUOBJ)/dioutput.o \
   $(EMUOBJ)/dirtc.o \
   $(EMUOBJ)/diserial.o \
   $(EMUOBJ)/dislot.o \
   $(EMUOBJ)/disound.o \
   $(EMUOBJ)/dispatch.o \
   $(EMUOBJ)/distate.o \
   $(EMUOBJ)/divideo.o \
   $(EMUOBJ)/drawgfx.o \
   $(EMUOBJ)/driver.o \
   $(EMUOBJ)/drivenum.o \
   $(EMUOBJ)/emualloc.o \
   $(EMUOBJ)/emucore.o \
   $(EMUOBJ)/emuopts.o \
   $(EMUOBJ)/emupal.o \
   $(EMUOBJ)/fileio.o \
   $(EMUOBJ)/hash.o \
   $(EMUOBJ)/image.o \
   $(EMUOBJ)/info.o \
   $(EMUOBJ)/input.o \
   $(EMUOBJ)/ioport.o \
   $(EMUOBJ)/luaengine.o \
   $(EMUOBJ)/mame.o \
   $(EMUOBJ)/machine.o \
   $(EMUOBJ)/mconfig.o \
   $(EMUOBJ)/memarray.o \
   $(EMUOBJ)/memory.o \
   $(EMUOBJ)/network.o \
   $(EMUOBJ)/output.o \
   $(EMUOBJ)/render.o \
   $(EMUOBJ)/rendfont.o \
   $(EMUOBJ)/rendlay.o \
   $(EMUOBJ)/rendutil.o \
   $(EMUOBJ)/romload.o \
   $(EMUOBJ)/save.o \
   $(EMUOBJ)/schedule.o \
   $(EMUOBJ)/screen.o \
   $(EMUOBJ)/softlist.o \
   $(EMUOBJ)/sound.o \
   $(EMUOBJ)/speaker.o \
   $(EMUOBJ)/sprite.o \
   $(EMUOBJ)/tilemap.o \
   $(EMUOBJ)/timer.o \
   $(EMUOBJ)/uiinput.o \
   $(EMUOBJ)/ui/ui.o \
   $(EMUOBJ)/ui/swlist.o \
   $(EMUOBJ)/ui/menu.o \
   $(EMUOBJ)/ui/mainmenu.o \
   $(EMUOBJ)/ui/miscmenu.o \
   $(EMUOBJ)/ui/selgame.o \
   $(EMUOBJ)/ui/filemngr.o \
   $(EMUOBJ)/ui/filesel.o \
   $(EMUOBJ)/ui/imgcntrl.o \
   $(EMUOBJ)/ui/imginfo.o \
   $(EMUOBJ)/ui/barcode.o \
   $(EMUOBJ)/ui/tapectrl.o \
   $(EMUOBJ)/ui/viewgfx.o \
   $(EMUOBJ)/validity.o \
   $(EMUOBJ)/video.o \
   $(EMUOBJ)/debug/debugcmd.o \
   $(EMUOBJ)/debug/debugcon.o \
   $(EMUOBJ)/debug/debugcpu.o \
   $(EMUOBJ)/debug/debughlp.o \
   $(EMUOBJ)/debug/debugvw.o \
   $(EMUOBJ)/debug/dvdisasm.o \
   $(EMUOBJ)/debug/dvmemory.o \
   $(EMUOBJ)/debug/dvbpoints.o \
   $(EMUOBJ)/debug/dvwpoints.o \
   $(EMUOBJ)/debug/dvstate.o \
   $(EMUOBJ)/debug/dvtext.o \
   $(EMUOBJ)/debug/express.o \
   $(EMUOBJ)/debug/textbuf.o \
   $(EMUOBJ)/profiler.o \
   $(EMUOBJ)/webengine.o \
   $(OSDOBJ)/osdcore.o \
   $(OSDOBJ)/osdepend.o \
   $(OSDOBJ)/osdnet.o \
   $(OSDOBJ)/modules/sound/none.o \
   $(OSDOBJ)/modules/debugger/none.o \
   $(OSDOBJ)/modules/debugger/debugint.o \

I can see how that's not going to match...

[OnePunchRob]

I am getting a compile error with 0.155

Make.exe: *** [obj/windows64/emu/cpu/h8/h8.inc] Error 2

I had this problem too.  I used an older version of MinGW, which I used to compile 153, and it works fine now.

If you are still having trouble, try using an older version of MinGW.

[bandit721]

Quick question - Is there any update for MAME .156 or do we just use the same diff as version .155?

Thanks in advance!

[haynor666]

I've taken 156 diff from http://forum.arcadecontrols.com/index.php/topic,135823.0.html

[abelenki]

I've taken 156 diff from http://forum.arcadecontrols.com/index.php/topic,135823.0.html

thanks for the link.

[bandit721]

Thanks haynor

[MKChamp]

FYI...the 155 patch works on 156.

[haynor666]

I need hi_156 to build groovymame without galaxian hack and since everything was together in post about groovymame 156 I didn't bother to test hi_155 if this version will work

[bandit721]

Thanks for the confirmation MKChamp!

[haynor666]

You know, there are some diffrences between 155 posted here and 156 posted on groovymame topic.

[Janez]

Hi everyone I'm new here.
I want to thank you MKChamp for your work with the diff file for hiscore support, I really find it useful.
May I make a request?
Can you add an option to choose the path of the hiscore.dat file?
Something like:

mame -hiscore_file /path/to/hiscore.dat pacman

It will be very useful for a Linux user like me, because in Linux, executables, configuration and library files are often in different directories of the filesystem.

I also have a question:
If I press F3 the game resets and the hiscore is resetted too. Is it a correct behaviour? When MAME had the hiscore support built-in, resetting didn't wipe the hiscore.

TIA

[Ansa89]

Taken from "mame.ini":

Code: [Select]

hiscore_directory         $HOME/hi

[haynor666]

If I press F3 the game resets and the hiscore is resetted too. Is it a correct behaviour? When MAME had the hiscore support built-in, resetting didn't wipe the hiscore.

That's normal. Highscores are read and put in memory only when game starts. When You hit reset game goes back to it's default state without highscore patch.

[lamprey]

Taken from "mame.ini":

Code: [Select]

hiscore_directory         $HOME/hi

Can you put the DAT file there too? Or is that just where the high scores are saved to? I was under the impression that you had to have the highscore.dat in the same folder with the MAME exe.

[Ansa89]

That is the directory where you need to put "hiscore.dat" (speaking of linux OSes; I don't know if windows has different options).

[Janez]

Sorry Ansa89 but it doesn't work.
hiscore_directory is the directory in which the .hi files are stored.
If I put hiscore.dat between them nothing happen.
To have hiscore support I need to have hiscore.dat in the same directory from which I launch MAME.
This is unconfortable and I wish to avoid.

[Ansa89]

That's strange, I have the dat file in a separated path and it works without any issue.
I'll check more deeply ASAP.

[haynor666]

On windows highscore.dat must be placed in hi directory. Tested - it works.

[abelenki]

hi_155_2.diff doesn't work with 0.157 source tree, many warnings and errors.

[haynor666]

You may try a small fixto already fixed hiscore 156 by Calamity.

[abelenki]

You may try a small fixto already fixed hiscore 156 by Calamity.

thanks, haynor666, works perfectly.