briggs@tamunix (Mark Lowe) (11/05/90)
I finally got things straightened out with this today. I actually had my mouse connected to a port that was configured as COM3, not COM2. The MSMOUSE driver evidentally can use ports other than COM1 and COM2, but Windows only likes it on one of these ports. Strangley enough, as I mentioned before, you can get the mouse to work in real mode as long as you start windows from a directory that contains the MOUSE.SYS file. Another interesting discovery... if you start Windows from a directory containing the MOUSE.DRV file, it will crap back out to the c: prompt after the opening screen. Explanation anyone? Seems like Windows and mouse drivers don't like each other so much!! Mark C. Lowe - KB5III