08-10-2004, 08:30 PM
|
|
Editor Emeritus
Join Date: Aug 2006
Posts: 15,171
|
|
Geekzone's Guide To XP SP2 Bluetooth Activesync
"If you haven't had your head in the sand lately, you'll know that Microsoft release Service Pack 2 (SP2) for Windows XP to manufacturing recently...There are big changes in XP Service Pack 2 with regards to Bluetooth. If you are already using Bluetooth for synchronizing your Windows Mobile device, you'll need to be smart about the upgrade process, because if you don't do it right, you won't be able to Bluetooth ActiveSync after the upgrade. This is a quick start guide to take you quickly through the steps to get Bluetooth ActiveSync working after the upgrade."
Yet another useful Bluetooth article from Geekzone. I'd use this, except neither of my Bluetooth cards aren't supported by Microsoft's native Bluetooth stack yet (I have a Portege 3505 with integrated Bluetooth and a TDK PC card at home). You can check the list of out-of-the-box supported devices here, and here's a Microsoft KB article giving a useful overview of the Bluetooth support built into SP2. If your BT device isn't supported, just install SP2 and it should leave your existing BT stack alone.
|
| |
|
|
|
08-10-2004, 09:34 PM
|
|
Mystic
Join Date: Jul 2003
Posts: 1,768
|
|
Re: Geekzone's Guide To XP SP2 Bluetooth Activesync
Quote:
|
Originally Posted by Janak Parekh
Yet another useful Bluetooth article from Geekzone. I'd use this, except neither of my Bluetooth cards aren't supported by Microsoft's native Bluetooth stack yet
|
Same here - with an IO Gear USB dongle... they refuse to even update the Widcomm stack they provided.
Quote:
|
Originally Posted by Janak Parekh
If your BT device isn't supported, just install SP2 and it should leave your existing BT stack alone.
|
Unfortunately, for me, SP2 totally breaks the stack that was provided. So, I have no MS stack and no support for the device with the existing software.
__________________
Jonathan (JonnoB)
"All that is necessary for the triumph of evil is that good men do nothing." -Edmund Burke
|
| |
|
|
|
08-10-2004, 09:56 PM
|
|
Philosopher
Join Date: Apr 2004
Posts: 545
|
|
Re: Geekzone's Guide To XP SP2 Bluetooth Activesync
Quote:
|
Originally Posted by JonnoB
Unfortunately, for me, SP2 totally breaks the stack that was provided. So, I have no MS stack and no support for the device with the existing software.
|
Makes me glad I had not bought a dongle yet! 
|
| |
|
|
|
08-10-2004, 11:01 PM
|
|
Thinker
Join Date: Jul 2003
Posts: 430
|
|
If you look at the list of supported devices, neither the DLink DBT120 or the Belkin dongles I used when writing the article are listed either - yet they both work fine.
The belkin show up as a "BCM2033 Bluetooth 2.4 GHz Single Chip Transceiver" and the DLink dongle shows up as a "Generic Bluetooth Radio".
There are far fewer Bluetooth chipsets than there are bluetooth OEMs, so chances are your device probably has one of the supported chipsets - unless it is based on a really new chipset.
From the KB Article Janak posted:
Quote:
|
To install a Bluetooth device, you only have to connect it. Microsoft Windows XP Service Pack 2 (SP2) includes drivers for many Bluetooth devices. If Windows does not recognize a Bluetooth device, you can still use it by using the generic software support that Windows includes, or you can use the driver that the device manufacturer provides.
|
__________________
Darryl BurlingReporting from the inside :-)blog: www.burling.co.nz |
| |
|
|
|
08-10-2004, 11:02 PM
|
|
Editor Emeritus
Join Date: Aug 2006
Posts: 15,171
|
|
Quote:
|
Originally Posted by darrylb
There are far fewer Bluetooth chipsets than there are bluetooth OEMs, so chances are your device probably has one of the supported chipsets - unless it is based on a really new chipset.
|
In my case, both devices are PCI/PCMCIA. As far as I could tell, the list only covers USB chipsets. :| Given that, I was afraid of messing with my BT stacks.
--janak
|
| |
|
|
|
08-10-2004, 11:07 PM
|
|
Thinker
Join Date: Jul 2003
Posts: 430
|
|
Quote:
|
Originally Posted by Janak Parekh
In my case, both devices are PCI/PCMCIA. As far as I could tell, the list only covers USB chipsets. :| Given that, I was afraid of messing with my BT stacks.
|
The form factor does not necessarily correlate to the chipset. That said, if it aint broke - dont fix it. :wink:
__________________
Darryl BurlingReporting from the inside :-)blog: www.burling.co.nz |
| |
|
|
|
08-10-2004, 11:21 PM
|
|
Neophyte
Join Date: Aug 2004
Posts: 1
|
|
My TDK USB adapter has a different Device PID than the two that are supported.
Mine is a USB\VID_04BF&PID_0309
The two that are supported are:
USB\Vid_04BF&Pid_0319
USB\VID_04BF&PID_0320
How many variations could they have made?
|
| |
|
|
|
08-10-2004, 11:49 PM
|
|
Sage
Join Date: Aug 2006
Posts: 667
|
|
Quote:
|
Originally Posted by darrylb
There are far fewer Bluetooth chipsets than there are bluetooth OEMs, so chances are your device probably has one of the supported chipsets - unless it is based on a really new chipset.
|
My Bluetooth adapter is an Ambicom and I don't see anywhere that it is listed, though I take your point that it still might use a supported chipset. The thing is, it sure doesn't make me feel comfortable to take a system that's working perfectly well and install this update based on something that might work. This brings me to two questions that I'm hoping someone can can answer.
1. If SP2 screws everything up, can it be uninstalled?
2. Where do you go to find those device PnPID numbers listed on the MS site? My computer doesn't show the Bluetooth adapter at all under USB devices. Instead, it shows under Other Devices with four entries also under COM Ports.
Thanks!
|
| |
|
|
|
08-11-2004, 12:27 AM
|
|
Oracle
Join Date: Aug 2006
Posts: 841
|
|
Quote:
|
Originally Posted by Rob Alexander
1. If SP2 screws everything up, can it be uninstalled?
2. Where do you go to find those device PnPID numbers listed on the MS site? My computer doesn't show the Bluetooth adapter at all under USB devices. Instead, it shows under Other Devices with four entries also under COM Ports.
Thanks!
|
If you have a Widcomm stack working, keep it that way. SP2 will actually reduce the number of services and clients available for your Bluetooth device. If you have a brand new XP installation, then install the Widcomm stack before installing SP2, since this will keep the Widcomm working.
There ways to revert the SP2 Bluetooth installation if needed, but then you start messing around with drivers.
I personally will not use SP2 Bluetooth.
|
| |
|
|
|
08-11-2004, 12:33 AM
|
|
Thinker
Join Date: Jul 2003
Posts: 430
|
|
Quote:
|
Originally Posted by Rob Alexander
1. If SP2 screws everything up, can it be uninstalled?
2. Where do you go to find those device PnPID numbers listed on the MS site? My computer doesn't show the Bluetooth adapter at all under USB devices. Instead, it shows under Other Devices with four entries also under COM Ports.
|
1. There is definately a remove option in Add/Remove programs. I'm not game enough to try it though :wink:
2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB or \PCMCIA if you are Janak :wink:
You will need to wander through the sub branches (two levels down from here) and find the branch for your device - look for the DeviceDesc key for the description of the device - find your Bluetooth dongle and there will be a HardwareID reg entry for it. This is cryptic and probably not for the uninitiated....
Interestingly enough, the Belkin adapter is different from the one I said earlier. It actually appears as a Blutonium BCM 2035 - not the BCM2033 as I said earlier. Also the PNPID for it is different to the one on the list. It is actually USB\VID_0A5C&PID_200A not USB\VID_0A5C&PID_200F - so it is not on the supported device list either.
Also - further investigation into the DLink reveals that it is detected as a "Cambridge Silicon Radio Ltd" chipset, but the PNPID is USB\Vid_0a12&Pid_0001&Rev_0443 - however the compatibility list says USB\Vid_0a12&Pid_0001&Rev_0524 is the supported device.
The bottom line is that MS have got reasonable coverage of devices and variations. If you are going to upgrade, there is a good chance it will work.
If you know someone who has already installed SP2, try plugging the device in and see if it is detected automagically. If it is, you are good to go.
__________________
Darryl BurlingReporting from the inside :-)blog: www.burling.co.nz |
| |
|
|
|
|
|
Linear Mode
