Xref: utzoo news.software.b:2185 comp.dcom.modems:3754
Newsgroups: news.software.b,comp.dcom.modems
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: flow control on TB+ (was: Re: TMN-netnews update)
Message-ID: <1989May1.190130.8619@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1RH0R8#4BF6fX=eric@snark.uu.net> <1989Apr29.224526.22914@utzoo.uucp> <163@sopwith.UUCP>
Date: Mon, 1 May 89 19:01:30 GMT

In article <163@sopwith.UUCP> snoopy@sopwith.UUCP (Snoopy) writes:
>|Aha, a chance to catch Eric in an error! :-)  The uucp-spoofing mode in the
>|Trailblazer, when it kicks in, shuts XON/XOFF off, so there is no conflict.
>
>Aha, a chance to catch Henry in an error!  :-)    (rare indeed!)  The
>uucp-spoofing only works using PEP, so if you have low-speed uucp connections
>with XON/XOFF enabled they will die...

Touche'.  (What, the whole world doesn't have Trailblazers yet?? :-))

>BTW, is the uucp-spoofing-turning-off-
>XON/XOFF feature documented anywhere?  This is the first I've heard of it.

It's totally undocumented; I confirmed my conjecture by asking Peter Honeyman
(who wrote the uucp spoofing code).
-- 
Mars in 1980s:  USSR, 2 tries, |     Henry Spencer at U of Toronto Zoology
2 failures; USA, 0 tries.      | uunet!attcan!utzoo!henry henry@zoo.toronto.edu