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.
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
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!”
@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
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
@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!
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.
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
@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!
Thanks for everything jon youve been a massive help
Clay
np – did you get it working?
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
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
@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.
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.
@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.
Thanks very much for this tip. Worked for me with a Safecom USB dongle, after struggling for ages with BlueSoleil – Many thanks!
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
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.
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
hi!
i cannot install the bluetooth software in my windows VISTA, please help & guid me to install. tank you.
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.
@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!
My BT Bluetooth working with BlueSoleil sw, but how to connect to internet in my mobile phon?
Thanks for help
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?
@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
yeah, but which section should I use?
@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
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
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
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]
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
@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.
MaudDib genius!!!
Thanks!!!
Got it working
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
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
@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.
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
@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!
@Jon
Sorry, thoght just it’s was you.
I have try but he don’t answer
Thanks you for answer me!!
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.
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
@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.
Thanks to Jon and Sam… that’s works like magic
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?
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.
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
cld some1 tell me how do u create a fake com port on ur computer for the BT dongle?
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
——————————–
Seems that i’ve found code 43 solution: http://my.opera.com/mishanja.b/blog/bluetooth-dongle-code-43
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.