Thanks Sly  this is the solution for my problem, to connect my nokia n73 to my Eeepc 1000H

greetings Peter from Holland

Thanks Sly for those tips.  I have just spent the best part of a day getting bluetooth dial up networking to work on my 1000H using my Blackberry Pearl (8100).  It now works perfectly, but only after a huge performance.  I tell my story in case it helps others (or inspires an epic novel).

I followed the instructions on the rim website

http://www.blackberry.com/btsc/search.d … 2082973898

And managed to contact orange to find out that their APN is 'orangeinternet'...

Thought it was meant to be plain sailing from there...

I can't tell you how frustrated I was... I got it to connect perfectly via USB tethering (but who wants to carry around a usb cable on the off-chance that I might need to con nect it to my phone?) but it refused to connect via bluetooth.  I was able to pair the Eee pc and the blackberry via bluetooth, I was able to enable the bluetooth modem, I was able to use dial up networking to make the phone call any number i wanted..... but, it refused to call the magic number - *99#.

I finally worked out that it was the Widcomm bluetooth stack causing all the problems (only after repeating the whole experiment on a second laptop that used the microsoft stack and getting it to connect first time...).  Apparently the widcomm bluetooth stack often causes these problems - it isn't just confined to Eee PCs.

So...

I uninstalled the widcomm drivers and suitably edited the bth.inf file (and I did check for errors..!) as suggested by Sly.  Unfortunately that resulted in the computer refusing to recognise the bluetooth module.  After some further wrestling with 'add new hardware' I eventually had a perfectly installed bluetooth device, but no windows stack (in fact no bluetooth stack at all...!), meaning I couldn't do anything with the Blackberry.

Anyway, finally managed to resolve it (4 hours later).  Turns out that it was a mistake to point 'add new hardware' to the Widcomm drivers I had downloaded from the Asus website.  When I completely uninstalled the Widcomm drivers (by reinstalling the entire widcomm software and then immediately uninstalling it) and instead used windows' own drivers, windows finally kicked in and enabled its own Bluetooth stack.

