Author Topic: hiscore diff (with no nag/white box removal) (Read 619683 times)

jimmy2x2x · « **Reply #640 on:** June 20, 2011, 04:44:14 pm »

Quote from: shrunkenmaster on June 20, 2011, 04:38:41 pm

I'm at a loss here. I've done this before without any hassle, but right now I'm ...

Trying to compile mame0137, just applying the 0137 hi diff, using the 1.22 compiler, not using any compile options.

This is the last part of blurb I'm getting:

src/osd/windows/d3d9intf.c: In function 'HRESULT d3d_device_set_texture_stage_state(d3d_device*, DWORD, D3DTEXTURESTAGESTATETYPE, DWORD)':
Finished!
1 Hours 7 Minutes and 29 Seconds Elapsed.
src/osd/windows/d3d9intf.c:427: error: 'D3DTSS_ADDRESSU' was not declared in this scope
src/osd/windows/d3d9intf.c:429: error: 'D3DTSS_ADDRESSV' was not declared in this scope
src/osd/windows/d3d9intf.c:431: error: 'D3DTSS_BORDERCOLOR' was not declared in this scope
src/osd/windows/d3d9intf.c:433: error: 'D3DTSS_MAGFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:435: error: 'D3DTSS_MINFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:437: error: 'D3DTSS_MIPFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:439: error: 'D3DTSS_MIPMAPLODBIAS' was not declared in this scope
src/osd/windows/d3d9intf.c:441: error: 'D3DTSS_MAXMIPLEVEL' was not declared in this scope
src/osd/windows/d3d9intf.c:443: error: 'D3DTSS_MAXANISOTROPY' was not declared in this scope
make: *** [obj/windows/mame/osd/windows/d3d9intf.o] Error 1

PC is a Core2 1.86.

Any ideas? Let me know if you need any more info.

I think you have the wrong version of the compiling tools, I ran into something similar last week.

mingw-mame-20110519.exe (0.142u4 - present)
mingw-mame-20100102.exe (0.136u1 - 0.142u3)

DL links here http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=207730&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1&new=1259743662

shrunkenmaster · « **Reply #641 on:** June 20, 2011, 05:26:27 pm »

Thanks jimmy,
I've downloaded this:
mingw-mame-20100102.exe (0.136u1 - 0.142u3)

When I run it, I just get the two folders (64/32, 64/64) - what do I do with these?

ps. Go easy on me, I'm a Mac user

jimmy2x2x · « **Reply #642 on:** June 20, 2011, 05:48:32 pm »

This is what I followed and it works great http://mrdo.mameworld.info/compile.html

shrunkenmaster · « **Reply #643 on:** June 20, 2011, 05:56:37 pm »

Cool, will look at it tomorrow as I've been up since 5am...

shrunkenmaster · « **Reply #644 on:** June 22, 2011, 02:07:25 pm »

Finally got this to work (i think), however...

When I click on the mame.exe I get the (infamous) windows blue screen, with an error "nv4_disp.dll".

I've looked this up and it appears to be video-related. Tried uninstalling/reinstalling the video driver (Nvidia Quatro FX 550), no luck.

Any ideas? Maybe I should now be posting in the software section.

Tafoid · « **Reply #645 on:** June 22, 2011, 04:08:04 pm »

Quote from: shrunkenmaster on June 22, 2011, 02:07:25 pm

Finally got this to work (i think), however...

When I click on the mame.exe I get the (infamous) windows blue screen, with an error "nv4_disp.dll".

I've looked this up and it appears to be video-related. Tried uninstalling/reinstalling the video driver (Nvidia Quatro FX 550), no luck.

Any ideas? Maybe I should now be posting in the software section.

Latest video drivers do not like the advancement that MAME is doing in recent builds (0.142u4+ HLSL). I'd suggest visiting the Nvidia site, select your video card and choose a driver that is earlier than than recent. Many Nvidia owners are getting similar BSOD issues until they rollback their driver. I, for example, am using one from late 2009 for my on-board GeForce 6100 chipset and MAME is happy now. It's hopefully an issue that Nvidia will address soon.

