Xref: utzoo comp.unix.xenix:1344 comp.unix.wizards:6228
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!laidbak!spl1!raj
From: raj@spl1.UUCP (Robert Alan Johnson)
Newsgroups: comp.unix.xenix,comp.unix.wizards
Subject: Re: Ultrix -> Xenix/386 uucp problem
Message-ID: <592@spl1.UUCP>
Date: 24 Jan 88 23:02:31 GMT
References: <9303@steinmetz.steinmetz.UUCP>
Organization: The Software Public Library, Chicago, IL.
Lines: 28

From article <9303@steinmetz.steinmetz.UUCP>, by davidsen@steinmetz.steinmetz.UUCP (William E. Davidsen Jr):
> I have a Xenix/386 (2.2.1) system which is called by an Ultrix 2.0 VAX
> for uucp transfer.  The connection procedes until the password is
> entered from L.sys, then the VAX hangs waiting for Shere.  A number of
> other systems have no trouble dialing into the system (it's the hub
> machine for the *IX user's group), so I don't think uucp logins are
> broken. 
> 
Hi, we've seen this a lot.  The answer is almost always the same.

**PARITY**

In xenix (starting with 2.2) they went to a no parity default.  It seems
that most UNIX's in the world are 7 bit even.  (BTW: SCO says the no parity
8 bit configuration is to permit support of non-english character sets.)
In some uucp's, uucico is sensitive to parity, PARTICULARLY ULTRIX.  
We feed news to quite a few sites and ALL ULTRIX and ENCORE systems seem
to have the problem EXACTLY as you've described it.

The solution is simple.  Almost all of the uucp's out there permit you
to specify parity with sepcial commands in the CHAT script, some 
use P0 as the specification for no parity.  Check with your uucp manual
to make sure.

Bob Johnson
The Software Public Library, Chicago, IL
...ihnp4!spl1!raj
...1-312-248-5777