Further Adventures with Bluetooth

Posted on by Jon

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:

  1. 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
  3. once you have determined the hardware ID locate the bth.inf file and make a copy of it
  4. open up the copy in an editor and scroll down to the Device section
  5. 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_1002

    I named it as an Erickson Bluetooth Adapter since the chipset in my dongle appears to be made by Erickson.

  6. Save the file
  7. Update the dongle drivers to use your newly edited inf file. If all goes well it will detect and install the adapter.
  8. Enjoy a working Bluetooth stack :)

To make it easy you can download a copy of the bth.inf file that I already edited here.

128 thoughts on “Further Adventures with Bluetooth”

  2. 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.

  3. just to say a WORD!!!

    MAN.. U ARE A F**** GENIUSSS!!!..
    THANX A LOT!!….

  5. 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.

  6. 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!

  7. 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

  8. 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

  10. 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

  11. 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

  12. had the same problem as keithy described,

    tried adding the “ISSC Bluetooth Radio= BthUsb, USB\Vid_1131&Pid_1001″ line but same code 43 :(

  13. 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 :(

  14. 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 :(

  15. have the same prooblem error code Windows has stopped this device because it has reported problems. (Code 43)

  16. 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.

  17. 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 :D , 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:

  18. 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

  19. 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” :)

  20. 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.

  21. 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.

  22. 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.

  24. 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

  25. Same error 43 for me too. I think am just gonna have to throw this piece of junk out

  26. 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..

  29. Jon, can you please help us for error code 43? I think that we’ve no clue how to fixed this. Pleaseeeeee.

  30. 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 :)

  31. 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!!!

  32. I gave the same problem: Error Code 43 with the very same BT dongle … tried everything mentioned here … HEEEEEEEEEEEEELP PLEASE! Any ideas??

  33. 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.

  34. 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!

  35. 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.

  37. 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.

  38. 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

  39. 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.

  40. 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.

  41. 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.

  42. 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.

  44. 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.

  45. where the hell is the bth.inf file located? is there a default in window or what?

  47. 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.

  48. 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 0x00001F43 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

  49. 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

  50. and how exactly did you deal with code 43 error? your bth.inf is not different from what was posted before.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>