Re: broken Win32 telnet client

[Aaron Jackson <jackson@negril.msrce.howard.edu>]

>I am having some pretty nasty terminal emulation problems whenever I telnet
>to just about any UNIX or UNIX-like OS. This is nothing specifically wrong
>with OpenBSD. The difficulties I describe also occur when I telnet to a
>Novell UnixWare machine. I am using Micro$oft's Win32 Telnet.exe, which I
>realize could be the problem. (In fact, probably IS the problem).

That is one of the worst telnet programs I have ever used.  Try Tera
Term Pro.  It's freeware and, so far, it works great.


>When I run vi, or more a file, the last line is never displayed. I have to
>do a series or ^R and ^L or go forward and backward in the file to find out
>which line I am truly editing. I have often edited a file, only to discover
>I made changes to the wrong line. Ex and/or ed work fine.
>And the backspace doesn't work. Delete functions like the backspace, and
>the backspace prints out ^H.
>
>I am using vt100 terminals, which I realize doesn't match OpenBSD's default
>of vt220, but my only other choice is ANSI or ansi or DEC-vt100. These
>terminals net the same result.
>
>Can anybody out there suggest a saner telnet client and/or some terminal
>tweaks to get some basic terminal functions operating properly?

There are a couple of things you can do. On the OpenBSD machine you can

1) 'set term=vt100' before you telnet to another computer from the
    OpenBSD machine.

2) 'set term=vt00' on the OpenBSD machine before you telnet out to
    another machine. 

3) Edit /etc/ttys so the terms are vt100 and not vt220 and never have to
   worry about this problem again. Of course, make a back up copy before
   you do this, just in case.

Aaron Jackson		jackson@msrce.howard.edu