Path: utzoo!attcan!uunet!aplcen!samsung!umich!umeecs!shim
From: shim@zip.eecs.umich.edu (Sam Shim)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Windows 3.0
Message-ID: <2447@zipeecs.umich.edu>
Date: 30 May 90 13:13:04 GMT
References: <62@altos86.Altos.COM> <9330008@hpihoah.HP.COM>
Reply-To: shim@eecs.umich.edu (Sam Shim)
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Lines: 22

In article <9330008@hpihoah.HP.COM> mj@hpihoah.HP.COM (Marlin Jones) writes:
>I had the same problem with the Logitech mouse.   It was caused by using the
>Logitech mouse driver in my config.sys file *and* trying to run windows.
>The work around is to not load the mouse driver - windows then boots (and the
>mouse works).   The problem is of course that non of your non-windows apps
>can use the mouse...

   I use the mouse.com driver and it works just fine under Windows 3.0.  My
guess is that there is a particular order in which drivers in config.sys have
to be loaded (probably himem.sys first), and loading them in the wrong order
can cause problems.  Running the mouse.com driver solves the problem, at
least for me.



 -----------------------------------------------------------------------------
|  Sam Shim                                   | "I didn't do it...            |
|  EECS Departmental Computing Organization   |  It wasn't me...              |
|  University of Michigan                     |  Nobody saw me do it...       |
|  Ann Arbor, MI 48109                        |  Nobody can prove a thing..." |
|  internet: shim@eecs.umich.edu              |  - Bart Simpson               |
 -----------------------------------------------------------------------------