Xref: utzoo comp.dcom.modems:3693 comp.unix.questions:12825 comp.sys.ibm.pc:27355
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!labrea!rutgers!okstate!romed!penguin!jac
From: jac@penguin.UUCP (James Carter)
Newsgroups: comp.dcom.modems,comp.unix.questions,comp.sys.ibm.pc
Subject: Re: MNP Auto-Reliable + getty: happy accident or design?
Summary: Finally got mine to work
Message-ID: <542@penguin.UUCP>
Date: 12 Apr 89 13:22:44 GMT
References: <475@oglvee.UUCP>
Organization: Penguin Software Service / Tulsa, Ok
Lines: 24

In article <475@oglvee.UUCP>, jr@oglvee.UUCP (Jim Rosenberg) writes:
> Lately I've discovered that if a UNIX machine is answering the phone at 1200
> baud and the caller is calling at 2400 in MNP auto-reliable mode, the MNP
> handshake seems to toggle the receiver's getty to 2400 just like that, just
> about every time.  The modems in both cases are similar:  Multitech external
> and Multitech internal.  Both have MNP, but only the caller is in auto-

I'm pretty sure you have an accident here, but only because both of your
modems are by the same manufacturer. I have been using the MT224EH as the
only working modem on this 3B1 for about a year now, and had a devil of a
time getting it set up properly. The modem serial port is strapped for NO-AUTO-
BAUD, but the modem phone port is set to auto-baud. This forces the modem to
buffer the data, and conduct speed changes. I also had to disable the modems
own handshaking so that only the remote devices perform the xon/xoff (the
modems do pass it through, but take no action). The cable had to be correct,
the cpu port had to ignore dtr/rts/cts, the modems had to do the speed changes,
and they had to ignore stop/start, before I finally got everything to work
with lot's of different remotes.

-- 
==========================================================================
Disclaimer: are you kidding? I own the place!
James A. (JC) Carter
Penguin Business Systems, Inc.