Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!husc6!ut-sally!ut-ngp!melpad!bigtex!james
From: james@bigtex.UUCP
Newsgroups: comp.unix.questions
Subject: Re: Microport Unix & UUCP
Message-ID: <298@bigtex.uucp>
Date: Fri, 16-Jan-87 04:20:04 EST
Article-I.D.: bigtex.298
Posted: Fri Jan 16 04:20:04 1987
Date-Received: Sat, 17-Jan-87 07:21:54 EST
References: <1040@hope.UUCP> <529@cti.cti.UUCP>
Sender: james@bigtex.uucp
Reply-To: james@bigtex.UUCP (James Van Artsdalen)
Organization: F.B.N. Software, Austin TX
Lines: 22

IN article <529@cti.cti.UUCP>, eric@cti.UUCP (Eric Black) wrote:
> [...] I'm running 1.36 and it works fine with a USR 2400.
> It works for dialout on an Avatex 1200 (cheap!), but not for dialin
> because there is no way to disable the status messages coming in from
> the modem (which confuses getty and login!).

The problem with the Avatex 1200 is probably *not* "disabling the status
messages" (these need to be enabled for outgoing calls anyway), but instead
the timing of when the Avatex prints the status message and enables
carrier detect after answering the phone.  My Courier, which also works
great as a bidirectional modem, appears to print the "CONNECT" message
and then enable the carrier detect signal.  The Avatex may do this the
other way around.  The U.S. Robotics Password 1200 seems to do something
else yet: when I tried to use it as an answer-only modem on a 3b2, I got
garbage on the "login: " line.  This happened with several other Passwords,
so I assume it's something about the Password.  Maybe the Password is
re-enabling the carrier detect signal while printing the CONNECT message.
In any case I doubt the status messages themselves are the problem, but
instead the timing the modem uses when a connection is made.
-- 
James R. Van Artsdalen   ...!ut-sally!utastro!bigtex!james   "Live Free or Die"
(512)-328-0282