Xref: utzoo comp.sys.3b1:1275 comp.dcom.modems:9567
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!suned1!slced1!zaft
From: zaft@slced1.nswses.navy.mil (Gordon C Zaft)
Newsgroups: comp.sys.3b1,comp.dcom.modems
Subject: Re: help wrt UUCP between 3B1 OBM and TB
Summary: Don't do it!
Message-ID: <9663@suned1.Nswses.Navy.MIL>
Date: 5 May 91 05:35:21 GMT
References: <1991May4.210605.28387@sceard.Sceard.COM>
Sender: efb@suned1.Nswses.Navy.MIL
Followup-To: comp.sys.3b1
Distribution: na
Organization: NSWSES, Port Hueneme, CA
Lines: 22

In article <1991May4.210605.28387@sceard.Sceard.COM> mrm@Sceard.COM (M.R.Murphy) writes:
>I've a friend with a 3B1 using OBM to attempt UUCP connection
>to two systems, each with a TB (one TB+, one 2500). The TB+
>system is HDB, locked interface speed 9600baud, hardware flow
>control. The TB2500 is HDB, locked interface speed 19.2Kbaud,
>hardware flow control. The TB systems talk fine with systems
>with 1200baud external Hayes clones, as well as with various
>2400baud, 9600baud V.32, and PEP sites, and with each other. The
>3B1 will not successfully complete a UUCP session with either TB
>system. A representative log entry from one of the TB sites is:

	I believe the notes in osu-cis say that this won't work because
the OBM makes noises that the TB+ thinks is PEP but aren't.  Perhaps
one of the Experts will elaborate further?



--
+  Gordon Zaft                        |  zaft@suned1.nswses.navy.mil         +
+  NSWSES, Code 4Y33                  |  suned1!zaft@elroy.jpl.nasa.gov      +
+  Port Hueneme, CA 93043-5007        |  Phone: (805) 982-0684 FAX: 982-8768 +
** ..et resurrexit tertia die secundum scripturas, et ascendit in coelum.. ***