MS IntelliPoint & WIDCOMM work!!!

[LION_III]

Hi all,

first of all I would like to say that only when reading these forum threads I could finaly get my MS BT Desktop (Dongle/Mouse/Keyboard) to work with my SE HBH-35 BT Headset (using the hacked WIDCOMM drivers). So a big thanks to all ;) !!

But there is a drawback if you use the WIDCOMM drivers. The Intellipoint software stops working and you can't modify the button assignments of your MS mouse or enable the accelerated scrolling etc, leaving the mouse to the default settings e.g. the thumb buttons are Forward - Back no matter what you set in the Intellipoint applet. This is because the filtering driver (point32.sys) and its user-mode application (point32.exe) don't load.

Well there is actually a workarround to this "problem". :eek: If you have already installed the Intellipoint software go to: "C:\Program Files\Microsoft Hardware\Mouse" and open "point32.inf" using a text editor (e.g. Notepad).

You should find 3 times the string:_VID&0001045e_PID& and replace it with:&VID_045e&PID_ in all 3.

Save "point32.inf" and exit the text editor. Then go to "Device Manager-->Mice and other pointing devices" and right click on the "HID-compliant mouse" and choose "Update Driver...". Do an "Advanced" update of the current driver and "Browse..." for the file you just edited, "point32.inf". Install the driver and if you have turned ON the alerts for digitaly signed drivers, the system will alert you, just click on "Install Anyway". After that the mouse is correctly recognised by Windows and the only thing left is to manually run (only for the first time) "point32.exe" in "C:\Program Files\Microsoft Hardware\Mouse" (just double-click it). And there you go ;) . Intellipoint runs gracefully again !! One last point is to make sure that "point32.exe" is in your startup list so that it loads every time you boot. If it isn't, just put it in your startup folder.

Enjoy!!!

[Phantasm4489]

Nice! I'm impressed, how did you figure that out?

[LION_III]

Nice! I'm impressed, how did you figure that out?

I was really happy that I could get all my BT devices to work with the WIDCOMM drivers but at the same time really upset :mad: that I lost the customization of the extra mouse buttons (have them as COPY - PASTE). To make a very very long story short among the many things I tried is opening the point32.inf and reading it.

Windows Drivers 101: The .inf is a script that says Windows what to install and where to install it. The actual drivers are (mainly) .sys files. In order for a device to properly work, the .inf may tell Windows to install more than 1 driver (in the case of the MS BT mouse the .inf installs 4 drivers). Also, the .inf has a string that contains the HardwareID of the device you wish to install which is saved in registry. Let's say that a newer driver version of your graphics card is out and you want to install it. When you try installing it, Windows will compare the HardwareID of the previous driver (registry) with the one in your new .inf and if the two match will proceed in installing the new driver.

Windows Bluetooth Drivers 101: In order to aid in driver development, reusability and ease of functionality, when you install a BT device in your pc, Windows create a virtual device (in the case of a BT mouse it creates a HID device). This gives the "impression" to Windows that the device is directly connected to the pc and not through another device (BT adapter). Also, this has the advantage of reusing existing drivers for this device. In this case it uses the USB mouse drivers (mouclass.sys and mouhid.sys).

(this is taking longer than expected :eek: )
When the WIDCOMM drivers are installed, the mouse drivers that Windows installs are only 2 (mouclass.sys and mouhid.sys), but luckily the same 2 out of 4 as those described in the point32.inf. Now, by looking at the remaining 2 drivers (point32.sys and ipcoin1.dll) that were not installed, I realised they were high up in the driver chain mainly used for filtering. This is important because it means that the WIDCOMM drivers would still be able to communicate with the mouse even if all 4 were installed. Finally, if you look under which HardwareID (registry) the mouse is installed and compare it to the one in point32.inf you will notice a slight difference. So if you make the 2 match, Windows will install the point32.inf (see above) and everything will continue to function. But when that happens, IntelliPoint (point32.exe) will be able to run.

Thats it.... :D

[Phantasm4489]

Thanks for the detailed description, im sure that will be useful for others as well.

[derek_bartram]

Hi all,

