Path: utzoo!mnetor!uunet!sco!arthure
From: arthure@sco.COM (All diagnostics are fatal)
Newsgroups: comp.unix.xenix
Subject: Re: vt102 termcap for SCO Sys V
Message-ID: <65@subsco>
Date: 1 Feb 88 20:14:15 GMT
References: <649@ut-emx.UUCP>
Reply-To: arthure@sco.COM (Arthur Evans)
Organization: The Santa Cruz Obfuscation, Inc.
Lines: 29
Keywords: termcap, kermit, vt102

In article <649@ut-emx.UUCP> chcu275@ut-emx.UUCP (chcu275) writes:
>I use Kermit-MS V2.29, which tries to emulate a vt102 
>on an IBM PC-AT running DOS, to connect to an IBM PC-AT running
>SCO XENIX Sys V.  An IBM serial/parallel adapter is used on each
>end.  The environment variable, TERM, is set to "vt100" because
>I do not have a termcap entry for "vt102".
>
>This arrangement is satisfactory except for use with vi.  In vi, 
>a deleted line except for the last line in a file is replaced with 
>an "@" character until it is scrolled off of the screen.  Additionally,
>in insert mode, freshly inserted text over-writes existing text 
>until leaving insert mode at which time the over-written text 
>reappears.

This doesn't sound like a termcap problem at all; I believe the problem
is that at low speeds (1200 baud, for example), vi defaults to
"noredraw" mode.  From your posting it isn't clear what speed you're
operating at, but your description sounds like vi with noredraw set.  If
this is the case, adding "set redraw" to your EXINIT environment
variable should fix the problem.

I use mskermit v2.29 with the vt100 entry regularly, without
much difficulty.

-arthur
-- 
"Sometimes I feel just like a dog ...      | this is not the voice of SCO
 I guess that that goes with my  job ..."  | this is not the voice of SCO
		      -The Jazz Butcher    | this is not the voice of SCO