Xref: utzoo comp.sys.att:2308 comp.dcom.modems:1304
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!hao!ames!lll-lcc!lll-winken!uunet!dmk3b1!dmk
From: dmk@dmk3b1.UUCP (David Keaton)
Newsgroups: comp.sys.att,comp.dcom.modems
Subject: Re: Trailblazer gets mad at AT&T 3b1 OBM (on board modem)
Keywords: thinks 3b1 has MNP protocol
Message-ID: <362@dmk3b1.UUCP>
Date: 1 Feb 88 06:39:35 GMT
References: <986@neoucom.UUCP>
Reply-To: dmk@dmk3b1.UUCP (David Keaton)
Organization: DMK, Branford, CT
Lines: 21

In article <986@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
>. . .  When the trailblazer placed the data call at
>1200 baud into the 3b1 OBM, it thought that the 3b1 had MNP
>protocol, as reported by the Telebit's "CONNECT 1200/REL".  At that
>point, the Trailblazer locked up, and I had to drop the DTR lead to
>get it to disconnect. . . .
>So the question is, is the 3b1's OBM really supposed to be an MNP
>modem, and this 3b1 is sick?

     This is MNP's fault, not the 3b1's or the Trailblazer's. 
Before I got my Trailblazer, I experimented with mixing
Multitech 224E's and other modems.  Autoreliable mode is simply
braindamaged.  It disables Unix PC OBM's, USR Courier's, and
other random modems.

     I finally gave up and I never use MNP any more.  Behavior
may vary slightly with Trailblazers, but the real problem is a
design flaw in MNP.
-- 
					David Keaton
					dmk%dmk3b1@uunet.uu.net
					uunet!dmk3b1!dmk