first of all I would like to say that only when reading these forum threads I could finaly get my MS BT Desktop (Dongle/Mouse/Keyboard) to work with my SE HBH-35 BT Headset (using the hacked WIDCOMM drivers). So a big thanks to all ;) !!

But there is a drawback if you use the WIDCOMM drivers. The Intellipoint software stops working and you can't modify the button assignments of your MS mouse or enable the accelerated scrolling etc, leaving the mouse to the default settings e.g. the thumb buttons are Forward - Back no matter what you set in the Intellipoint applet. This is because the filtering driver (point32.sys) and its user-mode application (point32.exe) don't load.

Well there is actually a workarround to this "problem". :eek: If you have already installed the Intellipoint software go to: "C:\Program Files\Microsoft Hardware\Mouse" and open "point32.inf" using a text editor (e.g. Notepad).

You should find 3 times the string:_VID&0001045e_PID& and replace it with:&VID_045e&PID_ in all 3.

Save "point32.inf" and exit the text editor. Then go to "Device Manager-->Mice and other pointing devices" and right click on the "HID-compliant mouse" and choose "Update Driver...". Do an "Advanced" update of the current driver and "Browse..." for the file you just edited, "point32.inf". Install the driver and if you have turned ON the alerts for digitaly signed drivers, the system will alert you, just click on "Install Anyway". After that the mouse is correctly recognised by Windows and the only thing left is to manually run (only for the first time) "point32.exe" in "C:\Program Files\Microsoft Hardware\Mouse" (just double-click it). And there you go ;) . Intellipoint runs gracefully again !! One last point is to make sure that "point32.exe" is in your startup list so that it loads every time you boot. If it isn't, just put it in your startup folder.

Enjoy!!!

If you have problems getting the widcomm drivers working, look in the admin panel>services... If the Bluetooth service is listed, you can then install the MS Intellipoint software [including the WinXP Bluetooth patch], and it might work [did for me]. I don't know where you get the "Bluetooth Perifarble Device" driver tho [for connection phones etc] tho :rolleyes:

[Kruemel]

Hello,

I have successfiully installed the Widcomm driver under Win2k.
But now I am discovering the problem that I cannot programm the button of my mouse.
The soulution with the edit of the oint32.inf soes not work, because I get an error message from Win2k that there is no driver found!
Is ther a solution to make IP 5 Work with WIn2k oder an edit with IP 4.9 [Org-CD]?

Kruemel

[leemperor]

I don't know why Win2k can't find a driver - perhaps this method doesn't work with Win2k. If you have the microsoft driver on the intellipoint CD then perhaps you could try installing it in "co-operation" with the Widcomm software. I have added a section that may work for this...

http://www.jonscaife.com/bt/details.html#microsoft

Good luck and please let us know how you get on! :)

[Kruemel]

SOrry, but i think you got something wrong.
The BT-Stick from MS is successfully installed!
the only problem i am discovering at the moment is that I am unable to Programm the mouse button with the IntelliPoint (IP) 5 Software.
THe Hack to modify the point32.inf does not work!
But I am unable to install th IP 4.9 from the ORg. CD, because I got the Message, OS not supportet!.
The setup finishes automatically without installing anything!

Is the a solution to get the IP to work under WIn2k to be able to programm the Mouse buttons?

[Little_rU]

IntelliPoint 4.9 from the CD supplied with MS dongle/mouse can be installed under Win XP _only_.
On the other hand, MS bluetooth mouse is not supported in IntelliPoint 5.0.
So Win XP is your only chioce if you want to use IntelliPoint with bluetooth mouse.

[LION_III]

I would like to confirm that the point32.inf hack works ONLY with Intellipoint 4.9 and WinXP because Win2k doesnt natively support bluetooth and Intellipoint 4.9 can only be installed on WinXP.
Thats Micro$oft for ya :rolleyes: !!

[Palimpalim]

so, if anybody have information how to get the Logitech MX-900 to work fully (800 DPI, _all_ mousebuttons working) without the Logitech-Hub let me know.

Thank you, Palim

[jdi]

yes, it works
i am appreciated.
thanks, lion

