Users who are planning to install Windows XP Service Pack 2 and wish to use the built-in Bluetooth stack instead of TDK's Widcomm drivers may need to update the device's firmware upgrade first, to allow Windows to properly recognise the device. This is not required if users plan to keep using the TDK software instead of the new Windows built-in stack.

The update is part of a FAQ TDK posted with answers to most common questions regarding the SP2 update. The company also says that users who want to keep using the Widcomm software already installed don't have to change anything. It also give instructions on how to switch from the SP2 Bluetooth stack to TDK's Widcomm stack, and vice-versa.

If you want to decide what software to use, take in consideration your needs, and what's provide in each driver. For example, TDK's Widcomm provides the following profiles:

Personal Area Networking (PAN and LAP). Enables IP connections over Bluetooth.

Hard Copy Replacement Profile (HCRP). Enables printing

Human Interface Device (HID). Enables Bluetooth keyboards, mice, and joysticks

Dial-Up Networking (DUN). Enables Bluetooth mobile phones to work as modems.

Object Push Profile (OPP). Enables file transfers.

Virtual COM ports (SPP). Enables legacy programs to communicate with Bluetooth devices.

And additionally:

Audio Headset

Audio Gateway

Fax

PIM Sync (OBEX)

The Microsoft Bluetooth release has support for these Bluetooth profiles:

Personal Area Networking (PAN). Enables IP connections over Bluetooth, client only.

Hard Copy Replacement Profile (HCRP). Enables printing

Human Interface Device (HID). Enables Bluetooth keyboards, mice, and joysticks

Dial-Up Networking (DUN). Enables Bluetooth mobile phones to work as modems.

Object Push Profile (OPP). Enables file transfers.

Virtual COM ports (SPP). Enables legacy programs to communicate with Bluetooth devices.