Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mandrill!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.dcom.modems
Subject: Re: autobauding a TrailBlazer on a UNIX PC
Summary: Some things to watch out for
Message-ID: <1199@neoucom.UUCP>
Date: 24 May 88 17:53:53 GMT
References: <282@ditka.UUCP> <1030@astroatc.UUCP>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 16


1.  When using the trailblazer, the MNP protocol will occasionally
get confused and think that a non-mnp modem is in fact MNP.  This
is not limited to the trailblazer; I've seen it on a US Robotics
HST and an AT&T CEO 2224.  I think it has to do with getty echoing
back MNP characters back into the modem when it tries to establish
a connection with a non-mnp moden on the end running getty.

2.  As alluded to in a previous article I wrote, running UUCP at
lower buad rate connects and the interface locked to 9600 (or 19200
if you dare on the 3b1) can result in the telebit sending back an
xoff to the host.  The uucp g-protocol will gag on the xoff.  Make
sure that the flow control is set to hardware on the 3b1, since the
3b1 tty driver handles either hardware or software handshaking.

--Bill