[pcristi]

IntelliPoint 4.9 from the CD supplied with MS dongle/mouse can be installed under Win XP _only_.

MS bluetooth mouse and IntelliPoint 5.2. work perfectly, not need Lion tips
with Widcomm 3.0.1.905 or Microsoft XP SP2 driver.

PS. thanks Lion at Feb. 2004 with Widcomm 1.4.3.4 and IntelliPoint 5.0 is was good tips. I used.

Kryss

[icomm]

I have a dell D800 with internal BT Card i can not seem to pair my MS Intellipoint Mouse I have an error in device manager i.e. Bluetooth Virtual Mouse. I am running the latest WIDCOM drivers from the dell site and also downloaded the latest drivers for the mouse from MS.

I can discover the mouse but will not pair. :confused:

Do you have any ideas?

[samPROlogic]

I have billington PCMCIA card, everything works - I connected IntelliMouse and Keyboard. Really cool! Before I read this, I spent 3 days with no results, thanks to YOU, in 3 hours I am complete!

For others - if your device name doesn't change, try a little bit different way: update driver -> No, not this time (do not connect to internet) -> Instal form a list ... -> Don't search, I will ... -> Microsoft wireless ...

Really, if the one doesn't change the device name in point32.inf and type32.inf, than choice 'Microsoft wireless ...' is not displayed.

Once more, much thanks to the author!

[b00t1e]

Hi all,

You should find 3 times the string:_VID&0001045e_PID& and replace it with:&VID_045e&PID_ in all 3.


Yes, I know this is a very old thread, but I had tried to apply this fix and at first it didn't work for me. I have the Microsoft Intellimouse Explorer for Bluetooth (apparently the second/latest bluetooth model). I did find out that if you replace this string:_VID&0002045e_PID& instead of this string:_VID&0001045e_PID& it works great.
Thanks for coming up with this fix! I was worried I'd have to stick with MS BT stack!

[adisor19]

Yes, I know this is a very old thread, but I had tried to apply this fix and at first it didn't work for me. I have the Microsoft Intellimouse Explorer for Bluetooth (apparently the second/latest bluetooth model). I did find out that if you replace this string:_VID&0002045e_PID& instead of this string:_VID&0001045e_PID& it works great.
Thanks for coming up with this fix! I was worried I'd have to stick with MS BT stack!

This is a VERY important thread and i wish i could mod it 5 stars !

You are right, for the sercond edition of the mouse, the string that you mentioned needs to be modified instead of the old one and the rest of the initial instructions apply. This is even valid for the very last version of the IntelliPoint software : v 5.4 wich is not even available to dl from micorsoft's site for the old BT mouse.. just google it instead if you need to get it.

Again, awesome thread that should be modded up as it still applies to this day !

Adi

[adisor19]

Quick update,

I've just tested this with version 5.5 of intellipoint and it works perfectly still :)

Adi

[angel1st]

