search for: protocol_info

Displaying 8 results from an estimated 8 matches for "protocol_info".

2009 Feb 09
2
Problem setting up a server on UDP port 59
...P. Under wine it fails, the log shows "Permission denied" for the WS_bind function. Has anyone else seen this? Does anyone know how to work around this? trace:winsock:WSAStartup succeeded trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0048 trace:winsock:WS_bind socket 0048, ptr 0x32fbec { family 2, address 127.0.0.1, port 0 }, length 16 trace:winsock:WS_listen socket 0048, backlo...
2005 Apr 06
0
Freelancer Gameserver - DirectPlay problem
...lMain 0x42ba0000 0x2 (nil) trace:winsock:DllMain 0x42ba0000 0x2 (nil) trace:winsock:DllMain 0x42ba0000 0x2 (nil) err:ole:CoInitializeEx Attempt to change threading model of this apartment from 0x2 to 0x0 trace:winsock:WS_socket af=2 type=2 protocol=0 trace:winsock:WSASocketA af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 017c trace:winsock:WS_bind socket 017c, ptr 0x43572bb8 { family 2, address 0.0.0.0, port 0 }, length 16 trace:winsock:WS_getsockname socket: 017c,...
2009 Feb 06
0
winsock errror for ioctl cmd 9800000c in wine 1.14
...XP, with wine I have a problem. Running with trace on gives the following output: trace:winsock:DllMain 0x7eba0000 0x2 (nil) trace:winsock:WSAStartup verReq=101 trace:winsock:WSAStartup succeeded trace:winsock:WS_socket af=2 type=2 protocol=0 trace:winsock:WSASocketA af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=2 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0070 trace:winsock:_remap_optname level=65535, optname=32 trace:winsock:WS_setsockopt socket: 0070, level 0xffff, name 0x20, ptr 0x7de44658, len 4...
2008 May 22
0
Socket timeout...
...gram Files/Internet Explorer> wine "C:\\Program Files\VTLS\Virtua\Virtua.exe" trace:winsock:DllMain 0x7dfb0000 0x1 (nil) trace:winsock:WSAStartup verReq=202 trace:winsock:WSAStartup succeeded trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 00d8 trace:winsock:WS_bind socket 00d8, ptr 0x98fa18 { family 2, address 0.0.0.0, port 0 }, length 16 trace:winsock:WS_getsockname socket: 00d8, ptr...
2005 Jan 08
1
Connection problems and weird WinSock warnings...
...RTEXBLEND (00000097) value : 00000000 ! [Then I connect] trace:winsock:WSAStartup verReq=101 trace:winsock:WSAStartup succeeded trace:winsock:WS_gethostbyname "droganor.no-ip.com" ret 0x40435c18 trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketA created 0148 trace:winsock:WS_ioctlsocket socket 0148, cmd 8004667e, ptr 0x408afabc trace:winsock:WS_connect socket 0148, ptr 0x64c0e0 { family 2, address 105.112.46.99, port 6900 }, length 16 trace:winsock:WS_select read (nil), write 0x408af...
2007 Dec 10
0
Fwd: Wine Problem SOLVED
...l:find_reg_tz_info Unable to open the time zones key trace:winsock:WS_getservbyname "autarquia_tcp", "tcp" ret 0x19d980 trace:winsock:WS_gethostbyname "cmplinux" ret 0x19d9b0 trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0140 trace:winsock:WS_bind socket 0140, ptr 0x34c36c { family 2, address 0.0.0.0, port 0 }, length 16 trace:winsock:WS_connect socket 0140, ptr 0x34c...
2002 Feb 27
3
winsock 16 BIT
Hi! In October I worked with a client-server (using winsock.dll) 16 bit aplication emulated in wine (Not using ODBC), it worked fine. This aplication needs to connect to a server using port ctsql 5557/tcp, this service is in my /etc/services. And wine made all realy fine (Version 20011108). With the release 20011226 (I think)started the problem. Something changed with winsock 16-bit. I've
2007 Dec 07
1
Wine Problem
...l:find_reg_tz_info Unable to open the time zones key trace:winsock:WS_getservbyname "autarquia_tcp", "tcp" ret 0x19d980 trace:winsock:WS_gethostbyname "cmplinux" ret 0x19d9b0 trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1 trace:winsock:WSASocketW created 0140 trace:winsock:WS_bind socket 0140, ptr 0x34c36c { family 2, address 0.0.0.0, port 0 }, length 16 trace:winsock:WS_connect socket 0140, ptr 0x34c...