http://bugs.winehq.org/show_bug.cgi?id=9528
Summary: Battlefield 2142 breaks on startup with ReportEventW errors Product: Wine Version: 0.9.44. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: blocker Priority: P2 Component: wine-advapi32 AssignedTo: wine-bugs@winehq.org ReportedBy: ruesch@fresh-powder.de
Created an attachment (id=7896) --> (http://bugs.winehq.org/attachment.cgi?id=7896) The log file
When starting Battlefield 2142 the monitor first turns black, which is the normal start-up behaviour of the game, but then suddenly I'm back at the desktop with error messages and a 800x600 monitor resolution. I already tried to rename the movie files so they don't play at startup but that didn't change anything. Game version is 1.0.
The log is attached to this bug.
My PC configuration: - Kubuntu 7.04 (Feisty) - Linux dreamy-desktop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux - NVidia GeForce 7800GTX - AMD Athlon64 3800+
http://bugs.winehq.org/show_bug.cgi?id=9528
killertux killertux@suomi24.fi changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal OS/Version|other |Linux Platform|Other |PC
--- Comment #1 from killertux killertux@suomi24.fi 2007-08-30 16:37:41 --- well appdb says some but not all systems can run this you could try older Wine versions to check if this is regression.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #2 from Alex R. ruesch@fresh-powder.de 2007-08-31 03:30:54 --- Already tried many older versions but the problem is always the same. Therefore I don't think it's regression. Also not sure which part of wine causes the program to crash. Is it a DirectX- or a advapi32-problem?
http://bugs.winehq.org/show_bug.cgi?id=9528
Sebastian ghettopolak04@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ghettopolak04@hotmail.com
--- Comment #3 from Sebastian ghettopolak04@hotmail.com 2007-08-31 16:33:31 --- The game has been crashing like this for a long time from what I know from my testing. However, it won't crash if it's run in a Virtual Desktop.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #4 from Alex R. ruesch@fresh-powder.de 2007-09-07 03:34:53 --- That is right, I tried loading the game in Virtual Desktop mode (and experienced all the other bugs related to this game) but didn't play it. Why? Because playing a first-person shooter in a windowed-mode is just pain. Therefore I think, concerning this game it's a major bug.
http://bugs.winehq.org/show_bug.cgi?id=9528
Chris Spencer spencercw@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spencercw@googlemail.com
--- Comment #5 from Chris Spencer spencercw@googlemail.com 2007-10-06 11:26:10 --- This is a regression:
chris@chrispc ~/Software/wine/wine-git $ git bisect bad 216c3b0d0aee29728adcd8f0b7846563fca030fb is first bad commit commit 216c3b0d0aee29728adcd8f0b7846563fca030fb Author: Miko��aj Zalewski mikolaj@zalewski.pl Date: Mon Aug 13 10:55:08 2007 -0700
kernel: Allocate global memory with execute permission.
:040000 040000 7986f16fb6a4ee32a75679e1f60cc29c58883b39 3f0c684de9f8aba983eabbdf8a375503c064b96d M dlls
However, undoing these changes in the current git does not fix this bug. I have double checked that this commit originally introduced the bug. Not sure where to go from here...
http://bugs.winehq.org/show_bug.cgi?id=9528
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|advapi32 |kernel32
--- Comment #6 from James Hawkins truiken@gmail.com 2008-01-13 11:18:14 --- Not a bug in advapi32. Setting component to kernel32, assuming the regression test is correct.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #7 from Alex R. ruesch@fresh-powder.de 2008-03-14 17:22:01 --- I tested again in wine version 0.9.57, with NVIDIA driver 169.12 and Kubuntu 7.10. It's still the same. Fullscreen doesn't work.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #8 from Alex R. ruesch@fresh-powder.de 2008-06-12 04:25:18 --- With wine version 1.0 rc4 the game doesn't start up anymore, even with virtual desktop enabled. The error message is the same as if virtual desktop wasn't enabled. Can anyone check that? I'm using NVidia drivers from the manufacturer.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #9 from Austin English austinenglish@gmail.com 2008-12-11 10:28:24 --- Is this still an issue in current (1.1.10 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=9528
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #10 from Chris Spencer spencercw@googlemail.com 2008-12-11 13:58:37 --- (In reply to comment #9)
Is this still an issue in current (1.1.10 or newer) wine?
No.
Wine 1.1.10, NVIDIA GeForce 8800GT (180.06). Tested both normal and virtual desktop with BF2142 1.0 and 1.50, this issue is no longer present on my machine.
http://bugs.winehq.org/show_bug.cgi?id=9528
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #11 from Austin English austinenglish@gmail.com 2008-12-11 17:38:33 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=9528
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2008-12-20 09:03:01 --- Closing bugs fixed in 1.1.11.
http://bugs.winehq.org/show_bug.cgi?id=9528
--- Comment #13 from Alex R. ruesch@fresh-powder.de 2009-01-04 13:40:43 --- I tried playing the game in fullscreen with Wine 1.1.12 and NVIDIA beta drivers 180.17. Not working! Still the same errors err:eventlog:ReportEventW L"6" and err:eventlog:ReportEventW L"7". Maybe the problem is related to my graphic chip (GeForce 7800GTX)?