Hi All,
I found this thread those days, and as long as I experience the problems re-assigning MS mouse buttons apart of default functions I am interested.
I have WIDCOMM v.3.0.1.900 and MS IntelliPoint 5.5 drivers installed.
I followed the instructions:
1. Edit point32.inf file, replacing _VID&0001045e_PID& with _VID&0002045e_PID& (in fact it was in "C:\Program Files\Microsoft IntelliPoint" directory).
2. Go to Device Manager, "Mice and other pointing devices", expand the node. First thing I noticed is that I have two "HID compliant mouse" nodes.
3. Any way - I right clicked the first one, choose "Update driver...", "No this time", "Next";
4. "Install from a list or specific location (Advanced)", "Next"
5. Choose "Don't search. I will choose driver to install", "Next"
6. On the next tab push "Have Disk..." button, navigate to "C:\Program Files\Microsoft IntelliPoint" and choose the point32.inf file.
7. Push "OK" button. I have got the following message "The specified location doesn't contain information about your hardware" :confused:
So I am not able to update "HID mouse driver". Please help :(

[adisor19]

Hi All,
I found this thread those days, and as long as I experience the problems re-assigning MS mouse buttons apart of default functions I am interested.
I have WIDCOMM v.3.0.1.900 and MS IntelliPoint 5.5 drivers installed.
I followed the instructions:
1. Edit point32.inf file, replacing _VID&0001045e_PID& with _VID&0002045e_PID& (in fact it was in "C:\Program Files\Microsoft IntelliPoint" directory).
2. Go to Device Manager, "Mice and other pointing devices", expand the node. First thing I noticed is that I have two "HID compliant mouse" nodes.
3. Any way - I right clicked the first one, choose "Update driver...", "No this time", "Next";
4. "Install from a list or specific location (Advanced)", "Next"
5. Choose "Don't search. I will choose driver to install", "Next"
6. On the next tab push "Have Disk..." button, navigate to "C:\Program Files\Microsoft IntelliPoint" and choose the point32.inf file.
7. Push "OK" button. I have got the following message "The specified location doesn't contain information about your hardware" :confused:
So I am not able to update "HID mouse driver". Please help :(

What version of the mouse do you have ? the old one or the new one with the horisontal wheel scrolling ?

Adi

[angel1st]

The new one - I have horisontal scroll feature. One more thing - yesterday I updated my WIDCOMM drivers, so now I have WIDCOMM 5.0.1.801 version. Nevertheless I still cannot update mi HID driver according to described procedure.
Any ideas?

[adisor19]

The new one - I have horisontal scroll feature. One more thing - yesterday I updated my WIDCOMM drivers, so now I have WIDCOMM 5.0.1.801 version. Nevertheless I still cannot update mi HID driver according to described procedure.
Any ideas?

Heh, i just realised your mistake. Check out the post by b00t1e just on the top of this page. Since you have the new mouse, you should replace the string : _VID&0002045e_PID& with the following string : &VID_045e&PID_


You should find 3 instances to replace in the file.

Adi

[angel1st]

OK I did it. It works. Thanks a lot!!!
One new "issue" I just discovered - when I opened MS Mouse dialog, where I can re-assing buttons and if I click on "Bluetooth" tab, after closing the dialog either by "OK" or "Cancel" I have got the following message "Run a DLL as an App" with "Close Message" button. After I closed the message box I have got standard Windows error report message box. Any ideas?

[adisor19]

OK I did it. It works. Thanks a lot!!!
One new "issue" I just discovered - when I opened MS Mouse dialog, where I can re-assing buttons and if I click on "Bluetooth" tab, after closing the dialog either by "OK" or "Cancel" I have got the following message "Run a DLL as an App" with "Close Message" button. After I closed the message box I have got standard Windows error report message box. Any ideas?

Never seen that happen.. did you do an upgrade of intellipoint or a fresh install ?

Adi

[Walt]

Hi all,

first of all I would like to say that only when reading these forum threads I could finaly get my MS BT Desktop (Dongle/Mouse/Keyboard) to work with my SE HBH-35 BT Headset (using the hacked WIDCOMM drivers). So a big thanks to all ;) !!

But there is a drawback if you use the WIDCOMM drivers. The Intellipoint software stops working and you can't modify the button assignments of your MS mouse or enable the accelerated scrolling etc, leaving the mouse to the default settings e.g. the thumb buttons are Forward - Back no matter what you set in the Intellipoint applet. This is because the filtering driver (point32.sys) and its user-mode application (point32.exe) don't load.

Well there is actually a workarround to this "problem". :eek: If you have already installed the Intellipoint software go to: "C:\Program Files\Microsoft Hardware\Mouse" and open "point32.inf" using a text editor (e.g. Notepad).

You should find 3 times the string:_VID&0001045e_PID& and replace it with:&VID_045e&PID_ in all 3.

Save "point32.inf" and exit the text editor. Then go to "Device Manager-->Mice and other pointing devices" and right click on the "HID-compliant mouse" and choose "Update Driver...". Do an "Advanced" update of the current driver and "Browse..." for the file you just edited, "point32.inf". Install the driver and if you have turned ON the alerts for digitaly signed drivers, the system will alert you, just click on "Install Anyway". After that the mouse is correctly recognised by Windows and the only thing left is to manually run (only for the first time) "point32.exe" in "C:\Program Files\Microsoft Hardware\Mouse" (just double-click it). And there you go ;) . Intellipoint runs gracefully again !! One last point is to make sure that "point32.exe" is in your startup list so that it loads every time you boot. If it isn't, just put it in your startup folder.

