WolfMAME .95 = Blue Screen of Death?

Weehawk · Post by **Weehawk** » Tue Mar 29, 2005 11:42 pm

Anybody out there successfully running Wolf95 on a Windows 95/98 machine?

At least three of us get BSOD'ed every time.

Apparently only on .95, and only on WolfMAME.

Any trick to getting it to work?

Frankie · Post by **Frankie** » Wed Mar 30, 2005 3:34 am

When does it happen, when you start up? I run Win98 and don't have any problems.

Post by **mahlemiut** » Wed Mar 30, 2005 4:46 am

That's two Win98 users that don't have this problem (diabolik is the other). Remember that you can use wlfview.exe to see the OS used.

destructor · Post by **destructor** » Wed Mar 30, 2005 5:37 am

On wolf95 games works fine. I have other problem: when wolf95 search new games I can't enter for example to "Options -> Interface Options".

Chad · Post by **Chad** » Sat Apr 02, 2005 12:10 am

ok this is got to be addressed, i'm not going to use wolf95 in T9 because of this problem, get a blue screen every time running wolf95 and win98

Fatal Exception 0E: address 0028:BFF98DCE

Also i'll report the problem i have with any other wolfmame (or mame plus i think) with win98 where the first time i run it it crashes (no bsod) but next time i run it it works. here's what mame says the first time (wolf94<)

-----------------------------------------------------
Exception at EIP=5667E5C3: FLOAT INVALID OPERATION
-----------------------------------------------------
EAX=0041B1B8 EBX=00418F20 ECX=0041B1B8 EDX=000001E0
ESI=0073CBA4 EDI=0041B1D0 EBP=0073CA9C ESP=0073CA90

Haze · Post by **Haze** » Sat Apr 02, 2005 11:29 am

ok.. I got similar on XP when the Direct 3D code was first added.. a blue screen relating to a floating point operation..

Don't ask how, it shouldn't be possible, but yes, the code could crash XP at any point.

That was fixed, however with that in mind maybe you're enabling D3D on Win98 and it doesn't like it, or your graphic card drivers suck, or your DirectX is broken / out of date.

As far as Mame is concerned Windows 98 is an unsupported platform, sorry, I wouldn't even oppose changes which made Mame run only on 2000 and above.

MJS · Post by **MJS** » Sat Apr 02, 2005 4:48 pm

Same for me (BSOD).

And I'm just doing "mamep95.exe -cc" or double-clicking mame32p95.exe

Haze · Post by **Haze** » Sun Apr 03, 2005 9:56 am

its quite clearly broken.. it crashed for me too, and if run it with GDB I get the following.

This is a wolfmame problem, not a mame problem.

E:\wolf>gdb mamep95
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...(no debugging symbols found)...
(gdb) run defense
Starting program: E:\wolf/mamep95.exe defense
warning: HEAP[mamep95.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003D0000, 682A61C0 )

Program received signal SIGTRAP, Trace/breakpoint trap.
0x7c901231 in ?? ()
(gdb) ^AQuit (expect signal SIGINT when the program is resumed)

Post by **mahlemiut** » Sun Apr 03, 2005 10:52 am

No idea where this problem occurs, it apparently doesn't affect MAME Plus either. Even harder to test for as neither of my systems (WinMe, WinXP Pro SP2, even Wine starts to run it, quitting when it can't find unicows.dll

) show this problem.

Post by **mahlemiut** » Wed Apr 06, 2005 10:47 am

The heap warning occurs in earlier versions too, and in at least one other MAME Plus derivative too (GareMamePlus!0.90).

In a compile built with debugging symbols I get:

Code: Select all

Starting program: C:\wolfmame\w095/mamep95.exe
warning: HEAP[mamep95.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003D0000, 689852E0 )


Program received signal SIGTRAP, Trace/breakpoint trap.
0x7c901231 in _libdsound_a_iname ()
(gdb) quit

Which suggests some oddity related to DirectSound... maybe their code requires DX8 or 9?

EDIT: the 'extra' tools and libraries include DirectX 7 libraries and headers, so I would presume not.

Chad · Post by **Chad** » Wed Apr 06, 2005 12:15 pm

i'm sure i have at least DX 8.0b installed, but don't remember if i installed to the latest version, will try that.

Post by **mahlemiut** » Thu Apr 07, 2005 8:02 am

http://wolfmame.marpirc.net/wolfmameplus-095-vc.7z

Try this version, it is compiled using VC++ Toolkit 2003.

SRMP6 and TX-1 drivers needed a bit of work to get VC to compile them too, so I hope it's all worth it

ah_web · Post by **ah_web** » Mon Apr 11, 2005 9:38 pm

Just for information,
wolfmameplus-095-vc.7z works well under my win98...

Chad · Post by **Chad** » Wed Apr 13, 2005 12:21 am

the vc version doesn't blue screen, cool! but it crashes (either during or after writing the wlf file) every time.

Writing .wlf file:
-----------------------------------------------------
Exception at EIP=100976BE: ACCESS VIOLATION
While attempting to read memory at FFFFFFFF
-----------------------------------------------------
EAX=00000000 EBX=00000000 ECX=00000119 EDX=00000000
ESI=0063FB99 EDI=11536C91 EBP=0063FE38 ESP=0063FB80

MJS · Post by **MJS** » Fri Apr 15, 2005 1:01 am

Also, sound doesn't seem to work during playback.