http://bugs.winehq.org/show_bug.cgi?id=16130
--- Comment #3 from dideldum ulf@dedio.de 2008-11-20 15:10:28 --- Thanks for your fast answer!
I called it like:
WINEDEBUG=+loaddll wine Runes\ of\ Magic.exe
This starts first the launcher. In the launcher I clicked the "Start" button. Until line 834 of the log file it's launcher related. Then (I assume from line 851 onwards) it is related to the real client. I haven't found out how to start the client directly, either exe starts first the launcher. I guess there is a parent-child-process-check to avoid direct client start... Just my imagination...
I entered the login data in the client and pressed the enter button. The effect is seen in line 5623 of the log, here the socket communication with the server is opened (the SYN packets in the wireshark trace).
I attach the log (compressed with bzip2) after this post.
Hope this helps. If you need more traces, please tell me the channels. I cannot trace all channels at once, as this leads to many GB of log (and my Linux partition has only 7GB left).
If there is any other activity to help you, I offer, whatever I can.