http://www.nvidia.com/Download/Find.aspx?lang=en-us

shrunkenmaster · « **Reply #646 on:** June 22, 2011, 04:40:45 pm »

Thanks Tafoid,
Using an earlier driver and now I can run the Mame binary. However, I still cant compile a version with the hi_diff patch.

I'm using the Headcaze compiler (1.20), trying to compile mame 0137 (with just the hi_0137 patch).

The latest error I'm getting is shown on the attached pic.

Three days of this, getting bored now...

jimmy2x2x · « **Reply #647 on:** June 22, 2011, 05:06:21 pm »

Dont use HeadKaze compiler - this has the latest version of mingw, which is incompatible with the version you are trying to compile.

1] delete everything you have (source, tools, compilers - the lot)

2] create a mamesrc folder in c:\ (so its c:\mamesrc)

3] unpack the mame source code to this folder

4] get this version of the compiler tools http://www.mameworld.info/misc/mingw-mame-20100102.exe

5] unpack that to c:\mingw

6] get the correct version of the hiscore patch and place it in c:\mamesrc

7] Open a command prompt and navigate to c:\mamesrc

8] type these commands into the prompt:

SET Path=c:\mingw\mingw64-w64\bin
patch -p0 -E <xxxxx.xxx (xxxxx.xxx = whatever your hiscore patch was called)
make

This will patch and compile 0.137 for a 64 bit system, for a 32 bit compile change the path in 8] to the mingw32 path.

This is all from memory, but im pretty sure it should work.

yotsuya · « **Reply #648 on:** June 22, 2011, 05:58:26 pm »

Interestingly enough, I can't compile any new versions of Mame that use HLSL. It errors out during compile, referencing what appear to be my video drivers.

shrunkenmaster · « **Reply #649 on:** June 23, 2011, 02:25:58 am »

Thank again Jimmy,

I've already tried that method but that was before I got my video drivers working properly.

I'll give that another try tonight.

shrunkenmaster · « **Reply #650 on:** June 24, 2011, 06:10:22 am »

Just tried your method again jimmy, worked first time! Thanks for running through that, you made it even simpler than Mr Do's instructions.

jimmy2x2x · « **Reply #651 on:** June 24, 2011, 08:35:19 am »

bclinton · « **Reply #652 on:** July 12, 2011, 07:46:32 pm »

After a few tries I got it to work. I patched mameui and the hiscore.diff update. All seems to work fine. I was wondering why all the patching is needed. Why wouldnt these additions simply be added to the regular version of mame? Is it a copyright issue?

Anyways, I appreciate all the help I got from here by reading all the posts.

Woodshop Flunky · « **Reply #653 on:** July 19, 2011, 08:26:16 pm »

Thanks for your post Jimmy. I had the same compile errors as Shrunkenmaster and your instructions worked great!

And thanks to everyone else that contributed to this thread. I was able to compile very easily, and get rid of the nag screens.

mrclean · « **Reply #654 on:** July 25, 2011, 11:43:48 am »

I was able to compile a variety of older mame versions and apply these .diffs however I'm running into a variety of problems :

In Command Prompt I'm getting the following error : " 'patch' is not recognized as an internal or external command, operable program batch file.

Using Mr. Do's Compiling MAME for Dummies the .bat files of "patch mame, and make mame" don't seem to work as I click on them they quickly exit.

In addition If I try to use HeadKazes Compiler and I apparently get an error that the .diff can't even be found when I Downloaded it and placed it in it's respective folder.

Nephasth · « **Reply #655 on:** July 26, 2011, 01:34:40 pm »

I tried this the other day following Mr. Do's instructions and those of Jimmy2x2x. I can patch the source (.135), but I get a few different errors when trying to compile. It compiled the longest before getting an error when I first tried Jimmy's technique. It became late and I gave up on it. I'll try giving it another go next week.

Generic Eric · « **Reply #656 on:** August 01, 2011, 10:56:56 pm »

