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

MKChamp · « **Reply #400 on:** January 05, 2010, 02:17:46 am »

Quote from: BamBam on January 04, 2010, 07:54:27 am

Quote from: Extreme8 on April 10, 2007, 09:02:48 am
If you need them....

Don't ask where I found them - a fella has to have his secrets.

A fellow like you wouldn't happen to have a friend who knows where a fellow like me could find .128 diffs do you?

I don't know about him...but a friend of a friend that knew a guy that knew told me. I think you will need to manually copy and paste them into your browser. Hyperlink may not work(may say forbidden).
http://mamedev.org/updates/0128u1_diff.zip
http://mamedev.org/updates/0128u2_diff.zip
http://mamedev.org/updates/0128u3_diff.zip
http://mamedev.org/updates/0128u4_diff.zip
http://mamedev.org/updates/0128u5_diff.zip
http://mamedev.org/updates/0128u6_diff.zip
http://mamedev.org/updates/0128u7_diff.zip

MKChamp · « **Reply #401 on:** January 16, 2010, 05:16:01 pm »

MAME went under some big changes for 136u1. You need new tools to compile (which can be found over at mamedev.org). Not sure if headkaze's compiler will need to be updated...but fairly certain it will.
Along with all the changes, the hiscore patch had to be changed more than usual, too. Please test to make sure it still works with all the games in 136u1 that it did work for in 136 and earlier.

Yoeddy1 · « **Reply #402 on:** January 17, 2010, 08:56:05 pm »

Could somebody please PM me or email me the hi_136.txt file? It looks like the site to grab it from has been suspended.

Thanks

Comtek · « **Reply #403 on:** January 17, 2010, 09:24:03 pm »

google had the site cached is this file right
not sure

MKChamp · « **Reply #404 on:** January 17, 2010, 09:45:41 pm »

