Remy Lebeau (TeamB) schrieb:
> 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.
Any idea how to detect or even better solve the problem?
> 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).
I'm using the version deployed together with D7 (afaik 9.00.10). I know
that's an outdated version, but as it works for at least 3 years without
any problems I've no idea what might it cause to fail know, especially
only on some machines.
>> AFAICS in the IdStack code there is no way it could return a 0.
>
> There is if that is what WSAGetLastError() is actually returing.
Hm. But what migth cause it? Even wild guesses may help :-)
Stephan
--
Logik ist die Kunst, zuversichtlich in die Irre zu gehen.
Stephan Jaschke - EDV-Beratung und Softwareentwicklung
Mail: support@stj-software.de - ICQ: 361511624
