My mouse lags very badly, when HDD activity happens. (I have Microsoft Desktop 6000 Wireless mouse)
Any ideas?
|
|
|||||||||||
|
|
You might have your hard drive in PIO mode. I say this because one of my friends had his hard drive in PIO mode and his mouse lagged all the time. Download and run the registry fix mentioned here: http://winhlp.com/node/10 Let me know if this was your problem, I hope it is! |
|||
|
|
|
My own solution to the problem of lag with wireless mouse, is not to use one. If you want your mouse to be responsive under conditions of heavy use, use a USB mouse. I just remark that a PS2 mouse is even more responsive, but very few computers today have the outlet. (The above reflects my personal experience, and might not be valid for all computer/mouse/driver combinations.) |
|||
|
|
|
My solution was to buy a USB extender cable so the transmitter is placed further away from the PC case. When there was a lot of activity on my HDDs, the mouse started lagging/stuttering. Anyone with this problem should give it a try. Could be your PC components interfering with the wireless USB mouse. |
||||
|
|
|
Take a look at the Windows Device Manager. Look for any red flags/indicators on any of the device icons. Pay particular attention to the disk drives and controllers. A flag here could indicate a resource conflict or a driver problem. I'm not sure whether this is still the case with Windows 7, but in earlier Windows versions, when a 32-bit disk driver somehow failed, Windows would revert to a 16-bit generic driver and the result was terrible performance and weird effects such as you describe. The solution may be a matter of finding and installing the correct disk system driver for the affected component, which might be the motherboard. How to access the Device Manager in Windows 7: It's also possible that it's a power-related issue. Disk access causes a spike in power use, potentially leaving peripheral devices (like a wireless USB mouse) with less power. But this is very unlikely; unless you have a lot of other power-hungry peripherals and/or an undersized power supply, it would tend to point to a faulty power supply. |
|||
|
|