http://bugs.winehq.org/show_bug.cgi?id=9576
Summary: Nfs 4 (high stakes) crashes using glidewrapper as suggested Product: Wine Version: 0.9.44. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-misc AssignedTo: wine-bugs@winehq.org ReportedBy: kristjan.ugrin@gmail.com
Created an attachment (id=7950) --> (http://bugs.winehq.org/attachment.cgi?id=7950) Log
Need for Speed 4 High Stakes Version - 4.50 crashes on newest wine (0.9.44), if using "One thread for both policy" in glidewrapper configuration. Setting to classic works, but then mouse pointer is stuck and game is not usable.
http://bugs.winehq.org/show_bug.cgi?id=9576
Gregor Münch greg87@online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |greg87@online.de
--- Comment #1 from Gregor Münch greg87@online.de 2007-09-03 15:19:52 --- Well glidewrapper makes strange things with threading. Because of that, things can work for user A and fail for user B, it just depends on the configuration. This bug is possibly invalid(besides you can proof that this works in windows for you).
Could you please tell me what your hardware specs are? I need graphic card with driver and the CPU.
http://bugs.winehq.org/show_bug.cgi?id=9576
--- Comment #2 from kriko kristjan.ugrin@gmail.com 2007-09-03 15:32:30 --- I think I screwed up something it doesn't work even with wine 0.9.43 anymore. I always used same glidewrapper settings as suggested, my hw specs:
Athlon 64 2800+ (opensuse 10.2 - 32bit) Geforce 7600GT (100.14.11) 1.5GB Ram
It works in windows with glidewrapper. Last time it was working I was playing a knockout. After that (software was updated, including wine) I wasn't able to start it anymore. Reinstall didn't help, though I installed in different manner than before (guide was updated).
http://bugs.winehq.org/show_bug.cgi?id=9576
kriko kristjan.ugrin@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #3 from kriko kristjan.ugrin@gmail.com 2007-09-03 17:48:54 --- I would like to inform you that it was because of kernel. When I updated my system, I recompiled kernel with new cfs. On the current one 2.6.22-ck1 game is working, but with 2.6.22.5-cfs It doesn't. As far as I know I didn't change anything else in config compared to current kernel (2.6.22-ck1). What could cause those memory could not be read issues?
http://bugs.winehq.org/show_bug.cgi?id=9576
--- Comment #4 from Gregor Münch greg87@online.de 2007-09-03 20:00:05 --- Very much thx to you for figuring that out.
The difference between these to kernels are the schedulers. Where ck uses rsdl (I think) the newer one uses cfs.
This could make indeed a difference.
http://bugs.winehq.org/show_bug.cgi?id=9576
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Dan Kegel dank@kegel.com 2008-01-28 05:32:51 --- Closing all RESOLVED INVALID bugs that haven't changed in over three months.