Enjoy!!!

Wow, I had almost give up! But with the help of some really smart people in this thread, I got it working!!!! :)

The differences from the instructions LION_III posted (quoted above) that I had to do to get it to finally work are:


Since I had the v2 mouse, I had to instead replace the string _VID&0002045e_PID&. Thanks b00t1e !!! ;)

And I had to "force" the driver to replace the "HID-compliant mouse" by (1) "Install from a list or specific location (Advanced)", "Next" (2) Choose "Don't search. I will choose driver to install", "Next" (3) On the next tab push "Have Disk..." button, navigate to "C:\Program Files\Microsoft IntelliPoint" and choose the point32.inf file. Thanks angel1st !!! ;)
You all are great! :D

[adisor19]

Just a quick update to confirm that this trick still works with the newest version of Intellipoint 5.5 :)

Adi

[LION_III]

very happy to see that my more than 2 year-old post is still useful.
I'll continue to watch out for this thread.

[adisor19]

very happy to see that my more than 2 year-old post is still useful.
I'll continue to watch out for this thread.

Yep, trick still works with version 6.1 :)

Adi

[playtowin]

Does this work with Intellipoint 6.2? I have the MS Bluetooth Notebook Presenter Mouse 8000 on a Dell X1 with internal Bluetooth using the Toshiba stack. After I make the changes to point32.inf and try to reload the driver it says it can't find a compatible device. I notice that there is also a point32k.inf in the "c:/windows/program files/microsoft intellipoint" folder. Also, there is not a point.exe file in the folder but there is an ipoint.exe.

Any suggestions?

[me2d09]

Hi,
at first thanks to LION_III and b00t1e.
I have Microsoft Wireless Mouse 8000 with HP notebook nc6400 (widcomm stack). After applying your trick it starts working except of horizontal scrolling. This feature works OK without using IntelliPoint 6.1 software, but after changing .inf file, it doesn't work anymore.
Have you got any suggestions?

[sunwei]

Does this work with Intellipoint 6.2? I have the MS Bluetooth Notebook Presenter Mouse 8000 on a Dell X1 with internal Bluetooth using the Toshiba stack. After I make the changes to point32.inf and try to reload the driver it says it can't find a compatible device. I notice that there is also a point32k.inf in the "c:/windows/program files/microsoft intellipoint" folder. Also, there is not a point.exe file in the folder but there is an ipoint.exe.

Any suggestions?
On my Dell 640m the driver can still be installed when I replaced the Hardware-ID with the one I found in my rigistry file, and Microsoft IntelliMouse Explorer for Bluetooth was showed in the device manager. Everything seemed ok but I still got the error message when opening IntelliPoint and couldn't modify the buttoms...

Anyone has an idea?

[Nickywan]

Great thread !

I m using MS wireless laser mouse 8000 and a dell M90 with the bluetooth motorola stack and it works great on Intellipoint 6.x :cool: . I think i found a easy method to install all the microsoft wireless bluetooth mices. You just have to insert two new lines in the point32.inf.



- First go to the device manager and then open the property of the connected "HID compliant mouse" (Easy to locate by switch on / switch off the mouse) in the mouse branche.

- In the "details" tab you will find all the needed information to built your own "driver"

HID\VID_045E&PID_0702&COL02\...


- Edit point32.inf then find a line beginning with the same vendor ID (VID_045E) and ending with your mouse description:

HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"


- The trouble comes from the different Product ID (Pid_0714). Copy this line and insert it just after the line above. And now you will two same lines:

HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"
HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"


- Edit the second line and change the product ID (Pid_0714) and set it as the Product ID (PID_0702) the details tab.

HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"
HID\Vid_045E&Pid_0702.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"


- Now search for an other line (at the beginning of the file) contains HID\Vid_045E&Pid_0714

%HID\Vid_045E&Pid_0714.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_0714&Col02


