http://bugs.winehq.org/show_bug.cgi?id=3978
------- Additional Comments From Speeddymon@gmail.com 2006-10-04 12:22 ------- Just a little bit of insite into how the original loader works and why it crashes when it does, compared to the loader script.
The original loader and the script are functionally the same, in that they both allow you to get on battle.net using a patched exe. The differences are that the original is a binary .exe, while the script is done in bash, and that the original attaches itself to the diablo process, while the script does not.
What this means for you is that when you use the loader while playing single player, the loader does absolutely nothing, but when you click enter battle net, it picks up on that, and does some file renaming, so that when battlenet checks the file named Game.exe, it finds the original and get the version info from it. The script does this file renaming automagically, regardless of single player or battlenet, and so it does not have the same problems because it is not a part of the diablo ii process.
My guess is that something broke in interprocess communication, since the loader watches your clicks on the main screen, and so since the loader is attached to diablo ii, when the loader dies due to this breakage, so does diablo ii..
Now, if anyone who watches this bug was ever able to get onto battle.net while using the regular D2Loader.exe file under wine (doesn't matter what version of diablo ii, nor what version of wine), please post a note saying so here, as this is a regression, and could affect other apps. If it does turn out to be a regression, we need to figure out what patch caused this regression, and fix it.
Hope that info clears things up for you.