Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!spool.mu.edu!sol.ctr.columbia.edu!cunixf.cc.columbia.edu!liggio
From: liggio@cunixf.cc.columbia.edu (Vincent J. Liggio)
Newsgroups: comp.windows.ms
Subject: Re: Problems with Logitech mouse
Message-ID: <1991Feb6.144109.6666@cunixf.cc.columbia.edu>
Date: 6 Feb 91 14:41:09 GMT
References: <ROWHI.91Jan30133457@hulk.hut.fi> <5500@bwdls58.UUCP> <1352@aut.autelca.ascom.ch>
Reply-To: liggio@cunixf.cc.columbia.edu (Vincent J. Liggio)
Distribution: comp.windows.ms
Organization: Columbia University
Lines: 26

In article <1352@aut.autelca.ascom.ch> nbladt@aut.autelca.ascom.ch (Norbert Bladt) writes:
>mlord@bwdls58.bnr.ca (Mark Lord) writes:
>Fine !
>BUUUUUTTTTTT:
>Ever used software outside of windows which uses the mouse, e.g.
>PC shell ???
>After using that, the mouse is set to Logitech mode. Try using
>Windows 3.0 after that !!!
>(You can make it work again by resetting the mouse - power on. For that
>you have to unplug the mouse and plug it in again :-)  (Just a
>warm reboot won't work, because the mouse is not re-set.) I have
>done that plug-out plug-in game for over six month for OS/2 ! Is there an
>OS/2 mouse driver, yet or will they wait several YEARS for writing a driver
>for that as they waited almost several years for a driver which supports
>standard VGA ?)

Two solutions for that:

Either install the mouse.com driver in your autoexec.bat file that seems to
take care of the DOS access problem.  I had the same problem whe I was
using the old windows lmouse.drv.

Or: Get the v5.00 software disk from Logitech, which includes a special
Logitech windows driver.  Then you won't have the above problem.

Vince