Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!teknowledge-vaxc!plim
From: plim@teknowledge-vaxc.ARPA (Pean Lim)
Newsgroups: comp.windows.ms
Subject: Re: Communications via Terminal
Message-ID: <27272@teknowledge-vaxc.ARPA>
Date: 10 Apr 89 00:44:58 GMT
References: <11861@pasteur.Berkeley.EDU> <13540@ncoast.ORG>
Followup-To: comp.windows.ms
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 18
In-reply-to: allbery@ncoast.ORG's message of 8 Apr 89 17:03:31 GMT

In article <13540@ncoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery) writes:

   Speaking of Windows 2.1 and WINQVT...

   I've tried to use WINQVT32 under Windows 2.1 on three different machines --
   ITT XTRA "turbocharged" via an Inboard/386, Altos 500 (fairly generic AT386)
   and PS/2 50Z -- and it always crashes Windows the first time I type
   something at it.  (The machine locks up.)  Am I doing something wrong, do I
   need a different version of WINQVT, or ???  (I've already verified that it's
   not a problem with, say, RTS/CTS flow control, which has locked up non-Windows
   terminal programs in my experience when the other side of the connection
   didn't use the same flow control.)  Or is it some kind of compatibility
   problem which requires the use of (ugh) true-Blue non-PS/2's or etc.?

I believe have the same problem you mention--with a Wyse
AT-compatible this time.  The strange thing is that WINQVT32 works on
a second Wyse AT-compatible (not identically endowed, though).
However both systems run Windows 2.1.