Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!jpradley!jpr
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit T2500 -> TB+ UUCP spoofing problem, HELP
Keywords: uucp spoofing T2500 TELBIT
Message-ID: <1991Mar05.051051.27651@jpradley.jpr.com>
Date: 5 Mar 91 05:10:51 GMT
References: <554@shograf.COM> <1991Mar4.030916.3429@bilver.uucp>
Organization: NYC Public Unix
Lines: 22

In article <1991Mar4.030916.3429@bilver.uucp> bill@bilver.uucp (Bill Vermillion) writes:
>T'bit support gave me all sorts of undocumented registers, and we tried
>them all.  Nothing. Nada. Zip.  Still the problem.  I would get a lockup
>after about 150k was sent.   A big file,  or smaller files.  With the
>smaller files all was fine until total data transmitted was in the 150k to
>200k range (typically).   Sometimes a big file would go all the way
>through.
>
>This is with uucp g spoofing and cts/rts flow contol, as opposed to your
>xon/xoff.   T'bit said they had not seen anything like this.  Well that now
>makes two of us doesn't it.

Whatever I do in my dialTBIT binary, or any chat script, SCO's uucico will
ALWAYS set:  -ctsflow -rtsflow -ixon -xoff -ixany.

Any time you have uucico running, go to another screen and do an stty
reading on the uucico port and see it for yourself.

So I've decided that S58=0 and S68=0 is the way to go, since uucico ignores
everything in the way of flow control.

 Jean-Pierre Radley   NYC Public Unix   jpr@jpradley.jpr.com   CIS: 72160,1341