Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!strath-cs!str-va!cids05
From: cids05@vaxa.strath.ac.uk (@Dr Stephen K Tagg@)
Newsgroups: comp.windows.ms
Subject: Re: It looks like a flow control problem with Win3
Message-ID: <1991Feb5.115747.9912@vaxa.strath.ac.uk>
Date: 5 Feb 91 11:57:46 GMT
References: <606@twg.bc.ca>
Organization: Strathclyde University VAX Cluster
Lines: 17

In article <606@twg.bc.ca>, bill@twg.bc.ca (Bill Irwin) writes:
> I have configured a Non-windows application to Win3 as the
> execution of a communication program, TERM (from Century
> Software).  TERM has been told to use Xon/Xoff terminal
> handshaking.  I have configured, through the Control Panel, COM1
> to be 19,200bps with Xon/Xoff.
> If I terminate Win3 before running TERM it will connect and run
> at 19200 perfectly.  It seems that having the data flow from the
> Xenix port, through TERM communications program, through Win3 to
> the monitor is causing flow control problems when Win3 is part of
> the route.
> 
> Anyone have any config ideas that I have missed?

Maybe no help, but winqvt runs fine at 19,200 to our vax, unless I try to
send files via Kermit. Then I have to revert to 9600. I just imagined it was a
limit to the effective baud rate somewher in windows....