Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!zephyr.ens.tek.com!tektronix!percy!m2xenix!quagga!proxima!olsa99!tabbs!aris
From: aris@tabbs.UUCP (Aris Stathakis)
Newsgroups: comp.dcom.modems
Subject: Re: SCO Unix uucico RTS/CTS (was re:T2500 -> TB+ spoofing problem)
Keywords: uucp spoofing T2500 TELBIT
Message-ID: <1991Mar21.174807.6103@tabbs.UUCP>
Date: 21 Mar 91 17:48:07 GMT
References: <1991Mar7.214200.20682@hq.demos.su> <1991Mar10.014152.26911@jpradley.jpr.com> <27682@netcom.COM> <1991Mar13.001850.20702@jpradley.jpr.com> <1991Mar17.210258.2194@robot.in-berlin.de>
Distribution: comp
Organization: TABBS - Totally Awesome BBS
Lines: 25

In <1991Mar17.210258.2194@robot.in-berlin.de> karl@robot.in-berlin.de (Karl-P. Huestegge) writes:

>jpr@jpradley.jpr.com (Jean-Pierre Radley) writes:

>>I'm just stating that what I observe is: no matter what a compiled dialer does,
>>or what uuchat does reading a chat script, uucico resets things when those have
>>terminated.

>right. do a stty ctsflow < /dev/tty1a while uucico starts working.
>Or better use FAS instead.

>BTW: I found CTSFLOW gets ignored in gettydef.

Works great for me.  I've got my 2400 baud modem locked at 9600 baud
under SCO Xenix 2.3.2 with absolutley no hardware flow control problems.

Be sure to enable hardware flow control in your modem AS WELL as in
gettydefs :-)

Aris

-- 
 Aris Stathakis | Bang: ..!uunet!ddsw1!olsa99!tabbs!aris or aris@tabbs.UUCP

             "ASHes to ASHes, DOS to DOS......"