midiwall

So, I was bored at work (well, not really, just sidetracked) and I got my Kensington 33348 to work with the stock Microsoft Bluetooth stack.

No, this isn't ideal and I bet that Scott and David have something better going on, but this sure beats the WIDCOMM drivers. This process should work for any dongle you have that isn't automatically recognized by Windows XP.

Overview
The general steps here are to:

• Modify the Windows INF file to include the Vendor and Product ID of your dongle.
• Re-run hardware discovery

It's just that easy.


Doing it
(I'm not being completely hand-holding here... If you don't understand something below, then you probably shouldn't be doing this! )

• Download this software as a trial:
  http://www.hhdsoftware.com/Products/...b-monitor.html
  
  
• Install that and fire it up
  
  
• The software ("HHD Device Monitor") should open up with the "Device Window". If not, hit F4 (or click on USB | Device Window from the top line).
  
  
• Plug in your Bluetooth dongle
  
  
• Now starts the hunt, you need to find your Bluetooth device. more than likely, you'll find MANY USB Controllers on your box. With this tool, you'll have to wander manually, looking at each device on each hub. You're looking for a "Manufacturer" entry that matches that of your dongle. "Level" wise, it'll be like:
  
  Controller/Hub/{possibly another hub}/Port/Device Descriptor/Manufacturer
  
  
• Once you find the device, you need two pieces of information. The Vendor ID and the Product ID. It will be in the Device Descriptor node, a couple of entries above Manufacturer. These will be hex numbers, like this:
  
  Vendor: 0x047d
  Product ID: 0x105e
  
  
• Now open a text editor and load up: c:\windows\inf\bth.inf (you may want to copy this file first as a backup!)
  
  
• Find the Manufacturer section, it'll look like this:
  
  Code:

  [Manufacturer]
  %Microsoft%=Microsoft
  ALPS=ALPS, NT.5.1
  Belkin=Belkin, NT.5.1
  Brain Boxes=BrainBoxes, NT.5.1
  ...

  
  
• Add an entry for your adapter:
  
  Code:

  Kensington=Kensington, NT.5.1

  
  
• Page down and create a section for the adapter. Use the Vendor ID ("Vid_") and Product ID ("Pid_") that you found using the port monitor: (NOTE: pay attention how the ID values are used and the formatting of the section header! It doesn't matter where in that block you put this)
  
  Code:

  [Kensington.NT.5.1]
  Kensington 33348 = BthUsb, USB\Vid_047d&Pid_105e

  
  
• Save the modified INF (in the same place)
  
  
• Open Control Panel then hit "Add Hardware | Next"
  The wizard should find your adapter
  
  
• Let the install run.. It will run in multiple stages. First loading the core drivers, then loading all the subsequent pieces.
  
  
• That should be it... By doing this, CF is now able to use my Palm Centro as a DUN modem through a Kensington 33348.

__________________
:: Mark