Path: utzoo!attcan!uunet!husc6!mailrus!ames!pacbell!att!chinet!les
From: les@chinet.UUCP (Leslie Mikesell)
Newsgroups: comp.dcom.modems
Subject: Re: Trailblazer Bugs (was Trailblazer, Misc)
Message-ID: <5668@chinet.UUCP>
Date: 25 May 88 17:28:02 GMT
References: <10273@ulysses.homer.nj.att.com> <10277@ulysses.homer.nj.att.com> <1084@teemc.UUCP> <1197@neoucom.UUCP>
Reply-To: les@chinet.UUCP (Leslie Mikesell)
Distribution: na
Organization: Chinet - Public Access Unix
Lines: 16

In article <1197@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
>It turned out that the vax end was running the trailblazer locked
>at 9600 baud and using xon/xoff protocol.  This caused problems for
>us when uucico on the vax started dumping data intot the modem at
>9600 baud, but the connection was only running at 2400.  Quite
>obviously, after a few seconds, the modem sent back what it felt
>was an obligatory xoff as the buffer filled up.  The xoff character
>apparently cuased the g-protocol to barf.  I'm not sure why the


I thought trailblazers were supposed to know about g protocol.  Did
you have the modem set in the correct mode for g protocol or does
it not limit its fake ACK packets to a number that will prevent its
internal buffer from filling?

  Les Mikesell