http://bugs.winehq.org/show_bug.cgi?id=14348
--- Comment #18 from Olivier Diotte olivier@diotte.ca 2011-02-03 03:39:49 CST --- (In reply to comment #17)
I made some more tests: first, Diablo still works even if I let it run on multiple cores as it pleases: I had first compiled Wine in a 32 bits environment (namely, by setting the path to point to 32 bits versions of gcc and al. before the 64 bits versions). Now that I don't specify anything, it seems to be less prone to crashing.
Correction: the game still crashes no matter what I do.
The problem seems to lie into the wineserver (or the system calls the former makes) which the game doesn't seem to be very fond of.
I have been succesfully able to play (and click NPCs frenetically) without crashing by using the following trick:
first, su root: su -
then start a chroot jail at the current root (limiting the chroot to a single processor): taskset -p 1 chroot /
Now, su back to the non-root user (vhann in my case): su - vhann
Now launch 'wine Diablo\ II.exe' from within that shell and it'll work flawlessly.