01-08-2007 03:37 PM
Bought this one cause I really liked my diNovo with the MX900 mouse and wanted to pass it on to my wife. The new MXLaser mouse feels great.
However, I've been having some oddball connection issues at first on a couple computers and I decided to install winxp fresh on a spare drive I had lying around. WinXP is SP2 and all patched up.
I plug in the BT receiver and get the generic USB HID device detection and install. Following the connect procedure under the keyboard, I get the keyboard and media pad connected no problems but the mouse does not connect. It's fully charged. No amount of pressing the connect buttons (receiver and mouse) seems to solve the issue.
Also the CTRL buttons on the keyboard doesn't work. Great fun when trying to press CTRL-ALT-DEL to log on All other buttons seem to be ok.
Many thanks for your time.
01-08-2007 09:21 PM
01-08-2007 11:05 PM
Thank you for your reply.
Infact that is what I've already done. It's what I always do when I have problems. I know my first generation dinovo works without setpoint drivers installed and I expected this one to work in a similar fashion.
So my test and results are from a completely clean windows xp install with just the basic windows detecting and installing a generic HID device when I plugged in the BT receiver (Embedded mode as you described). No setpoint drivers are installed at all.
The CTRL key does not work and the mouse does not connect at all. The Media pad connected ok.
01-08-2007 11:13 PM
Hope this information helps
Hope this information helps
01-09-2007 03:17 PM
01-23-2007 01:33 PM
It works normally under windows in embedded mode, but after install installing Setpoint 3.15bt and the Widcomm bluetooth stack from logitech for both Windows XP x64 and on another machine using just XP SP2, only the mouse works properly. The keyboard and media pad cannot get connection past the enter security pin correctly. The Widcomm driver gives back error pairing the Media pad or keyboard.
I also tried uninstalling and then choosing to not install the Widcomm bluetooth software stack, now I can get the keyboard and media pad to be recognized by the setpoint. However the mouse won't work and trying to connect it disconnects everything.
Now suspecting that it's either a driver thing or hardware problem, I tried connecting the keyboard and media pad to a Playstation 3's native bluetooth controller runnning under linux with the blueZ bluetooth stack, and the secure connection worked fine. I noticed that the mediapad will display the dialog for entering pin, but it doesn't show up in Windows under the Logitech / Widcomm bluetooth stack. So I think it's a driver problem.
Any ideas on how to remedy it? or perhaps will the upcoming Setpoint 3.3 fix it?