Xref: utzoo comp.sys.dec:5009 comp.unix.ultrix:6148
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ub!dsinc!bagate!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.sys.dec,comp.unix.ultrix
Subject: Re: Can Ultrix 3.1 getty autobaud to 19200?
Keywords: ULTRIX, getty, autobaud, dialup
Message-ID: <18777@cbmvax.commodore.com>
Date: 11 Feb 91 00:04:56 GMT
References: <303@asihub.autosys.com>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 28

In article <303@asihub.autosys.com> dano@asihub.autosys.com (Dan O'Neill) writes:
> 
> Problem:    I would like to have getty autobaud to 19200, the getty
> 	    in ULTRIX 3.0 (VAX) doesn't seem to support this speed.
> 	    Am I correct, and if so, is there a way to patch getty
> 	    to support a speed of 19200?

I played with it a long time ago, and concluded that it didn't
want to work.  The general technique is to set the speed to some
value and see what kind of garbage is detected when a return is
received.  I think the way it's set up, anything 9600 or above
yields the same result.  You'd have to change the initial trial
speed or do a second pass to distinguish faster rates from the
olde 300/1200/2400 junk.

Sequencing via breaks seems to work just fine though, although
there's no guarantee that all DEC interefaces suppport 19200,
although most do, unofficially.

Note that if you were getting autobaud action by the fact that
sending random characters at the wrong speed causing framing errors
which unix seems to treat pretty much like breaks, I guess the
stuff at 19200 just doesn't seem like breaks.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)