> I'm now testing TnCnx for my purposes. It works fairly well so far. > The only issue I have so far is that I#m receiving NUL characters at the > end of line. For example: > > ' Simplified orbitography parameters :'#$D#0#$D#$A' ND 021:23'... > > Is this an server issue or could it be related to ICS?
This is a server issue. Historically NUL characters are used for dumb rs232 terminals to avoid overflowing them (They where really slow for scrolling, erasing, and so on). > If I use the Demo for TnCnx it stops receiving at the end of this line > while the EmulVT Demo works properly. The problem in the TnCnx (like > it was in my software) is that Len is is longer than this line and > output ends at the NUL. Hyperterm works well here, but I can't see if > it receives the NUL character. > There is a test account at netdis.cls.fr. > username: EVERYONE > password: ARGOS > Please use it only for this verification (if you have the time to). You problem here is a Delphi problem. If you handle received data as a nul terminated string (PChar), then you don't see anything after the NUL character. If you handle the string as a pure Delphi string, the NUL byte is like any other characters. To be clear, when you have a PChar, nothing prevent you from accessing data after the NUL character, but most functions won't do that. You may consider writing a routine which remove the NUL characters before processing. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- 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