- Copy this line and insert the new one just after it.

%HID\Vid_045E&Pid_0714.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_0714&Col02
%HID\Vid_045E&Pid_0714.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_0714&Col02


- Edit the second line and set the right Product ID (PID_0702) twice :

%HID\Vid_045E&Pid_0714.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_0714&Col02
%HID\Vid_045E&Pid_0702.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_0702&Col02

- Save the file

- Then replace the driver of the "HID compliant mouse" as explaining in this thread. Don't pay attention to the windows warnings for the non thrusted driver,etc...:o
At this time your mouse should be work perfectly.;)


Nickywan

[Aqualinx]

First off, thanks to LION_III and Nickywan for their thoughtful entries! Any thoughts or suggestions are greatly appreciated! I apologize for the length of this post, but I have tried to be thorough.

I have an HP Compaq nc6400 that I bought late July 2006. I purchased and installed today Microsoft Wireless Laser Mouse 8000 Model 1062 along with the provided Intellipoint v 6.1 software. While I can get the mouse to work, I cannot assign buttons nor does autoscroll work.

I have tried first LION_III's original suggestion, then Nickywan's suggestion, and then I tried uninstalling Intelipoint, ran HP Update and installed all recommended drivers and tested my hardware sucessfully. I then restarted, ran JV16 2007 registry cleaner a couple times, compacted the registry, and restarted.

