http://bugs.winehq.org/show_bug.cgi?id=30815
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |http://www.labcenter.com/do | |wnload/prodemo_download.cfm CC| |dank@kegel.com Ever Confirmed|0 |1
--- Comment #3 from Dan Kegel dank@kegel.com 2012-05-31 23:06:03 CDT --- Reproducible with the free demo, 49c2d7644db31e8b4ce0c81fae738c13419675ce prodemo.exe
Here's +winsock,+relay of BIN\ISIS.EXE with wine-1.5.4 when turning on the "remote debug monitor" as the OP described:
0024:Call ws2_32.WSAStartup(00000002,0089f554) ret=004b8e4e trace:winsock:WSAStartup verReq=2 trace:winsock:WSAStartup succeeded 0024:Ret ws2_32.WSAStartup() retval=00000000 ret=004b8e4e 0024:Call ws2_32.socket(00000002,00000000,00000000) ret=004b8e6e trace:winsock:WS_socket af=2 type=0 protocol=0 trace:winsock:WSASocketA af=2 type=0 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=0 protocol=0 protocol_info=(nil) group=0 flags=0x1 fixme:winsock:convert_socktype_w2u unhandled Windows socket type 0 warn:winsock:WSASocketW failed! 0024:Ret ws2_32.socket() retval=ffffffff ret=004b8e6e
MSDN says "To preserve backward compatibility, the Ws2_32.dll treats the value of zero for either address family or socket type as a wildcard value."