Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!rutgers!mailrus!ames!ncar!tank!nucsrl!blekko!skrenta
From: skrenta@blekko.home.nwu.edu (Rich Skrenta)
Newsgroups: comp.unix.xenix
Subject: Re: uucico problem -- is XCLUDE really supposed to work this way?
Message-ID: <248@blekko.home.nwu.edu>
Date: 11 Mar 89 17:25:17 GMT
References: <715@vector.UUCP>
Organization: BlekkoTek World Headquarters, Chicago, IL USA
Lines: 29


Disclaimer first:

      I know nothing about the XCLUDE flag.  I'm also using Xenix 286 2.2.1.

When you say "uucico aborts" do you mean abnormally, or every time?
I had a problem that if uucico died for some reason (typically "bad baud rate"
when my Hayes compatible modems fell from 2400 to 1200) it would give the
symptoms you describe--modem hung, getty still suspended, the works.  Since
the getty is still suspended, further attempts to ungetty it result in
"line in use".

I found that the culprit was the dial programs that SCO provides.  Fortunately,
we have source to those.  I took me nearly three hours of hacking to figure
out how they work, but I was able to patch them NEVER to leave a line hosed.
I also increased the delay time between commands sent so I could change my
modem from &D2 to &D3--reinitialize to start up values every time DTR goes
low.  (My anchor modem resets very quickly, but my Maxum takes more than
a second, and the dial program was croaking on it).

If this fix sounds like it would help you out, I'd be happy to mail you
my modified dialHA24.c  I'm hesitant to send off a diff because our Xenix
versions are different.  If enough people want it, I suppose I could post it.

Rich

-- 
Rich Skrenta                 skrenta@blekko.home.nwu.edu
skrenta@eecs.nwu.edu         ...nucsrl!blekko!skrenta