Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!samsung!dali.cs.montana.edu!ogicse!pdxgate!parsely!percy!qiclab!onion!jeff
From: jeff@onion.rain.com (Jeff Beadles)
Newsgroups: news.software.b
Subject: Re: uucico (sorry if this is the wrong group!)
Keywords: uucico, smarter
Message-ID: <1991Jan19.021424.9888@onion.rain.com>
Date: 19 Jan 91 02:14:24 GMT
References: <6115@qip.UUCP>
Lines: 31

In article <6115@qip.UUCP>  writes:
...
>I have been watching our uucico process a bit, and thinking that
>it could go MUCH faster if uucico were just a bit smarter in its
>chat script.  For example, it would be REAL nice if it were able
>to detect the "BUSY" return from the modem and take appropriate
>action, rather than waiting 30 (60?) seconds for "ogin:" (which,
>of course, never shows up).  It would also be nice if we could
>change the timeout time for certain waits (make it 10 seconds, for
>example, rather than the default 30, but only for certain strings).
...

Well, on the older-style UUCP (V2ish) I use the following:


qiclab Any;5 DIR 19200 tty00 "" \d\b "" AAAAT&E2M0S50=255S7=60 OK \
 ATDT123-4567 ABORT BUSY CONNECT-\c-CONNECT-\c-CONNECT \r \
 ogin:-\r-ogin:-\r-ogin-\r-ogin LOGIN word PASSWORD

Note, the "ABORT BUSY"  That says that the modem should abort the dial if it
receives the string "BUSY" from the modem before it sees 'CONNECT'.

Your milege may vary.  I've given up on ACU style dialing, as it never seems
to do quite what I've wanted...


Hope this helps,

	-Jeff
-- 
Jeff Beadles		jeff@onion.rain.com