rich@iwarp.intel.com (Rich Jolly) (09/08/90)
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 solution of using the "Mouse Systems or VisiOn Mouse on COMx" drivers will not work for my PS/2 port system (windows tries to fire up then dies). I tried to call Microsoft and the technical service recording warned me of a 30 minute wait on hold. Not wanting a long distance bill larger than the cost of the upgrade I decided to turn to the net. Any help will be greatly appreciated. Thanks in advance. Rich Jolly -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rich Jolly -- Intel Corp. | rich@iwarp.intel.com 5200 NE Elan Young Pkwy. CO4-03 | ...!uunet!iwarp.intel.com!rich Hillsboro OR 97124-6497 | Phone: (503)629-6321
griffin@sequoia.execu.com (Terry Griffin) (09/08/90)
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