Further Adventures with Bluetooth
Last week I picked up a new Bluetooth dongle for my laptop in order to use my cell phone as a wireless modem while I was out of town. I ended up picking up a D-Link DBR-120 since I had recalled hearing good things about them (compared to the shitty Ambicom adapter I also have). I was pleased to find that it worked out of the box with the native Windows XP Bluetooth stack included in XP SP2 . The Microsoft stack works well allowing one to avoid all of the hoops necessary to configure and bond two devices when using the Widcomm (Broadcom) Bluetooth stack. Given the choice between the two I would use the Microsoft stack hands down as it provides a nice UI and it actually works - providing a USB like automagical experience when using Bluetooth devices on Windows.
This got me to thinking if it would be possible to make my Ambicom dongle work with the Microsoft Bluetooth stack. After uninstalling the Widcomm drivers I was using and rebooting I found Windows would detect the Bluetooth adapter but complained that it did not have a suitable driver to support it. Fortunately with a bit of Googling, I was able to find a way to make it work simply by altering the contents of the Windows bth.inf file. The info here at Jon’s Guides was pretty helpful to putting me on the right track. To make it work you simply need to add the applicable hardware IDs to the list of supported devices. Once this is done Windows will detect the adapter correctly and load the Microsoft Bluetooth stack. After the drivers are installed Bluetooth support is ready to use - in my case after bonding my Nokia 3650 phone to my PC (using the included wizard) I was able to fire up Nokia’s PC Suite and everything worked automagically.
In case anyone is curious here is how I edited the bth.inf file to support my Ambicom adapter:
- determine the hardware ID of your adapter. This can be done by clicking on the device in the Windows Device Manager and selecting “Hardware IDs” from the Details tab. My Ambicom device had a hardware ID of: vid_0bdb&PID_1002
- once you have determined the hardware ID locate the bth.inf file and make a copy of it
- open up the copy in an editor and scroll down to the Device section
-
select one of the headings (I placed mine under [Belkin.NT.5.1]) and paste in the following:
; AmbiCom Support
Erickson Bluetooth Adapter= BthUsb, USBVID_0BDB&PID_1002I named it as an Erickson Bluetooth Adapter since the chipset in my dongle appears to be made by Erickson.
- Save the file
- Update the dongle drivers to use your newly edited inf file. If all goes well it will detect and install the adapter.
- Enjoy a working Bluetooth stack
To make it easy you can download a copy of the bth.inf file that I already edited here.
Indy said,
October 7, 2004 @ 6:18 am
http://www.technostan.com/archives/000068_windows_xp_sp2.html
Nice copying!
Sheryl said,
January 10, 2005 @ 2:36 am
THANKS!! I’ve been trying for hours to figure out why I didn’t seem to have bluetooth support on my SP2 system. Your advice solved it!
I’m using a dongle made by CSR (a company that’s already in the INF) for Creative Labs. It’s new, but the Creative Labs Bluetooth Modem has been wiped from their Web site like it never existed - don’t know why. So it’s not on Microsoft’s “supported” list, though it is very standard.
full0ut said,
January 11, 2005 @ 9:28 am
just to say a WORD!!!
MAN.. U ARE A F**** GENIUSSS!!!..
THANX A LOT!!….
Jon said,
January 11, 2005 @ 10:17 pm
I’m glad to hear it helped you both
Roy said,
June 2, 2005 @ 1:59 am
Hello Sir
I have an Ambicom Bluetooth Wireless USB Adapter Model: BT2000C-USB. I want to install the CSR based Driver “csrbc01.inf” into the USB Adapter.Whenever I try to install the CSR based USB Adapter “csrbc01.inf” it says that the driver is not suitable for the particular hardware. Please let me know as how to install the CSR based driver in the USB Adapter. Please let em know if any other information is required.
jon said,
June 2, 2005 @ 6:35 am
Hi Roy,
In theory you can make this work by following a similar process to what I described above. Edit the csrbc01.inf file and include the hardware ID of your Ambicom adapter - this will allow it to be be detected as a “supported” device by the driver and allow it to be installed. I have never used the CSR driver so I can’t speak if it is actually compatible with your hardware or not. In the past I’ve had pretty good luck with the naitive XP Bluetooth drivers and my Ambicom dongle.
Good luck!
Sam said,
February 7, 2006 @ 12:39 pm
Hi,
Thanks for the tip it worked for my ISSC USB dongle a treat!
I added the line
ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001
in the [Cambridge.NT.5.1] category
Sam
Vaibhav said,
May 6, 2006 @ 11:19 am
Hi Jon,
Thanks for the great tip! It worked for me too.
Within minutes I could add the Bluetooth Adapter. I had been struggling to install it for last couple of days. But as soon as I entered the line
Broadcom Bluetooth Adapter= BthUsb, in bth.ini, the installation was a breeze.
Great job!!!
Vaibhav
jon said,
May 6, 2006 @ 11:35 am
Glad to hear it worked.
xploitzz said,
May 12, 2006 @ 2:35 am
Many Thanks, This info has allowed me to use my ISSC dongle with some pen-testing tools I wanted to try. WIDCOMM is closed source so there are no tools available to use with it
keithy said,
May 20, 2006 @ 11:42 pm
I have a ISSC Bluetooth dongle and i did every thing you said. it all installed right but as soon as it came to actually using the device its not being detected. I had a look in hardware propeties and it said
location: location 0 (ISSCBTA)
Device Status: Windows has stopped this device beacause it has reported a problem. (Code 43)
My device also dosnt come up as ISSC bluetooth radio but as ISSC bluetooth device
Ambro said,
May 28, 2006 @ 10:08 am
had the same problem as keithy described,
tried adding the “ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001″ line but same code 43
dudi said,
May 31, 2006 @ 12:35 am
had the same problem as keithy & ambro described,
tried adding the ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001? line but same code 43
dudi said,
May 31, 2006 @ 12:36 am
had the same problem as keithy & ambro described, tried adding the ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001? line but same code 43
hamada said,
June 5, 2006 @ 3:55 pm
have the same prooblem error code Windows has stopped this device because it has reported problems. (Code 43)
jason said,
June 7, 2006 @ 11:15 pm
Hey Jon.
First of all, cool. My ISSC Bluetooth Adapter was detected by Windows. But, as three other people had noted, Windows tells me this: “Windows has stopped this device because it has reported problems. (Code 43)”. What should I do? Please help.
jason said,
June 9, 2006 @ 10:11 pm
A tip: If your trying to get Activesync working over Bluetooth and using the ISSC Bluetooth Dongle with BlueSoleil software, let me tell you, I got it working:
Here’s what I posted in another forum:
:rolleyes:
Alright.
I’ve been trying connect my Jam to the PC using Activesync 4.1 over bluetooth for over three days now… and… I’ve finally got it (quite unexpectedly)…..
I dunno what I set right to get it working
, but these are things I did and it started working:
- First of all, you can use almost any bluetooth stack on your PC to get it working. I used the ISSC Bluetooth dongle with BlueSoleil software, which is supposedly the most buggy BT software!
-Your BT stack should support Serial Port Profile… btw I think, all BT stacks support that - this is only a conjecture.
These are my current working settings:
Settings–>Connections–>Bluetooth–>Mode–>(Checked)Turn on Bluetooth
Settings–>Connections–>Bluetooth–>Mode–>(Checked)Make this device discoverable to other devices
Settings–>Connections–>Bluetooth–>Devices–>[u][/u]
Settings–>Connections–>Bluetooth–>COM Ports–>[i][/i] (COM0) [u][/u]
Settings–>System–>Bluetooth Setting–>Outbound COM Port (Checked ?) [u][/u]
Settings–>System–>Bluetooth Setting–>Outbound COM Port (Checked ?) [u][/u]
Settings–>System–>Bluetooth Setting–>Inbound COM Port (Unchecked ?)
Now this is what I did, step by step:
1: On my PC, I deleted the existing parterneship between the PPC and the computer in Activesync
2. In my Bluetooth program, I actually didn’t [i]do[/i] anything. I only noted that it assigns COM 8 (in my case - it may be different for you - that’s for you to find out) to any incoming COM port connections. NOTE: I did not pair the devices yet.
3. I went back to Activesync–>File–>Connection Settings–>Allow connections to one of the following–>COM 8 (as I had noted in the prev. step).
4. Then, on the JAM, I went to Settings–>System–>Bluetooth Setting–> Bluetooth Activesync Setup–> click on Start. Now it will tell you something in a dialog box…”Please start bonding with other….” Click on OK. Now you will be taken to another familiar window.
6. Then I turned on Bluetooth went to the Devices tab.
7. (Though i already had my computer on the devices list, I deleted it). Clicked on New… (……) then my computer was detected… gave a passkey.. and clicked on next… now on the computer a dialog popped asking for the same passkey… entered it and OK. Then, I entered the Display name on the Jam. And this is where I actually paired the devices - note that I initiated it from the Pocke PC.
8. Then, I went to the COM Ports tab, clicked on New Outgoing port… it wanted me to select my computer’s name –> then selected COM0 –> OK.
9. Now I went to Programs–>ActiveSync.
8. Tools–>Options–>PC tab–>PC synchronisation–>[u][/u]–>Options–>in the list box, select Bluetooth. [u][/u]
9. Now all set, in the ActiveSync window on the PPC, Tools–>Connect via Bluetooth–> and tada, it connected.
My primary interest to connect via bluetooth was that, I could now use the Internet connection of my PC on the PPC.
Note: Intially, while trying to get AS working over BT, I started the activesync on the PC, so even if it did find my PPC on the virutal COM port, it would say, “Microsoft activesync cannot recognize this device…….”–> so you ought to start AS on the PPC.
So, the thing is, you intiate everything from the PPC, right from the pairing to the [i]activesyncing[/i]
Whew. That was one long post… Hope it helps.
Meanwhile, if you have any queries, do tell me - shall be glad to help. :rolleyes: :rolleyes: :rolleyes:
shai espiem said,
June 11, 2006 @ 6:03 pm
Thanks god. You save me from buying another brand of bluetooth dongle. Currently i’m using ISSC USB with bluesoeil driver but never works with Nokia PC suites. With your guide, i able to connect to my nokia7610 with bluetooth now!. Thanks again
jon said,
June 12, 2006 @ 10:42 am
Glad to hear you got your ISSC dongle working. I’ve moved on to an iBook so I’m enjoying a bluetooth stack that “just works”
Scott said,
June 21, 2006 @ 12:06 am
Same boat, code 43 error on an issc usb card - error 10 when trying to start it etc.
I DID install the bluesoleil driver from CD though so I thought that might have corrupted something?
I’m thinking they might have changed chipset in the card and hence editing the bth.inf file is pointless?
I’m very pissed as this thing is useless to me without native support, what a peice of crap.
ali said,
June 23, 2006 @ 5:34 pm
Had the same problem as keithy & ambro described, tried adding the ?ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001? line but same code 43
Notice the Device IDs are same for all of us.
Ganesh said,
June 26, 2006 @ 9:23 am
I’m using ISSC Bluetooth too. Had been struggling to use it with BlueSoleil & Nokia PC Suite. Your solution made the dongle work with the XP bluetooth suite. Thanks very much for the excellent tip.
MEast said,
June 27, 2006 @ 12:59 am
Code 43 here too… Anyone have a solution??
Murali Krishna said,
July 24, 2006 @ 5:50 am
i, murali krishna
i purchased ISSCBTA. i lost my that USB Blour tooth drivers cd
please give a right choice what i have to do
Avi said,
July 28, 2006 @ 12:34 am
Same error 43 for me too. I think am just gonna have to throw this piece of junk out
TomT said,
August 6, 2006 @ 1:57 am
This workd for me and my ISSC USB Bluetooth dongle:
[Belkin.NT.5.1]
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0081
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0084
;Custom Entry
;ISSC BT Dongle
ISSC Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
;End Custom
Thanks..
Gabriel said,
August 6, 2006 @ 2:26 pm
Same 43 error.. any ideas?? please help us..
Mike said,
August 7, 2006 @ 12:04 am
YOU ROCK!!!!!!
Ying said,
August 9, 2006 @ 10:50 pm
Jon, can you please help us for error code 43? I think that we’ve no clue how to fixed this. Pleaseeeeee.
jon said,
August 9, 2006 @ 11:30 pm
Are you sure your using the right VID and PID for your particular device? Assuming they are correct it is possible the Microsoft stack doesn’t work with your device. Have you tried it with the Widcomm stack instead to see if it works?
Hope this helps. I replaced my PC with a Mac a while ago and I don’t miss hassling with Bluetooth support
sam said,
August 19, 2006 @ 12:01 pm
has anyone managed to sort this error code 43 out? iv got the same hardware id as all the others who seem to be getting the message but another sam at the top of the thread seems to have got hers working with the same hardware id so i dont think it can just be that. please anybody….help!!!
Rudy said,
August 24, 2006 @ 2:36 pm
I gave the same problem: Error Code 43 with the very same BT dongle … tried everything mentioned here … HEEEEEEEEEEEEELP PLEASE! Any ideas??
Tony said,
August 30, 2006 @ 3:00 pm
Error Code 43 with ISSC BT dongle.
OK guys, some success here. After many happy hours, I installed the Blue Soleil package from IVT at http://www.ivtcorporation.com. You can download the eval package for free and it works for phone purposes. I have a Tosh laptop running XP and a Nokia 6102i phone. I am now able to connect and transfer files. Only problem, Blue Soleil is not supported by PC Suite. Next step is to try the Widcomm driver which is supported. However, it seems to be a 40Mb download, so I thought I’d try BS first.
jon said,
August 30, 2006 @ 5:25 pm
The Widcomm (or Broadcom now since Widcomm was acquired) stack should work fine with PC Suite. I had good luck with it back when I still had a Windows PC and my Nokia. The only tricky part was getting the BT COM port recognized correctly by PC Suite.
Good luck!
Liew said,
September 27, 2006 @ 8:16 pm
I got mine ISSC usb dongle working as well, thanks for the information as i am not able to use windows bluetooth stack for quite sometimes.
£@$Z said,
September 29, 2006 @ 5:48 am
Tony’s suggestion worked for me. Go to http://www.ivtcorporation.com./ and downlanded (std) package.
Thank you and good luck to others…
Paco McDooby said,
October 5, 2006 @ 9:03 pm
Unfortunately, that didn’t help at all. I don’t know why. I have an ISSC dongle. The hardware IDs are USB\Vid_1131&Pid_1001&Rev_0373 and USB\Vid_1131&Pid_1001. I put those in the bth.inf file. I tried updating the drivers from Device Manager. It didn’t work. (And no previous drivers for the adapter are on the computer.) I get this error: http://img201.imageshack.us/img201/3062/isscbta0nt8.gif
I actually do have the BlueSoleil drivers, but they’re absolute trash. They constantly corrupt files that are transferred from my phone.
Mike Kayzz said,
October 7, 2006 @ 8:54 am
I have a bluetooth device that shows the driver required as ISSCBTA….and the cd in which i have it has a major problem and therefor i am not able to install it….could you please help me out
AngerManagement said,
October 24, 2006 @ 1:42 am
If you happen to purchase a V1.2 Class1 100M Bluetooth Adapter Dongle Antenna Wireless USB from E-bay. Then be aware that it could be a FAKE.
My CD is a FAKE and if your CD rom drive pauses and can not detect the CD, I would suggest that yours might be as well.
If are lucky enough to be able to get the real bluesoleil driver’s then you will have a part working system.
However about 10M is the best I can get and in looking at this I noticed the Quality of the BT00AN bluetooth dongle (e-bay and from China) was not as expected. Further inspection shows that the unit pulled apart very easly and that the antenna (Expanded signal via external antenn…. states the specs) in fact is a dummy.
At the end of the day, only give positive feedback if the product has been tested and found to be working as described. If not then use the dispute process and provide the correct feedback so that others are made aware.
So what did I get from my purchase….. a 12″ USB extention cable ROFLMAO and I have become a little wiser.
jon said,
October 25, 2006 @ 4:12 pm
Sorry to hear you bought a fake/broken dongle. I hope you didn’t pay too much for it - you can pickup a new bluetooth dongle for about $30 (or less) here in the states.
jus said,
November 3, 2006 @ 6:57 am
i have a bluetooth dongle and get the code43 also. all i have to say is that the bluesoleil doesn’t do the job and the hardware stinks as well. thanks for the info jon. learn something new every day.
jus said,
November 3, 2006 @ 7:28 am
I was trying to get activesync to work on this dongle, and what Jason said is true, if you activate everything from the device, it will work even over bluesoleil. worked for me. still wish it hadn’t been so complicated from the start though. thanks Jason.
adham said,
November 12, 2006 @ 5:03 pm
well done guys
Pete said,
November 14, 2006 @ 2:02 pm
Help. same problem here, CODE 43. I have been trying for 11 hours with an ISSCBTA dongle. Have tried all the bth.inf stuff on 3 computers….all code 43.
The driver CD that came with it is rubbish. HELP! Pete.
kama said,
November 14, 2006 @ 11:44 pm
where the hell is the bth.inf file located? is there a default in window or what?
jon said,
November 14, 2006 @ 11:52 pm
Kama,
You should be able to find a copy of the file here -> %WINDIR%\inf\Bth.inf
PSM said,
November 19, 2006 @ 2:28 pm
thanx jon.
I wanted my ISSC dongle to be detected by windows itself. UR TRICK WORKED SUCCESSFULLY. sooner I will post how I did it with ISSC without stupid error 43 for my friends facing error 43. Really wish to post now, but I m in hurry.Sorry for delay.
PSM said,
November 19, 2006 @ 3:16 pm
What I did??
1) Uninstall Bluesoleil software
2) Plug out dongle and restart PC
3) backup c:\windows\bth.inf
4) opened original bth.inf
Then this is the entire modified code (you can copy the same in your bth.inf):-
; Microsoft Windows Bluetooth Driver INF
; Copyright (c) 2002 Microsoft Corporation
[Version]
LayoutFile=layout.inf
Signature=”$Windows NT$”
Class=Bluetooth
Provider=%MS%
CLASSGUID={e0cbf06c-cd8b-4647-bb8a-263b43f0f974}
DriverVer=08/03/2004,5.1.2600.2180
[DestinationDirs]
DefaultDestDir = 11 ;LDID_SYS
BthPort.NT.CopyFiles = 12 ;DIRID_DRIVERS
BluetoothClass.NT.CopyFiles=11 ;LDID_SYS
BthUsb.NT.Copy = 12 ;DIRID_DRIVERS
BthEnum.NT.Copy = 12 ;DIRID_DRIVERS
Serial.NT.Copy = 12 ;DIRID_DRIVERS
Fsquirt.NT.CopyFiles = 11 ;LDID_SYS
Bthprops.NT.CopyFiles = 11 ;LDID_SYS
[ClassInstall32.NT]
AddReg=BluetoothClass.NT.AddReg
CopyFiles=BluetoothClass.NT.CopyFiles
[BluetoothClass.NT.AddReg]
HKR,,,,%BluetoothClassName%
HKR,,NoInstallClass,,1
HKR,,Installer32,,”bthci.dll,BluetoothClassInstaller”
HKR,,Icon,,”201″
[BluetoothClass.NT.CopyFiles]
bthci.dll
bthserv.dll
[ControlFlags]
ExcludeFromSelect=”BTH\MS_BTHBRB”
[Manufacturer]
%Microsoft%=Microsoft
ALPS=ALPS, NT.5.1
Belkin=Belkin, NT.5.1
Brain Boxes=BrainBoxes, NT.5.1
Broadcom=Broadcom, NT.5.1
Cambridge Silicon Radio Ltd.=Cambridge, NT.5.1
Dell=Dell, NT.5.1
FIC=FIC, NT.5.1
GVC=GVC, NT.5.1
HP=HP, NT.5.1
IBM=IBM, NT.5.1
Microsoft=Microsoft, NT.5.1
Motion Computing=MotionComputing, NT.5.1
Silicon Wave=SiliconWave, NT.5.1
Sony=Sony, NT.5.1
TDK=TDK, NT.5.1
TOSHIBA=Toshiba, NT.5.1
Wistron NeWeb=Wistron, NT.5.1
Zeevo=Zeevo, NT.5.1
;————- Device section - Start ———————–
[ALPS.NT.5.1]
ALPS Integrated Bluetooth Device= BthUsb, USB\Vid_044e&Pid_3005
Alps Bluetooth USB Adapter= BthUsb, USB\Vid_044e&Pid_3006
[Belkin.NT.5.1]
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0081
Belkin Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
Belkin Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0084
[BrainBoxes.NT.5.1]
Brain Boxes USB Bluetooth Adapter BL-554= BthUsb, USB\Vid_05d1&Pid_0003
[Broadcom.NT.5.1]
Blutonium BCM2035 Bluetooth 2.4 GHz Single Chip Transceiver= BthUsb, USB\VID_0A5C&PID_200A
BCM2033 Bluetooth 2.4 GHz Single Chip Transceiver= BthUsb, USB\VID_0A5C&PID_200F
[Cambridge.NT.5.1]
Generic Bluetooth Radio= BthUsb, USB\Vid_0a12&Pid_0001
CSR Nanosira= BthUsb, USB\Vid_0a12&Pid_0003
CSR Nanosira WHQL Reference Radio= BthUsb, USB\Vid_0a12&Pid_0004
CSR Nanosira-Multimedia= BthUsb, USB\Vid_0a12&Pid_0005
CSR Nanosira-Multimedia WHQL Reference Radio= BthUsb, USB\Vid_0a12&Pid_0006
[Dell.NT.5.1]
Dell TrueMobile Bluetooth Module= BthUsb, USB\VID_413C&PID_8000
Dell Wireless 350 Bluetooth Module= BthUsb, USB\VID_413C&PID_8103
[FIC.NT.5.1]
FIC Bluetooth Wireless Adapter= BthUsb, USB\Vid_05b1&Pid_1389
[GVC.NT.5.1]
GVC Bluetooth Wireless Adapter= BthUsb, USB\Vid_0525&Pid_a220
[HP.NT.5.1]
“HP USB BT Transceiver [1.2]“= BthUsb, USB\Vid_03F0&Pid_0C24
[IBM.NT.5.1]
Bluetooth UltraPort Module from IBM= BthUsb, USB\Vid_04BF&Pid_0317
IBM Integrated Bluetooth= BthUsb, USB\Vid_04BF&Pid_0318
IBM Integrated Bluetooth II= BthUsb, USB\Vid_1668&Pid_0441
IBM Integrated Bluetooth III= BthUsb, USB\Vid_1668&Pid_2441
[Microsoft.NT.5.1]
Microsoft Wireless Transceiver for Bluetooth= BthUsb, USB\Vid_045e&Pid_007e
Microsoft Wireless Transceiver for Bluetooth 2.0= BthUsb, USB\Vid_045e&Pid_009c
[Microsoft]
%BTH\MS_BTHBRB.DeviceDesc%= BthEnum, BTH\MS_BTHBRB
[MotionComputing.NT.5.1]
Motion Computing USB Bluetooth Device= BthUsb, USB\Vid_10ab&Pid_1002
[SiliconWave.NT.5.1]
Silicon Wave Bluetooth Wireless Adapter= BthUsb, USB\Vid_0c10&Pid_0000&Rev_1350
Silicon Wave Bluetooth Wireless Adapter= BthUsb, USB\Vid_0c10&Pid_0000
USB Bluetooth Wireless Adapter= BthUsb, USB\Vid_1310&Pid_0001
[Sony.NT.5.1]
USB Bluetooth Device= BthUsb, USB\Vid_044E&Pid_3002
USB Bluetooth Device= BthUsb, USB\Vid_044E&Pid_3003
Sony Bluetooth USB Adapter= BthUsb, USB\Vid_044E&Pid_3004
USB Bluetooth Device= BthUsb, USB\Vid_044E&Pid_3007
[TDK.NT.5.1]
TDK Bluetooth USB Adapter= BthUsb, USB\Vid_04BF&Pid_0319
TDK Bluetooth USB Adaptor= BthUsb, USB\VID_04BF&PID_0320
[Toshiba.NT.5.1]
TOSHIBA Integrated Bluetooth= BthUsb, USB\Vid_0930&Pid_0502&Rev_1350
TOSHIBA Integrated Bluetooth 2= BthUsb, USB\Vid_0930&Pid_0505
TOSHIBA Integrated Bluetooth 3= BthUsb, USB\VID_0930&PID_0506
TOSHIBA Bluetooth Adapter= BthUsb, USB\Vid_0930&Pid_0507
[Zeevo.NT.5.1]
Zeevo Bluetooth Solution= BthUsb, USB\Vid_0b7a&Pid_07d0&Rev_0126
Zeevo Bluetooth Solution= BthUsb, USB\Vid_0b7a&Pid_07d0&Rev_0133
;————- Device section - End ———————–
;—————————————————————————-
; USB Bluetooth radios
;—————————————————————————-
[BthUsb.NT]
AddReg=BthPort.NT.Setup.AddReg,BthPort.NT.AddReg
CopyFiles=BthUsb.NT.Copy, BthPort.NT.CopyFiles, Fsquirt.NT.CopyFiles, Bthprops.NT.CopyFiles
ProfileItems=Fsquirt.NT.ProfileItems
[BthUsb.NT.Copy]
BTHUSB.SYS
[BthUsb.NT.HW]
AddReg=BthPort.NT.HW.AddReg
[BthUsb.NT.Services]
Addservice = BTHUSB, 0×00000002, BthUsb_Service_Inst, BthUsb_EventLog_Inst
Addservice = BTHPORT, , BthPort_Service_Inst, BthPort_EventLog_Inst
[BthUsb_Service_Inst]
DisplayName = %BTHUSB.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_AUTO_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\BTHUSB.sys
LoadOrderGroup = PNP Filter
[BthUsb_EventLog_Inst]
AddReg=BthUsb_EventLog_Inst.AddReg
[BthUsb_EventLog_Inst.AddReg]
HKR,,EventMessageFile,0×00020002,”%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\Drivers\Bthport.sys;%%SystemRoot%%\System32\Drivers\BthUsb.sys”
HKR,,TypesSupported,0×00010003,7
;—————————————————————————-
; BthEnum support sections
;—————————————————————————-
[BthEnum.NT]
CopyFiles=BthEnum.NT.Copy
[BthEnum.NT.Copy]
bthenum.sys
[BthEnum.NT.Services]
AddService = BthEnum, 0×00000002, BthEnum_Service_Inst
[BthEnum_Service_Inst]
;—————————————————–
DisplayName = %BthEnum.SVCDESC%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\BthEnum.sys
;—————————————————————————-
; BthPort support sections
;—————————————————————————-
[BthPort.NT.AddReg]
; permanent child drivers
HKLM,%Bthport.Parameters%\PnpId,”RFCOMM”,,”MS_RFCOMM”
HKLM,%Bthport.Parameters%\PnpId,”BTHBRB”,,”MS_BTHBRB”
HKLM,%Bthport.Parameters%\PnpId,”BTHPAN”,,”MS_BTHPAN”
HKLM,%Bthport.Parameters%\PerDevices,,,
; HID
HKLM,%Bthport.Parameters%\SupportedServices,”{00001124-0000-1000-8000-00805f9b34fb}”,0×00010003,1
; HCRP
HKLM,%Bthport.Parameters%\SupportedServices,”{00001126-0000-1000-8000-00805f9b34fb}”,0×00010003,1
; DUN
HKLM,%Bthport.Parameters%\SupportedServices,”{00001103-0000-1000-8000-00805f9b34fb}”,0×00010003,1
; SPP
; SPP is enabled by bthport
; Local Services
; SPP default settings are done by bthport
HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Run,”BluetoothAuthenticationAgent”,0,”rundll32.exe bthprops.cpl,,BluetoothAuthenticationAgent”
[BthPort.NT.Setup.AddReg]
HKLM,%Bthport.Parameters%,,0×00000010
HKLM,%Bthport.Parameters%\Devices,,0×00000010
HKLM,%Bthport.Parameters%\Services,,0×00000010
[BthPort.NT.Setup.AddReg.Security]
; add the ability for power users and LocalService to modify the key and subkeys
“D:AR(A;CI;GRGW;;;PU)(A;CI;GRGW;;;LS)”
[BthPort.NT.CopyFiles]
bthport.sys
[BthPort.NT.HW.AddReg]
HKR,,%ScansBeforeOutOfRange%,0×00010003,8
;List of COD mask/value pairs. This info is used to enable the ’stored link key’ feature for
;the specified devices. The feature is enabled if the expression (COD & mask) == value is true.
;Each value is 4 bytes and written in big-endian format to make the user input easier.
;For example: mask 0×00001F43 with value 0×00000540 matches Bluetooth keyboard devices.
HKR,,%StoreLinkKeyCodMasks%, 0×00000001, 00,00,1F,43, 00,00,05,40, 00,00,1F,83, 00,00,05,80
[BthPort_Service_Inst]
DisplayName = %BTHPORT.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_AUTO_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\BTHport.sys
LoadOrderGroup = PNP Filter
AddReg=BthPort_Service_Inst.AddReg
[BthPort_Service_Inst.AddReg]
HKR,”Parameters\Restrictions\COD Major 05 Minor 10″,”DontAddIncomingSPPInWizard”, 0×00010001, 1
HKR,”Parameters\Restrictions\COD Major 05 Minor 20″,”DontAddIncomingSPPInWizard”, 0×00010001, 1
HKR,”Parameters\Restrictions\COD Major 05 Minor 30″,”DontAddIncomingSPPInWizard”, 0×00010001, 1
HKR,”Parameters\Restrictions\COD Major 06 Minor 20″,”DontAddIncomingSPPInWizard”, 0×00010001, 1
[BthPort_EventLog_Inst]
AddReg=BthPort_EventLog_Inst.AddReg
[BthPort_EventLog_Inst.AddReg]
HKR,,EventMessageFile,0×00020002,”%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\Drivers\Bthport.sys”
HKR,,TypesSupported,0×00010003,7
[Fsquirt.NT.CopyFiles]
fsquirt.exe
[Fsquirt.NT.ProfileItems]
Name = %FSQUIRT_DESC%
CmdLine = 11,, fsquirt.exe
SubDir = %COMMUNICATIONS_GROUP%
WorkingDir = 11
IconIndex = 0
InfoTip = “@%11%\xpsp2res.dll,-2305″
DisplayResource = “%11%\xpsp2res.dll”,2303
[Bthprops.NT.CopyFiles]
bthprops.cpl
[Strings]
;
; Not localizable
;
ScansBeforeOutOfRange=”Scans Before Out of Range”
PeriodicInquiryEnabled=”Periodic Inquiry Enabled”
PeriodicInquiryPeriod=”Inquiry Period”
PeriodicInquiryMinSilence=”Minimum Silence Period”
PeriodicInquiryMaxSilence=”Maximum Silence Period”
Unsupported_HCI_Commands=”Unsupported HCI commands”
StartDelay=”StartDelay”
AclWriteDelay=”AclWriteDelay”
StoreLinkKeyCodMasks=”Store Link Key COD Masks”
Bthport.Parameters=”SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters”
;
;Localizable
;
BluetoothClassName=”Bluetooth Radios”
BTHPORT.SvcDesc=”Bluetooth Port Driver”
BthEnum.SVCDESC=”Bluetooth Request Block Driver”
Bthser.SVCDESC=”Bluetooth Radio Serial Driver”
BTHUSB.SvcDesc=”Bluetooth Radio USB Driver”
BthBCSP.SVCDESC=”BCSP Transport Protocol Driver”
Serial.SVCDESC = “Serial port driver”
FSQUIRT_DESC=”Bluetooth File Transfer Wizard”
COMMUNICATIONS_GROUP=”Accessories\Communications”
Bth.Diskname=”Bluetooth”
MS=”Microsoft”
Microsoft=”Microsoft”
; ————- Device Strings - start ————————-
; Microsoft
BTH\MS_BTHBRB.DeviceDesc=”Microsoft Bluetooth Enumerator”
; ————- Device Strings - end ————————–
and it is now working fine for me and should also work for you,, Good Luck
Jax said,
November 19, 2006 @ 11:09 pm
I tried all the bth.inf mine is isscbta dongle, came with bluesoleil 1.6 bt software driver and work great, than i download the latest bs 2.3.0 std version and Widcomm 5.0.1.2500, both work just fine, but widcomm sw took up much resource than bs, so now i’m stick with bs.
sorry for my english
Liviu said,
November 21, 2006 @ 3:45 pm
and how exactly did you deal with code 43 error? your bth.inf is not different from what was posted before.
PSM said,
November 22, 2006 @ 3:30 pm
here is the difference:=
i put the hardware id under belkin (know it doesnt matter under which adapter i put it),
but if your ISSC dongle id is same, i believe the same format is going to work …..
[Belkin.NT.5.1]
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0081
Belkin Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
Belkin Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0084
JuanFrugal said,
November 26, 2006 @ 9:42 am
My Bluetooth dongle appears to be a fake as well. It includes a “Bluesoleil” 1.6 software disk that cannot be read by the computer. I have tried installing various Widcomm packages (from several BT providers), but all tell me the current license does not support my device. The provider’s answr to my problem was “You should see my e-store, all my products work!”
jon said,
November 27, 2006 @ 9:52 am
@JuanFrugal
Actually I don’t think your dongle is fake. IIRC the Widcomm drivers have dumb license so the stack it tied to certain types of OEM hardware - you would need a license file for the particular dongle you have. A couple of years ago I remember reading about this while googling for some BT info. At the time I didn’t have to worry about it since my Ambicom dongle came with a licensed copy of the Widcomm stack.
Is there any reason you don’t just use the MS BT stack? The Widcomm stack was always kind of flaky after paring / unpairing with my Nokia 3650. I had much better luck with the MS stack which is what prompted me to write the original post.
@PSM
Glad you got it to work. Hopefully your info helps others as well
ClayBratt said,
November 28, 2006 @ 10:52 am
ok same code 43, i have a slim ISSC dongle, and ive been installing the modified drivers from the desktop and ive tried PSM’s code line for line. i tried it on two different computers the second haveing never saw the included Bluesoleil drivers. im thinking the people that have been able to get their issc dongles too work have been useing the larger ones and not the slim ones, but if someone can prove me wrong id love to eat my words. anyway could there be some sort of eccess or under voltage being sent to the device any ideas?
Clay
Jon said,
November 28, 2006 @ 12:27 pm
@ClayBratt
Did you check the hardware ID of your slim ISSC dongle? I’m assuming that it would be different than the larger ones which is why the code PSM posted won’t work. Look in the Windows Device Manager and selecting “Hardware IDs” from the Details tab. Edit accordingly and it should detect your dongle.
Good luck!
PSM said,
November 28, 2006 @ 3:27 pm
Thanx jon. It coudnt be possible without your help.
Also I believe the same thing that ClayBratt needs to check hardware id only.
And one small trick. If you fill :
[Belkin.NT.5.1]
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0081
PSM Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
PSM Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001
Belkin Bluetooth Adapter= BthUsb, USB\Vid_050d&Pid_0084
then windows installs PSM Bluetooth adapter (also in device manager).
little funny. you can change it with your name.
ClayBratt said,
November 29, 2006 @ 6:47 pm
yeah the Device id was the same one
USB\Vid_1131&Pid_1001&Rev_0373
USB\Vid_1131&Pid_1001
this is really driveing me nuts, i hope there is native support in vista because i hate third party drivers
should i be modifying a copy of the bth.inf file in the original folder or would that matter?
and if it has the same hardware id wouldnt that mean it uses the same hardware?
Clay
Jon said,
November 30, 2006 @ 10:34 am
@PSM
No problem - glad it helped
@Clay
If the hardware id is the same I’d assume that the internals of both types of dongles are the same. It sounds like the only difference is the external form-factor. I don’t have one so I can’t really comment further. The good news is if others got it working then yours should too.
If I were you I would modify a copy of the bth.inf file and point the add new hardware wizard at it when looking for an updated driver. At the very least this would rule out Windows File Protection from interfering with you editing the original.
I can’t comment on Vista support since I moved on to OS X and haven’t looked back
Bluetooth support works much nicer out of the box.
Good luck!
ClayBratt said,
November 30, 2006 @ 2:12 pm
Thanks for everything jon youve been a massive help
Clay
Jon said,
November 30, 2006 @ 3:30 pm
np - did you get it working?
Alex said,
November 30, 2006 @ 3:51 pm
hi guys
being having the same problems ClayBratt has had. Mine too is a slim bluey-green device. Tried it with Jon’s inf and adding PSM’s bit too but to no luck.
XP tries to install it then fails, claiming a parameter is incorrect.
Anything else you cud provide would be much help
ClayBratt said,
December 6, 2006 @ 8:15 am
no i never did get it working on any of four computers im crossing my fingers and just hopeing vista has naitive support but im gonna keep trying and if i make any progress ill post it
jon said,
December 6, 2006 @ 10:53 pm
@Clay
Sorry to hear you didn’t get it working. At this point the only thing I can think of that would be worth looking at would be the actual firmware/microcode version of your particular dongle. This would be the only potential difference I could see between your adapter and the ones reported to work - assuming it just isn’t a case of Windows being screwy. I thought the device manager entry for the device had an entry for this; however, I don’t have a Windows box available anymore to check with.
DJosephDesign said,
December 23, 2006 @ 6:16 pm
Same old ISSC dongle, same old story. I’ve tried all of the fixes above and all resulted in “Code 43″ error.
And I’m suspecting BlueSoleil of having issues with the hardware because although I can pair with my Jabra BT250v headset, I can’t make the audio work with anything.
jon said,
December 25, 2006 @ 5:46 pm
@DJoseph
Did you check if your ISSC dongle supports an audio headset (the actual name escapes me right now) profile? Since you said it pairs correctly it might just be an issue with the hardware and/or stack not supporting the right profile. I don’t have a ISSC dongle so can’t really say what it can / can-not do. Based upon the various comments above I’d assume they are pretty crappy.
Dave said,
December 27, 2006 @ 1:08 pm
Thanks very much for this tip. Worked for me with a Safecom USB dongle, after struggling for ages with BlueSoleil - Many thanks!
chrispriddy said,
December 28, 2006 @ 5:51 am
Hi all, just read through this entire thread as im struggling with the same thing. Really helpful posts however:-
WinXP SP2, ISSCBTA dongle, just want it to work without BlueSoleil so that i can get Nokia PC suite working.
Have tried the posts about adding to the bth.inf file, and recieved the code 43 error.
Have tried using PSM’s entire bth.inf file and got an ‘incorrect parameter’ error.
Any further thoughts.
Having a real disgust for windows recently.
thanks
chris
knifepoint said,
December 29, 2006 @ 2:21 am
Hi,
I’m also having problems with the ISSCBTA usb-dongle, I just copied the entire bth.inf file over and got Invalid Paramater, with BlueSoleil latest installed and Nokia PC Suite it detects two stacks (Microsoft and BlueSoleil) but when I select microsoft it says (invalid hardware, please check config, etc) and then when I select BlueSoleil it just wont show my phone at all and I keep pressing “rescan devices” but nothing happens.
chrispriddy said,
December 29, 2006 @ 11:54 am
Hi Knifepoint, thanks for posting.
Sounds like your in exactly the same situation as me.
Blue Soleil and PC suite just dont seem to work together, and I just can work out how to get XP to install the ISSCBTA properly.
I’ve cheated somewhat with a step backwards. Bought a cable on ebay for £3 to connect phone to PC. Seems daft when wireless is meant to be so convienent and great, but it gets the job done!
Maybe someone else can help us with a further solution to the ISSCBTA/XP problem!
Chris
SOHAIL said,
December 30, 2006 @ 10:08 am
hi!
i cannot install the bluetooth software in my windows VISTA, please help & guid me to install. tank you.
SOHAIL said,
December 30, 2006 @ 10:10 am
hi!
i cannot install the bluetooth software in my windows VISTA, please help & guid me to install. tank you.
The hardware ID of my device is: USB\VID_1131&PID_1001&REV_0373.
jon said,
January 2, 2007 @ 10:33 am
@knifepoint
I’d suggest you uninstall the BlueSoleil stack and just try with just the MS stack. I wonder if PC Suite is getting confused - from what I recall (I don’t have a Nokia anymore) it was kinda particular about the virtual COM port used to connecting… if each stack is presenting 1 or more COM ports this could be part of the problem.
@sohail
I don’t think BlueSoleil has a Vista compatible stack available yet. The whole point of this posting was to use the MS Bluetooth stack in lieu of a 3rd party stack - the concept should work for Vista as well. I don’t have a copy to try it with; however, if your dongle radio is supported but isn’t natively recognized editing the .inf file should do the trick.
Happy new year all!
Byshi said,
January 14, 2007 @ 1:19 pm
My BT Bluetooth working with BlueSoleil sw, but how to connect to internet in my mobile phon?
Thanks for help
grawity said,
January 15, 2007 @ 9:42 am
Which section should I use?
I successfully installed my Targus ACB20 dongle in one computer, and it shows like this:
Broadcom Bluetooth 2.0+EDR USB dongle
Hardware ID: USB\VID_0a5c&PID_2100
How to add it to other computers?
jon said,
January 16, 2007 @ 12:07 pm
@Byshi
You want to tether your laptop and phone. The details of how to do this will vary depending on your OS & BT stack, phone, and carrier. I’d suggest you check out HowardForums.com and look in the specific carrier and/or phone section. I wrote a post about how to tether with my Nokia 3650 which you can find in the archives.
@grawity
You would edit the .inf file to include a section with the particular VID & PID for your adapter. Assuming your broadcom chipset is supported by the MS stack it should work
grawity said,
January 16, 2007 @ 11:44 pm
yeah, but which section should I use?
Jon said,
January 18, 2007 @ 3:30 pm
@grawity
Look at step #5 above. Essentially you want to add a device description to the .inf file that has the matching VID & PID for your dongle. For example using what you had commented on earlier:
;grawity’s dongle
Bluetooth Adapter= BthUsb, USBVID_0a5c&PID_2100
Assuming the actual hardware is supported by the MS stack this should work as the .inf file edit will cause it to detect the device.
Hope this helps!
@Ranjan
It is possible your dongle isn’t actually supported by the MS stack. Assuming you made the .inf file edits properly that would be my best guess. My advice would be to pickup a supported dongle (look at the HCL), use a non-MS stack that supports your hardware, or pick a new OS
jon said,
January 18, 2007 @ 9:34 pm
Hey Ranjan,
If you tried editing the .inf and it still isn’t working then I’m thinking your out of luck - your hardware doesn’t seem to be supported by the MS stack. You probably can get it working with the Widcomm stack or some other stack (did it come with one)?
Thanks for pointing out that error - it looks like the max memory configured for my PHP interpreter is too low. I’ll fix my config
Ranjan said,
January 18, 2007 @ 11:04 pm
Hi jon,
Thanks for your replay,
I think i dont have luck, If you get any solution about Code 43 error please mail me to ranjancse@gmail.com ok..
I even Develop , Implement and Test Sofwares..so seem there’s some problem it was typical could’nt understand about your php’s max memory so I told U.
May I know you are from which place are U from wht are u doing?
if no probs and will U give me your personal mail Id so that I can contact U more easily..if any problems
Thanks
Ranjan.D
MuadDib said,
January 19, 2007 @ 1:32 pm
Hi to all… i haved the same problem with my ISSC Bluetooth Adapter… after i try to modify bth.inf on windows\inf , i haved the same driver error problem (Code 43) …. then i try to modify the bth.inf file to follow:
i created a new driver group and after reinstall the driver, it works properly
[ISSC.NT.5.1]
ISSC Bluetooth Adapter= BthUsb, USB\VID_1131&PID_1001
also put it not to [Belkin.NT.5.1], but create a own group [ISSC.NT.5.1]
Theguy said,
January 21, 2007 @ 5:51 pm
Been having the same troubles with this ISSC, i tryed that new group thing and still having code 43 problems.. what rev are your ISSC devices? perhaps that might be the problem, mine is &Rev_0373
Jon said,
January 22, 2007 @ 11:28 am
@MaudDib
Glad to hear you were able to get it working
@Ranjan
If you look in the sidebar (to the right) there is a link to a contact form you can use if you wanted to email me.
Haymon said,
January 25, 2007 @ 9:57 am
MaudDib genius!!!
Thanks!!!
Got it working
covax said,
February 18, 2007 @ 2:50 pm
tried to fix that “Code 43″ error
and cannot…But I find this: http://discussion.forum.nokia.com/forum/showthread.php?t=82994&highlight=IVT
So, it seems some ISSC dongles cannot be used with Microsoft BT Stack :/
WARNING
Some Bluetooth adapters DO NOT HAVE the CSR code and only simulate CSR working therefore coming up with errors like.
“windows has stopped this device as it reported problems (code 43)”
simply means you cannot use that BTUSB with Windows XP2
Kevin said,
February 19, 2007 @ 8:57 am
Hallo Jon
I will trying to download a patche Widcomm drivers to try the guide at http://www.jonsguides.com/bluetooth/prepare.html
but the download link is not working. Can you help me?
I get also a error code 43 when i try to install the driver and i have do that with bth.inf and try all what they say on this side.
I have a ISSC dongle
[ISSC.NT.5.1]
ISSC Bluetooth Adapter= BthUsb, USB\VID_1131&PID_1001
and i have try this i past in. When i plug the dongle in the pc after i remove the driver. I have a little cd(not the normal size) there can the pc find a driver so the pc can see its a bluetooth dongle but it say it not working correctly.
I hope some can help me
//Kevin
jon said,
February 19, 2007 @ 9:48 pm
@Kevin
I don’t have a copy of the Widcomm drivers anymore since I don’t use Windows machines anymore. You don’t need them to use the MS stack - you just need to use the right VID & PID for your dongle. See above for details on how to figure that out.
Kevin said,
February 20, 2007 @ 11:03 am
Hi Jon
I use the right VID & PID id for my dongle. But is ot your site this?
http://www.jonsguides.com/bluetooth/prepare.html
The link i doesnt work so i hope if is your site you will repare that link.
In MS stark i also get code 43. I buy the dongle at “Sonofon” a large company which sell mobilfones. On the case there is nothing about who there har made it. Only the specifications and what it support and a little description. On the bottom at the bagside is some icons and in big font “Make Life Freedom”
- Have you a case like me? -
//Kevin
Jon said,
February 20, 2007 @ 2:42 pm
@Kevin
I’m not the same Jon as the guy from Jon’s guide. You would need to talk to him about the content you find there - try the contact link you find on his site.
Good luck!
Kevin said,
February 21, 2007 @ 4:31 am
@Jon
Sorry, thoght just it’s was you.
I have try but he don’t answer
Thanks you for answer me!!
Amardeep Singh said,
February 23, 2007 @ 8:50 pm
It’s Magic… Yes Just we need to write a single Line & Its…… working Ohhhh i do not believe it”””””””’ REALLY UR A Computer MAGICIAN………….
keeep it Up………….!!!!!!!!!!!!!!!
Hurrrrrrrrrrrrrhhhhhhhhhhhhh.
MadCow said,
February 23, 2007 @ 11:37 pm
Has anyone got this to work with windows vista? it doesnt work for me….
Put the last 2 lines under:
[GenericAdapter.NTx86...1]
Generic Bluetooth Adapter= Bthusb, USB\MS_COMP_BLUTUTH
Generic Bluetooth Adapter= BthUsb, USB\Vid_0B05&Pid_1712
Generic Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
Generic Bluetooth Adapter= BthUsb, USB\Vid_1131&Pid_1001
jon said,
February 25, 2007 @ 7:52 pm
@Amardeep Singh
Glad it worked for you
@MadCow
Not sure about Vista - I don’t have a Windows machine anymore. Is the .inf format the same in Vista? With the “new” driver model it is supposed to have you might need to tweak the entry to suit.
Dr4k0 said,
March 14, 2007 @ 11:47 pm
Thanks to Jon and Sam… that’s works like magic
Andre said,
March 29, 2007 @ 3:08 pm
VID 0A5C
PID 2035
edited inf file from windows xpsp2 driver : code 43
edited inf file from WIDCOMM : license error
bluesolei driver, also no luck.
Is there any other driver available?
Hristo Bojkov said,
April 4, 2007 @ 10:08 pm
As many of you I’ve f*** my self with that stupid BT dongle. I liked the coin size - this why I took this dongle. Why I should carry a big CD with drivers for coin-size dongle. The whole idea behind small size easy carry dongle was killed in childhood, when the designers of that dongle decided to go for bluesoleil drivers, and not using standard stack. There is no difference which MS OS you are using, as long as the dongle is not fully compatible with standart drivers.
I tryed yor suggestion to add Vendor ID and Product ID in standard bth.inf file. I put:
ISSC Bluetooth= BthUsb, USB\Vid_1131&Pid_1001&Rev_0373
ISSC Bluetooth= BthUsb, USB\Vid_1131&Pid_1001
unfortunately it didn’t work for me, and I ended with error code.
As info for any of you - the last part - the one you wrote is the hardware ID that the P&P manager reads from the dongle, the first part in front of the = is the name that will be shown in the installation wizard, and middle - the BthUsb - define the install section from the INF file that should be used. In fact this means that the driver will be BTHUSB.SYS.
Shuja Zaidi said,
April 25, 2007 @ 12:28 pm
I’ve a bluetooth device (IVT bluesoleil 1.6 )
i m facing the problem that when i instl. bluetooth soft.
in my windows vista ultimate the ISSCBTA can’t instl.
plzzzz help me…..thaxxxxxxxxxxxxxxxxxx
Harish said,
May 4, 2007 @ 1:32 pm
cld some1 tell me how do u create a fake com port on ur computer for the BT dongle?
Connecting Smartphone to PC via Bluetooth - The Church Media Community said,
May 30, 2007 @ 11:10 am
[...] was a bit off. It’s the bth.inf file that I had to edit. Here are the instructions I used. That was my jumping off point, anyway. Joel Osborn __________ If life gives you gators, make [...]
Nayan said,
June 13, 2007 @ 11:11 pm
I just got a BCM2035B usb dongle (broadcom old product)
I tried the driver 5.1.0.1500 from broadcom’s site.
I tried editing the bth.inf file too.
But I always got 43 error.
Any hope???? or Covax is right??
———————–
covax said, February 18, 2007 at 2:50 pm
tried to fix that “Code 43″ error
and cannot…But I find this: http://discussion.forum.nokia.com/forum/showthread.php?t=82994&highlight=IVT
So, it seems some ISSC dongles cannot be used with Microsoft BT Stack :/
WARNING
Some Bluetooth adapters DO NOT HAVE the CSR code and only simulate CSR working therefore coming up with errors like.
“windows has stopped this device as it reported problems (code 43)”
simply means you cannot use that BTUSB with Windows XP2
——————————–
mishanja.b said,
June 29, 2007 @ 12:37 am
Seems that i’ve found code 43 solution: http://my.opera.com/mishanja.b/blog/bluetooth-dongle-code-43
Amor said,
July 10, 2007 @ 1:17 pm
Hi all.
I use MuadDib solution, with creating new group in bth.inf
[ISSC.NT.5.1]
ISSC Bluetooth Adapter= BthUsb, USB\VID_1131&PID_1001
Driver does woks! Thanks.
And what is benefit I’m working in MS-drivers?
How shall i send file to my phone? receive?
How can i scan for any devices nearby my dongle?
And the point: I want this programm written in C to be worked perfectly
SOCKET sock = socket( AF_BTH, SOCK_STREAM, BTHPROTO_RFCOMM );
How can i get it? Please help.
Thanks.
Amor said,
July 11, 2007 @ 11:14 am
I found that MS-drivers really don’t work with my dongle.
In the example above, the “Bluetooth Adapter” installed (or smth about this). Not “Bluetooth Radio”.
“Bluetooth Adapter” - i suppose remained from previosly installation. Maybe when I’ve installed Blue Soleil or maybe when I install drivers using MS Update. I don’t know. But whed i recover previous restore point of Windows XP. There were no “Bluetooth Adapter”.
And was “Bluetooth Radio”, I try to do like MuadDib did. Try to do as pointed at link at mishanya.b post. But every methods give out an Error 43.
Thats all.
PSM said,
July 16, 2007 @ 3:50 pm
Hi, glad Maudbid kicked out his error 43. Hi jon the genius. It still works fine for me. I tried it in vista, when I put my dongle id in some other group, not in belkin. It didnt work. It only work if i put it in belkin. So, plz try with all the groups. Tough job, but hope for the best. Bye………. And also use \ only, / didnt work for me, if you type it yourself.
NS said,
August 26, 2007 @ 11:48 am
Hello, Did anyone get a solution to this ISSC dongle problem?
if you got it to work in XP without error code please email overloaded@gmail.com
thanks
Ron W Hardy said,
August 28, 2007 @ 6:01 pm
BlueSoleil and Vista success!
I finally have Bluesoleil running on Vista without any errors and without any modification of INF files. I just had to clean up my system, download new BT stack, and install by running Setup.exe.
Here are the details.
I found at http://www.bluesoleil.com a new (less that a week old) BT version 5, which is Windows Vista compatible and works with most cards (or at least CSR and ISSC dongles). It also runs on Windows 2000 and XP They also have a version 3.2 that they say is Vista compatible (runs only on CSR dongles). Both versions are free to download and try, 14.99 Euros to buy (about $21 US dollars). I tried both and could get neither to work at first. I discovered that I have the ISSC dongle chip, so I used BS version 5.0.
Then I went to their FAQ page, which informed me to not let Vista load a Bluetooth driver, because it will load the wrong one. Since I had already allowed Vista to do this, before going to Bluesoleil’s website, I had to go into Control Panel > System and Maintenance > Device Manager, find the Bluetooth device, Bluesoleil install.
I restarted the computer to allow it to clear out any registry entries from the old Vista BT stack. The Bluesoleil stack 5.0 which I had previously installed still did not work, so I uninstalled it, then rebooted the computer again to allow the registry to clean itself out.
I next tried to reinstall Bluesoleil 5.0 by running BlueSoleil.msi because this works on many Windows 2000 program installations. The installation did not work.
Then I noticed that there was a Setup.exe file in the download. So I removed the dongle, rebooted to allow the registry to normalize, then uninstalled BS again, rebooted again to clean out the registry. Finally, I installed BS 5.0 by running Setup.exe. I rebooted and then reinserted the dongle.
Success!!!
BS worked great immediately. No windows errors. My BT headset was recognized and paired up easily. I heard sound from my movie DVD playing in Windows Media Player through the headset and was able to record from the headset using Windows Sound Recorder. I could then hear the playback of my voice file through Windows Media Player.
It is too bad that we have to buy drivers instead of being able to just reuse the old ones, but I guess the developers need to make a living too. If I had to rewrite my drivers all the time to keep up with incompatibilites introduced by operating system changes that I had not control over, I would need to be paid for my time also.
BlueSoleil allows you to transfer 5megabytes across the BT link before you have to buy it. This allows enough time to see that it is really going to work for you. I only consumed about 700 bytes in and 700 bytes out while pairing and testing.
This is not a free solution, but it works!
Good luck to all.
Ron W Hardy said,
August 28, 2007 @ 6:08 pm
Also, while I have not yet tried it, BS 3.2 and 5.0 downloaded from their website is advertised as being Skype enabled.
Ron W Hardy said,
August 28, 2007 @ 6:26 pm
Sorry, I just found a typographical error in the fifth paragraph of my original post. I mistakenly said:
Then I went to their FAQ page, which informed me to not let Vista load a Bluetooth driver, because it will load the wrong one. Since I had already allowed Vista to do this, before going to Bluesoleil’s website, I had to go into Control Panel > System and Maintenance > Device Manager, find the Bluetooth device, Bluesoleil install.
The end of the paragraph should have read:
… Control Panel > System and Maintenance > Device Manager, find the Bluetooth device, highlight it, and uninstall it, checking the box to delete the driver also. This uninstalls and deletes the driver that Vista loaded (Way Point driver).
I hope this helps.
Ron W Hardy said,
August 31, 2007 @ 8:19 pm
I checked the Bluesoleil 5.0 BT stack with the ISSC dongle and my BT headset.
It worked fine and I was even able to make a couple of short phone calls using my iConnectHere.com SIPphone account.
So, I went ahead and bought the Bluesoleil BT program and registered it.
Fairly painless. It is working fine and I have made several 30 minute calls with the above setup. I have also watched a movie using the BT dongle/BS5.0/BT headset.
govindra said,
September 6, 2007 @ 9:32 am
hi everyone!
just a few words here:
- yes some dongles try to imitate a CSR code and so XP de-recognizes them. so you may have a ISSC-type dongle, but it may work for some (with embedded CSR) and not for others.
- to work PC suite with BlueSoleil, do this:
- use ONLY BS version 1.6.1.4 (Google it, you’ll find it, and it’s free)
- first uninstall ALL Bluetooth dongles, PC suite, Nokia Cable driver and PC cable connection
- disconnect any dongle
- reboot, clean registry
- load BS 1.6.1.4 using the setup.exe
- reboot, connect the dongle, let XP load BS drivers (it’ll do that auto)
- load PC suite
- reboot, make sure the dongle is connected, open PC suite
- go to manage connections, select BS USB BT, click configure
- you should be able to connect
- if it doesn’t, make sure your phone is NOT paired, if it is, un-pair it, make sure it’s discoverable (not hidden) and let BS discover again
- lastly, stay away from generic-and-cheap ‘e-bay’ dongles, invest well once, you’ll be happier!
- yes for Vista, BS 3.x is out, download, try the 5MB and then if you’re happy, buy…
hope this settles this thread once and for all and writes the epitaph for some cheap dongles. these cheapsters helped this thread grow…
thanx to Jon, you are great…
waldo said,
October 27, 2007 @ 11:27 am
Sh… what a piece of sh.. this hardware I tried everyting cambridge, belking all sorts of things
my bth.inf is really fu..ked and is driving me crazy. The blusoleil stack is broken when I try their example it doesn’t even works. This company is so abusive against third partie software that should be demanded for abuse monopolization and cheat to the users. No wonder that there are millionaires. Of course cheating on the persons anyone can do that. On tiop of that when you try to see inside the stack with a debugger they fuck you application. When you aske them about the API no answer. I should burn this piece of hardware and warn everybody around. A boot with strength on top of it is the solution. Or maybe alcohol and a match. Grrrrrrr. Beware they are selling shit from china. Chinese products are usually so shitty. Grrrrrrr.
waldo said,
October 27, 2007 @ 11:28 am
Sh… what a piece of sh.. this hardware I tried everyting cambridge, belking all sorts of things
my bth.inf is really fu..ked and is driving me crazy. The blusoleil stack is broken when I try their example it doesn’t even works. This company is so abusive against third parties software that should be demanded for abuse, monopolization and cheat to the users. No wonder that there are millionaires. Of course cheating on the persons anyone can do that. On top of that when you try to see inside the stack with a debugger they fuck your application. When you ask them about the API no answer. I should burn this piece of hardware and warn everybody around. A boot with strength on top of it is the solution. Or maybe alcohol and a match. Grrrrrrr. Beware they are selling shit from china. Chinese products are usually so shitty. Grrrrrrr.
Rohos - USB ключ » Blog Archive » Продолжаем тестировать Bluetooth logon said,
November 1, 2007 @ 8:04 am
[...] программа Rohos не видит ваш телефон: Можно посмотреть тут - смысл в том чтобы определить ID адаптера и прописать [...]
Comment on Further Adventures with Bluetooth by Rohos - USB ключ » Blog Archive » Продолжаем тестировать Bluetooth logon said,
November 26, 2007 @ 8:48 pm
[...] This is the cached version of http://joncellini.com/blog/archives/2004/10/07/further-adventures-with-bluetooth/#comment-63867 We are neither affiliated with the authors of this page nor responsible for its content. Comment on Further Adventures with Bluetooth by Rohos - USB ключ » Blog Archive » Продол… [...]
mukesh kumar said,
November 27, 2007 @ 4:54 am
sir,
here iam mukesh kumar i need ur help … pla solve my problem.. here i got lenova vista basic laptop, n mobile st is nokia7610…. iam not abl to install the pc suit n ther drivers of my mobile sset… even i hae install the.vista 761 0 nokia .. but still not working out .. i wanna acces ther intecrnet by gprs … so plz advice me wat to do ..
thanking u
urs mukesh
Comment on Further Adventures with Bluetooth by waldo said,
November 28, 2007 @ 7:43 am
[...] This is the cached version of http://joncellini.com/blog/archives/2004/10/07/further-adventures-with-bluetooth/#comment-63445 We are neither affiliated with the authors of this page nor responsible for its content. Comment on Further Adventures with Bluetooth by waldo [...]
Rohos Mini Drive » Blog Archive » Rohos Logon Key 2.5 beta version with BueTooth Logon - testing said,
December 30, 2007 @ 5:53 am
[...] If the driver was not gotten and installed or the Rohos software was not able to detect your Mobile read the following instructions here here [...]
fahim faizi said,
January 31, 2008 @ 3:19 pm
hi i have the mikomi bluetooth adaptor USB\VID_1131&PID_1001&REV_0373.
i need to download the softwear i dont no wear to download this from
Alamaven said,
February 16, 2008 @ 3:53 pm
Many Thanks Jon,
I’ve tried to find a solution since I’ve bought my ovislink BT usb…without success.
Until I’ve found your webpage!!!
Merci beaucoup!
jahwisdom said,
February 24, 2008 @ 1:22 pm
thanks a lot ! now my ovislink dongle works withou the bluesoleil f… stack.
anf pc suite works fine too !
Jarred said,
April 3, 2008 @ 2:43 am
Thanks for this great advice. Bluesoleil and PC Suite are a nightmare, they work intermittently but I personally wouldn’t waste any more time on them. This solution above is the ONLY way to get this stuff to work, and it’s simple. Thanks for this great information, and FUCK YOU Bluesoleil
John Anderton said,
June 4, 2008 @ 1:46 pm
Could I have the entire thing zipped up and sent to me by any chance? I had done this (by looking at a similar tut from some other site) and it worked but that was ages ago and now I’ve lost my driver cd
Thanks 
Could I get a precooked driver package?
You have my contact info
Andrew said,
June 4, 2008 @ 8:46 pm
Ive been working with/selling on Ebay these ISSC Bluetooth dongles and they are the better ones of the cheap crap. When first using on vista with vista BT stack I get a Error code 43. After a reboot they work fine. I cant comment on XP as I only use Vista a nix. Ive sold thousands of these adapters and not 1 complaint.
I think there are a few differnt issues here causing problems with BT.
#1 - Having 2 stacks/drivers causing XP/vista to get confused so it complains.
#2 - People not editing there inf file properly or editing the wrong one. Need to reinstall the driver after a inf change. Xp wont pick the change automaticly. Maybe also saving the inf as encoded text ?
#3 - Some people have no clue when it comes to computers and blame the hardware/software.