http://bugs.winehq.org/show_bug.cgi?id=13388
Summary: Final Fantasy 7 crashes upon start Product: Wine Version: 1.0-rc2 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs@winehq.org ReportedBy: nethaven@hotmail.com
Created an attachment (id=13297) --> (http://bugs.winehq.org/attachment.cgi?id=13297) FF7 crash
When starting the program, a blank screen pops up, then immediately closes. It appears (to me of little programming knowledge) to be related to Direct3D, yet placing the game in "software render" mode still results in a crash. In either case, the display is using DirectDraw.
http://bugs.winehq.org/show_bug.cgi?id=13388
Luke nethaven@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|other |Linux Platform|Other |PC-x86-64
http://bugs.winehq.org/show_bug.cgi?id=13388
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|directx-ddraw |ntoskrnl Ever Confirmed|0 |1 Summary|Final Fantasy 7 crashes upon|Final Fantasy 7 crashes upon |start |start (needs | |KeInitializeMutex)
--- Comment #1 from Lei Zhang thestig@google.com 2008-05-27 11:44:50 --- No, it's not direct draw related. There's a function that's not implemented - KeInitializeMutex.
http://bugs.winehq.org/show_bug.cgi?id=13388
--- Comment #2 from Luke nethaven@hotmail.com 2008-05-27 16:37:37 --- Ok thanks for clearing that up for me. I was just confused by the output at the end: Only one Direct3D device per DirectDraw object supported
I've seen this here and there, but again, my programming knowledge is limited, so if it means more than the words imply, I'm unsure.
http://bugs.winehq.org/show_bug.cgi?id=13388
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #3 from André H. nerv@dawncrow.de 2008-08-30 05:47:56 --- Same Problems in Phase5 5.6xx installing, but the right way is in sight: We possible can use some Functions of ReactOS, the ReactOS-Kernel is very improved in this way. So some Pro could port the KeInitialize* Functions from ReactOS to Wine. Its hard work, but would be good for many Apps.
http://bugs.winehq.org/show_bug.cgi?id=13388
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #4 from Anastasius Focht focht@gmx.net 2008-08-30 08:26:26 --- Hello,
--- quote --- Same Problems in Phase5 5.6xx installing, --- quote ---
No, the bug reporter used a tainted WINEPREFIX. The ntoskrnl messages are misleading and not the cause of problem (which is Direct3D). That "elbycdio.sys" most likely comes from earlier CloneCD/whatever malware installation which is not supported.
You probably operate on a broken WINEPREFIX too. Please install apps using clean WINEPREFIX (no apps installed) otherwise the bug report would be automatically invalid.
Your problem is a bug in msiexec program arguments parsing which prevents the Phase5 installer from being successfully run. Although a valid bug it's a complete different issue than this bug is about.
Open a new bug report for your app and attach the trace output from following command there (using a new WINEPREFIX):
WINEDEBUG=+msiexec,+process wine ./phase562install.exe >log.txt 2>&1
This should be enough to recognize and fix the problem. Hint: current argument counting incorrectly skips first argument when CreateProcessA/W( "C:\windows\system32\msiexec.exe", "<arg1> <arg2>", .. ) flavour is used.
Regards
http://bugs.winehq.org/show_bug.cgi?id=13388
--- Comment #5 from Austin English austinenglish@gmail.com 2008-08-31 00:12:53 --- (In reply to comment #3)
Same Problems in Phase5 5.6xx installing, but the right way is in sight: We possible can use some Functions of ReactOS, the ReactOS-Kernel is very improved in this way. So some Pro could port the KeInitialize* Functions from ReactOS to Wine. Its hard work, but would be good for many Apps.
ReactOS code is not accepted in Wine.
http://bugs.winehq.org/show_bug.cgi?id=13388
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Component|ntoskrnl |-unknown Resolution| |INVALID
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-02 03:51:46 --- Please retry with empty ~/.wine. Feel free to reopen this bug if the problem still persists after that.
http://bugs.winehq.org/show_bug.cgi?id=13388
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-09-02 03:51:57 --- Closing.
-
wine-bugs＠winehq.org