Re: [twsocket] OnClientDisconnect on Linux

Hi Kris, Thank you for your reply. The code is written using Borland C++ and I don't think this will solve my problem. Thank you anyway » » Juan Carlos Seguí » » Kris Leech escribió: Juan Carlos - CAE

[twsocket] Accept generate an AV when running on W2K3 SP1

A user reported to me that winsock.accept generate an access violation at address 7C8224B2 in ntdll.dll when is program runs on a w2K3 SP1 computer, and only one such computer. He found that changing the lines: FSelectEvent := FD_READ or FD_WRITE or FD_ACCEPT or

Re: [twsocket] Accept generate an AV when running on W2K3 SP1

A user reported to me that winsock.accept generate an access violation at address 7C8224B2 in ntdll.dll when is program runs on a w2K3 SP1 computer Assuming this function is used to accept connections in Wsocket, it's certainly not causing any problem here in W2K3 SP1. I've been using the

Re: [twsocket] Accept generate an AV when running on W2K3 SP1

Here in my Windows XP x64 build 2003, the current code works fine. Regards, SZ On 9/27/06, Francois PIETTE [EMAIL PROTECTED] wrote: A user reported to me that winsock.accept generate an access violation at address 7C8224B2 in ntdll.dll when is program runs on a w2K3 SP1 computer, and only

[twsocket] How can I know that my client is connected?

I have a server and some number of clients any of which may or may not be present. If the server is not available then the functionality of the server is not available but the clients have functionality of their own. When the sever starts it opens a listening socket...