Hello:
It seems like the connection was dropped unexpectedly by the other
side. Socket operation on non-socket means that a WinSock call was sent on a
closed socket or invalid handle.
dZ.
On Apr 16, 2010, at 03:48, Anton Sviridov wrote:
*something wrong with my previous
Anton Sviridov wrote:
wilfried, dZ, the strangest thing is that socket is created and
connected directly before the bug. Here is what happens next:
Can you tell what is being called exactly at the moment the error
occurs? Try adding the ICS source directory to your Library Path and
setting