From: dawson@willard.waffle.atl.ga.us
Newsgroups: comp.bbs.waffle
Subject: uucico stuff
Date: 14 Oct 92 00:46:31 GMT
Organization: Willard's House BBS, Atlanta, GA -- +1 (404) 664 8814

I've got a different modem.  OK, so it's a little slower to recover from
a dropped carrier.  UUCICO flies on the i486, and there is little, if any,
delay from the end of one session to the beginning of a session with another
host.  So, the "NO CARRIER" result code sometimes appears, as UUCICO is
sending the AT dialing sequence.  The "NO CARRIER" message is really
associated with the previous session, but UUCICO sees it as it is dialing
the new session.

If I put
    uu.drops : BUSY ERROR RING NO_DIALTONE NO_CARRIER
                                           ^^^^^^^^^^
in my STATIC file, UUCICO ~correctly~ drops that attempt and proceeds to
the next.

I think there needs to be more delay after the end of a UUCICO session,
perhaps configurable.  I know about the uu.between parameter, and that
is something I'd like to see available for configuration "between" all
sessions, not just attempts to successive entries for the same host.

If I shorten the "delay from lost carrier to hang up," or S10 on the
Supra, then the likelihood that noisy lines will cause UUCICO to crap
out increases.  Is altering that register the only other alternative?

(On the off chance that someone out there might have an insight into
 something I might be doing incorrectly, I include for your pleasure
 my current system configurations, as applicable.)


On a slightly different note, I've got a bit of a problem with UUCICO's
handling of the uu.drops : RING setting.  If UUCICO detects an incoming
ring, the ENTIRE session should be terminated, so that Waffle may return
to it's mode of answering the phone.  The current setup is that UUCICO
will continue on to the next host entry with work scheduled (assuming
that it is called as "uucico -r0" ).  This means that most of those
remaining entries will fail (depending on how many there are), while
the incoming call keeps ringing...

What is the group's consensus on this?

#----------------------------------------
# Dialers file:

Supra  Default 38400 "" \pAT OK-\d\dAT-OK ATM0 OK ATDT\T CONNECT \m\c
Supra1 Default 38400 "" \pAT OK-\d\dAT-OK AT%C0 OK ATDT\T CONNECT \m\c

#----------------------------------------
# RUN.BAT (from which Waffle is started):

LH C:\WAFFLE\BIN\BNU.COM /L:0=19200 /R:2048 /T:2048 /M-

#----------------------------------------
# STATIC file hardware parameters

device       : 1
speed        : 19200
locked       : 19200
driver       : fossil
multitask    : dos windows
channel      : 1
auto-ata     : ATA

# SupraFAXModem v.32bis

initialize   : AT H0 S0=0 S11=55 V1 E1 X4 &C1 &D3

#----------------------------------------
# Active and stored profiles from at&v

ACTIVE PROFILE:
B1 E1 L3 M1 N1 Q0 T V1 W0 X4 Y0 %G1 &C1 &D3 &G0 &J0 &K3 &Q5 &R0 &S0 &T4 &X0 &Y0
S00:000 S01:000 S02:128 S03:013 S04:010 S05:008 S06:002 S07:070 S08:002 S09:006
S10:014 S11:055 S12:050 S18:000 S25:005 S26:001 S36:007 S37:000 S38:020 S44:003
S46:138 S48:007 S49:008 S50:255

STORED PROFILE 0:
B1 E1 L3 M0 N1 Q0 T V1 W0 X4 Y0 %G1 &C1 &D3 &G0 &J0 &K3 &Q5 &R0 &S0 &T4 &X0
S00:000 S02:128 S06:002 S07:070 S08:002 S09:006 S10:014 S11:055 S12:050 S18:000
S25:005 S26:001 S36:007 S37:000 S38:020 S44:003 S46:138 S48:007 S49:008 S50:255

STORED PROFILE 1:
B1 E1 L2 M1 N1 Q0 T V1 W1 X4 Y0 %G1 &C1 &D2 &G0 &J0 &K3 &Q5 &R0 &S0 &T4 &X0
S00:000 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000
S25:005 S26:001 S36:007 S37:000 S38:020 S44:003 S46:138 S48:007 S49:008 S50:255


-- 
dawson@willard.waffle.atl.ga.us (Willard Dawson)
Willard's House BBS, Atlanta, GA -- +1 (404) 664 8814