I have Win7 x32 on my office desktop PC and recently I bought Microsoft Sculpt Ergonomic Desktop which consists of wireless mice, keyboard and numpad.
The communication between these input devices is performed via 2.4GHz transceiver (Microsoft … v9.0).
So, I plugged transceiver and turned on the devices, Windows started auto-detection and it successed.
However, the keyboard seemed to be "dead", since typing produced no text on the screen (in notepad). So I got the microsoft recommendations list and checked everything.
One of my next steps was installing Microsoft software for keyboard and mice management.
After reboot, I found an interesting behavior of the keyboard and numpad. When I pushed any button for the first time after reboot – it was okay, everything seemed to be nice (I checked caps, num, tried to type text (first letter was typed)), but only for the first key press.
After first key press several buttons are still functioning: calculator call, volume up/down/mute; but nothing happens when pressing other keys.
I also tested the devices on similiar PC (both DELL Optiplex 390, W7 x32, approximately same uptime) and everything was fine. So I came up with idea that there is some software conflict on my computer… which I don't know how to find and solve.
I will highly appreciate any thoughts on how to solve the problem, or how to diagnoze it.
Thank you beforehand.
Best Answer
I have one of these and have noticed that plugging the receiver into a 10cm usb extension cable massively improves the reliability of the signal , before doing this i would get random cutouts and lags. This also helps for my Logitech wireless mouse. The battery life for these devices is also improved.
I can only guess that the transmission pattern was not well thought out to escape the electromagnetic sweet nothings my computer seems to intimidating it with.
Whilst this sounds unscientific i have noticed this with both my laptop and hub combo and the desktop where i used to work. Both run linux but this should not make a difference as this behaviour was observed when controlling the BIOS as well.