Mice - Bluetooth

[superiorx]

I've read several older posts on the forums noting this problem, but I still haven't found a solution.

I have the MX5000 bluetooth desktop set that comes with the MX1000 bluetooth mouse. My Sony VAIO notebook with Win Vista 32bit comes built in bluetooth with the Toshiba Bluetooth stack (v.5.10.10), and I absolutely cannot get the SetPoint software (v.4.4) to recognize the MX1000 mouse when I have it paired with the Toshiba bluetooth stack. The keyboard is recognized fine in SetPoint, but the mouse is not recognized in SetPoint at all, thus disabling all the advanced features. When I look in Device Manager it lists the mouse as a generic HID compliant mouse, so thus the Logitech drivers are not getting installed properly.

I found some older posts that suggested editing some of the .inf files, but it seems with Vista (or the newer versions of SetPoint) that these .inf files don't exist anymore, I can't find them in the Logitech folder or anywhere else on the computer.

So does anyone have a solution for getting the MX1000 to work correctly with the Toshiba bluetooth stack and the newer version of SetPoint?

Thanks!

-Matt

[kleb]

I have exactly the same problem with my Dell Precision m6300 and MX5000 mouse & keyboard combo.  I can connect the mouse, but it shows up as a HID-compliant device and SetPoint does not detect it.  I have some custom button mappings that I really would like to set.

The keyboard, on the other hand, connects and Setpoint detects it just fine.

Logitech, could you look into this?

Message Edited by kleb on 03-13-2008 10:26 AM

[superiorx]

Yeah Logitech was absolutely no help in fixing the problem. I however found a way to end up fixing it myself. Here is what you do:

Go to the folder C:\Program Files\Common Files\Logishrd\CCDRV2\

Edit the file called LfMouHid.inf using Notepad or a similar text-only editor.

Find the section with the label ";------------- Toshiba BT IDs --------------------------" and add the following line at the bottom of that section and save the file:
%PID_B003.mouse.desc% = LOGIHIDMOUSE,HID\VID_046D&PID_B003&Col01

It's possible that your mouse might have a different PID, other than B003&Col01. You can check this by right-clicking on the HID-compliant driver entry in the device manager, selecting properties and then selecting the Details tab. Then select Hardware Ids from the combo box and you will see the proper PID in the first line. Use this to modify the first and last parts of the line from step 5.

Choose to Update the driver and select to install it from a specific location.

Choose "don't search" and hit next.

Click Have Disk... and navigate to C:\Program Files\Common Files\Logitech\CDDRV. Note that this is the location of the driver that you modified.

Hit OK and you should see that it finds a driver listed as Logitech MX1000 Bluetooth Laser Mouse. Choose it and hit next.

It will install whatever files it needs to for the driver, and now the mouse will appear in the SetPoint software and should operate properly, including functionality for all of the buttons.


That should be it. It worked for me. The problem is that Logitech doesn't support the Toshiba bluetooth stack, so thus by default the drivers aren't compatible. I was extremely disappointed that Logitech couldn't provide this solution for me. After hours of emails between me and their technical support the only answers I kept getting were to "reinstall set point" over and over. Like that is really going to fix the problem.

[kleb]

Wow! You just made my day

Thanks so much for figuring that out and posting.  Maybe Logitech will include that id in their next setpoint release.

Message Edited by kleb on 03-14-2008 08:52 AM

[Kiwipat]

Congratulations superiorx on solving this problem. I cannot understand why Logitech do not explain this. They restrict their market by forcing customers to either use their bluetooth dongle or to change their bluetooth stack.

The next question (there is always another question isn't there) is how to get the Media Pad in the diNovo Media Desktop fully working also. The Media Pad is a separate keypad with a three line LCD screen which also serves to control Windows Media Centre. It does work for Media Centre control already on my system but the additional functionality that would display info on the LCD screen does not work. I would like to apply the same technique for the Media Pad as described for the Mouse but cannot tell which inf file corresponds to the Media Pad. My CDDRV2 folder contains the following inf files:

LfHidHid.inf
LfHidUsb.inf
LfKbdHid.inf
LfMouHid.inf

It would be helpful to know which of these coresponds to the Media Pad or even which is present on a system which does not have a Media Pad.

Any help appreciated.

Kiwipat

[superiorx]

Hmmm... I've never had any experience with the Media Pad before... but I'd imagine that it might be under the LfKbdHid.inf file since the Media Pad is more like a keyboard than a mouse, but I'm not sure. The best thing I could suggest would be to find the PID number much like we did the mouse and try entering it as it's own line in the LfKbdHid.inf file, and then just seeing what happens. Just back up the file before you mess around with the lines.

I'll try looking further into it and post if I come up with anything.

[kleb]

Hmm, after using the mouse for a while, it doesn't seem that custom button mappings (which I can now set in SetPoint) do not affect the mouse's behavior.

Not sure what I can do at this point since the mouse is being detected in SetPoint...

[Tseng]

Well, the SetPoint 4.60 was released last week.  This issue still exists.!

[gokhart]

First post ;-)

I had similar problems. I am using a Toshiba U400 laptop running XP Pro SP2 and the Toshiba Bluetooth stack (v 6.10.02). The Logitech product I have is the DiNovo Cordless Desktop Laser for Bluetooth.

Until now I have used the bluetooth mouse and keyboard without installing SetPoint. However, I was unable to use extended features such as the additional function keys and so forth.

I downloaded SetPoint 4.6 from Logitech - the keyboard was recognized but not the mouse or media pad.

I followed SuperiorX's instructions above and edited the LfMouHid.inf file and updated the driver - MX1000 mouse was then recognized fine.

I then pressed the 'Connect' key on the underside of my media pad and ran the New Connection wizard in the Toshiba Bluetooth Settings utility - and that was recognized fine too ;-) As soon as they were paired SetPoint added the media pad tab.

Govind

[davejet]

I am using the Toshiba Stack ver 6.10.10 with windows xp SP2. Toshiba Portege MX700

I have Logitech MX1000 mouse and can get the BlueTooth Manager to recognise and connect to the Mouse, but the Mouse does NOT work and SetPoint Ver 4.6.122 does not see it and show the Mouse tab.

I tried to modifiy the LfMouHid.inf as instructed but it did not work.

Device Manger shows

Bluetooth HID Port Properties under Hardware IDS-----

Bluetooth\0004&0005

Bus Relations-========

HID\VID_046D&PID_B003&Col01\9&69201A5&4&0000

HID\VID_046D&PID_B003&Col02\9&69201A5&4&0001

I tried several varations of the LfMouHid.inf one with the exact as shown in this thread and then I udated the driver as shown but still get the message that "The wizard could not find a better match for your hardware than the software you currently have installed."

Then I tried it adding B003&Col02.

Nothing works.