http://bugs.winehq.org/show_bug.cgi?id=6086
--- Comment #65 from Stefan Dösinger stefandoesinger@gmx.at 2009-01-20 12:52:37 --- I disagree on a technical basis that it should be Wine's job to deal with that(and thus essentially clone the functionality of taskset).
Two points: 1) This is not a Wine-specific problem. There can be Linux apps that are broken in the same way too. As such Wine is the wrong place to deal with the problem 2) Wine leaves the thread scheduling to the Operating System. It deliberately doesn't care about where each thread runs, so Windows apps in Wine behave like normal Linux(MacOS, *BSD, ...) apps.
There's obviously a usability issue now. Wine is the wrong place to fix this, and distributions usually don't care(because they are Windows apps, and Linux apps with the same problem are rare, or open source and thus fixable).