"Guillem" <guillemvicens-nospam@clubgreenoasis.com> wrote in message
news:460252c7$1@newsgroups.borland.com...
> there is no socket error #0 in Windows.
WSAGetLastError() is returning 0. Obviously, it is getting called at
a time when the Indy code detects a problem with the socket, but the
OS is not reporting the actual error.
> The lowest value for a socket error is 6 and corresponds to
WSA_INVALID_HANDLE.
Indy doesn't use the WSA extensions for accessing sockets. It uses
the core socket API directly instead. In which case, the lowest error
code is WSABASEERR (10000).
> AFAICS in the IdStack code there is no way it could return a 0.
There is if that is what WSAGetLastError() is actually returing.
Gambit