I compiled successfully for .143 with the u1 and u2 diffs as well as the hi_143 diff. I wasn't successful until moved the src files up a directory if that makes since. Some how in the unzipping, I unzipped into an extra 143 source folder. After that it was just fine.

Avrus · « **Reply #657 on:** September 04, 2011, 07:32:04 pm »

Running into a bizarre issue with 143. If I patch 143 or 143u4 with the hiscore patch (no errors) and try and then while in mame right to pause or use tab to hit the config window mame crashes. If I load 143 unpatched it runs fine and all functions are available.

Edit: I just noticed my hiscore.dat file is from last year and the latest one is from January of this year. Going to update that and recompile see if it makes a difference.

Edit2: Does not make a difference. Going to try compiling without any optimizations in place.

Edit3: Removing all optimizations has resolved the issue.

Justin · « **Reply #658 on:** October 20, 2011, 11:03:31 pm »

Hello all... loooooong mame builder here, early member. Coming back lately for my newest cab upgrade!

Anyhow, I am trying to compile a custom version of MAME (non-GUI) based on 0.132
Having several errors/issues, given up after 2 hours...

I now re-read everything, and I conclude 0.132 is not supported under this tutorial - is this correct? I interpret 0.136 or newer is what this tutorial is for?

If anyone could provide assistance for a custom 0.132 compile with non-nag that would be much appreciated.

EDIT: nvm, I think I figured it out... ended up grabbing an older version of mingw (mingw-mame-20070810.exe) and this seems to be compiling just fine...!

EDIT 2: Spoke too soon lol... it started comiling fine, and about 8 mins into it, I got a large number of errors and then it halted... all seemed to be related to DirectDraw. here are the last few:

Code: [Select]

src/osd/windows/drawdd.c:1211: error: 'DDENUM_ATTACHEDSECONDARYDEVICES' undeclar
ed (first use in this function)
src/osd/windows/drawdd.c:1212: error: 'DD_OK' undeclared (first use in this func
tion)
src/osd/windows/drawdd.c: At top level:
src/osd/windows/drawdd.c:1230: error: expected ')' before 'desc'
src/osd/windows/drawdd.c: In function 'pick_best_mode':
src/osd/windows/drawdd.c:1333: warning: implicit declaration of function 'IDirec
tDraw7_EnumDisplayModes'
src/osd/windows/drawdd.c:1333: error: 'dd_info' has no member named 'ddraw'
src/osd/windows/drawdd.c:1333: error: 'DDEDM_REFRESHRATES' undeclared (first use
 in this function)
src/osd/windows/drawdd.c:1333: error: 'enum_modes_callback' undeclared (first us
e in this function)
src/osd/windows/drawdd.c:1334: error: 'DD_OK' undeclared (first use in this func
tion)
mingw32-make: *** [obj/windows/mame/osd/windows/drawdd.o] Error 1

Giving up on this - anyone knowledgeable enough to enlighten me please?

EDIT 3: Deleted all files, started from scratch, compiled in 13 mins! Thanks for your wonderful work with this, it is my first MAME compile after 20 years of emulation!!!

ShaggyNerd · « **Reply #659 on:** November 19, 2011, 08:55:22 am »

I compiled MAME 0.144 but still no nag screen removal. What do I do?

mamejay · « **Reply #660 on:** November 27, 2011, 08:27:47 pm »

Hi everyone,

Does anyone know where I can get an older dat file?

Looking for 0.103
I use this version as I find it works best on older hardware.

Havok · « **Reply #661 on:** November 27, 2011, 09:34:31 pm »

Quote from: ShaggyNerd on November 19, 2011, 08:55:22 am

I compiled MAME 0.144 but still no nag screen removal. What do I do?

Sounds like you didn't apply the hiscore.diff before compiling...

ShaggyNerd · « **Reply #662 on:** November 28, 2011, 04:19:34 pm »

Quote from: Havok on November 27, 2011, 09:34:31 pm

Quote from: ShaggyNerd on November 19, 2011, 08:55:22 am
I compiled MAME 0.144 but still no nag screen removal. What do I do?

