Blitzkrieg 2 anthology page fault at startup

[willb]

Blitzkrieg 2 (1.6) and additions in Blitzkrieg 2 Anthology from gog.com causes exception when starting bin/game.exe with the following error.

I run wine 1.5.18. An old post http://forum.winehq.org/viewtopic.php?t=11374 seems to indicate this may be a regression that was never resolved.

Should I install an old wine (1.3.6 seems to run the game according to appDB)? Would there be a problem with mismatched kernel version?

Code: Select all

Unhandled exception: page fault on read access to 0x00000088 in 32-bit code (0x00a4dce4).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:00a4dce4 ESP:0032f7c0 EBP:3d3f6000 EFLAGS:00010246(  R- --  I  Z- -P- )
 EAX:00000000 EBX:00000000 ECX:0032f810 EDX:37ff4a90
 ESI:00000000 EDI:00000000
Stack dump:
0x0032f7c0:  3d3f6000 00a4dc00 00000000 0032f7d0
0x0032f7d0:  3f198d8b 000004e4 3b7f4a7b 387fd0de
0x0032f7e0:  00000000 7c350400 38bfd6e0 38bfd6e8
0x0032f7f0:  38bfd6fb 0032f854 0000000b 005f6b28
0x0032f800:  3e3fb350 37ff6a40 0000000b 7c35043c
0x0032f810:  0032f8d0 00b36ada 00000002 005e80e6
Backtrace:
=>0 0x00a4dce4 in game (+0x64dce4) (0x3d3f6000)
0x00a4dce4: movl        0x88(%esi),%ebp

...
Threads:
...
00000024 (D) C:\Blitzkrieg2\Bin\Game.exe
        00000030    2
        0000002f   15
        0000002e   15
        0000002b    0
        0000002a   15
        00000029    0
        00000026    0
        00000025    0 <==

This is the trace with WINEDEBUG around where the page fault seems to occur:

Code: Select all

0025:Call KERNEL32.MultiByteToWideChar(00000000,00000000,00bc5c80 " Texture: ",0000000a,0032efb0,00000400) ret=005fa99f
0025:Ret  KERNEL32.MultiByteToWideChar() retval=0000000a ret=005fa99f
0025:Call KERNEL32.GetLastError() ret=7c34963e
0025:Ret  KERNEL32.GetLastError() retval=00000000 ret=7c34963e
0025:Call KERNEL32.MultiByteToWideChar(00000000,00000000,00bc5c8c " FSAA: ",00000007,0032efb8,00000400) ret=005fa99f
0025:Ret  KERNEL32.MultiByteToWideChar() retval=00000007 ret=005fa99f
0025:Call KERNEL32.GetLastError() ret=7c34963e
0025:Ret  KERNEL32.GetLastError() retval=00000000 ret=7c34963e
0025:Call KERNEL32.GlobalMemoryStatus(0032f7a4) ret=00a91039
0025:Ret  KERNEL32.GlobalMemoryStatus() retval=7fffffff ret=00a91039
0025:Call KERNEL32.MultiByteToWideChar(000004e4,00000000,37ff6d60 "0.599816",00000008,387faa40,0000000b) ret=00709142
0025:Ret  KERNEL32.MultiByteToWideChar() retval=00000008 ret=00709142
0025:Call KERNEL32.WideCharToMultiByte(000004e4,00000000,387fd0c8 L"set_quality",0000000b,3b7f4a70,00000020,00000000,00000000) ret=007090c8
0025:Ret  KERNEL32.WideCharToMultiByte() retval=0000000b ret=007090c8
0025:Call KERNEL32.WideCharToMultiByte(000004e4,00000000,387fd0c8 L"0.599816",00000008,38bfd6e0,0000001a,00000000,00000000) ret=007090c8
0025:Ret  KERNEL32.WideCharToMultiByte() retval=00000008 ret=007090c8
0025:Call KERNEL32.GetLastError() ret=7c34963e
0025:Ret  KERNEL32.GetLastError() retval=00000000 ret=7c34963e
... repeats above 2 lines ...
0025:Call KERNEL32.WideCharToMultiByte(000004e4,00000000,383fdff0 L"",00000000,37ff4b20,0000000a,00000000,00000000) ret=007090c8
0025:Ret  KERNEL32.WideCharToMultiByte() retval=00000000 ret=007090c8
0025:Call KERNEL32.VirtualQuery(00b7cb98,0032f2f8,0000001c) ret=7c34d435
0025:Ret  KERNEL32.VirtualQuery() retval=0000001c ret=7c34d435
0025:Call KERNEL32.InterlockedExchange(7c391358,00000001) ret=7c34d4b3
0025:Ret  KERNEL32.InterlockedExchange() retval=00000000 ret=7c34d4b3
0025:Call KERNEL32.InterlockedExchange(7c391358,00000000) ret=7c34d518
0025:Ret  KERNEL32.InterlockedExchange() retval=00000001 ret=7c34d518
0025:Call KERNEL32.GetLastError() ret=7c34963e
0025:Ret  KERNEL32.GetLastError() retval=00000057 ret=7c34963e
0025:Call KERNEL32.UnhandledExceptionFilter(0032f334) ret=7c34c456
wine: Unhandled page fault on read access to 0x00000088 at address 0xa4dce4 (thread 0025), starting debugger...

