Xref: utzoo comp.unix.microport:354 comp.unix.xenix:1810 comp.unix.questions:6326 comp.unix.wizards:7461
Path: utzoo!yunexus!ists!mike
From: mike@ists (Mike Clarkson)
Newsgroups: comp.unix.microport,comp.unix.xenix,comp.unix.questions,comp.unix.wizards
Subject: Re: UUCP Problems
Keywords: UUCP XENIX
Message-ID: <175@ists>
Date: 29 Mar 88 02:16:46 GMT
Article-I.D.: ists.175
Posted: Mon Mar 28 21:16:46 1988
References: <1113@csuna.UUCP| <10126@steinmetz.steinmetz.ge.com>
Organization: I.S.T.S.
Lines: 31

In article <10126@steinmetz.steinmetz.ge.com>, davidsen@steinmetz.steinmetz.ge.com (William E. Davidsen Jr) writes:
| In article <1113@csuna.UUCP| abcscnge@csuna.UUCP (Scott "The Pseudo Hacker" Neugroschl) writes:
| | When attempting to run UUCP from a IBM XENIX 1.0 system to an SCO
| | XENIX V 2.2.1 system, the IBM system calls up and logs in, and the
| | SCO system responds with
| | 
| | Shere
| | 
| | and then times out the IBM system.  I also can't seem to get 2 IBM 1.0 systems
| | to talk via UUCP.  Any suggestions?
| 
| Having spent several weeks finding a similar problem, I would suspect
| parity is the problem. Particularly if the call working in one direction
| and not the other. If that's the case let me know, I think I have the
| solution to the problem.

Very likely.  SCO defaults its port to no parity, while most other
Unixes default to even parity.  You have 2 choices; either change the
parity for your port to even using /etc/gettydefs, or at the IBM end,
try adding 

	"" P_ZERO 

at the beginning of the chat script, after the phone number.  This (may)
tell the IBM uucico to start up using parity = none.

-- 
Mike Clarkson						mike@ists.UUCP
Institute for Space and Terrestrial Science
York University, North York, Ontario,
CANADA M3J 1P3						(416) 736-5611