c9c-ct@dorothy.Berkeley.EDU (A SUN) (04/03/89)
I am using an internal modem on COM3 (COM2 and COM1 are occupied by other peripherals, switching to a different COM is not an alternative) Is there any way the Terminal(or WINQVT) program in Windows 2.1 will recognize COM3? Thanks in advance, ----- A Sun (Mail replies to: c9c-ct@dorothy.Berkeley.EDU -or- ucbvax!dorothy!c9c-ct ) -----
allbery@ncoast.ORG (Brandon S. Allbery) (04/09/89)
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
plim@teknowledge-vaxc.ARPA (Pean Lim) (04/10/89)
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.