Arno Garrels wrote: > Paul wrote: >> No, it's specific : on slower PC's <2Ghz. >> All were XP SP2 > > I'm able to confirm, no error on my development box XP Pro SP 3, > however error on an old Athlon box, XP Home SP 3. > > Using Wireshark gives the following result: > 1 0.000000 192.168.178.20 62.213.206.217 TCP > [SYN] Seq=0 Win=65535 > Len=0 MSS=1452 2 0.051336 62.213.206.217 192.168.178.20 TCP > [SYN, > ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1452 3 0.051376 192.168.178.20 > 62.213.206.217 TCP > [ACK] Seq=1 Ack=1 Win=65535 Len=0 4 0.164614 > 192.168.178.20 62.213.206.217 TCP > [RST, ACK] Seq=1 Ack=1 Win=0 > Len=0
Sorry folks, ** false alarm **, I forgot to copy the certificate file, the demo eats any exception. Paul, you should drop a TIcsLogger on the form of your demo to get at least some useful information from your testers. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
