Re: broken Win32 telnet client

[Chris Cappuccio <chris@sefl.satelnet.org>]

On Sun, 5 Jul 1998, Steven Campbell wrote:

> 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).
> 

M$ telnet sucks... Use teraterm.. If this isn't an option, 'set
term=vt100' since MS telnet incorrectly says it's 'ansi' but works like
vt100. M$ telnet uses very significant amounts of CPU time to scroll,
among other things, not suprisingly (I'm not JUST trying to bash M$)

> 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?
> 
> Thanks,
> 
> 
> Steven Campbell,
> Manager of Computing Services,
> J&A Media Services,
> Thornhill, Ontario, Canada.
> 
> 
> 
> 

*--chris at satelnet.org--*