Xref: utzoo comp.dcom.modems:1482 comp.sys.apollo:750
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!agate!ig!uwmcsd1!tut.cis.ohio-state.edu!husc6!m2c!ulowell!dino!rimbold
From: rimbold@dino.cpe.ulowell.edu (Rob Rimbold)
Newsgroups: comp.dcom.modems,comp.sys.apollo
Subject: Re: trailblazer modems and apollo UUCP
Message-ID: <1938@dino.cpe.ulowell.edu>
Date: 27 Feb 88 21:38:43 GMT
References: <121@vader.UUCP> <130@vader.UUCP> <3381@cbmvax.UUCP>
Reply-To: rimbold@dino.ulowell.edu (Rob Rimbold)
Organization: University of Lowell
Lines: 29
Keywords: trailblazer

In article <3381@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
>In article <130@vader.UUCP> bcs212@vader.UUCP (Vince Skahan) writes:
>> 
>> [..stuff deleted..]   Only detail
>> is that Apollo UUCP won't take a speed above 9600 in the L.sys and
>> L-devices files  [..stuff deleted..]
>
>  [..stuff deleted..]   I'd contact Apollo and see if
>they can do something about the 19200.


I doubt that they will. It's a generic problem with UUCP. When I was first
setting up UUCP on my (dare I say it :-) Sun, I had the same problem.
I wanted to use 19200, since we have a physical line to our UUCP partner,
but the UUCP implementation didn't want to handle it..

The partial solution was to add a gettytab entry for the speed 19200, and
change your incoming port in ttys to use 19200. That way, incoming calls
can be had at 19200, but you're still stuck with 9600 for outgoing ones.

BTW: It took Sun about a week to figure out that UUCP wouldn't handle
	19200, and that the problem wasn't in my configuration.. :-)


-- 
'Rob
    Usenet: rimbold@dino.ulowell.edu
    AT&T  : (617) 452-5000 x2693
    University of Lowell Productivity Center, Lowell MA.