[Bug 6377] Diablo II deadlocks when accessing battle.net
http://bugs.winehq.org/show_bug.cgi?id=6377 jand03(a)space.aau.dk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE | ------- Additional Comments From jand03(a)space.aau.dk 2006-16-10 02:02 ------- Looked into it. From the faq on a loader page, it indicates that the error message does not only come from the loader, but general unhandled errors in diablo 2 "Q. I get 'Hey guys we got a big error here :('. A. [...]This error comes from the very top level of the structured exception handler, meaning ANYTHING that causes a crash in Diablo II (even D2 itself) will show this message. As such, it's impossible to really figure out what causes it. Usually though you will find a crash log (D2XXXXXXX.txt) in your Diablo II directory, go to the end of the file and copy all the debug information and maybe post it on some forum to see if anyone is able to make sense of it. [...]" albatros(a)helium:~/.wine/drive_c/Program Files/Diablo II$ strings Diablo\ II.exe | grep error We got a big error here :( I'll look further into if it is a configuration problem -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
participants (1)
-
Wine Bugs