J
Jack Watts
My Microsoft Wirless Optical Mouse has very slow response on clicks
(not on the move). When I installed it at the first time on Windows XP
I had this problem: When you click on buttons or links or menu items,
the click does not engage the action, not right away at leasl. Some
time if I hold button down it does the job, sometime I loose patience
and click several times on the button and it does the job. However the
dragging - works. This indicates that the button itself is ok.
Sometime you can see the button being depressed indicating that
Windows has received command from the mouse, but there's no action
behind the button, like "it was pressed but not all the way". When I
use keyboard on the same buttons, links, menus - everything works.
Here's "funny" part: I immideately tested mouse on other computers and
it works fine. I never had chance to test it on my computer because I
installed driver that come with the mouse before connecting the mouse
JUST LIKE MICROSOFT SUGGESTS !!! Apparently default drivers that build
in WinXP where perfectly fine.
I had to uninstall the driver, but UNINSTALL DOES NOT REMOVE ALL FILES
AND REGISTRY SETTINGS. I had to manually compare registry and remove
all trails of new driver.
Finally I fixed that computer with WinXP and it work fine for almost 6
months. Now I've got the same problem with another computer. I just
installed Windows 2003 Server on another machine. I knew about problem
with the driver, so I havent even tried to install the driver (nor it
would work since it is not designed for 2003). However immideately
after fresh install Windows 2003 Server I had this problem.
I have same mouse connected to 3 other computers via KVM switch and it
works fine on Win2000, WinXP (after removing original driver), and
another WinXP which always worked because I never installed driver.
At this time I can not fix my Windows 2003 because I never had chance
to use it with other mouse.
I posted this message to Windows XP group because I had same problem
on Windows XP once.
P L E A S E H E L P ! ! !
Sincerely,
Jack Watts
(fix my e-mail for reply)
(not on the move). When I installed it at the first time on Windows XP
I had this problem: When you click on buttons or links or menu items,
the click does not engage the action, not right away at leasl. Some
time if I hold button down it does the job, sometime I loose patience
and click several times on the button and it does the job. However the
dragging - works. This indicates that the button itself is ok.
Sometime you can see the button being depressed indicating that
Windows has received command from the mouse, but there's no action
behind the button, like "it was pressed but not all the way". When I
use keyboard on the same buttons, links, menus - everything works.
Here's "funny" part: I immideately tested mouse on other computers and
it works fine. I never had chance to test it on my computer because I
installed driver that come with the mouse before connecting the mouse
JUST LIKE MICROSOFT SUGGESTS !!! Apparently default drivers that build
in WinXP where perfectly fine.
I had to uninstall the driver, but UNINSTALL DOES NOT REMOVE ALL FILES
AND REGISTRY SETTINGS. I had to manually compare registry and remove
all trails of new driver.
Finally I fixed that computer with WinXP and it work fine for almost 6
months. Now I've got the same problem with another computer. I just
installed Windows 2003 Server on another machine. I knew about problem
with the driver, so I havent even tried to install the driver (nor it
would work since it is not designed for 2003). However immideately
after fresh install Windows 2003 Server I had this problem.
I have same mouse connected to 3 other computers via KVM switch and it
works fine on Win2000, WinXP (after removing original driver), and
another WinXP which always worked because I never installed driver.
At this time I can not fix my Windows 2003 because I never had chance
to use it with other mouse.
I posted this message to Windows XP group because I had same problem
on Windows XP once.
P L E A S E H E L P ! ! !
Sincerely,
Jack Watts
(fix my e-mail for reply)