Xref: utzoo unix-pc.general:7079 comp.sys.att:11378
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!cmcl2!uupsi!vmp!sonyd1.Broadcast.Sony.COM!blilly.UUCP!balilly.UUCP!bruce
From: bruce@balilly.UUCP (Bruce Lilly)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: OBM connection problems solved.
Message-ID: <1991Jan5.142440.18139@blilly.UUCP>
Date: 5 Jan 91 14:24:40 GMT
References: <1036@ecicrl.UUCP> <1991Jan3.175725.4228@yenta.alb.nm.us>
Sender: news@blilly.UUCP (News Administrator)
Followup-To: unix-pc.general
Distribution: na
Organization: Bruce Lilly, Flushing, NY
Lines: 22

In article <1991Jan3.175725.4228@yenta.alb.nm.us> dt@yenta.alb.nm.us (David B. Thomas) writes:
>
>Anybody ever manage to get the OBM to call a telebit with uucp?

Sure, I used to call 3 systems, all with Telebits.  Now for the bad news;
I had no problems with two of the systems, using high-end Telebits, but
one system had an older Telebit which had the bit-shaving problem.  I
could only communicate successfully with that system at 300 baud.  Due to
hardware constraints on that system, its Telebit modem was operated w/o
flow control, with the interface speed locked. I believe one or both of
those conditions is when the bit-shaving problem shows up.

I used HDB uucp at the time (still do).

I'm now using an external, pain-in-the-butt, quasi-modem (ROLM 244PC, made
by Int'l BM) on the system with those 3 connections, so I haven't used the
OBM to talk to Telebits in the last 2 1/2 months.

IMEO, the problem is the Telebit bit-shaving, which violates the timing
constraints for asynchronous serial communications.
--
	Bruce Lilly		blilly!balilly!bruce@sonyd1.Broadcast.Sony.COM