Sounds like you didn't apply the hiscore.diff before compiling...

I said this wrong. I did apply the diff. I got those info screens to disappear, but I still get those messages that say that certain games have video and/or sound emulation problems. Anything I can do about those?

Havok · « **Reply #663 on:** November 28, 2011, 04:43:02 pm »

I thought that got disabled too with the hiscore diff. Perhaps not. Try editing your mame.ini file. Look for the following:

# CORE MISC OPTIONS

and change the skip_gameinfo to 1.

ShaggyNerd · « **Reply #664 on:** November 28, 2011, 04:56:58 pm »

Quote from: Havok on November 28, 2011, 04:43:02 pm

I thought that got disabled too with the hiscore diff. Perhaps not. Try editing your mame.ini file. Look for the following:

# CORE MISC OPTIONS

and change the skip_gameinfo to 1.

It was already set to 1. It gets rid of those info screens, but whenever I load up certain games, I still get a little yellow box that says, "There are known problems with this game." How do I get rid of those?

harveybirdman · « **Reply #665 on:** December 17, 2011, 09:06:38 pm »

just a quick word of advice for morons like me. If you're going to compile MAME make sure you have the source version and NOT one of the binaries...

The source download is in the first table on Mamedev's download page...

If you're new to Mame like me you might have failed to extract it from this source the first time because.... "duh it don't have an application for me to double click?!?!?"

I now know the real reason, and you will too. I'm literally dancing now that I have a MAME version with no Nag screens.

herg · « **Reply #666 on:** December 28, 2011, 09:28:11 pm »

I spent a little time with Gorf, and I've been able to get it working. It requires a write to a particular I/O address before each write to the protected ram where hiscores are located. Here's a diff file that I created that works with mame0144u4 after patching with hi_144u3.

File removed since it's now included in the main patch.

It may also help other astrocde.c games. If it works for others, maybe it can be included in the mainline patches.

MKChamp · « **Reply #667 on:** December 29, 2011, 04:57:03 pm »

Nicely done, herg.
I added it to the u3-u4 patch (re-uploaded it) and it will be included in all future patches.

Thanks!!

gatordad · « **Reply #668 on:** January 30, 2012, 10:24:36 pm »

I am moving all my mame stuff to a new computer so I decided to compile my first version

I used HK compiler for my 114 build, applied the u1, u2, u3 and u4 build updates along with the hs diff for 114 to 116 in the first post, I have added a hi folder in my mame directory, however where do I get the high score dat file from?
The link to leezers site only has the one for 14X, will that one work for 114?

MKChamp · « **Reply #669 on:** January 31, 2012, 11:54:33 am »

Yes, that one will work or you can get it here (I believe more current): http://www.hitotext.com/HiScoreDat/index.php

Khenemet Heru · « **Reply #670 on:** February 03, 2012, 04:35:33 pm »

MKChamp, just a quick question, I'm trying to add no-nag/whitebox removal to the MamePlus source so I can compile that. I wanted to know what sections of the diff file I can delete to get rid of the hiscore stuff, since MamePlus already has it implemented. This is using hi_144.diff for MamePlus 0.144r4932 source. Thanks!

MKChamp · « **Reply #671 on:** February 05, 2012, 12:16:40 am »

You could probably just remove the section that begins with: diff -Nru old/emu/hiscore.c src/emu/hiscore.c and be all good.

ataruzzolo · « **Reply #672 on:** February 07, 2012, 06:54:32 am »

Thanks for the 145 update

atarinut · « **Reply #673 on:** February 10, 2012, 03:42:55 pm »

Hmmmm. Getting this error with the patch installed on 0.145 (compiles fine without patch):

Compiling src/mame/video/mappy.c
src/mame/video/mappy.c: In function 'void palette_init_mappy(running_machine&, const UINT*)':
src/mame/video/mappy.c:92: internal compiler errror: Segmentation fault

Anyone seen this before? Thanks

headkaze · « **Reply #674 on:** February 10, 2012, 03:53:37 pm »

Try compiling without any optimizations.