[dimesio]

An old post http://forum.winehq.org/viewtopic.php?t=11374 seems to indicate this may be a regression that was never resolved.

I gather you didn't actually read that thread; it was clearly pointed out that the crash being reported was in the poster's graphics driver and not a Wine bug.

Your crash is not in your graphics driver and has nothing to do with that poster's issue.

According to the game's AppDB entry, this game is affected by bug 3260.

[mogorva]

Have you installed the game in a clean wineprefix? Please upgrade to Wine 1.5.21 and try again. If the problem still exists post the full terminal output.
Blitzkrieg 2 Anthology starts fine here, tested with 1.5.18 and 1.5.21. What video card and driver are you using? I tested with a Nvidia gfx card and with the binary drivers.
The GOG.com version is DRM free, thus it is not affected by bug 3260

[willb]

I tried wine 1.5.21, both nvidia gfx and intel gfx PCs, also with clean wineprefix. Same problem.
I also tried registry VideoMemorySize=1024, glsl=disabled. Tried full screen and virtual desktop. Didn't solve it.

The terminal output:

Code: Select all

fixme:win:EnumDisplayDevicesW ((null),0,0x32f4f8,0x00000000), stub!
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
err:d3d:resource_init Out of adapter memory
fixme:d3d_texture:texture_init Failed to create surface 0x4a24bc58, hr 0x8876017c
fixme:d3d:query_init Unhandled query type 0x4.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
wine: Unhandled page fault on read access to 0x00000088 at address 0xa197f4 (thread 0025), starting debugger...
Unhandled exception: page fault on read access to 0x00000088 in 32-bit code (0x00a197f4).

[core]

willb, update Wine to 1.5.22 and try to install game in clean prefix with native directx.

[willb]

God, I feel so very stupid. After 1 and a half years later, I decide to tackle this one more time.

I upgrade to wine 1.7.19, then try to install native d3dx9_36.dll. In the process of installing d3dx9_36.dll, I came up with a question: since I run the game from the top game directory using "wine bin/Game.exe", I wondered if I should be installing dll in the game directory, or inside the bin subdirectory. By chance, I change to bin directory and run wine Game.exe. And it works perfectly!!!

And all this time I've been hacking my brain trying to find where the fault is! And how the hell would I have known that Windows applications work in mysterious ways: run from a subdirectory, and still have the nerve to access the parent directory. And why couldn't it just plainly say to run from bin directory instead of CRASHING! This is why I hated Windows so much.