Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!think!ames!haven!umd5!oppenhei
From: oppenhei@umd5.umd.edu (Richard Oppenheimer)
Newsgroups: comp.windows.ms
Subject: Re: terminal communications
Message-ID: <5799@umd5.umd.edu>
Date: 19 Dec 89 03:32:52 GMT
References: <8167@cs.yale.edu> <1989Dec13.063712.25818@polyslo.CalPoly.EDU>
Reply-To: oppenhei@umd5.umd.edu (Richard Oppenheimer)
Organization: University of Maryland, College Park
Lines: 25

In article <1989Dec13.063712.25818@polyslo.CalPoly.EDU> pdavid@polyslo.CalPoly.EDU (Erbivore) writes:
>keegan-edward@cs.yale.edu (Edward Keegan) would have us believe:
>>Does anyone (like MicroSoft for instance if they read this) have
>>an update to Windows 286/386 for the terminal application that permits
>>a baud rate of 9600?
>
>	In this same vein, does anyone know how to tell a
>	windows terminal app to talk to COM3:, which is
>	used by many internal modems for machines that
>	already have two serial ports?
>		-Paul.
>
>-- 
>Paul C. David		pdavid@polyslo.CalPoly.EDU

Alas there is no solution at this time. I spoke to MS about the
COM3: problem recently. Apparently alot of people have. They could
not give me a answer whether or not it would be supported by the time
version 3 is out. We can only hope!!!! I know it is still not supported
under 2.11

Richard Oppenheimer
oppenhei@umd5.umd.edu
Computer Science Center
University of Marland, College Park