syncmaster · « **Reply #675 on:** February 10, 2012, 04:02:56 pm »

Quote from: MKChamp on February 05, 2012, 12:16:40 am

You could probably just remove the section that begins with: diff -Nru old/emu/hiscore.c src/emu/hiscore.c and be all good.

Sorry but I've just tested this and it doesn't work. MAMEplus has it's own modifications so files don't match

Help please

Thank you

TrojanBarber · « **Reply #676 on:** March 11, 2012, 07:19:32 am »

Need to compile my own 0.142u4 hiscore mame and i am a little late

Tried with plain 0.142 and 0.143 hiscore diff just to find out what i already suspected. It won't work that way of course...
Compiled 0.142 hiscore without problem with older version of mingw.

What i want to try now is 142u4 with hiscore using new mingw. Versions 0.143-0.145 are useless to me... All compile fine (with or without hiscore diff with newer mingw) but mame throws error when you press ESC on second run (not first not third and so on, only after second run and i really dont get it, why only in direct3d version 9 which i need most). Tried with precompiled versions 0.143-0.145 from mamedev.org, same problem.
Didn't find anything usefull on mametesters.org

Anyone with 142u4 hiscore diff download link?

Thx in advance

milhouse · « **Reply #677 on:** March 15, 2012, 09:20:07 am »

The latest hi_score diff is named "hi_145u1.diff" but the latest u release is 0145u4.diff. When I apply diffs, do I apply in the order

0145u1.diff
hi_145u1.diff
0145u2.diff
0145u3.diff
0145u4.diff

or

0145u1.diff
0145u2.diff
0145u3.diff
0145u4.diff
hi_145u1.diff

Thanks....

deadkat37 · « **Reply #678 on:** March 20, 2012, 10:37:48 am »

Quote from: atarinut on February 10, 2012, 03:42:55 pm

Hmmmm. Getting this error with the patch installed on 0.145 (compiles fine without patch):

Compiling src/mame/video/mappy.c
src/mame/video/mappy.c: In function 'void palette_init_mappy(running_machine&, const UINT*)':
src/mame/video/mappy.c:92: internal compiler errror: Segmentation fault

Anyone seen this before? Thanks

Hi,

I got this same error compiling 0.145 - compiling with no optimizations (just 64-bit ticked) did resolve it - thanks Headkaze! - but I am curious as to why it has suddenly happened in 0.145 and whether the lack of optimisations will cause a noticeable slowdown of MAME performance.

Will this go away in future patches?

TIA for any advice.

bullrees · « **Reply #679 on:** March 20, 2012, 06:10:25 pm »

Quote from: milhouse on March 15, 2012, 09:20:07 am

The latest hi_score diff is named "hi_145u1.diff" but the latest u release is 0145u4.diff. When I apply diffs, do I apply in the order

0145u1.diff
hi_145u1.diff
0145u2.diff
0145u3.diff
0145u4.diff

or

0145u1.diff
0145u2.diff
0145u3.diff
0145u4.diff
hi_145u1.diff

Thanks....

Same question. If I do it the second way I get an error when I do the patch and when I try to compile. I didn't try the first way yet but if I leave it out all together it compiles fine.


Main	Restorations	Software	Audio/Jukebox/MP3	Everything Else	Buy/Sell/Trade
Project Announcements	Monitor/Video	GroovyMAME	Merit/JVL Touchscreen	Meet Up	Retail Vendors
Driving & Racing	Woodworking	Software Support Forums	Consoles	Project Arcade	Reviews
Automated Projects	Artwork	Frontend Support Forums	Pinball	Forum Discussion	Old Boards
Raspberry Pi & Dev Board	controls.dat	Linux	Miscellaneous Arcade	Wiki Discussion	Old Archives
Lightguns	Arcade1Up	Try the site in https mode		Site News


Unread posts \| New Replies \| Recent posts \| Rules \| Chatroom \| Wiki \| File Repository \| RSS \| Submit news

Author Topic: hiscore diff (with no nag/white box removal) (Read 619683 times)

Nephasth