Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!execu!sequoia!griffin
From: griffin@sequoia.execu.com (Terry Griffin)
Newsgroups: comp.windows.ms
Subject: Re: Mouse-on-drugs
Message-ID: <24003@sequoia.execu.com>
Date: 8 Sep 90 01:16:45 GMT
References: <1990Sep7.205624.27167@iwarp.intel.com>
Organization: Execucom Systems Corp.
Lines: 20

In article <1990Sep7.205624.27167@iwarp.intel.com> rich@iwarp.intel.com (Rich Jolly) writes:
>
>  I am experiencing the problem referred to on the net as the "mouse-on-drugs"
>effect.  At various times the mouse will begin racing across the screen randomly
>opening and closing windows.  If you stop moving the mouse you can still operate
>windows with the keyboard.  If I exit windows and restart, the problem goes 
>away - for awhile.  This problem occurs on by 286 Packmate II machine with a
>logitech mouse running on the PS/2 mouse port.  I have seen the problem with
>either the logitech or microsoft windows mouse drivers.  The previously posted
[remainder deleted...]

I, too, have witnessed the mouse-on-drugs effect on a Toshiba T5200 with
a Logitech mouse on COM2.  I discovered that if I run the Logitech mouse.com 
driver in DOS prior to entering Windows, it somehow resolved the problem.  I
realize this eats up supposededly unnecessary RAM from DOS apps, but I have
not had the problem since adding mouse.com to my autoexec.bat.  I don't know
if this technique will work with the mouse on the PS/2 mouse port, but it's
worth a try.

-Terry Griffin