Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mandrill!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.dcom.modems
Subject: Re: Trailblazer Bugs (was Trailblazer, Misc)
Summary: Brain Damage at 2400 baud
Message-ID: <1186@neoucom.UUCP>
Date: 19 May 88 00:38:26 GMT
References: <10273@ulysses.homer.nj.att.com> <10277@ulysses.homer.nj.att.com> <9999@tekecs.TEK.COM>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 24


At the moment, I am "stuck" using an aged TB, version 3.  I've
found that uucp is broken when some other machine dials in at 1200
or 2400 baud.  I can only get one C or D file though per call which
means that it takes an awful long time to get mail through!!  What
happens is that the first file gets though, and then uucp returns
to control state to begin the next file and then fails a checksum
on the first packet.  It seems like there is some risidual of the
spoofing alogorithm that is munging up uucp at the lower speeds
when there should be no spoofing at all.

We sent the TB+, version 4 down to Mark Horton, so I can't currently
verify if this bug in in the newer firmware.  Sure is aggrivating,
though!  I've tried just about every combination I can think of,
with and without MNP, etc, but they always gag on uucp at 1200 or
2400.  Normal interactive person-typing-at-a-CRT type calls seem to
be just fine at the lower speeds.  Uucp seemed to work OK when
regular old Hayes were swapped back in on the connection.

I guess the Trailblazer is kind of like a mother in law; you just
gotta love it anyway, despite the quirks.

--Bill
  wtm@neoucom.UUCP