Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: polygen!stern@eddie.mit.edu (Hal Stern)
Newsgroups: comp.sys.sun
Subject: Resolution of Trailblazer woes
Keywords: Hardware
Message-ID: <466@bogart.UUCP>
Date: 5 Apr 89 02:09:07 GMT
Sender: usenet@rice.edu
Organization: Polygen Corporation, Waltham, MA
Lines: 24
Approved: Sun-Spots@rice.edu
Original-Date: 24 Mar 89 00:00:39 GMT
X-Sun-Spots-Digest: Volume 7, Issue 226, message 4 of 12

Thanks to all who responded with ideas and patches for using a Trailblazer
Plus with UUCP on a Sun 3/160.

Most of my problems stemmed from strangeness in our version of UUCP (based
on some old RTI-4.3 style code).  I traced our dialing problems to the
manner in which the Trailblazer behaves after seeing an "AT DT" sequence,
but before the other end picks up.  

I solved this one by writing my own dialer for a Trailblazer, based on the
hayestone dialer.  I added some more informative error logging and made it
a little more tolerant of the TB "RRING" verbose return code.  

The result is that we're online at 19200, and I ported the code rather
quickly to a Silicon Graphics 4D/80GT, which had even larger headaches
dealing with high speed modems.


--hal stern
  polygen corporation
  200 fifth avenue
  waltham, ma  02254
  (617) 890-2888

  {mit-eddie, bu-cs, princeton, sunne}!polygen!stern