Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!wuarchive!decwrl!shelby!portia.stanford.edu!earthsea.stanford.edu!gyugyi
From: gyugyi@earthsea.stanford.edu (Paul Gyugyi)
Newsgroups: comp.windows.ms
Subject: <None>
Message-ID: <1991Feb12.222208.2891@portia.Stanford.EDU>
Date: 13 Feb 91 04:16:34 GMT
References: <1991Feb12.190322.22184@gpu.utcs.utoronto.ca>
Sender: news@portia.Stanford.EDU (Mr News)
Organization: AIR, Stanford University
Lines: 47


 GMT
Message-ID: <1991Feb12.141634@earthsea.stanford.edu>
Reply-To: gyugyi@earthsea.stanford.edu (Paul Gyugyi)
Organization: Stanford University
Subject: Re: Windows and COM3
Keywords: mouse COM3

In article <1991Feb12.190322.22184@gpu.utcs.utoronto.ca>,
barry@gpu.utcs.utoronto.ca (Barry Lay) writes:
|> I have been following the discussion on the use of COM3 and COM4
with
|> applications in Windows.  Now, can the mouse be placed on COM3 so
that a
|> modem can go on COM1?  I have set up my PC with a modem on COM1, the
mouse
|> (Microsoft) on COM3, and COM2 missing (it is a bizarre serial card). 
Some
|> applications work fine (Shanghai, for instance) with the mouse, and
the modem
|> appears fine on COM1 now, but Windows will not recognise the mouse. 
Neither
|> will my own programs which use the mouse (under DOS, not Windows).  I
would
|> have thought that MOUSE.COM goes looking for the mouse on all of the
COMx
|> ports, then installs itself as INT 33 so that Windows doesn't have to
worry
|> about where the mouse really is.  Is it perhaps running into trouble
with 
|> the missing COM2?  If so, how do I fix this?
|> 
|> Barry

Two problems:
1) The missing COM2 port.  Check the FAQ sheet.  I remember hearing
that missing com ports might prevent higher ports from showing up.
If it is actually a problem, I've seen way to fix it.

2) Get a better bus.  COM1 and COM3 share the same interrupt
level.  This doesn't work very well on the normal AT ISA bus.
The big adavantage of EISA and microchannel are , IMHO, the hardware
support to let you share interrupt levels.

--
Paul Gyugyi
gyugyi@earthsea.stanford.edu