Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!wuarchive!uunet!olivea!oliveb!amdahl!rtech!dosbears!mikel
From: mikel@dosbears.UUCP (Mike Lipsie)
Newsgroups: comp.windows.ms
Subject: Re: Windows Termininal...
Message-ID: <283@dosbears>
Date: 3 May 91 18:54:35 GMT
References: <12845@aggie.ucdavis.edu> <12848@aggie.ucdavis.edu>
Reply-To: dosbears!mikel@ingres.com (Mike Lipsie)
Organization: DOS Bears
Lines: 25

In article <12848@aggie.ucdavis.edu> cccstevn@underdog.Ucdavis.EDU (Steven T. Ansell) writes:
>The com port problem has to do with the way Windows 3.0 handles
>serial ports.  There is a program that attempts to fix this called
>setcom.  I have not tried it because I have no need for such a 
>program.  You can attain it from cica.cica.indiana.edu by 
>anonymous ftp in the directory pub/pc/win3/uploads.  

I think this is covered in the FAQ in more and better detail, but...

If you are using an "old" version of DOS (before 3.1?), it does not
recognize COM3 and COM4 and setcom might help.

If you are using a recent version of DOS (I use 3.30), the problem is
that IBM was a follower not a leader.  There is no standard for the
comm port addresses.  So Windows (Microsoft) had to choose one.  I
don't know whose they chose but a LOT of people use other addresses.

The answer is in your SYSTEM.INI file.  Check the SYSTEM*.TXT files
for the details but basically you need to alter the COMnBase to match 
the address that your card actually uses.


--
Mike Lipsie
mikel%dosbears.uucp@ingres.com