Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!pacbell.com!att!ucbvax!van-bc!cynic!curt
From: curt@cynic.wimsey.bc.ca (Curt Sampson)
Newsgroups: comp.unix.xenix.sco
Subject: ctsflow and uucico
Summary: uucico doesn't work on a locked modem when dialing out
Keywords: uucp uucico serial modem
Message-ID: <1991Jun9.040907.16677@cynic.wimsey.bc.ca>
Date: 9 Jun 91 04:09:07 GMT
Sender: curt@cynic.wimsey.bc.ca (Curt Sampson)
Organization: Mad Artists' Technological Hangout
Lines: 30

I just bought a V.32 modem for my 286 Xenix 2.3.2 system.  I've
set the modem to lock the baud rate, and modified /etc/gettydefs
to open the port at EXTB (38400 bps) and turn CTSFLOW on.  Dialins
seem to work just fine.  No characters are lost, even at 1200 bps,
and uucico talk to remote systems at 2400 bps (I haven't had a
chance to try a higher speed or compression-enabled system yet)
just fine.

Unfortunately, things aren't working so smoothly when I dial out.
I've modified the dialer based on the one in /usr/lib/uucp/dialHA24.c.
It now sets the port to the highest rate given in the Devices file and
enables ctsflow (term.c_iflag |= CTSFLOW;) before dialing.  It dials
fine and exits.  Unfortunately, uucico and cu seem to turn off ctsflow
(as evidenced by doing an stty -a </dev/tty2A from another
multiscreen).  I regularly loose characters when using cu (though not
all that many) and uucico bombs on the larger files because it
transmits a packet, waits fifteen seconds or so, alarms, and transmits
the next packet.

What secret setup clue am I missing here?

If there is any demand I will summarize my experiences here once I get
everything fixed.

cjs
-- 
                        | "This sound system comes to you with fuel injection.
Curt Sampson            |  Toes tapping, the unthinking masses dance to a new
curt@cynic.uucp         |  tune. . . . Undress yourself to this bastard.  Suck
curt@cynic.wimsey.bc.ca |  on this plan of noise, bimbo!"       --Gary Clail