Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!mit-eddie!smh
From: smh@mit-eddie.UUCP (Steven M. Haflich)
Newsgroups: net.news.sa
Subject: Re: uucp log in on spilt baud rate line
Message-ID: <1393@mit-eddie.UUCP>
Date: Mon, 5-Mar-84 21:54:45 EST
Article-I.D.: mit-eddi.1393
Posted: Mon Mar  5 21:54:45 1984
Date-Received: Tue, 6-Mar-84 06:56:15 EST
References: <312@mddc.UUCP>
Organization: MIT, Cambridge, MA
Lines: 20

>	The break will change the baud rate OK, but the baud rate
>	seems to change back again before the login name can
>	be sent.

Remember that 1200 baud modems are very sensitive to framing of
successive characters.  (Ever notice that garbled characters usually
happen in twos and threes?)  The active filters in some modems need a
significant recovery period after receiving a break.  This is rarely a
problem when a human is pounding the keys, but it may be that your
uucico after asserting break should delay before sending anything else.
What may be happening is that the remote modem gets a framing error on
your `uucp' login name (which generates *another* break) and toggles the
baud rate again.  The 4.2 uucico (specifically conn.c:sendthem) accepts
a specification of PAUSEn, where n is an integer number of seconds
(default 3 in my sources).  If not, add the code yourself.  Instead of
just putting BREAK in the L.sys login script, try:
	BREAK "" PAUSE2 ogin: uucp ...

Steve Haflich
MIT Experimental Music Studio