Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc!tank!shamash!nic.MR.NET!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: comp.windows.ms
Subject: Re: Communications via Terminal
Message-ID: <13540@ncoast.ORG>
Date: 8 Apr 89 17:03:31 GMT
References: <11861@pasteur.Berkeley.EDU>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.windows.ms
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 26

As quoted from <11861@pasteur.Berkeley.EDU> by c9c-ct@dorothy.Berkeley.EDU (A SUN):
+---------------
| Is there any way the Terminal(or WINQVT) program in Windows 2.1 
| will recognize COM3?
+---------------

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.?

Thanks in advance.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser