[Bug 3217] Regression:Can't run Balls of Steel. Refresh rate monitor not found

Wine Bugs wine-bugs at winehq.org
Fri Oct 21 15:03:32 CDT 2005


http://bugs.winehq.org/show_bug.cgi?id=3217





------- Additional Comments From saulius.krasuckas at elst.vtu.lt  2005-21-10 15:03 -------
> This way i could actually start playing without the "refresh rate" error. Seems
> as if you somehow you have to slow down the game a bit to avoid the error. 

Hehe, I experience very similar effect on one old 16-bit application.  AFAIR,
this effect is called a "race conditions" or "racing".  When application shows
message box about a refresh rate error, you could launch winedbg, select a
process (info proc), attach to it (attach 0xB , for example) and to get
backtraces of all its threads (bt all).  That may bring more information to you.

But if your app hangs and debugger isn't able to attach to it (this is the case
for me) then the only way to find a cause of this is to get two different logs,
'+all' versus '+relay,+all' and to try diffing them (diff -u), I think.  This
would require gigabytes of free diskspace, I am afraid.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the wine-bugs mailing list