1.

Solve : Wireless Mouse Issue?

Answer»

Quote from: Geek-9pm on July 10, 2015, 09:30:50 PM

No, you n are wrong. Mice are cheaper that motherboards.
If I said that Mice were more expensive than motherboards, I would certainly agree that I was wrong. However, given that I've said absolutely nothing about motherboards, or suggesting buying a new motherboard, since the motherboard isn't even relevant, so I'm afraid I have to disagree. Not buying anything, and instead ISOLATING the actual problem is even cheaper.

Quote
It's the mouse.

Testing one  mouse on on two computers is not an acceptable verification.
For a true test, you need at least five five computers and as meany mice. Now if four out of five mice failed on just one PC, you might say the PC is bad. But the done mouse that worked would be a piratical solution for the defective PC.
I'm afraid there may be a miscommunication here. Very little of what you have suggested seems very logical.

If you have a peripheral with an issue, and you are able to connect it to another system and the issue goes away, this is a incredibly strong indicator that the issue is unrelated to the DEVICE. Strong enough to rule out the device as a 'suspect'. If we apply your suggested logic to any number of peripherals we can see how silly it appears. If somebody has an issue with the monitor not showing a picture, but the monitor works fine with another system, following your logic they would need to test five computers and at least as many monitors to determine that the issue is not the monitor in question, which is of course ridiculous. Using a device on another system and verifying that it works is a perfectly well established and logical course of action in determining that the device itself is functioning properly.

The root of the problem is the mouse can not reject ELECTRICAL (radio) interference
coming from the motherboard. Better mice can. Weak mice don't.

My logic is sound and it is for wireless mice, not for other peripherals. Other peripherals do not use radio frequency in close proximity to the computer.
Retrofitting a motherboard that does not WORK with wireless mouse is a time-consuming endeavor. A manufacturing firm can do that kind of research, Burt for the average user the protocol is much to hard to carry out.

Burt if the OP is a professional Electronic Engineer E or a super tech, and has the laboratory equipment, I will do a summary of the work and testing needed to clean up the motherboard. The cost for a single unit is more that the cost of a new computer.

He will need a spectrum analyzer and a RF probe for UHF.


Quote from: Geek-9pm on July 11, 2015, 12:06:11 AM
The root of the problem is the mouse can not reject electrical (radio) interference
coming from the motherboard. Better mice can. Weak mice don't.
On what basis do you make the claim that the source is interference coming from the motherboard? You have posted a number of links; none of which would appear to substantiate what you are saying. WITHIN them there are people who fixed their problem by trying a different port; several others have fixed it by no longer using a mouse pad they were using, and there is a lot of speculation. Some of the posts in the linked threads are gibberish. "I believe it was my interface drivers causing system interrupts which were peaking my processors. ". Another of the links has the user describing that the issue was that they had the mouse sensitivity in control panel too high.

None of the links you provided support the claim that this is interference from the motherboard. The Original Poster didn't even mention their Motherboard Model #. You are operating on baseless assumptions.




Quote from: Geek-9pm on July 11, 2015, 12:06:11 AM
The root of the problem is the mouse can not reject electrical (radio) interference
coming from the motherboard. Better mice can. Weak mice don't.

He will need a spectrum analyzer and a RF probe for UHF.

I will see what our scope meter does at work

I'm inclined to believe that this is a software/firmware issue as the interference is always after a protracted period of time. Then again if I really knew then I wouldn't be here. Quote
software/firmware issue as the interference is always after a protracted period of time.
Can you document the time periods?
Also, can you reproduce this behavior in safe mode?


Discussion

No Comment Found