Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!mikes
From: mikes@ncoast.UUCP (Mike Squires)
Newsgroups: comp.dcom.modems
Subject: Re: TB+'s and hardware flow control on Sun 3's
Summary: Modify dial.c, not uucico
Keywords: Waking up a TB+
Message-ID: <12635@ncoast.UUCP>
Date: 1 Oct 88 20:00:50 GMT
References: <1151@natinst.UUCP>
Reply-To: mikes@ncoast.UUCP (Mike Squires)
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 27

In article <1151@natinst.UUCP> brian@natinst.UUCP (Brian H. Powell) writes:
>
>     We just got a Trailblazer for our Sun 3/160 running SunOS 4.0, which we
>use for uucp.
>
>     We talk to one site that can't handle anything faster than 9600 baud.  We
>talk to another site that talks 19.2 to its modem.  Ideally, we'd like to
>autobaud between the TB and the Sun, so that we'd always be talking at
>whatever baud rate was expected.  Unfortunately, if you set the S51 register
>to 254 or 255, and you want to talk 19.2 kbaud, you have to type AAT initially
>instead of AT.  Our uucico doesn't (seem to) let you change how it talks to
>the modem, so I can't just tell it to use AAT instead of AT.

XENIX uucico calls /usr/lib/uucp/dial first if the L.sys entry is
"ACU <speed>".  A TB+ dialer was posted to one of the newsgroups some
time ago (it does not work under XENIX, different .h files, but it told
me how to modify the generic dial.c to work).  The dialer I am using now
outputs AT\r at the correct speed, looks for an OK, tries again if no OK,
ad nauseum until the timer stops it.  

I believe that BSD UNIX does the same sort of thing and know nothing about
HDB uucp.

Mike Squires Allegheny College Meadville, PA 16335 814 724 3360
uucp: ..!cwjcc!ncoast!{mikes,peng!sir-alan!mikes} or ..!pitt!sir-alan!mikes
BITNET: mikes%sir-alan@pitt.UUCP (VAX) MIKES AT SIR-ALAN!PITT.UUCP (IBM)
Internet: sir-alan!mikes@vax.cs.pittsburgh.edu