Hello Markus,
> I haven't yet a failure message or so
if a socket can't connect then onsessionconnect is fired with an error
code. then onsessionclose is fired, eventually also with an error code.
I assume you keep these errorcodes in an errorlog file or so. you have
to give this so we can see wh
Markus Humm wrote:
> Hello,
>
> I'm wrining a 2-part application where both parts use a TWSocket to
> communicate with each other.
>
> The one part is started and creates a listining socket on localhost's
> port 8999 where the other will connect to.
>
> Now on some PCs (Windows 2000 at least in
Hello,
I'm wrining a 2-part application where both parts use a TWSocket to
communicate with each other.
The one part is started and creates a listining socket on localhost's
port 8999 where the other will connect to.
Now on some PCs (Windows 2000 at least in one case) this fails. The user
has on