So I can now use my Orange GPRS connection to browse the internet.... the only problem now is having the discipline not to use it (my wallet can't cope with the extra data charges).

Has anyone else had these problems?

Thanks again Sly

Ben

Sly, great idea to use the ms-stack since i have problems with the widcom and my BB Pearl to. Only problem is that after complete deinstallation of the widcom stuff and modifing the bth.inf no device driver will be found. Any Idea? I have already checked the vid/pid in Device manager etc. Is there any way to force the MS stack installation?

; 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=04/13/2008,5.1.2600.5512

[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
Azwave=Azwave, NT5.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_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

[Azwave.NT.5.1]
BT253=                                           BthUsb, USB\Vid_0b05&Pid_b700

;------------- 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, 0x00000002, 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,0x00020002,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\Drivers\Bthport.sys;%%SystemRoot%%\System32\Drivers\BthUsb.sys"
HKR,,TypesSupported,0x00010003,7

;----------------------------------------------------------------------------
; BthEnum support sections
;----------------------------------------------------------------------------
[BthEnum.NT]
CopyFiles=BthEnum.NT.Copy

[BthEnum.NT.Copy]
bthenum.sys

[BthEnum.NT.Services]
AddService = BthEnum, 0x00000002, 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}",0x00010003,1
; HCRP
HKLM,%Bthport.Parameters%\SupportedServices,"{00001126-0000-1000-8000-00805f9b34fb}",0x00010003,1
; DUN
HKLM,%Bthport.Parameters%\SupportedServices,"{00001103-0000-1000-8000-00805f9b34fb}",0x00010003,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%,,0x00000010
HKLM,%Bthport.Parameters%\Devices,,0x00000010
HKLM,%Bthport.Parameters%\Services,,0x00000010

[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%,0x00010003,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 0x00000540 matches Bluetooth keyboard devices.
HKR,,%StoreLinkKeyCodMasks%, 0x00000001, 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", 0x00010001, 1
HKR,"Parameters\Restrictions\COD Major 05 Minor 20","DontAddIncomingSPPInWizard", 0x00010001, 1
HKR,"Parameters\Restrictions\COD Major 05 Minor 30","DontAddIncomingSPPInWizard", 0x00010001, 1
HKR,"Parameters\Restrictions\COD Major 06 Minor 20","DontAddIncomingSPPInWizard", 0x00010001, 1

[BthPort_EventLog_Inst]
AddReg=BthPort_EventLog_Inst.AddReg

[BthPort_EventLog_Inst.AddReg]
HKR,,EventMessageFile,0x00020002,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\Drivers\Bthport.sys"
HKR,,TypesSupported,0x00010003,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-Funkgeräte"

BTHPORT.SvcDesc="Bluetooth-Porttreiber"
BthEnum.SVCDESC="Bluetooth-Anforderungsblocktreiber"
Bthser.SVCDESC="Serieller Treiber für Bluetooth-Funkgerät"
BTHUSB.SvcDesc="USB-Treiber für Bluetooth-Funkgerät"
BthBCSP.SVCDESC="BCS-Transportprotokolltreiber"
Serial.SVCDESC   = "Treiber für seriellen Anschluss"
FSQUIRT_DESC="Dateiübertragungs-Assistent für Bluetooth"

COMMUNICATIONS_GROUP="Zubehör\Kommunikation"

Bth.Diskname="Bluetooth"
MS="Microsoft"
Microsoft="Microsoft"

; ------------- Device Strings - start -------------------------
; Microsoft
BTH\MS_BTHBRB.DeviceDesc="Microsoft Bluetooth-Auflistung"

; ------------- Device Strings - end  --------------------------

jbkerner32 wrote:

Sly, great idea to use the ms-stack since i have problems with the widcom and my BB Pearl to. Only problem is that after complete deinstallation of the widcom stuff and modifing the bth.inf no device driver will be found. Any Idea? I have already checked the vid/pid in Device manager etc. Is there any way to force the MS stack installation?

Ok, yes erm, from the looks of it your bth.inf looks perfectly fine, now I'l admit I never bothered with the Widcomm software so I don't know 100% the steps in removing it, although unistalling the software should get rid of the drivers for the device as well.

I probably should of written this up better, I'll do screen shots if I do a re-install later on... When you go into the device manager find the bluetooth device, Right click properties, go to driver tab, click update driver, then select install from specific location (advanced) and click next, Then click, 'Don't search, I'll choose the driver to install' then select Bluetooth Radios and it should come up with the 'BT253' driver (without the digitally signed symbol next to it), select that then go next, allow the driver to be installed althought it's not digitally signed... and that should be it... if it asks for any other drivers, just tell it to search automatically and should find it, like the Microsoft Bluetooth Emunrator thingy... lol

you should find in the taskbar icons theres a different bluetooth icon to the Widcomm version and in the contol panel there if you want to double check it worked.

jbkerner32, my apologies, I didn't look hard enough, I've just noticed an error in your editing of the bth.inf file, you missed out a fullstop between the NT and the 5.1

Azwave=Azwave, NT5.1   needs to be... Azwave=Azwave, NT.5.1

save it and then try installing it the driver now. hopefully it'll work this time.

Sly wrote:

jbkerner32, my apologies, I didn't look hard enough, I've just noticed an error in your editing of the bth.inf file, you missed out a fullstop between the NT and the 5.1

Azwave=Azwave, NT5.1   needs to be... Azwave=Azwave, NT.5.1

save it and then try installing it the driver now. hopefully it'll work this time.

Hey Sly, your original post is missing the "."

Sly wrote:

Now add a line to the that section a line such as (without quotes of course):  'Azwave=Azwave, NT5.1 '

fair dos, I was drunk pretty drunk when I made the original post, lol. luckily most seemed to have noticed my mistake when they edited there files tho.

woohoo....no more BTTray errors!

I could use some help. I'm trying to follow these instructions to set up my ATT Blackberry as a bluetooth modem with my 1000H.

When I uninstall the Widcomm software, the bluetooth connection wizard goes away and I can't reestablish the bluetooth connection.

I did make the changes to bth.inf

Bluetooth doesn't show up in the device manager now.

What am I missing?

Thanks

Thanks for the tips, it works for my Asus USB-BT21 too

BTW, BT GPS vs USB GPS, which is less resource intensive?

wai wrote:

Thanks for the tips, it works for my Asus USB-BT21 too

BTW, BT GPS vs USB GPS, which is less resource intensive?

Well both are using emulated serial ports so I doubt there's much difference, espically with the Windows Stack being used as it uses nothing compared to Widcomm's. I'd personally say, Bluetooth is good because it means it'll work with anything, even future mobiles so it's worth more value, plus it'll never need drivers for any new OS. Only main problem I have with Bluetooth GPS is charging it, it runs off a battery so can't be run constantly and can't be charged of USB, but then a phone couldn't charge it then either.

ViciousXUSMC wrote:

I think the Asus G50V-A1 uses the widcomm stack for its card its also the BT-253, my major qualm with the stack it isues is that it totally sucks!  Its not slow or anything but it has a super limited interface, no disconnect option, and my worst issue of all it does not work with my wiimote!

I solved the problem temporarily by using bluesoleil, but problem with that is that its like $30 for the full version, the demo version has a 2mb limit, thats pretty good for the wiimote actually but listening to my headphones its like 30 seconds

So can you tell me how to know if I am using the Widcomm or MS stack? (I see bluetooth radios as widcomm and blutooth enumerator as microsoft) And how to find and make this change on any computer (meaning I probably have to find a different value like the usb port and all that jazz) Im going to give this a shot now tho and see if it works for me.

Im also getting a EEE 1000H and will probably make use of this information.

Update: I tried to change the microsoft bluetooth enumerator drive to the BT-253 (should be broadcom) driver and it fails it installs but wont start. Maybe because its not x64 compatible?

I use Vista x64 so dont know if it changes anything.

Sadly I can't really throw out much advice for this, as I neither use Vista nor a x64 version, as neither of these would go with my EEE PC anyways. I personally think it's probably not a case of the 64-bit tho as I believe primarily all USB (internal or otherwise) use pretty much the same chips bar maybe a minor few, so driver wise they all use the same ones, hence what I published here is just a way for Windows XP to recognise the bluetooth by it's VID and PID to use generic bluetooth drivers.

I think your best to look into it through google, it didn't take me long to find some stuff... http://www.insanelymac.com/lofiversion/ … 19881.html

It speaks about doin it there but seems rather involved, plus there running Vista on Mac hardware so it might only need the correct work done in the bth.inf file to get it working.