Hello Frank, > its right, that have i trying, too. but this recognizes only normal > disconnect and fires an AccessViolation. ;<
As I have explained in at least 2 other replys, a disconnect is a packet sent to the socket. If no packet can be send because for example the network cable is pulled out, then no event can fire. Only when you try to send something you will have exception eror and after it OnClientDisconnect is fired with a winsock error. Maybe did I misundersteand the original question ? --- Rgds, Wilfried http://www.mestdagh.biz -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
