Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!kksys!orbit!pnet51!pj
From: pj@pnet51.orb.mn.org (Paul Jacoby)
Newsgroups: comp.dcom.modems
Subject: Re: New Modems, Telebit Fails under impairments in PC Magazine
Message-ID: <3667@orbit.cts.com>
Date: 21 Dec 90 13:52:56 GMT
Sender: root@orbit.cts.com
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 19

[comments regarding difficult in setting up a T2500]

That's odd; when we installed two Telebit T2500's on our UNIX machines, I
think we only had to change two parameter settings and about 4 registers.  We
found the easiest way to configure the modem was to start with AT&F, and then
change one thing at a time.  Having a target system to dial into helps loads,
but as long as you hit both modems with factory defaults, then make small,
testable changes, all goes pretty smoothly.
  After a week of '10 minutes here, 5 minutes there' configuration, we had
both T2500's jammin with PEP between them, V.32 to a couple 9600 boards, and
2400/MNP5 to appropriate destinations.  To say nothing of the work it took to
set the silly /usr/lib/uucp/* files!  That was far more challenging.

  Of course, your mileage may vary.
.-----------------------------------------------------------------------------.
| UUCP: {crash tcnet}!orbit!pnet51!pj            | RTFD = Read The Silly Doc! |
| INET: pj@pnet51.orb.mn.org                     |                            |
`-----------------------------------------------------------------------------'