Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ll-xn!mit-eddie!killer!dcs!wnp
From: wnp@dcs.UUCP (Wolf N. Paul)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Procomm Plus Question ...
Message-ID: <42@dcs.UUCP>
Date: 4 Mar 88 14:08:49 GMT
References: <335@ttrdf.UUCP>
Reply-To: wnp@dcs.UUCP (Wolf N. Paul)
Organization: DCS, Dallas, Texas
Lines: 29
Keywords: Procomm Plus

In article <335@ttrdf.UUCP> rdj@ttrdf.UUCP (Robert D. Jackson) writes:
>
>I have been "Test Driving" Procomm Plus, and have a problem.
>I use Crosstalk all the time set to 9600,N,8,1 and it works
>great on a direct connect to Unix.  My terminal is also set
>to this with no probelm.  I set Procomm Plus to the same thing 
>and it gets brain damaged (i.e. prints characters that are not 
>recognizably English).  It seems to works better when I set it 
>to 7 data bits.  Don't you need 8 data bits to use XMODEM?  I 
>thought I read that somewhere.  Is Crosstalk just a more robust
>package?  Is Procomm right and just not very robust?  What is
>the deal here?

I don't know Crosstalk so can't comment on it. However, if you use
Procomm (either Plus or 2.4.2) in 7-bit mode, it will AUTOMATICALLY
switch to 8 bits when you start transferring a file with XMODEM or
one of the other 8-bit protocols.

I suspect that Procomm and Crosstalk handle the UART configuration 
differently, but can't be sure. Most UNIX systems, unless you specifically
tell them otherwise using stty or one of the system calls, run in 
7bit, even parity mode, therefore Procomm is consistent in not working
too well at 8N. UNIX Xmodem programs also will temporarily switch their
tty to 8N during a transfer, and restore original conditions when they
exit.
-- 
Wolf N. Paul                  Phone: (214) 306-9101 (h)   (214) 404-8077 (w)
3387 Sam Rayburn Run          UUCP: ihnp4!killer!{dcs, doulos}!wnp
Carrollton, TX 75007          INTERNET: wnp@dcs.UUCP       ESL:  62832882
Pat Robertson does NOT speak for all evangelical Christians--not for me, anyway!