search for: ws_connect

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

...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 0x34c3c4 { family 2, address 192.168.20.40, port 1526 }, length 72 Wine failed with return code 1 I dont get anymore output Can anyone help -- Sem Mais Assunto Pedro Miguel Nunes Ferreira Telf: +351 917427847 -------------- next part -------------- An HTML attachment was scrubbe...

...7ee60000 0x2 (nil) 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 0054 trace:winsock:WS_connect socket 0054, ptr 0x7e85169c { family 2, address 127.0.0.1, port 56208 }, length 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:wi...

...anor.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 0x408af9a4, excp (nil) timeout 0x408afaa8 trace:winsock:WS_select read 0x408aee68, write (nil), excp (nil) timeout 0x408aef6c [Same message repeated 953 times] trace:winsock...

...k: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 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.

...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 0x34c3c4 { family 2, address 192.168.20.40, port 1526 }, length 72 Wine failed with return code 1 I dont get anymore output Can anyone help -- Sem Mais Assunto Pedro Miguel Nunes Ferreira Telf: +351 917427847 -- A Fonte da Pra?a do Geraldo tem uma Coroa A Fonte das Portas de...