Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms
Subject: Re: Windows comes up to SLOW
Message-ID: <1101@venice.SEDD.TRW.COM>
Date: 20 May 91 16:33:16 GMT
References: <5185@czech.sw.mcc.com> <1991May17.172837.110@skyler.mavd.honeywell.com>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 18

In article <1991May17.172837.110@skyler.mavd.honeywell.com> eckert@skyler.mavd.honeywell.com writes:
>I agree with the person stating that having the mouse on com2 causes a
>delay.  I couldn't belive that this makes a difference, but I tried it and
>it totally eliminated the time the cpu spent doing something without
>accessing the disk.  Anyone know why Windows sleeps for a while on startup
>when the mouse is on com2?

(Expanding on my original post ...)

What I assume is going on is that Windows is looking to see where the
mouse is connected.  Although I don't have the details, there are a
fair number of places to check, including an inport mouse, two serial ports,
and a bus port.  There is a requirement to meet timeout limits when checking
for mouse presence, and apparently they are set fairly high for Windows
(higher than in the MS mouse.sys, I suspect).

-- 
Barry Press                                 Internet: press@venice.sedd.trw.com