[comp.unix.xenix] Logging in on TB+ at 19.2

dick@slvblc.UUCP (Dick Flanagan) (01/06/90)

I have a Telebit TrailBlazer Plus modem that I use to converse with uunet.
My system is an AST 286 running SCO XENIX/286 SYS V 2.3.2.  I am able to
dial out on the TB+ to uunet just fine; the connection is made, I log on,
and all communications are normal.

However, when uunet attempts to dial up my system, they consistently get
failed logins.  Their TB connects (CONNECT FAST) to my TB, but they receive
junk from me instead of a login prompt.  It would appear the connection
between uunet and my modem is good.  The problem seems to be that my system
cannot accept their login at 19.2 because of a baudrate problem between
it and my TB.

I have spoken with the good folks at uunet (thanks, James) and they have
suggested that I pose my problem to the net.

My /etc/ttys entry for the TB line is:

16tty2A

My /etc/gettydefs entry for the '6' line speed is:

4 # B2400 HUPCL # B2400 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\n@!login: # 6
5 # B4800 HUPCL # B4800 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\n@!login: # 4
6 # B9600 HUPCL # B9600 CS8 SANE HUPCL TAB3 ECHOE IXANY #\r\n@!login: # 5

SCO does not provide a gettydefs entry explicitly for 19.2.  Should I be
declaring it as 'EXTA' or some such?  How can I get getty to accept a login
from my TB at 19.2?

Once I solve this mystery, one way or another, I will share my findings
with the rest of the net.  Any and all help will be appreciated.  Thanks.

Dick
-- 
Dick Flanagan, W6OLD, CFII, CFIG             Cherokee 235 N9212W
UUCP: ...!uunet!slvblc!dick                  GEnie: FLANAGAN
Internet: slvblc!dick@uunet.UU.NET           POB 155, Ben Lomond, CA 95005

maxim@subch.imp.com (Maxim Samo) (01/10/90)

In article <96@slvblc.UUCP> dick@slvblc.UUCP (Dick Flanagan) writes:

>However, when uunet attempts to dial up my system, they consistently get
>failed logins.  Their TB connects (CONNECT FAST) to my TB, but they receive
>junk from me instead of a login prompt. [...]

Just two days ago I had the same problem! The reason was the S51 (interface
speed) register, which was set to 255 causing the traily to send with 9600
bps to the computer instead of 19200. Try to set the S51=254. That did the
job over here...

   Maxim
-- 
		     Maxim Samo, P.O.Box, CH-4125 Riehen
			  UUCP: maxim@subch.imp.com