The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results (selected in 'Test Results' table below)
What works
Installation
What does not
Cannot execution
What was not tested
another instances for not pass setup
Additional Comments
The program crashes with error message "Internal errors: invalid parameter received"
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Anything new?
by Sabun on Friday April 12th 2013, 11:34
Last wine version I tried was 1.5.25, and it still crashes as soon as the game starts. I only have the Steam version. I even tried bypassing the launcher and just running the dxd9 exe of the game. No dice.
My system specs:
CPU - AMD Phenom II 965 3.4GHz
GPU - Nvidia GTX 680 2GB GDDR5
RAM - 8GB DDR3 1333MHz
Anyone know what this game might depend on? I'll give it a shot in CrossOver 12.1, but it'll probably be the same.
The game crashes on start
by Alexey on Thursday February 23rd 2012, 2:35
The game crashes on start with an error:
wine: Unhandled page fault on read access to 0x00000000 at address 0x49bcf9 (thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0049bcf9).
I installed it with help of PlayOnLinux (there is no script, i just used it to create wineprefix and install some components). I installed vcrun2005, dxfullsetup, gdiplus and mfc42. Also I choosed gdi as Direct Draw Renderer. There is no result.
Still Crashed
by Galym Kerimbekov on Wednesday February 1st 2012, 2:29
user@tux /media/ST3/Games/Saints Row - The Third $ wine '/media/ST3/Games/Saints Row - The Third/saintsrowthethird.exe'
Setting breakpad minidump AppID = 55230
Steam_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no]
ERROR:
Could Not Find D3DKMTEscape in gdi32.dll
Could Not Find D3DKMTOpenAdapterFromHdc in gdi32.dll
wine: Unhandled page fault on read access to 0x00000000 at address 0x49bcf9 (thread 0009), starting debugger...
