How To
How to support Multi-Bluetooth adapter on one computer?
You have to install different bluetooth driver for each Bluetooth dongle (adapter). For example: one dongle with MS, other one with BS and so long.
How to Install Microsoft Bluetooth Driver on any PC?
If you have installed Bluetooth dongle driver from the manufacturer or third party drivers it is necessary for you to install the standard drivers from Microsoft.
To do that, follow these simple steps:
- Uninstall all third party Bluetooth drivers then reboot your PC.
- Let Windows detects your Bluetooth hardware. Wait until Windows detects new hardware and installs its drivers. If Windows found new device and installed it correctly then done. Otherwise follow to the next step.
If Windows did not install drivers for your Bluetooth device we must teach it how to do it:
- Open your file manager and change it settings for showing system and hidden files.
- Go to Windows folder (for example C:\Windows) and find there folder Inf. If you can't find that folder check that Show hidden files option checked in Windows Explorer settings.
- Open it and find here bth.inf file. If you can't find that file then you have unchecked Show hidden files option or does not have Windows XP.
- Go to Device Manager and find there Unrecognized device.
- Open its property sheet go to Detail tab and remember text which looks like this: USB\VID_1311&PID_0021\B7E4090D0B00.
- ext, find in bth.inf file this text line: USB Bluetooth Wireless Adapter = BthUsb, USB\Vid_1310&Pid_0001.
- Now you must change Vid_1310 to the Vid_1311 (like in remembered text) and Pid_0001 to the PID_0021.
- If you have other remembered VID and PID then you must change it to your.
- Save changes in bth.inf file and reboot your PC.
- If the Bluetooth device not found go to the Device Manager and refresh devices list.
Or you can use Bluetooth Driver Installer.
How can I get the MAC address of the bluetooth adapter?
To do so you have to use wclBluetoothRadio (TwclBluetoothRadio/CwclBluetoothRadio) object and its property (method) Address/GetAddress().
How to disconnect a device user without closing the server?
Unfortunately there is no method to disconnect a user without closing a server. The right way to disconnect a remote client/device is to close a server and then open it once again.
How to redistribute WCL with your application?
DO NOT REDISTRIBUTE WCL PACKAGE WITH YOUR APPLICATION!
All the redistributable files are located in (WCL_INSTALL_DIR)\Redist. All redistributed files must be copied into the same folder as your application if other was not specified.
VCL Edition
- wcl2wbt.dll
(this DLL from redist folder has been built with a latest WidComm SDK but it may have some issues when WidComm is used with Microsoft Bluetooth Drivers. The wc2wbt.dll from (WCL_INSTALL_DIR)\Redist\old folder has been built with an old WidComm SDK and it is recomended to use with Proximity Marketing applications. But this DLL (from the old folder) has issue with pairing with Bluetooth > 2.1 enabled devices.)
COM Edition
- wcl.dll
(must be registered as COM server) - stdvcl40.dll
(must be registered as COM server and placed in SYSTEM32 folder. Do not ovewrite file if it is already exists.) - wcl2wbt.dll
(this DLL from redist folder has been built with a latest WidComm SDK but it may have some issues when WidComm is used with Microsoft Bluetooth Drivers. The wc2wbt.dll from (WCL_INSTALL_DIR)\Redist\old folder has been built with an old WidComm SDK and it is recomended to use with Proximity Marketing applications. But this DLL (from the old folder) has issue with pairing with Bluetooth > 2.1 enabled devices.)
C++ Edition
- wcl.dll
- wcl2wbt.dll
(this DLL from redist folder has been built with a latest WidComm SDK but it may have some issues when WidComm is used with Microsoft Bluetooth Drivers. The wc2wbt.dll from (WCL_INSTALL_DIR)\Redist\old folder has been built with an old WidComm SDK and it is recomended to use with Proximity Marketing applications. But this DLL (from the old folder) has issue with pairing with Bluetooth > 2.1 enabled devices.)
.NET Edition
- wcl.dll
(must be referenced) - wcl2wbt.dll
(this DLL from redist folder has been built with a latest WidComm SDK but it may have some issues when WidComm is used with Microsoft Bluetooth Drivers. The wc2wbt.dll from (WCL_INSTALL_DIR)\Redist\old folder has been built with an old WidComm SDK and it is recomended to use with Proximity Marketing applications. But this DLL (from the old folder) has issue with pairing with Bluetooth > 2.1 enabled devices.) - .NET 2.0 - all files from (WCL_INSTALL_DIR)\Redist\Microsoft.VC80.CRT folder: Microsoft.VC80.CRT.manifest;
msvcm80.dll; msvcp80.dll; msvcr80.dll
(Microsoft.VC80.CRT must be referenced) - .NET 3.0 - all files from (WCL_INSTALL_DIR)\Redist\30\Microsoft.VC90.CRT folder: Microsoft.VC90.CRT.manifest;
msvcm90.dll; msvcp90.dll; msvcr90.dll
(Microsoft.VC90.CRT.manifest must be referenced) - .NET 3.5 - all files from (WCL_INSTALL_DIR)\Redist\35\Microsoft.VC90.CRT folder: Microsoft.VC90.CRT.manifest;
msvcm90.dll; msvcp90.dll; msvcr90.dll
(Microsoft.VC90.CRT.manifest must be referenced) - .NET 4.0 - all files from (WCL_INSTALL_DIR)\Redist\40\Microsoft.VC100.CRT folder: msvcp100.dll; msvcr100.dll