I just got off the phone with powweb. They said they suspended it because one of my files there was flagged as having a virus (the rcrclient_install.exe)...but it definitely is NOT a virus. The WinVNC bundled with it (it's for connecting and working on remote computers) is what flagged as a trojan. Stupid. They said a representative will call me in 24 to 48 hours. So, it looks like it will be at least a day before the site is active again. All they needed to do was look at: http://www.csd.uwo.ca/~magi/doc/vnc/virus.html
really chaps my hiney.

MKChamp · « **Reply #405 on:** January 18, 2010, 12:24:31 am »

Ok...they got back to me quicker than expected. Site is back up...hiscore files are all available again.

buzbard · « **Reply #406 on:** January 31, 2010, 10:21:51 pm »

I seem to be having a problem compiling the newest version of MAME(.136u2) with your patch.
I've been compiling MAME since ver. .127 and haven't had any problem 'till now.

I did download and install the new tool chain for .136u1, and it compiled fine.

I've downloaded and applied all the patches, .136u1, .136u2 & hi_136u2 in that order but I keep getting this message:

Code: [Select]

src/emu/sound/fm2612.c: In function 'void ym2612_update_one(void*, FMSAMPLE**, int)':
src/emu/sound/fm2612.c:2170: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [obj/windows/mame/emu/sound/fm2612.o] Error 1

Can some one tell me what I'm doing wrong please?

I'm using:
1.28Ghz Pentium4
1.5Gb RAM
WinXP Home SP3

Thanks...

MKChamp · « **Reply #407 on:** February 02, 2010, 12:34:22 am »

I'm not familiar with seg faults. But a quick search reveals it could be due to hardware issues. What I would do is completely delete the mingw directory and start from scratch. See if you get the same error after doing that.

buzbard · « **Reply #408 on:** February 02, 2010, 12:12:48 pm »

Thanks for replying.

I already tried that, a couple times. I'm going to try and compile on my notebook later this afternoon, hopefully it will work, although it's has a slower processor, just might work.

I'll let you know.

Thanks again.

Update:
It successfully compiled on my notebook, which tells me that there is something wrong with my PC (I haven't reinstalled WinXP for about 4 years now, maybe it's time for a reinstall).
Thanks again for your help.

scept1c · « **Reply #409 on:** February 04, 2010, 02:54:04 am »

yeah I think the faults are due to hardware problems. 4 years of running a system without uninstall

romshark · « **Reply #410 on:** February 08, 2010, 11:42:49 pm »

The computer in my cabinet is an Athlon X2 64, but I got rid of whatever Vista came with it and put on Windows XP Home (32-bit). It shows up on my system properties "AMD Athlon(tm) Dual Core".

I was wondering: would I get any performance boost if I use the AMD Athlon 64 compile option?

I guess what I really need to know is if compiling as an Athlon 64 would make it a 64-bit version of MAME. I don't see where else in the compiling directions would specify 32 or 64 bit, and I'm not sure if a 64-bit OS is needed to fully use this processor (I don't know if the original Vista on the system was 32 or 64 bit.)

MKChamp · « **Reply #411 on:** February 09, 2010, 03:02:55 pm »

Quote from: romshark on February 08, 2010, 11:42:49 pm

The computer in my cabinet is an Athlon X2 64, but I got rid of whatever Vista came with it and put on Windows XP Home (32-bit). It shows up on my system properties "AMD Athlon(tm) Dual Core".

I was wondering: would I get any performance boost if I use the AMD Athlon 64 compile option?

I guess what I really need to know is if compiling as an Athlon 64 would make it a 64-bit version of MAME. I don't see where else in the compiling directions would specify 32 or 64 bit, and I'm not sure if a 64-bit OS is needed to fully use this processor (I don't know if the original Vista on the system was 32 or 64 bit.)

Unless I am totally mistaken, the 64 builds are only for 64 bit operating systems. So, since you have XP 32-bit, the 64-bit build wouldn't work...

romshark · « **Reply #412 on:** February 09, 2010, 03:23:29 pm »

So compiling with the "ARCHOPTS = -march=athlon64" option does produce a 64-bit MAME? Just want to make sure I'm getting the most from my computer.

I though I used that option when I compiled MAME 134, and that version runs on all my systems OK. Although, that would explain why I have problems compiling this latest version...

RoadRunn · « **Reply #413 on:** February 09, 2010, 03:53:08 pm »

Quote from: romshark on February 09, 2010, 03:23:29 pm

So compiling with the "ARCHOPTS = -march=athlon64" option does produce a 64-bit MAME? Just want to make sure I'm getting the most from my computer.

I though I used that option when I compiled MAME 134, and that version runs on all my systems OK. Although, that would explain why I have problems compiling this latest version...

I have had quite a bit of experience with compiling and cross-compiling.

The toolchain that I got from the updated instructions (mingw64-w32) is a 32-bit compiler and creates 32-bit binaries. These binaries can be run on either a x86 or AMD64 version of the operating system. In order to create a native AMD64 binary, you either need a x64 cross compiler (need to build one yourself) on a 32-bit OS, or create a native compiler (again build one yourself) on an AMD64 operating system. You MUST be running an AMD64 version of the operating system to execute AMD64 built binaries.

It's going to take quite a bit more work to build a 64-bit Mame than just compiler options.

GCC has deprecated certain compiler options in the past. This may be the reason why you are not able to use these options with the new toolchain. If you really want to use 64-bit binaries, the first step is to get the AMD64 version of the operating system back on your machine. Although in my experience there are very few applications that really get a performance gain from running true 64-bit (Mame may be one of them, but have not tested myself).

shateredsoul · « **Reply #414 on:** February 22, 2010, 05:49:01 am »

Hi so I successfully compiled my own mame! Woo hoo.. the nag screen is gone

But I realized I miss the loading screen, it sucks to have to wait a while just looking at a blank screen. Some people start thinking it doesn't work when it's just loading.

I tried using the command to disable the loading patch (disable_loading_patch 1)

but the loading screen won't come back. Can anyone tell me where in there mame.ini to place the command? I tried at the beginning and at avrious places and nothing. I also tried the mamui64.ini

nevermind figured it out

MKChamp · « **Reply #415 on:** February 24, 2010, 03:34:50 am »

Quote from: shateredsoul on February 22, 2010, 05:49:01 am

Hi so I successfully compiled my own mame! Woo hoo.. the nag screen is gone

But I realized I miss the loading screen, it sucks to have to wait a while just looking at a blank screen. Some people start thinking it doesn't work when it's just loading.

I tried using the command to disable the loading patch (disable_loading_patch 1)

but the loading screen won't come back. Can anyone tell me where in there mame.ini to place the command? I tried at the beginning and at avrious places and nothing. I also tried the mamui64.ini

nevermind figured it out

Just curious....what did you figure out?

shateredsoul · « **Reply #416 on:** February 24, 2010, 04:18:46 am »

well for some reason my ini file already had the patch command in there, so I just changed the value to 1 for the one I wanted to disable (I wanted to see the loading screen, but not the nag screen)

I compiled another version for my desktop though, and just added the following

#
# CORE MISC OPTIONS
#
bios
cheat 0
skip_gameinfo 0

#
# CORE MKChamp OPTIONS
#
disable_hiscore_patch 0
disable_nagscreen_patch 0
disable_loading_patch 1

I included the "core misc options" as a frame of reference if anyone wants to include this in theirs, it shouldn't matter where you put these commands but for some reason it did for me.

Also, I placed the files for hi scores in the root folder for mame instead of in "hi" folder, when I had it in "hi" it wouldn't record the scores.

So it works perfectly now!

RobbyMac · « **Reply #417 on:** February 28, 2010, 10:08:45 pm »

K
not sure what I am doing wrong.
I've got two different machines ive tried compiling .135 on. Both are xp (one is tiny xp, my cab)
Both I get the same errors after the drivers compile and all the game names go wizzing by.

all stuff about directx i think... ie. c:\mingw\minw64-w32\bin\../lib/gcc/1686-w64-ming32/4.4.3/../../../../i686-w64-mingw32/include/d3d9types.h:1145: note: previous definition of 'd3dtss_mipmaplodbias' was here

3 or three errors like the above, a bunch others with an 'redeclaration of enumerator' error. all relating to d3d9types.h

So then I went ind downloaded the directx-headers file, and extracted the files into the c:\mingw\minw64-w32\include folder (found further down in the 'harder' section of http://mamedev.org/tools/#compile
And I get the same errors.

ANyone have anysort of updated compiling instructions? or an idea of what I am doing wrong, because it's difficult being a first timer, let alone tyring to determine the new directory structure/names for the mingw stuff. I changed the paths in the .bat's to c:\mingw\minw64-w32\bin and changed the 'mingw32-make' command to 'make'. It all appears to be working properly, until it gets to the d3d stuff

shateredsoul · « **Reply #418 on:** February 28, 2010, 10:23:58 pm »

these instructions helped me a lot and made it very easy
http://www.headsoft.com.au/index.php?category=mame&page=mc64

RobbyMac · « **Reply #419 on:** February 28, 2010, 11:02:07 pm »

AWESOME!!!!
Same friggin error using that compiler.
make: ***[obj/windows/mame/osd/windows/d3d9intf.o] Error 1

um... screwit. I've spent enough time building this damn thing I don't need to spend another 20 hours trying to compile a friggin version just for hi-scores that should be there in the first place.

EDIT: YOU HAVE TO USE OLD COMPILER mingw-mame-20070810.exe WITH VERSIONS 0.135 & EARLIER

I thought I read through the last few pages thoroughly, but hadn't found it. Mamedevs page has a byline about where to download the old compiler, but no info pertaining to needing it prior to version 136
It is currently compiling and has gotten further than previous attempts. Sorry. Hopefully noone else runs into this problem as apparantly so many others have?!?

Huggybaby · « **Reply #420 on:** February 28, 2010, 11:27:28 pm »

You have to use the old compiler, this is covered at least twice already in this thread. The new compiler only works with .136u1 and newer.

Haterot · « **Reply #421 on:** March 02, 2010, 11:36:25 am »

Little help on this error. Patched u1-u3 and hi136u2 tried this on two different machine same errors.

headkaze · « **Reply #422 on:** March 03, 2010, 03:55:53 pm »

Quote from: Haterot on March 02, 2010, 11:36:25 am

Little help on this error. Patched u1-u3 and hi136u2 tried this on two different machine same errors.

Mame Compiler uses a custom compiled version of make, so it looks like you're not using the version of MinGW installed with Mame Compiler.

Haterot · « **Reply #423 on:** March 04, 2010, 10:27:22 am »

Quote from: headkaze on March 03, 2010, 03:55:53 pm

Quote from: Haterot on March 02, 2010, 11:36:25 am
Little help on this error. Patched u1-u3 and hi136u2 tried this on two different machine same errors.

Mame Compiler uses a custom compiled version of make, so it looks like you're not using the version of MinGW installed with Mame Compiler.

HK thanks. You were right I had reinstalled the tools from the mamedev page and it overwrote your install. Thanks for the tip.

lolo-le-haricot · « **Reply #424 on:** May 10, 2010, 12:46:24 pm »

Hi guys

(Sorry for my bad english, french inside ^^)

I have a problem with the highscore diff 137u4.

If I try to compile mame with hi_137u4.diff, compilation crash, but if I compile the file without using mame hi_137u4.diff, the compilation goes through without problem.

Do you have the same problem?

- l0l0 -

MKChamp · « **Reply #425 on:** May 10, 2010, 11:15:01 pm »

Couple of things...
What are the errors it gives you? Are you starting with the 137u4 source?
I don't think anyone else is having this issue (I can see alot of people have downloaded it...and no complaints...)
I hope this translates back to french ok :-)

lolo-le-haricot · « **Reply #426 on:** May 11, 2010, 02:30:04 am »

This is what I do :

I downloaded the source for 137.
I patched with 0137u1.diff with no errors.
I patched with 0137u2.diff with no errors.
I patched with 0137u3.diff with no errors.
I patched with 0137u4.diff with no errors.
I patched with hi_137u4.diff with no errors.

I try to compile code, it start but after a few minutes, it crash.

If I do not apply the patch hi_137u4.diff, I have no problem.

I give you the error message I get tonight (France time)

Thank's for reply

- l0l0 -

lolo-le-haricot · « **Reply #427 on:** May 11, 2010, 06:34:49 am »

This is the error message :

Uploaded with ImageShack.us

MKChamp · « **Reply #428 on:** May 11, 2010, 01:02:58 pm »

The module isn't modified at all by the hiscore patch. I've heard that segmentation faults can occur due to hardware issues (not 100% sure that is correct or not). Can you try to compile on a different machine and see if it works there? No one else has reported the issue you are having...

lolo-le-haricot · « **Reply #429 on:** May 11, 2010, 01:07:23 pm »

I will try tomorrow to compile on my work computer.

But what is strange is that if I did not patch with hi_137u4, the compilation goes through without problem.

lolo-le-haricot · « **Reply #430 on:** May 12, 2010, 02:43:31 am »

Well, I tried compiling at my work, and I did had no problem.

So the problem must come from my compilation environment at my home...

shateredsoul · « **Reply #431 on:** May 12, 2010, 12:16:29 pm »

take the mame you compiled at work..... home

lolo-le-haricot · « **Reply #432 on:** May 12, 2010, 12:23:53 pm »

lol, thank's Great idea, but I had already thought, but it does not solve the problem of compiling at my home

MKChamp · « **Reply #433 on:** May 12, 2010, 01:01:03 pm »

Take the machine at work.... home

lolo-le-haricot · « **Reply #434 on:** May 12, 2010, 01:17:05 pm »

lol

Maybe the problem is my hardware ?

CPU : INTEL Core 2 duo E7600
CG : GAINWARD GTX260 896Mio
CM : ASUS P5P43TD
RAM : CORSAIR DHX XMS3 3Go (3x1Gio)

Windows XP Pro SP3

I have tried to compile again, stopping my antivirus but it did not work.

MKChamp · « **Reply #435 on:** May 13, 2010, 01:56:07 am »

Well...this would coinside with what I've read on segmentation fault errors in compiling...hardware related. Although, I do not have enough exposure in this to pin-point the exact failure.

tylervalo · « **Reply #436 on:** May 24, 2010, 10:51:26 am »

Woulds someone be kind enough to upload their compile mame version? No matter how I try I can never get a version to compile with out something going wrong.

Tomy. · « **Reply #437 on:** June 07, 2010, 03:54:21 pm »

I have compiled the last week or so several Windows versions of 137 and 138 with and without the hiscore diff. Compilation goes without a problem.

The original (no hiscore diff added) executable works like a charm for all of 137 U's and 138 and 138 U1. However after adding the hiscore diff and recompiling, every time mame.exe throws an exception and bails.

I have step by step pulled everything from the diff (warning removal etc.) now I'm down to only the changes for the hiscore and I'm still seeing this behavior. If I remove the highscore part of the diff and leave the other parts (like the warning removal) the problem goes away.
Anyone else seeing this? I'd really like to get the highscore saves work on my box. Thanks!

Havok · « **Reply #438 on:** June 07, 2010, 04:00:05 pm »

Just compiled 137 64bit, no problems...

Tomy. · « **Reply #439 on:** June 07, 2010, 04:41:28 pm »

Thanks, Havok! I haven't tried 64 bits. Can you try 32?
32 bit runs perfectly for me ONLY without the hiscore diff.


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