I then reinstalled Intellipoint 6.1, re-editted "point32.ing" under "C:\Program Files\Microsoft Intellipoint" with the three "Pid_0714" to "Pid_0702" edits, saved, and recieved "The specified location does not contain information about your hardware." dialog box when I tried to manually install the driver, the same as I recieved when I first tried these suggestions prior to updating/restarting/cleaning/etc. I have also tried placing the edits before the line with "Pid_0714" vs. after (prob. sounds silly - I'm a noob when it comes to driver .inf files, but worth a try I thought).

Again, I would be very grateful for any help or suggestions. I have been working on this for several hours and now it's become a point of frustration/stubbornness for me.

Thanks!
Aqualinx

[wlumm]

Did you ever find an answer for this, Aqualinx? I am having the exact same problem.

I am using the Microsoft Wireless Notebook Presenter Mouse 8000 on a Dell Inspiron E1405 with Windows XP Professional and the internal Dell 355 Bluetooth card (WIDCOMM v5.1.0.3400). I currently have Intellipoint 6.2 installed, but have tried with v6.1, as well. I also tried the 5.0.1 version of the WIDCOMM software.

Since I am using the notebook version of the 8000, I was changing "Pid_0713" to "Pid_0701" in the point32.inf. Aside from that, I followed the steps above to the letter. On trying to update the driver, like others, I get the message "The specified location does not contain information about your hardware."

Thank for any suggestions, and for creating this great post.

[Aqualinx]

Did you ever find an answer for this, Aqualinx? I am having the exact same problem.

I am using the Microsoft Wireless Notebook Presenter Mouse 8000 on a Dell Inspiron E1405 with Windows XP Professional and the internal Dell 355 Bluetooth card (WIDCOMM v5.1.0.3400). I currently have Intellipoint 6.2 installed, but have tried with v6.1, as well. I also tried the 5.0.1 version of the WIDCOMM software.

Since I am using the notebook version of the 8000, I was changing "Pid_0713" to "Pid_0701" in the point32.inf. Aside from that, I followed the steps above to the letter. On trying to update the driver, like others, I get the message "The specified location does not contain information about your hardware."

Thank for any suggestions, and for creating this great post.

Sorry wlumm, but I never did figure this issue out. While I was able to get basic functionality, it was unstable (disconnected a lot) and required me to mannually reconnect from the bluetooth manager. Please let me know if you ever find a solution to this issue - I would be most grateful. If you know of a different bluetooth mouse that does work, I would be interested in that also. - Aqualinx

[momitty]

I'm new to this bluetooth stuff, and not sure what WIDCOMM even is, but my mouse buttons 4 and 5 and horizontal scroll wouldn't work without the dongle. Who wants a dongle when your computer has built in BT??? After a Google on the subject it turned up this thread. Anyway, I made my mouse (Wireless Notebook Presenter 8000 Laser) work with the built in BT by somewhat following the directions Nickywan posted on 6-19-2007. Although I noticed sometimes you have to watch that _ and & are in the right place.

There's another catch though, I have IP6.2! In Intellipoint 6.2 there is no longer a point32.inf, it's been split into a pnt32uk.inf and pnt32uw.inf. Not sure which one matters, but I edited both of them and got it to work but not right away. It wouldn't ever take. Here's what I had to do (kinda goofy)

1. I made a copy of the inf's I modified.
2. I uninstalled Intellipoint.
3. I did the manuall install driver bit that's been well documented already here using my backups
4. It found and installed the drivers
5. I reinstalled Intellipoint 6.2
6. I copied my backups of the inf files back over the new install ones

[Aqualinx]

Thanks momity for posting your solution. While I was able to connect my MS Laser 8000 Bluetooth mouse to my HP nc6400, it would frequently disconnect, enough so to make it too much trouble to use and I went back to the dongle. I will try your solution.
Sincerely, Aqualinx

[Walt]

Great thread !

- First go to the device manager and then open the property of the connected "HID compliant mouse" (Easy to locate by switch on / switch off the mouse) in the mouse branche.

- In the "details" tab you will find all the needed information to built your own "driver"

HID\VID_045E&PID_0702&COL02\...


- Edit point32.inf then find a line beginning with the same vendor ID (VID_045E) and ending with your mouse description:

HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"


- The trouble comes from the different Product ID (Pid_0714).



Anyway, I made my mouse (Wireless Notebook Presenter 8000 Laser) work with the built in BT by somewhat following the directions Nickywan posted on 6-19-2007. Although I noticed sometimes you have to watch that _ and & are in the right place.

There's another catch though, I have IP6.2! In Intellipoint 6.2 there is no longer a point32.inf, it's been split into a pnt32uk.inf and pnt32uw.inf. Not sure which one matters, but I edited both of them and got it to work but not right away. It wouldn't ever take. Here's what I had to do (kinda goofy)


Well, I am going down this path again, upgrading my old "version 2" Bluetooth mouse, to a new "8000" mouse with its recharging cradle.

This, of course, lead me to return back to this ol' topic as the best reference around. ;)

Like momitty, I am using version 6.2, since that supports the "8000" mouse. And like momitty, I am finding that point32.inf does appear to have been split into a pnt32uk.inf file and a pnt32uw.inf file.

What has got me kind-of confused, is that I am finding that the .inf files already have Pid_0702. In other words, the line in the .inf files which ends with my mouse description, "Microsoft Wireless Laser Mouse 8000 (IntelliPoint)", has Product ID set as Pid_0702 and not Pid_0714. as Nickywan found in his. So there is nothing to change! Right? :eek:

Was there a Product ID error by Microsoft in the early .inf files, and Microsoft has since changed it ?????

I am also noticing momitty caution about "watch that _ and & are in the right place". Does anyone know what these two symbols mean in an .inf file? Because, sometimes I see something like "VID&0002045e_PID&0702" and sometimes I see something like "VID_0002045e&PID_0702". I even see this flip-flop in syntax as I read through this very topic thread! All I have been able to figure out, is that _ and & alternate. Is there any meaning beyond that?

[Walt]

In looking at these .inf files a bit more closely, I see that there are already two lines, both for the same "8000" mouse. When I posted before (above), I hadn't caught that yet (needed to turn wordwrap off). It seems that the same mouse can return two different Vender ID's and Product ID's.

HID\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002045e_PID&0702&Col02.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

I am also confused by the Vendor ID of 2045e since from everything I have been able to read, Vendor IDs are only 4 hex digits long, not 5 ! Though, the last character "e" might not be a hex digit since in the rest of the .inf file, I noticed that all other hex digits are always in upper case.

Is there a ".INF FOR DUMMIES" somewhere, that I can read???? :D

[Walt]

Well, I am teaching myself a lot, and I thought I would share with anyone still watching this thread, what I have found out. First, let me once again thank Nickywan. His post was very helpful, but I found my situation a bit different.


HID\VID_045E&PID_0702&COL02\...


I found this in my Device Manager for the "unknown" device instead...

hid\{00001124-0000-1000-8000-00805f9b34fb}&vid_045e&pid_0702&col01

Now when editing the point32.inf file (or the pnt32uk.inf + pnt32uw.inf), the most important thing is to look for, are the lines which are very similar but not completely.



HID\Vid_045E&Pid_0714.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"


The line I found closer for my case was:

HID\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002045e_PID&0702&Col02.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

Note for me, that BIG long hex number between the braces "{" and "}", is the same, and the PID of 0702 is the same. That was the big clue as to which lines to change. It is the VID which is different. Plus also the ampersands "&" and underscores "_" also flipped around (I still don't know why).

So, I had to change that line to this:

HID\{00001124-0000-1000-8000-00805f9b34fb}&vid_045e&pid_0702&Col02.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

I had to do this kind of edit, a total of three times in each .inf file.

Good luck!

[jacb]

Well, I am teaching myself a lot, and I thought I would share with anyone still watching this thread, what I have found out. First, let me once again thank Nickywan. His post was very helpful, but I found my situation a bit different.

I found this in my Device Manager for the "unknown" device instead...

hid\{00001124-0000-1000-8000-00805f9b34fb}&vid_045e&pid_0702&col01

Now when editing the point32.inf file (or the pnt32uk.inf + pnt32uw.inf), the most important thing is to look for, are the lines which are very similar but not completely.

The line I found closer for my case was:

HID\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002045e_PID&0702&Col02.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

Note for me, that BIG long hex number between the braces "{" and "}", is the same, and the PID of 0702 is the same. That was the big clue as to which lines to change. It is the VID which is different. Plus also the ampersands "&" and underscores "_" also flipped around (I still don't know why).

So, I had to change that line to this:

HID\{00001124-0000-1000-8000-00805f9b34fb}&vid_045e&pid_0702&Col02.DeviceDesc="Microsoft Wireless Laser Mouse 8000 (IntelliPoint)"

I had to do this kind of edit, a total of three times in each .inf file.

Good luck!
Hi Walt

Great work .... and yes people are still interested.

I am using "IntelliPoint 6.3" and a "Microsoft Wireless Notebook Presenter Mouse 8000". - I have been trying to make this comb' work using the above method. Whilst I have made progress and the mouse in now identified by it's full name in the Device Manager .... Intellipoint refuses to let me program buttons?!

Could I ask a favour ...... would you take a look at my pnt32uk.inf + pnt32uw.inf files and see if you can shed any light on why things are not working?

Maybe we could save these "modified" files for other users when we get them working ..... any idea where we could store them on the internet?

Thanks in advance

:D

[Walt]

Whilst I have made progress and the mouse in now identified by it's full name in the Device Manager .... Intellipoint refuses to let me program buttons?!


I have found that for me, that means the default Windows mouse driver is being used, and not the Intellipoint driver.

When this happened to me, I went through the Update Driver wizard, and let it pick/offer the drivers it thinks are compatible. In that short list, was Intellipoint and of course, I picked that one. BTW, by being offered in that list, means it was successfully installed at some point prior, but just not selected for the mouse (for some reason).

Let me also add that I found that one can't just select one of the .inf files, and left click select "install". For some reason, that doesn't work. One has to do the full disk install, starting with the Setup file in the CD's root directory. Of course, that means building a CD (or a full image of the CD) with the appropriately modified files.


Maybe we could save these "modified" files for other users when we get them working ..... any idea where we could store them on the internet?


I was thinking of kind-of the same thing.

Personally, I found that ver 6.1 to be the best/easiest to get working. Ver 6.1 is still new enough to support all of the current, and past, Bluetooth mice from Microsoft.

I built a modified install disk for ver 6.1, and would certainly make it available for other owners of Microsoft Bluetooth mice, if there was a place from which to appropriately distribute it.

[asdfjk]

walt, can you email me that stuff??

joeblo32*aim.com

*=@

thanks!