Why is wine using both of my cpu threads?

I was installing a game on my netbook with wine and it seems that it's using both of the cpu threads.

Did wine fix the multi-thread bug?

EDIT:

Sorry to get anyones hopes up, but I did later find that I was misreading some data. When I saw it say 100% cpu usage I thought it meant both threads, but I later found out that it only applied to one thread.

Myth 9: "Wine is for Linux only"

This is just plain incorrect. OK, as of now Wine does not run on many platforms: just Linux, MacOS X, FreeBSD and Solaris. Still, this is not 'Linux only'.

It is true too that most developers work on Linux. So you run a higher risk of having a specific release of Wine not compile/work on a non-Linux platform. But this is usually fixed in the next release. Also Wine has been known to be missing some important functionality on non-Linux, e.g. good multi-threading. As far as I know these problems are now solved and Wine works just as well on any of the three platforms mentioned above.

There also is a Win32 compatibility project for OS/2 (Odin), which makes use of Wine code.

Originally Posted by jefro Myth 9: "Wine is for Linux only" This is just plain incorrect. OK, as of now Wine does not run on many platforms: just Linux, MacOS X, FreeBSD and Solaris. Still, this is not 'Linux only'. It is true too that most developers work on Linux. So you run a higher risk of having a specific release of Wine not compile/work on a non-Linux platform. But this is usually fixed in the next release. Also Wine has been known to be missing some important functionality on non-Linux, e.g. good multi-threading. As far as I know these problems are now solved and Wine works just as well on any of the three platforms mentioned above. There also is a Win32 compatibility project for OS/2 (Odin), which makes use of Wine code.

I really don't see a need for this.