X-country training flight

Well, I thought that was a CNTRL-J, but I haven't tried that.


"zatatime" wrote in message
...
On Thu, 9 Dec 2004 17:45:59 -0600, "Stan Prevost"
wrote:


"zatatime" wrote in message
. ..
On 9 Dec 2004 11:49:17 -0500, (Roy Smith) wrote:

Yeah, that's what happens when you use the telnet client that comes
with windows. It's not negotiating the end-of-line processing
correctly with the telnet server at the other end.


Try using CNTRL - M instead of enter. This will only send a CR, no
NL.

HTH.
z

I had already tried that, same response.

Stan

How about CNTRL-L. That's just a linefeed, no CR.

HTH.
z

Stan Prevost wrote:

Well, I thought that was a CNTRL-J, but I haven't tried that.


"zatatime" wrote in message
...

On Thu, 9 Dec 2004 17:45:59 -0600, "Stan Prevost"
wrote:


"zatatime" wrote in message
...

On 9 Dec 2004 11:49:17 -0500, (Roy Smith) wrote:


Yeah, that's what happens when you use the telnet client that comes
with windows. It's not negotiating the end-of-line processing
correctly with the telnet server at the other end.


Try using CNTRL - M instead of enter. This will only send a CR, no
NL.

HTH.
z

I had already tried that, same response.

Stan


How about CNTRL-L. That's just a linefeed, no CR.

HTH.
z




You are right. Control-L is a Form Feed (014 octal).

On Fri, 10 Dec 2004 02:57:21 GMT, "William W. Plummer"
wrote:

You are right. Control-L is a Form Feed (014 octal).


So CNTRL-J is line feed and CNTRL-L is form feed?

I used to know all of these, and be able to convert to ascii code.
Getting old, and all this GUI crap doesn't help my memory at all!

Thanks.
z

(A perfect example of a thread that gets hard to read without
following posting standards.)

zatatime wrote:
On Fri, 10 Dec 2004 02:57:21 GMT, "William W. Plummer"
wrote:


You are right. Control-L is a Form Feed (014 octal).



So CNTRL-J is line feed and CNTRL-L is form feed?
Right.

I used to know all of these, and be able to convert to ascii code.
Getting old, and all this GUI crap doesn't help my memory at all!
Agree. And, I'll switch to hex when I grow 6 more fingers.

"Stan Prevost" wrote:

Boy, I haven't used telnet in a decade! More civilized things come along,
you know. :-)

Under WinXP, I can't get it to work. When I enter "telnet 131.131.7.102",
nothing seems to happen, no response. When I enter "telnet
direct.duats.com", I get to the system. It asks for the user code, I enter
it, then I get two lines back, "Enter Password:", and "Invalid Password".
Can't get past that. Three tries, it quits.

I just looked at my duats alias on one of my boxes and found I've been
using "telnet -K". The manpage (Mac-OSX) says -K "Specifies no
automatic login to the remote system."

It shouldn't be necessary, since the telnet client and server should
negotiate this stuff automatically. Still, if memory serves, on some
long-forgotten system, adding the -K did allow me to connect when
leaving the -K out didn't. It's worth a try if all else fails.