http://bugs.winehq.org/show_bug.cgi?id=8958
jkohen@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |
------- Additional Comments From jkohen@users.sourceforge.net 2007-14-07 15:01 ------- Would you care to comment why you closed this bug without giving any additional information?
I'm reopening it. Since you didn't deny seeing the 100% CPU usage, we have to assume that Wine has a bug or is abusing the scheduler in a way that works in some systems, but not in others. Since this works in low-end Windows computers, I don't think you want to argue that this behavior is incorrect. My computer is definitely not low-end and the game itself runs perfectly. The Linux version of the AGS interpreter doesn't suffer this probles; unfortunately it cannot be used to run games that rely on external DLLs or video codecs.
If I can supply for information to track the high CPU usage, let me know and I'll be glad to help. I'm afraid that AGS source code is not available, but I might be able to generate a simpler "game" that just contains the basic load/save screen and not much else, if that would help.
By the way, your kernel is clearly not from pristine kernel.org sources and you didn't specify what distribution it comes from or what patches it includes. Not that it matters, unless Wine's policy is to rely on scheduler modifications that upstream kernel doesn't want to merge.