[Bug 17258] New: M.A.X.2 : error "Screen init failed" when starting the game

Summary: M.A.X.2 : error "Screen init failed" when starting the game Product: Wine Version: 1.1.14 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jazzedupj0sh@gmail.com

Created an attachment (id=19245) --> (http://bugs.winehq.org/attachment.cgi?id=19245) Game does not start, instead shows this error

Installation works fine. This is a game meant for Windows 98. Not sure which version of Directx it uses.

The game does not start, instead I get an error. The screenshot of the error is attached.

-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

Show replies by date

wine-bugs＠winehq.org

5 Feb 5 Feb

12:12 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #1 from Austin English austinenglish@gmail.com 2009-02-04 18:12:56 --- Terminal output?

wine-bugs＠winehq.org

12:14 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #2 from Joshua jazzedupj0sh@gmail.com 2009-02-05 06:13:59 --- Created an attachment (id=19251) --> (http://bugs.winehq.org/attachment.cgi?id=19251) WINE output when the game is started

Game does not start, the output is an error dialog box with the message "Screen Init Failed"

wine-bugs＠winehq.org

6 Feb 6 Feb

7:20 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

Joshua jazzedupj0sh@gmail.com changed:

wine-bugs＠winehq.org

5 Aug 5 Aug

3:24 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #3 from Austin English austinenglish@gmail.com 2009-08-05 10:24:14 --- Is this still an issue in current (1.1.26 or newer) wine?

wine-bugs＠winehq.org

4 Feb 4 Feb

3:27 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

devent@deventm.org changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |devent@deventm.org

--- Comment #4 from devent@deventm.org 2010-02-03 21:27:06 --- (In reply to comment #3)

Is this still an issue in current (1.1.26 or newer) wine?

Yes, just tested it in wine 1.1.37.

wine-bugs＠winehq.org

29 Aug 29 Aug

10:43 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

http://www.cdaccess.com/html/pc/max2.htm

volkerobhof@web.de changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |volkerobhof@web.de

--- Comment #5 from volkerobhof@web.de 2010-08-29 05:43:56 CDT --- I tested it with wine 1.3.0 stable release. Here it doesn't start, too. The installation works fine.

But I found some addition system requirements for this game.

Requirements:

IBM or 100% compatible PC Pentium 133MHz (P200 recommended), Windows 95 or above, DirectX 5.0, 16MB RAM (32MB recommended), approximately 80MB hard disk space, 2x CD-ROM drive (4x recommended), DirectX certified sound card and 1MB DirectX certified video card, 100% Microsoft compatible mouse.

Tested OK on Windows XP. To install run SETUP.EXE from the CD-ROM and DO NOT install DirectX 5.0.

The original game can not be installed and startet under windows XP so you have to switch to 98 or ME.

But I get the same screen error dialog "Screen Init Failed". I have even started it from shell but there not error output is displayed.

It's a really strange bug.

wine-bugs＠winehq.org

18 Jul 18 Jul

10:06 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

Bruno Jesus 00cpxxx@gmail.com changed:

--- Comment #6 from Bruno Jesus 00cpxxx@gmail.com 2012-07-18 17:06:59 CDT --- Confirming in wine 1.5.9. No console output.

wine-bugs＠winehq.org

30 Dec 30 Dec

8:07 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

Martin Fontaigne martinrs@softhome.net changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |martinrs@softhome.net

--- Comment #7 from Martin Fontaigne martinrs@softhome.net 2012-12-30 14:07:55 CST --- It seems the problem is related to version checking of ddraw.dll, dinput.dll, and dsound.dll. Running wine with WINEDEBUG=+relay shows the following snippet of log:

0025:Call version.GetFileVersionInfoA(0032f8e8 "c:\windows\system32\ddraw.dll",00000000,000006e4,0075e9f8) ret=0046a7ee ... 0025:Ret version.GetFileVersionInfoA() retval=00000001 ret=0046a7ee 0025:Call version.VerQueryValueA(0075e9f8,005938ac "\",0032f7cc,0032f7bc) ret=0046a807 ... 0025:Call user32.MessageBoxA(00000000,005942f4 "\nScreen Init failed.\n\n",00000000,00000010) ret=004b3118

wine-bugs＠winehq.org

9 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #8 from Martin Fontaigne martinrs@softhome.net 2012-12-30 15:00:00 CST --- (In reply to comment #7)

It seems the problem is related to version checking of ddraw.dll, dinput.dll, and dsound.dll.

It looks like wine ddraw.dll and others have image version 0.0 as confirmed using pev (sourceforge.net) while the original ddraw.dll has 5.x, and even wine source ddraw/version.rc shows 5.3, so maybe VerQueryValA() is not returning the right version number in wine?

wine-bugs＠winehq.org

28 Jul 28 Jul

3:39 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #9 from volkerobhof@web.de 2013-07-28 10:39:01 CDT --- this bug still exists in Wine 1.6 Release version. But here I don't get any bug report or command line output.

wine-bugs＠winehq.org

29 Jul 29 Jul

11:32 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #10 from volkerobhof@web.de 2013-07-29 06:32:24 CDT --- In AppDB there is a fix how you can start the game.

"It would have been garbage without the patch, but seems to work without problems with a single byte change.

To patch, use a hex editor like okteta, open max2.exe, and change byte 05 to 00 at offset 0x69D2F."

It's from: http://appdb.winehq.org/objectManager.php?sClass=version&iId=26046

It also works with original version of M.A.X. 2.

wine-bugs＠winehq.org

1:04 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #11 from Bruno Jesus 00cpxxx@gmail.com 2013-07-29 08:04:50 CDT --- Please attach a +ver log.

wine-bugs＠winehq.org

1:36 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #12 from volkerobhof@web.de 2013-07-29 08:36:13 CDT --- Created attachment 45441 --> http://bugs.winehq.org/attachment.cgi?id=45441 M.A.X. 2 +all and +relay trace. It's about 160 MB.

wine-bugs＠winehq.org

1:36 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #13 from volkerobhof@web.de 2013-07-29 08:36:58 CDT --- Comment on attachment 45441 --> http://bugs.winehq.org/attachment.cgi?id=45441 M.A.X. 2 +all and +relay trace. It's about 160 MB.

Sorry it's only +relay trace

wine-bugs＠winehq.org

1:45 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #14 from volkerobhof@web.de 2013-07-29 08:45:39 CDT --- Created attachment 45442 --> http://bugs.winehq.org/attachment.cgi?id=45442 M.A.X. 2 +all trace. Part 1/3

wine-bugs＠winehq.org

1:46 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #15 from volkerobhof@web.de 2013-07-29 08:46:03 CDT --- Created attachment 45443 --> http://bugs.winehq.org/attachment.cgi?id=45443 M.A.X. 2 +all trace. Part 21/3

wine-bugs＠winehq.org

1:46 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #16 from volkerobhof@web.de 2013-07-29 08:46:26 CDT --- Created attachment 45444 --> http://bugs.winehq.org/attachment.cgi?id=45444 M.A.X. 2 +all trace. Part 3/3

wine-bugs＠winehq.org

2:08 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #17 from volkerobhof@web.de 2013-07-29 09:08:32 CDT --- Created attachment 45445 --> http://bugs.winehq.org/attachment.cgi?id=45445 M.A.X. 2 +ver trace.

wine-bugs＠winehq.org

2:17 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #18 from Bruno Jesus 00cpxxx@gmail.com 2013-07-29 09:17:10 CDT ---

wine: cannot find L"C:\windows\system32\max2.exe"

I guess you run from the wrong directory. Also, please try in a clean prefix.

wine-bugs＠winehq.org

2:45 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #19 from volkerobhof@web.de 2013-07-29 09:45:39 CDT --- Created attachment 45446 --> http://bugs.winehq.org/attachment.cgi?id=45446 +ver.log trace

Ok, I started from "C:/Program Files/Interplay/MAX2/max2.exe".

wine-bugs＠winehq.org

3:31 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #20 from volkerobhof@web.de 2013-07-29 10:31:29 CDT --- Created attachment 45447 --> http://bugs.winehq.org/attachment.cgi?id=45447 +ver.log trace

Ok, some additional information.

It only starts solid if I run it with the following command:

WINEDEBUG=+ver env WINEPREFIX="/home/volker/.wine" wine C:\windows\command\start.exe /Unix /home/volker/.wine/dosdevices/c:/users/volker/Start\ Menu/Programs/Interplay/MAX2.lnk &> /home/volker/Arbeitsfläche/ver.log

wine-bugs＠winehq.org

1 Dec 1 Dec

4:02 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

roger@mailinator.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |roger@mailinator.com

--- Comment #21 from roger@mailinator.com --- I just found this from winehq appdatabase

"Additional Comments

It would have been garbage without the patch, but seems to work without problems with a single byte change.

To patch, use a hex editor like bless, open max2.exe, and change byte 0x05 to 0x00 at offset 0x69D2F."

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

8:31 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #22 from volkerobhof@web.de --- That's right. I can confirm this and it works. Few months ago I played M.A.X with modified max2.exe file.

But the question is, what 0x05 stands for?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

9 Oct 9 Oct

11:25 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

winetest@luukku.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com

--- Comment #23 from winetest@luukku.com --- (In reply to Martin Fontaigne from comment #8)

(In reply to comment #7)

...
It seems the problem is related to version checking of ddraw.dll, dinput.dll, and dsound.dll.

It looks like wine ddraw.dll and others have image version 0.0 as confirmed using pev (sourceforge.net) while the original ddraw.dll has 5.x, and even wine source ddraw/version.rc shows 5.3, so maybe VerQueryValA() is not returning the right version number in wine?

Could someone somehow confirm this? It feels like the hex patch is fixing this issue.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

11:27 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #24 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to winetest from comment #23)

Could someone somehow confirm this? It feels like the hex patch is fixing this issue.

Still in 1.9.20.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

11:43 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #25 from winetest@luukku.com --- I meant the analyze that ddraw represents certain version that wine has 0 and therefore it wont work.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

11 Oct 11 Oct

1:24 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

Christian Costa titan.costa@gmail.com changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |titan.costa@gmail.com

--- Comment #26 from Christian Costa titan.costa@gmail.com --- I get the same message and editing the exe works. MAX 2 requires DX5 so that's why it check the version against the value 5. It checks 3 libs whose product numbers are: - dsound 5.3.xxx - ddraw 5.3.xxx - dinput 5.1.xxx Unfortunaly the game checks the minor number and does not care about the major one. It gets the version number by reading 16-bit data at a particular address. When I read 32-bit with the debugger I get 0x00050001 or 0x00050003 which means the major is after the minor in memory which makes think they are inverted.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

8:52 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #27 from Christian Costa titan.costa@gmail.com --- Created attachment 55861 --> https://bugs.winehq.org/attachment.cgi?id=55861 hack

The hack makes the game work.

Note the it seems the 16-bit values order is correct as native and builtin resources have for instance version number 1.2.3.4 stored as 02 00 01 00 04 00 03 00.

So the game wants DX5 and check the minor is >= 5 for all 3 dlls.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

10:14 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #28 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Christian Costa from comment #27)

Created attachment 55861 [details] hack

The hack makes the game work.

Note the it seems the 16-bit values order is correct as native and builtin resources have for instance version number 1.2.3.4 stored as 02 00 01 00 04 00 03 00.

So the game wants DX5 and check the minor is >= 5 for all 3 dlls.

It would probably not even be a hack if it consistently updated the version to some value used by newer MS DLLs.

For reference, I checked ddraw.dll from a not-up-to-date Win10 installation and the product version is 10.0.10586.0, so IF the game works there, either the higher major version is enough or Windows has some compatibility shim or similar.

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

30 Oct 30 Oct

4:01 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

--- Comment #29 from winetest@luukku.com --- I just installed an started aida32 for testing purpose how well it works with wine. There is directx section and it shows dates and versions of dx files.

ddrawex.dll is empty but ddraw.dll has value 5.0.3.01.0904

These has emtpy value too.

dpnsvr.dll dpwsockx.dll kuser.dll qedit.dll

Does this help fixing this bug?

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

wine-bugs＠winehq.org

8 Jul 8 Jul

7:26 a.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game

joaopa jeremielapuree@yahoo.fr changed:

What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr

--- Comment #30 from joaopa jeremielapuree@yahoo.fr --- Nothing to do to fix this bug? That looks easy to fix though

-- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

WineHQ Bugzilla

23 Sep 23 Sep

8:08 p.m.

New subject: [Bug 17258] M.A.X.2 : error "Screen init failed" when starting the game