Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!pacbell.com!pacbell!pb2esac!mavanamm
From: mavanamm@pb2esac.UUCP (Marnix A. van Ammers)
Newsgroups: comp.windows.ms
Subject: Re: Win3.0 vs. LogicTech Mice
Keywords: mouse Win3.0
Message-ID: <255@pb2esac.UUCP>
Date: 29 Aug 90 16:55:00 GMT
References: <589@eds1.UUCP>
Reply-To: mavanamm@pb2esac.UUCP (Marnix A. van Ammers)
Distribution: comp
Organization: Pacific Bell ESAC SCCS support
Lines: 43

In article <589@eds1.UUCP> cdh1@eds1.UUCP (C. Daniel Hassell) writes:
>Maybe the world already knows about this, but we have found a bug in
>the standard Win 3.0 driver for LogicTech mice.  Gateway 2000 used
>to ship these mice to us with their systems (they have since switched
>to MS rodents).  The problem is that when you open a non-Windows
>app, in our case Lotus Symphony, and then close it and return to 
>Windows, the mouse goes bananas: the smallest movement will resize
>all of the open windows, execute commands at random, open files, close
>files, etc.  All of this excitement occurs without touching the mouse
>buttons.  We have dubbed this the mouse-on-drugs effect.
>
>The keyboard works normally and can (must!) be used to 
>quit Windows.  Restarting Windows is enough to restore order.  By the
>way, this happens in 386 enhanced mode.
 ...
>Anyway, if you reset the mouse driver (under Windows Setup) to read
>"Mouse Systems or VisiOn Mouse on COMx" then it will work.
>
Yes!  My God, I've been having this exact same problem and it's been
driving me nuts!  What's been especially bothersome is that whenever
I freshly install Win3.0 (I've done this about 10 times already), the
problem is gone, at least for a while.  I change nothing, and sooner
or later if I switch to DOS and back, then I've got this problem.  I
do have to touch the mouse for it to go bananas, but I don't have to
touch any buttons.  If I restore my \windows directory to its exact
original state (by copying everything back from a tape I made right
after initial installation when things were working), then I *still*
had the problem.  But if I reloaded Win3.0 from the floppies using
setup.exe, then my problem would be gone (for a couple of hours of
use or so).

I finally decided to check the NET and see if there were any articles
about mouse problems, and there it is!  I sure hope the fix mentioned
above will work.

I also still have some slight problem with little colered specks
on my screen especially when I'm running at 20 Mhz (instead of 8 Mhz),
and moving colored windows around.  Gotta check for articles on that.
Netnews came through!  Great!

--
Marnix A. van Ammers
...!pacbell!pttesac!mavanamm