Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!gatech!udel!burdvax!sdcrdcf!trwrb!felix!ccicpg!turnkey!root
From: root@turnkey.UUCP (Super user)
Newsgroups: comp.unix.xenix
Subject: Re: sco 2.2 dial-in
Message-ID: <132@turnkey.UUCP>
Date: Thu, 20-Aug-87 19:01:06 EDT
Article-I.D.: turnkey.132
Posted: Thu Aug 20 19:01:06 1987
Date-Received: Sun, 23-Aug-87 23:39:15 EDT
References: <43@nancy.UUCP> <28@blft1.UUCP>
Organization: Turnkey Computer Consultants, Costa Mesa, CA
Lines: 40
Summary: Problem lies in /etc/gettydefs

In article <28@blft1.UUCP>, gah@blft1.UUCP (Gregg Houck SysOp) writes:
> In article <43@nancy.UUCP>, las@msudoc.ee.mich-state.edu (Larry A. Sheilds {runs Lunapark}) writes:
> > Although I experienced no trouble getting dial-ins to work with 2.1.3
> > I have not been able to to get them to work with 2.2.  The computer
> > dialing in sees the login prompt but nothing happens after they type
> > their login name.  Has anyone had a similar problem and how did you
> > solve it or not had any problem and what tty did you enable, what setting
> > in the inittab file did you make, etc.
> > 
> Yes Larry I have had the problem you list above.  I was trying to use
> 1200 baud 7 data, even parity, 1 stop on the calling unit.  I got the
> same results.  I had to use the following:
> 
> 1200 baud, 8 bits, No parity, 1 stop.
> 
We experienced the identical problem here at TCC, Gregg's solution ,however,
while perhaps acceptable between small systems is not going to work in all
instances. In the case where your system is polled by a large site using,say,
BSD 4.3 ( as we are) you cannot very well ask the system administrator to
change their port definitions. No, the problem must be resolved elsewhere.

The heart of the problem lies in the change SCO made in /etc/gettydefs between
release 2.1.3 and 2.2. On the dialup entries the initial flags are OK which is
why, Larry, they can enter their login name, at that point, however the second-
ary flags take effect and if you look at the entries they are as Gregg said,
CS8, and no parity enabled. Since the sending site is sending its password at
7E1 it will be garbled. So, to eliminate the problem you must edit each of
the dialup entries that you use (i.e.,1200 and 2400 baud), change the CS8 to
CS7 and add to each PARENB. This will resolve the problem.

Best of luck! And, for anyone from SCO reading this I would like to know why
the change was made in the first place. I assume there was good reason; care
to respond?


-- 
Jack F. Vogel
Turnkey Computer Consultants, Costa Mesa, CA
UUCP: ...seismo!uunet!ccicpg!turnkey!root 
      ...ucbvax!ucivax!mickey!conexch!turnkey!root