-=> Quoting Isaac Grover to All <=-
-=> FidoMail to 1:163/215, please.-=<
IG> I've set up all of my scripts for infinite redial until connected
IG> using dial ("4",0,1);.  Since 90% of my connections are now
IG> controlled by scripts, is there a way to determine how many times
IG> a number was dialed before there was a connection, just so I can
IG> print it to a capture file for later review?
Sure.  Simply create a variable which you increment on each dial
attempt.  Print the variable to a file after you connect.  You may
have to modify your script so that it dials only once, and you put
that single dial attempt in a loop until you get a connect.
Here's a trick you may consider implementing:  With a busy BBS you
may make repeated calls and get a BUSY each time.  Finally, you may
get a ring, but no answer.  Here's what's happened:  the BBS has
finished with the previous caller, so the line is free, but the BBS
system has not finished configuring for another call.  You just
happened to call during that short "hiatus" period.  Now, if you're
calling multiple numbers (for example, a BBS with four unique lines)
the _normal_ process would have you time-out on that line and you'd
proceed to the next number.  Unfortunately, that creates a "window of
opportunity" for someone else to snag that now-free line before you
get back to it.  Bummer.
So, here's what you do.  Your script is programmed to detect the
"ring no answer" - perhaps based on a timer.  Here, I'll get a
connect within 25 seconds of dialling if the line is actually free. 
So, after 25 seconds, if the script hasn't completed the dial attempt
with a BUSY or a CONNECT, the script _assumes_ it just made an
attempt during the hiatus.  So, the attempt is terminated, and
instead of cycling to the next number, it calls the _same_ number
again. (on a USR this is easy:  ATDL will dial the last-dialed
number).  Chances are very good the BBS will have completed its
configuration and I'll get a connect immediately. :-)
I'll leave it to you and your cunning mind to determine how to write
such a script. :-)
TTFN. Rick.
Ottawa, ON 12 Mar 15:49 
--- Blue Wave/DOS v2.20
---------------