Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!pyramid!prls!philabs!linus!raybed2!rgc
From: rgc@raybed2.UUCP (RICK CARLE)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm in vt-100 mode
Summary: procomm+ in terminal emulator mode (N8 vs E7)
Message-ID: <1294@raybed2.UUCP>
Date: 6 Apr 89 20:03:27 GMT
References: <2672@garth.UUCP>
Organization: Raytheon Co., Bedford, Mass.
Lines: 18

In article <2672@garth.UUCP>, dbarnes@garth.UUCP (Dave Barnes) writes:
> Anyone out there have any experience with Procomm 2.4.2 as a vt-100 
> terminal emulator? . . .

I've been trying the pcplus test drive as a PC/AT vt102 terminal connected
to our Ultrix VAX.  In order to log on the VAX and process as a vt102,
I have to set pcplus to even-parity/7-bit.  Then, if I want to send
files back-and-forth to the PC (kermit protocol), I have to switch to
no-parity/8-bit.  Then back again when the transmission ends.  This
works, albeit awkwardly.  In any case, pcplus has never hung the PC.
When I use pckermit to do the same thing, it only needs to be set to
no-parity/8-bit for file transmission and handles the terminal stuff
transparently (no switching to 7-bit).  Much easier!  (But pcplus does
so much more than pckermit.)  In both cases, I use wermit on the VAX
end.  I suspect I don't have the connection set quite right (another VAX
behaves slightly differently), but I could live with it.  Maybe.

	Rick Carle, rgc@raybed2.ray.com