Displaying 6 results from an estimated 6 matches for "ws_closesocket".
Did you mean:
win_closesocket
2009 Feb 09
2
Problem setting up a server on UDP port 59
...gth 16
trace:winsock:DllMain 0x7ee60000 0x3 (nil)
trace:winsock:WS_select read 0x8210b0, write (nil), excp (nil) timeout
0x32fb9c
trace:winsock:__WSAFDIsSet (72,0x8210b0(1))
trace:winsock:WS_accept socket 0048
trace:winsock:WS_getpeername socket: 004c, ptr 0x32fbfc, len 00000010
trace:winsock:WS_closesocket socket 0048
trace:winsock:WS_select read 0x8210b0, write (nil), excp (nil) timeout
0x32fb6c
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)
gr...
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
2005 Apr 06
0
Freelancer Gameserver - DirectPlay problem
...ocketW 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, ptr 0x43572bb8, len 10
trace:winsock:WS_closesocket socket 017c
trace:winsock:DllMain 0x42ba0000 0x2 (nil)
trace:winsock:DllMain 0x42ba0000 0x3 (nil)
--------------------------------------------------------------------------------------------------------------
TimeFX
2009 Feb 06
0
winsock errror for ioctl cmd 9800000c in wine 1.14
...e:winsock:WS_bind socket 0070, ptr 0x7de446e0 { family 2, address
0.0.0.0, port 0 }, length 16
trace:winsock:WS_ioctlsocket socket 0070, cmd 9800000c, ptr 0x7de44674
warn:winsock:WS_ioctlsocket unknown WS_IOCTL cmd (9800000c)
warn:winsock:wsaErrno errno 22, (Invalid argument).
trace:winsock:WS_closesocket socket 0070
Has anyone had a similar problem, and (hopefully) found a solution?
Steve
-
This message is subject to Imagination Technologies' e-mail terms: http://www.imgtec.com/e-mail.htm
-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wineh...
2008 May 22
0
Socket timeout...
...gth 16
trace:winsock:WS_getsockname socket: 00d8, ptr 0x98fa08, len 10
trace:winsock:WS_connect socket 00d8, ptr 0x98fa50 { family 2, address 193.0.118.2, port 9999 }, length 16
trace:winsock:WS_shutdown socket 00d8, how 1 0
trace:winsock:WS2_register_async_shutdown s 216 type 2
trace:winsock:WS_closesocket socket 00d8
and i don't have any idee where is the problem.
2005 Jan 08
1
Connection problems and weird WinSock warnings...
...socket 0148, ptr 0x64c0e0 { family 2, address
105.112.46.99, port 6900 }, length 16
trace:winsock:WS_select read (nil), write 0x408af9a4, excp (nil) timeout
0x408afaa8
trace:winsock:WS_select read 0x408aee68, write (nil), excp (nil) timeout
0x408aef6c
[Same message repeated 953 times]
trace:winsock:WS_closesocket socket 0148
[Then a message comes "Unable to connect to the server" and I close the
client]
trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\Gravity\\RO\\Mp3dec.asi" : native
trace:loaddll:MODULE_FlushModrefs Unloaded module L"C:\\Program Files\\Gravit...