Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!swrinde!cs.utexas.edu!uunet!pds3!ravi
From: ravi@pds3 (Gorur R. Ravi)
Newsgroups: comp.terminals
Subject: Re: Termcap entries for vt102 terminal.
Message-ID: <1990Mar2.171453.10657@pds3>
Date: 2 Mar 90 17:14:53 GMT
References: <1990Feb21.180504.3081@pds3> <875@pmday_2.Dayton.NCR.COM> <1990Feb26.201434.1196@pds3>
Reply-To: ravi@pds3.UUCP (Gorur R. Ravi)
Distribution: usa
Organization: Project Design Systems, Inc.
Lines: 21

In article <1990Feb26.201434.1196@pds3> ravi@pds3.UUCP (Gorur R. Ravi) writes:
>In article <875@pmday_2.Dayton.NCR.COM> steve@pmday_2.Dayton.NCR.COM (Steve Bridges) writes:
>>Our PCs connected to our Tower are using Procomm+ in the vt102 mode, and
>>their termcap is set to vt100.  We haven't noticed any problems or
>>differences.
>>
>Well, we also use Procomm+ to connect to our Prime computer running
>SYS V (ver 3.?) and we have problems using vi (like it doesn't display
>characters while using 'h' in command mode). Besides we have problems
>in running ....
>

Recently the above problem was solved by our local Unix/DOS guru. I was
told that if one sets up the Back Space (BS) translation option (which can 
be accessed through Procomm Plus' Setup utility --> Terminal Option -->
Genaral Option), to NON DESTRUCTIVE, the above problem will be solved.

-- 
Gorur Ravi (ravi)   uunet!pds3!ravi
Project Design Systems, Inc., 2231 Crystal Drive, Suite 1114,
Arlington, VA 22202