XDAII and bluetooth gps.

[stevew]

Hi all,

I have just bought a tomtom bluetooth gps system, I can bond to the gps receiver ok, but it just wn't connect. There is deffinately a connection during the bonding process but that is it, it never connects again.

Any help would be greatly appreciated.

Thanks

Steve

[Puff The Magic Wagon!]

If its anything like the EMTAC then it needs to be considered as a serial port...

Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.

I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously

[stevew]

If its anything like the EMTAC then it needs to be considered as a serial port...

Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.

I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously

I think the problem is that the xdaII doesn't support a bluetooth serial port profile. I have tried virtually everything and had no luck.

Please keep me posted on how you get on, I really hope we can get this sorted or I will have a gps reciever paper weight.

Steve

[Puff The Magic Wagon!]

Hmm :(

Due to the nature of yesterday, it wasn't until midnight (GMT) that I could get to have a play with my XDA II & EMTAC BTGPS (& I wasn't sober ;) )

Installed TTN2 and tried to connect - not a sauasage :(

There "seems" to be something using COM6 and as such TTN2 can't use that as the path to the EMTAC - check box in the GPS options won't check. Turn off BT & you can check the box, but it won't connect as something else obviously can't use it either :? Dunno - I'm not a programmer but I'm going to have to check this out.

I'll speak to a contact @ EMTAC & see if they have been sucessful in bonding to an XDA II (HTC2?) & if so how. Otherwise I'll keep on playing with it & see what I can find out.

Anyone else got any tips or ideas what might be the way of resolving this?

[cruisin-thru]

Have you tried turning off the "receive incoming beams" under settings/connections, that may or may not free up the first com port.

[xdaguru]

I know someone with the same problem. O2 have told him that Tom Tom are working on a new version of software to fix this specific issue and it will be downloadable from the TT site. They couldn't say when.

xdaguru

[Puff The Magic Wagon!]

Beam off did seem to allow me to connect to COM6 but not for my device :( Might be worth trying Steve because TT Wireless was one I could connect to.

IIRC from iPaq Bluetooth Manager, you had to bring up the device options once bonded and then select a serial connection. Pocket Loox as well. The BT Manager in the XDA II is very basic. So I do wonder if its a TT soluble solution or does it need an upgrade to the BT Manager?

If its a problem soluble by TT then I'm prehaps more hopeful ;)

[DannyBoy]

Sorry to go off topic but I wonder if this is the same PTMW that I know?

How you doin m8?

[Puff The Magic Wagon!]

Hello Danny

Yes it is I :D

Can't be that many PTMW!'s about ;)

All's well & I'll catch you on the other side one day :)

[DannyBoy]

Yeah I guessed there could be only one PTMW ;)

I take it you're lucky enough to have an XDA2 already? I always knew u were a gaget fan like myself. I have a month left on my XDA1 contract :(

Hopefully Tom Tom will have the problem ironed out by then as I have TTN2 aswell.

Pay us a vist on Scoobycity soon. Alots changed and we're alot bigger now ;)

[Marco van Berkel]

Is there anyone who got the XDA2 working with a bluetooth GPS ? I am very eager to get one (both the XDA2 and a bluetooth GPS) but I would like to hear from some who got a combination working .

Thanks,
Marco

[Puff The Magic Wagon!]

Its being looked into Marco

It may be that the BT Manager may not have various BT options enabled, so it may need a software update/patch from O2.

[Puff The Magic Wagon!]

Spoke to O2 this morning.

They are "aware that not everything works with BT" and are working on a software update.

No timescale offered :(

[mother]

I have an Emtac and was going to buy the XDAii to replace my Loox but without this bluetooth connectivity I will save my money. However interestingly it does say on the XDA website...

...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car

I'd say this is enough to get a refund if you want one. Page in question is located here...

http://www.my-xda.com/gps.html

[Southern_Man]

The fault with the TomTom software and Bluetooth lies solely in TomTom's software. TomTom have recognised this and are aggresively working to fix the problem.

The TomTom GPS software doesn't know to read the details of the virtual com port. So give them some time to fix the problem....

[mother]

Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?

[domloff]

Hi

I too have just upgraded to the XDA II from the Ipaq 3970, and I also have an Emtac BTGPS.

Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.

It would be very interesting to find out if any one has a TomTom BTGPS and can serial link it to the XDA II

Dom

[Southern_Man]

Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?

The fact you're able to bond with the unit shows that bluetooth is working correctly.

The issue is that the tomtom software can't read com6: (which is where bt is hiding) or do anything with it, because of the way the software works.

This is because the Bluetooth manager on Xda II is from MICROSOFT, whereas on other devices it's manufacturer specific. As far as I know this is the first ever deployment of the MS Bluetooth stack directly.

[mother]

Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.


Then why do they say they support TomTom on their website? Seems like a few people at O2 dont really know what's going on?

[Puff The Magic Wagon!]

I've not known that O2 has ever supported EMTAC BTGPS 'cos the XDA (1) didn't have bluetooth support :?

Surely it is the BT manager that is at fault? Not allowing the a serial connection from the manager to the Emtac?

TomTom is looking to read Com6 (when told to) but the info its getting is not sufficient or mapable.

I've run BTGPS with a TDK B/tooth card and it needs to be told (as do other managers) to make a serial connection to the BT device.



Test for someone (I'll try & do it too)

Find an alternate mapping software that *should* accept a BTGPS device & try to connect...

[Puff The Magic Wagon!]

Alternatively, anyone got an iPaq/Loox & a BT GPS device?

Can you get THIS (http://www.pocketgear.com/software_detail.asp?id=8269&associateid=9) piece of software working on it?

In theory it *should* work but once again Com6 is not available to the software with BT on when you try and connect.



So why is Com6 not available?

[domloff]

I've got an IPAQ and the Emtac BT GPS. This is what I have used for the last year (well nearly a year).

I've had no problems using it with CoPilot, TomTom and all sorts of different GPS programs.

The XDA II just does not support the proper serial profile for all these programs.

I find it very hard to believe that TomTom are working on a fix to their software as its a much more fundamental issue.

[RedBull]

I've tried it with pocket gps, pocket navigator and tomtom navigator 2. Although they work with a cable gps, NONE of them work with a bluetooth gps on the xda2.

Looks like the problem is with the XDA

:(

[mother]

dissapointingly and worryingly for those who have brought an XDA2 and are hoping to use it with their bluetooth GPS the section on the XDA site that says:

...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car

...has been erased! Lets hope this has just been removed temporarily whilst they get the thing working and is not a perminant change! :(

[RedBull]

I hope they fix it or some produces a fix as this is the main reason I brought the XDA2 !
:evil: :( :evil: :( :evil: :( :evil: :( :evil:

[mother]

recieved this from O2 today...

Dear Mr Stockley,

Thank you for your email.
Unfortunately, we have been experiencing difficulties with the Bluetooth aspect of TOMTOM. TOMTOM are aware and are currently developing a patch to be able to get this to work. We have only tested the TOMTOM and DESTINATOR GPS softwares, and the cable connections work fine.

Please keep an eye on www.my-xda.com for any updates on the XDA II

Kind regards
Mark
O2 Data Support



Now... is this a problem with Bluetooth or TomTom? o2 say TomTom but others say bluetooth and i did read somewhere that somebody couldn't get their Emtac working with destinator either?

[mrg2003]

Will TOMTOM 2 bluetooth GPS work with XDA2 from O2

Thank you for contacting TomTom E-Support and Services.
We apologies for the delay and thank you for your patience,
We are still in the testing stage with the XDA 2 and will announce it on website when the device tested .

[sdjones]

My friend and I have just got our XDA II's and are very impressed. They are probably the best devices in the market at the moment...

My friend just purchased the BT version of the GPS TomTom, needless to say I just purchased the cable connection...Anyone wanna guess which one works :-)

Hope TomTom or O2 sort out the problem soon with the BT...

[cruisin-thru]

I just bought a gizmo that converts gps signal to irda, just align the ir ports, set tomtom or whatever to use irda and thats it, its a brilliant device for people without serial port etc. I believe I am the first in the country to get this device and pleased to say it is very good running on ipaq 1910 "they all said gps couldnt be added to it", plus other ipaqs.

[towa]

As you already might know, there is nearly no way to get it to work with the Microsoft BlueTooth stack. Nevertheless my GPS works perfectly with the IPAQ of my colleage, which is using the Widcomm stack. Finally I decided to take the files from his PDA and to adapt the registry and 10 hours later I got it to work. Unfortunately there seems no way to buy this software so the only way is to extract from another PDA. If anyone is interessted I can post some more details :D

[ppcitaly]

Yes! Sure!
We are really interested in your method!
Please tell us.
My Thanks

[domloff]

From all of us who have an 'old' 3970 which worked perfectly with BTGPS, and now have a XDA II we look forward to seeing how you did it! :D

Dom

[Helio]

:D Please let us know what you did. :wink:

[orinoco]

Hello:

I am very interested to know how you got this to work. Are you talking about the Widcomm BT software, cuase I have it and can email it or post it.

Fernando

[Helio]

Please post it

Helio

[RedBull]

I can host it on my web server if you email it to me, Les.field @ Virgin.net

[orinoco]

Go to:

ftp://www.shawus.com

Username is hydrosphere, password is 12345

Goto the Widcomm subdirectory and download the zip file.

Let me know if/how it works.

Fernando

[sweeney]

Absolutely we want to know what you did. The XDAII is near perfect except for the bluetooth stack, which appears to have been a friday afternoon job (after a liquid lunch).

Using a bluetooth equiped desktop PC and service discovery shows what an incomplete job they did of it. The XDA reports a single mysterious service called SSA, compared to an iPaq which admits to 5 services which are all obviously named and fundemental in nature (serial and network access for example).

Steve

[RedBull]

Hi Fernando,

It tries to install as a desktop or laptop then it wants data1.cab and quits.

What next.....

[sweeney]

I've uploaded a newer and complete bluetooth driver for CE (to the above FTP server), but it won't install without finding an adaptor on the target machine.

Steve

[orinoco]

I tried it, and as you indicate, it will not install on the XDAII. It does not seem to recognize that the XDAII has a BT radio. So, are we stuck with a crappy BT stack?

Fernando

[Helio]

Hi I´m trying copy some files from the ipaq to the xda II as "towa" did yesterday. I will let you know if it works.
I hope TOWA let us know ´what he did.
:?
Helio

[towa]

Well, I did the following:

- I took al the files from an update I found the IPaqs
(Take the .cab and open it with a double click. Extract all files and rename them to their real name. The .000 file contains the real name of all the others.)
- Then I recognized that BTREZ.DLL was missing. That's the one with all the resource like dialogs, menus a.s.o. I got a copy from the IPaq of a friend
- I extracted the Registry Part HKLM\Software\Widcomm from an IPaq and changed the following keys:

Widcomm\BTCOnfig\General\TransportLibrary to "BtCeBCSPTrans.dll because our BT Device in the XDA uses BCSP protocoll
Widcomm\BTConfig\SerialTransport\Port to 6 (This is the serial port of our BT device)
Widcomm\BtConfig\Applications\0001\ComPortNumber to 7 (This is the virtual com port which will use the TomTomGPS later on)

Then there some more keys in HKLM\Drivers\BuiltIn which must be set. I will post them later on when I'm at home

Finally you have to know that the BTCETray always restores the TransPortLibrary to "BTCESerialTrans" and I just patched it to BTCEBSCPTrans.dll using a Hex Editor.

That's all, basically.

Finally I created the source code for the BTREZ.DLL to translate everything to german. (The BTREZ.DLL I got was in spanish. I speak spanish but I prefer german :D ) It's nearly complete

[towa]

http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/19650.html
:wink:

And I forgot something important: Some registry entries must be removed to deactivate the Microsft BT Stack. Otherwise COM6 is obviously in use.

Remove all values in HKLM\Microsoft\Bluetooth\HCI and remove the complete key HKLM\Microsoft\Bluetooth\Transports\BuiltIn\3

[orinoco]

Hi Towa:

I tried your procedure above and have some questions:

a) When I downloaded the ipaq update from the HP web site you provided, I did not see any .cab files to open with a double click. Are you talking about the data1 and data2 files that appear when you extract the files?
b) I did not see any .000 files either. I think I am misunderstanding something here.
c) Do you have the BTREZ.DLL file you can share with us? I can give you an ftp site to post (see above).
d) Same for Registry Part HKLM\Software\Widcomm; do you have this to post?
e) Can you post these instructions when you complete the process?

Many thanks in advance.

Fernando

[Helio]

Hi,
Will the bluetooth headset profile work after this?

:? Just wonder

Helio

[Helio]

Hi Fernando,
I just upload the file.
Let us know how it´s going.

Helio :wink:

[Roadster]

I don't know if this will help but I have a BT gps smart made by fortuna and use it with a hp 2210 which is ppc2003 and ms stack and this works ok with navigator 2. I also have XDA and have just ordered the XDA 2 hoping to then not need the 2210 and sell it but from your experiences this is not looking good at the mo. :cry:

[tadzio]

I don't know if this will help but I have a BT gps smart made by fortuna and use it with a hp 2210 which is ppc2003 and ms stack and this works ok with navigator 2.

That sounds good :-) It would be nice if you could do us a favor: make the Extended_ROM visible on your device (set HKLM\System\StorageManager\Profiles\TRUEFFS_DOC\Mo untFlags to 0 in the registry) and check if there's anything Bluetooth-related in there. Also, it may be helpful to see the registry entries of your device under HKLM\Microsoft\Bluetooth.

What Bluetooth services does your PC list for your iPAQ when they are connected?

Thanks in advance!

Daniel

[JoseF]

@Daniel
Hi , I have one ipaq 5550 let me know whitch information you need
And how I can get it.

[domloff]

I don't know if this will help but I have a BT gps smart made by fortuna and use it with a hp 2210 which is ppc2003 and ms stack and this works ok with navigator 2. I also have XDA and have just ordered the XDA 2 hoping to then not need the 2210 and sell it but from your experiences this is not looking good at the mo. :cry:

I could be wrong but as far as I know the XDA II is the first implementation of the MS BT stack. All IPAQs (inc. 2210) use WIDCOMM as the BT stack.

MS have never really grasped the ideal of compatability if you look at the 'BT' keyboard and mouse you'll see what I mean! :cry:

Getting the WIDCOMM stack up and running on the XDA II is a very good thing and very important to all of us that have a BTGPS and a XDA II.

Looking forward to seeing everybodies efforts in getting this to work. I'll be have a play at getting it working myself! :lol:

[tadzio]

@Daniel
Hi , I have one ipaq 5550 let me know whitch information you need
And how I can get it.

Very good. It seems the HP2210 doesn't use the MS stack (as Roadster wrote), so I'm back to trying to get the Widcomm stack to work. Still trying to collect the necessary information though. It seems most of what is needed is described in this thread, except for the precise registry changes.

@JoseF:
It would be very helpful if you could post the registry entries of your iPAQ 5550 for the following branches:
- HKLM\Software\Widcomm
- HKLM\Drivers\BuiltIn

To get these, you need a registry editor that runs on you iPAQ. There are many of them. One that is used quite often is the one contained in Resco Explorer 2003, see http://www.resco-net.com/explorer.asp. You can download a free 14 day trial version from their site.

HKLM stands for "HKEY_LOCAL_MACHINE". Just go to the branches mentioned above, and export them to a file. ActiveSync these files to the PC, and paste their content into a message on this board. :-)

Many thanks in advance!

Oh, and if you happen to have a German iPAQ, I wouldn't mind a German BTREZ.DLL... :-) should be in the Windows directory (I guess). Again, just use ActiveSync to copy it to your PC. Then you can either upload them (under a different name) to the FTP site mentioned above, or email them to me (tadzio@tadzio.com), and I'll upload it.

Cheers
Daniel

[towa]

These are the registry entries

REGEDIT4

[HKEY_LOCAL_MACHINE\Comm\BTCEPAN]
"DisplayName"="Bluetooth PAN User Driver"
"Group"="NDIS"
"ImagePath"="doesnotexist.dll"

[HKEY_LOCAL_MACHINE\Comm\BTCEPAN\Linkage]
"Route"=hex:42,00,54,00,43,00,45,00,50,00,41,00,4e,00,31, 00,00,00,00,00

[HKEY_LOCAL_MACHINE\Comm\BTCEPAN1]
"DisplayName"="Bluetooth PAN User Driver"
"Group"="NDIS"
"ImagePath"="doesnotexist.dll"

[HKEY_LOCAL_MACHINE\Comm\BTCEPAN1\Parms]
"BusNumber"=dword:00000000
"BusType"=dword:00000000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC1]
"DeviceArrayIndex"=dword:00000001
"Dll"="BtCeIf.dll"
"FriendlyName"="Bluetooth Port 1:"
"Index"=dword:00000001
"Order"=dword:00000001
"Prefix"="BTC"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC2]
"DeviceArrayIndex"=dword:00000002
"Dll"="BtCeIf.dll"
"FriendlyName"="Bluetooth Port 2:"
"Index"=dword:00000002
"Order"=dword:00000001
"Prefix"="BTC"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC3]
"DeviceArrayIndex"=dword:00000003
"Dll"="BtCeIf.dll"
"FriendlyName"="Bluetooth Port 3:"
"Index"=dword:00000003
"Order"=dword:00000001
"Prefix"="BTC"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC4]
"DeviceArrayIndex"=dword:00000004
"Dll"="BtCeIf.dll"
"FriendlyName"="Bluetooth Port 4:"
"Index"=dword:00000004
"Order"=dword:00000001
"Prefix"="BTC"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtCeProfiles]
"DeviceArrayIndex"=dword:00000001
"Dll"="BtCeIf.dll"
"FriendlyName"="Shims to BtCeProfiles on BTP1:"
"Index"=dword:00000001
"Order"=dword:00000001
"Prefix"="BTP"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtCeStack]
"DeviceArrayIndex"=dword:00000001
"Dll"="BtCeIf.dll"
"FriendlyName"="Shims to BtCeStack on BTS1:"
"Index"=dword:00000001
"Order"=dword:00000001
"Prefix"="BTS"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial4]
"DeviceArrayIndex"=dword:00000004
"Dll"="BtCeIf.dll"
"FriendlyName"="BT Serielle Schnittstelle COM4:"
"Index"=dword:00000004
"Order"=dword:00000000
"Prefix"="COM"

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial7]
"DeviceArrayIndex"=dword:00000007
"Dll"="BtCeIf.dll"
"FriendlyName"="BT Serielle Schnittstelle COM7:"
"Index"=dword:00000007
"Order"=dword:00000000
"Prefix"="COM"

[HKEY_LOCAL_MACHINE\ExtModems\BtDialupModem]
"DeviceType"=dword:00000001
"FriendlyName"="Bluetooth Dialup Modem"
"Port"="BTC1:"

[HKEY_LOCAL_MACHINE\ExtModems\BtNullModem]
"DeviceType"=dword:00000000
"FriendlyName"="Bluetooth Null Modem"
"Port"="BTC2:"

[HKEY_LOCAL_MACHINE\ExtModems\BtFaxModem]
"DeviceType"=dword:00000001
"FriendlyName"="Bluetooth Fax Modem"
"Port"="BTC3:"

[HKEY_LOCAL_MACHINE\ExtModems\'BlueToothActiveSync]
"DeviceType"=dword:00000000
"FriendlyName"="Widcomm BT Null Modem"
"Port"="BTC4:"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Calendar\AddIns\WidcommSendto]
"Dll"="\\Windows\\BtCeSendTo_Poom.dll"
"Menu"="Mit Bluetooth übertragen"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Contacts\AddIns\WidcommDialer]
"Dll"="\\Windows\\BTDialer.dll"
"Menu"="Mit Bluetooth wählen"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Contacts\AddIns\WidcommSendto]
"Dll"="\\Windows\\BtCeSendTo_Poom.dll"
"Menu"="Mit Bluetooth übertragen"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Tasks]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Tasks\AddIns]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PimApps\PimE xtensions\Tasks\AddIns\WidcommSendto]
"Dll"="\\Windows\\BtCeSendTo_Poom.dll"
"Menu"="Mit Bluetooth übertragen"

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0001]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"ComPortNumber"=dword:00000007
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"Name"="Serielle Schnittstelle"
"SecurityId"=dword:00000001
"UserInstalled"=dword:00000000
"UUID"=dword:00001101

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0002]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"AutoConnect"=dword:00000001
"ComPortNumber"=dword:0000000c
"Encryption"=dword:00000000
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:ffffffff
"ModemInstalled"=dword:00000001
"Name"="LAN Access Using PPP"
"Password"=""
"SecurityId"=dword:00000002
"UserInstalled"=dword:00000000
"UserName"=""
"UUID"=dword:00001102

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0003]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"ComPortNumber"=dword:0000000b
"Encryption"=dword:00000000
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:ffffffff
"ModemInstalled"=dword:00000001
"Name"="Dialup Networking"
"SecurityId"=dword:00000003
"ShowWizard"=dword:00000000
"UserInstalled"=dword:00000000
"UUID"=dword:00001103

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0004]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX Object Push"
"SecurityId"=dword:00000005
"UUID"=dword:00001105

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0005]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX File Transfer"
"SecurityId"=dword:00000006
"UUID"=dword:00001106

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0006]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"ComPortNumber"=dword:0000000d
"Encryption"=dword:00000000
"GUID"="{00001111-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"ModemInstalled"=dword:00000001
"Name"="Fax"
"SecurityId"=dword:0000000b
"UserInstalled"=dword:00000000
"UUID"=dword:00001111

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0007]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"ComPortNumber"=dword:0000000e
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"Name"="ActiveSync Serial Port"
"SecurityId"=dword:00000001
"UserInstalled"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0008]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000001
"Encryption"=dword:00000000
"GUID"="{00001112-0000-1000-8000-00805F9B34FB}"
"Name"="Voice Gateway"
"SecurityID"=dword:0000000c
"UUID"=dword:00001112

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0009]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001108-0000-1000-8000-00805F9B34FB}"
"Name"="Headset"
"SecurityID"=dword:0000000c
"SecutiryID"=dword:00000008
"UUID"=dword:00001108

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Debug]
"LogIPAddr"=dword:00000000
"Transport"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devic es]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Filte rs]
"AllowOthersToDiscover"=dword:00000001
"PeriodicInquiry"=dword:00000001
"UseInquiryFilters"=dword:00000000
"WhoAllowedToConnect"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Gener al]
"AutoDiscovery"=dword:00000000
"DeviceName"="Pocket_PC"
"LicenseKey"="E3E534E19B3E82141321561D913215633CC92760F687E82F"
"MaxSimultConnections"=dword:00000007
"MinorClass"=dword:00000010
"ModuleType"=dword:00000000
"NoChangeNameAllowed"=dword:00000000
"NoResetAllowed"=dword:00000000
"NoSleepingWhileConnected"=dword:00000001
"PeriodicInquiry"=dword:00000000
"PeriodicInquiryRetryTime"=dword:0000001e
"PinCode"=""
"PnpId"=""
"PowerControlLibrary"="Auto"
"SecurityType"=dword:00000002
"StackMode"=dword:00000000
"TransportLibrary"="BtCeBCSPTrans.dll"
"UseFixedPin"=dword:00000000
"UseIconView"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Seria lTransport]
"BaudRate"=dword:000e1000
"ByteSize"=dword:00000008
"Device"="COM"
"FlowControl"=dword:00000001
"Parity"=dword:00000000
"Port"=dword:00000006
"StopBits"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0001]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000001
"ComPortNumber"=dword:00000004
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"Name"="Serielle Schnittstelle"
"SecurityId"=dword:00000001
"UserInstalled"=dword:00000000
"UUID"=dword:00001101

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0002]
"AcceptBusinessCards"=dword:00000001
"AcceptCalendarItems"=dword:00000001
"AcceptEmailMessages"=dword:00000001
"AcceptNotes"=dword:00000001
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000001
"DefaultBusinessCard"=""
"Encryption"=dword:00000000
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"InboxDirectory"="\\Temp"
"Name"="OBEX Object Push"
"SaveInPIM"=dword:00000001
"SecurityId"=dword:00000005
"SendBusinessCardOnRequest"=dword:00000001
"UUID"=dword:00001105

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0003]
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"Auto"=dword:00000001
"Encryption"=dword:00000000
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX File Transfer"
"Root"="\\My Documents"
"SecurityId"=dword:00000006
"UUID"=dword:00001106

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0004]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000000
"BaudRate"=dword:0000e100
"Enabled"=dword:00000001
"Encryption"=dword:00000000
"FlowControl"=dword:00000001
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"ModemComPortNumber"=dword:00000001
"Name"="Dialup Networking"
"SecurityID"=dword:00000003
"UUID"=dword:00001103

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0005]
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Auto"=dword:00000000
"Baudrate"=dword:00000004
"Enabled"=dword:00000000
"Encryption"=dword:00000000
"FlowControl"=dword:00000000
"GUID"="{00001112-0000-1000-8000-00805F9B34FB}"
"ModemComPortNumber"=dword:00000000
"Name"="Voice Gateway"
"PropertiesDll"=""
"SecurityID"=dword:0000000c
"StatusDll"=""
"UUID"=dword:00001112

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0006]
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"Auto"=dword:00000001
"Description"="Netzwerk"
"Encryption"=dword:00000000
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"MaxConnections"=dword:00000007
"Name"="PAN Netzwerk"
"NetworkAccessDescription"=""
"NetworkMode"=dword:00000001
"PropertiesDll"=""
"SecurityID"=dword:00000002
"StatusDll"=""
"UUID"=dword:00001102

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\Profiles]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\Profiles\0000]
"Dll"="BTWizardProfiles.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections]

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Locations]
"CurrentLocation"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Locations\0000]
"Name"="Standard"

[JoseF]

@daniel here it is:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Locations]
"CurrentLocation"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Locations\0000]
"Name"="Default"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\AutoC onnect]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\AutoC onnect\0008]
"ClassID"=hex:01,11,00,00,00,00,00,10,80,00,00,80,5F,9B,34, FB
"SecurityLevel"=dword:00000000
"SecurityID"=dword:00000001
"UUID"=dword:00001101
"BDName"=hex:42,54,2D,47,50,53,2D,32,30,39,45,34,34,20,00
"BDDevClass"=hex:00,1F,00
"BDAddress"=hex:00,90,4B,20,9E,44
"ServiceName"=hex:00


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devic es]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devic es\00:07:a4:00:2f:73]
"TrustedMask"=dword:00000000
"LinkKey"=hex:C7,4C,60,D0,48,90,DF,1E,E5,01,90,68,5D,79,15, 84
"TimeStamp"=dword:00000110
"Features"=hex:FF,FF,0B,00,00,00,00,00
"DevClass"=hex:20,04,04
"Name"=hex:4A,41,42,52,41,20,32,35,30,00


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devic es\00:90:4b:20:9e:44]
"LinkKey"=hex:A9,D1,FD,23,A3,71,9C,77,26,4E,CD,DC,67,D1,31, 2D
"TimeStamp"=dword:00000110
"Features"=hex:FF,FF,0F,00,00,00,00,00
"DevClass"=hex:00,1F,00
"Name"=hex:42,54,2D,47,50,53,2D,32,30,39,45,34,34,20,00
"TrustedMask"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Devic es\00:03:89:05:27:e2]
"TrustedMask"=dword:00000000
"TimeStamp"=dword:08C3F9C0
"Features"=hex:7C,38,01,00,00,00,00,00
"DevClass"=hex:20,04,04
"Name"=hex:4D,31,30,30,30,20,62,79,20,50,6C,61,6E,74,72, 6F,6E,69,63,73,00


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0009]
"SecurityID"=dword:0000000C
"GUID"="{00001108-0000-1000-8000-00805F9B34FB}"
"UUID"=dword:00001108
"Auto"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Encryption"=dword:00000000
"SecutiryID"=dword:00000008
"Name"="Headset"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0008]
"GUID"="{00001112-0000-1000-8000-00805F9B34FB}"
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"UUID"=dword:00001112
"SecurityID"=dword:0000000C
"Auto"=dword:00000001
"Authorization"=dword:00000000
"Name"="Voice Gateway"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0007]
"UUID"=dword:00001101
"UserInstalled"=dword:00000000
"SecurityId"=dword:00000001
"HwPortNumber"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Encryption"=dword:00000000
"ComPortNumber"=dword:0000000E
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"Name"="ActiveSync Serial Port"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0006]
"UUID"=dword:00001111
"UserInstalled"=dword:00000000
"SecurityId"=dword:0000000B
"ModemInstalled"=dword:00000001
"Encryption"=dword:00000000
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"GUID"="{00001111-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"ComPortNumber"=dword:0000000D
"Name"="Fax"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0005]
"UUID"=dword:00001106
"SecurityId"=dword:00000006
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX File Transfer"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0004]
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"Encryption"=dword:00000000
"UUID"=dword:00001105
"SecurityId"=dword:00000005
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX Object Push"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0003]
"HwPortNumber"=dword:FFFFFFFF
"UUID"=dword:00001103
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"SecurityId"=dword:00000003
"Encryption"=dword:00000000
"UserInstalled"=dword:00000000
"ShowWizard"=dword:00000000
"ModemInstalled"=dword:00000001
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"ComPortNumber"=dword:0000000B
"Name"="Dialup Networking"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0002]
"HwPortNumber"=dword:FFFFFFFF
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"UUID"=dword:00001102
"Encryption"=dword:00000000
"UserName"=""
"UserInstalled"=dword:00000000
"SecurityId"=dword:00000002
"Password"=""
"ModemInstalled"=dword:00000001
"AutoConnect"=dword:00000001
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"ComPortNumber"=dword:0000000C
"Name"="LAN Access Using PPP"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0001]
"Authorization"=dword:00000000
"Authentication"=dword:00000000
"SecurityId"=dword:00000001
"UUID"=dword:00001101
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"HwPortNumber"=dword:00000000
"UserInstalled"=dword:00000000
"ComPortNumber"=dword:00000008
"Name"="Generic Serial"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Debug]
"LogIPAddr"=dword:00000000
"Transport"=dword:00000002


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Filte rs]
"PageScanWindow"=dword:00000000
"PageScanInterval"=dword:00000000
"InquiryScanWindow"=dword:00000000
"InquiryScanInterval"=dword:00000000
"InquiryScanMode"=dword:00000002
"WhoAllowedToConnect"=dword:00000001
"AllowOthersToDiscover"=dword:00000001
"UseInquiryFilters"=dword:00000000
"PeriodicInquiry"=dword:00000001


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Gener al]
"StackMode"=dword:00000000
"UseIconView"=dword:00000001
"DefaultPropertiesDll"=""
"DefaultStatusDll"=""
"UnnamedDeviceName"="<No Name>"
"NoSleepingWhileConnected"=dword:00000001
"MaxSimultConnections"=dword:00000007
"CountryCode"=dword:00000000
"SecurityType"=dword:00000002
"MinorClass"=dword:00000010
"DeviceName"="POCKET_PC"
"RadioInitLibrary"="LGERadioInit.dll"
"PnpId"=""
"PeriodicInquiry"=dword:00000000
"PeriodicInquiryRetryTime"=dword:0000001E
"UseFixedPin"=dword:00000000
"PinCode"=""
"AutoDiscovery"=dword:00000000
"NoResetAllowed"=dword:00000000
"NoChangeNameAllowed"=dword:00000000
"TransportLibrary"="BtCeSerialTrans.dll"
"LicenseKey"="E3E534E19B3E82141321561D913215633CC92760F687E82F"
"PowerControlLibrary"="CompaqGen3Power.dll"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Seria lTransport]
"ByteSize"=dword:00000008
"Device"="COM"
"Parity"=dword:00000000
"StopBits"=dword:00000000
"FlowControl"=dword:00000001
"Port"=dword:00000007
"BaudRate"=dword:000E1000


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0006]
"StatusDll"=""
"PropertiesDll"=""
"MaxConnections"=dword:00000007
"NetworkMode"=dword:00000001
"NetworkAccessDescription"=""
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"UUID"=dword:00001102
"SecurityID"=dword:00000002
"Auto"=dword:00000001
"Authorization"=dword:00000001
"Description"="Personal Network"
"Name"="Network Access"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0005]
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001112-0000-1000-8000-00805F9B34FB}"
"Name"="Voice Gateway"
"SecurityId"=dword:0000000C
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"UUID"=dword:00001112
"Enabled"=dword:00000001
"ModemComPortNumber"=dword:00000000
"FlowControl"=dword:00000001
"Baudrate"=dword:00000004


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0004]
"Baudrate"=dword:0000E100
"FlowControl"=dword:00000001
"ModemComPortNumber"=dword:00000001
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"Name"="Dial-Up Networking"
"SecurityId"=dword:00000003
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"UUID"=dword:00001103
"Enabled"=dword:00000001


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0003]
"FlistFormat"=dword:00000000
"Root"="\\My Documents"
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX File Transfer"
"SecurityId"=dword:00000006
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"UUID"=dword:00001106


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0002]
"SaveInPIM"=dword:00000001
"SendBusinessCardOnRequest"=dword:00000001
"AcceptNotes"=dword:00000001
"AcceptEmailMessages"=dword:00000001
"AcceptCalendarItems"=dword:00000001
"AcceptBusinessCards"=dword:00000001
"InboxDirectory"="\\My Documents\\Business"
"DefaultBusinessCard"="0"
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX Object Push"
"SecurityId"=dword:00000005
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"UUID"=dword:00001105


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\0001]
"UserInstalled"=dword:00000000
"ComPortNumber"=dword:00000005
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="Generic Serial"
"SecurityId"=dword:00000001
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000001
"UUID"=dword:00001101
"HwPortNumber"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Version]
"RadioLmpSubVersion"=dword:00000180
"RadioManufacturer"=dword:00000015
"RadioLmpVersion"=dword:00000001
"RadioHciRevision"=dword:00000180
"RadioHciVersion"=dword:00000001
"Apollo"="1.7.0"
"Software"="1.4.1.07"
"ModuleReleaseDate"="04.15.2003"
"ModuleRevision"="LMX9814V5"
"ModuleInfo"="NSC"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections\00 02]
"Shortcut"="BT-GPS-209E44 : Serial 209e44"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000000
"LocalDirectory"="\\My Documents"
"BDName"="BT-GPS-209E44 "
"BDDevClass"=hex:00,1F,00
"BDAddress"=hex:00,90,4B,20,9E,44
"UserInstalled"=dword:00000008
"ComPortNumber"=dword:00000008
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="Serial 209e44"
"SecurityId"=dword:00000001
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"UUID"=dword:00001101


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connections\00 01]
"Shortcut"="Headset connection to 'JABRA 250'"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000000
"LocalDirectory"="\\My Documents"
"BDName"="JABRA 250"
"BDDevClass"=hex:20,04,04
"BDAddress"=hex:00,07,A4,00,2F,73
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001108-0000-1000-8000-00805F9B34FB}"
"Name"="Headset"
"SecurityId"=dword:0000000C
"Encryption"=dword:00000000
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001108


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard]
"ConnectTo"="Headset connection to 'JABRA 250'"


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\Profiles]


[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Connection Wizard\Profiles\0000]
"Dll"="BTWizardProfiles.dll"


AND

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn]
"Dll"="RegEnum.dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PPExtra]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PPStatistics]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PPCommand]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PPData]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Battery]
"IClass"="{DD176277-CD34-4980-91EE-67DBEF3D8913}"
"Order"=dword:00000000
"Flags"=dword:00000008
"Dll"="battdrvr.dll"
"Prefix"="BAT"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDBusDriver]
"Entry"="SDBusDriverStartUp"
"Dll"="SDBusDriver.dll"
"Order"=dword:00000020


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Backlight]
"IClass"=hex(7):7B,00,41,00,33,00,32,00,39,00,34,00,32,00, 42,00,37,00,2D,00,39,00,32,\
00,30,00,43,00,2D,00,34,00,38,00,36,00,62,00,2D,00 ,42,00,30,00,45,00,36,00,\
2D,00,39,00,32,00,41,00,37,00,30,00,32,00,41,00,39 ,00,39,00,42,00,33,00,35,\
00,7D,00,00,00,00,00
"Index"=dword:00000001
"Order"=dword:00000001
"Prefix"="BKL"
"Dll"="backlitdrv.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\OHCI]
"MemBase"=dword:00450000
"Irq"=dword:0000000D
"UseExistingSettings"=dword:00000000
"Order"=dword:00000001
"Index"=dword:00000001
"Dll"="ohci.dll"
"Prefix"="HCD"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\USB]
"DevConfig"=hex:10,00,00,00,05,00,00,00,00,01,00,00,00,4B,00, 00,00,00,08,00,00,00,00,\
00,00
"FriendlyName"="USB Cable:"
"DeviceType"=dword:00000000
"Index"=dword:00000009
"Order"=dword:00000000
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000009
"Tsp"="Unimodem.dll"
"IoLen"=dword:00001000
"Irq"=dword:00000011
"Dll"="serial.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IrDA]
"DevConfig"=hex:10,00,00,00,05,00,00,00,00,01,00,00,00,4B,00, 00,00,00,08,00,00,00,00,\
00,00
"FriendlyName"="Native IR:"
"Priority256"=dword:000000A0
"Index"=dword:00000002
"DeviceType"=dword:00000002
"Order"=dword:00000001
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000004
"IoLen"=dword:00000024
"Tsp"="Unimodem.dll"
"Irq"=dword:00000020
"IoBase"=dword:B4700000
"Dll"="serial.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial]
"DevConfig"=hex:10,00,00,00,05,00,00,00,10,01,00,00,00,4B,00, 00,00,00,08,00,00,00,00,\
00,00
"FriendlyName"="Serial Cable on COM1:"
"DeviceType"=dword:00000000
"Order"=dword:00000000
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000000
"IoLen"=dword:00000024
"Tsp"="Unimodem.dll"
"Irq"=dword:00000022
"IoBase"=dword:B4100000
"Dll"="serial.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCMCIA]
"IClass"=hex(7):7B,00,36,00,42,00,45,00,41,00,42,00,30,00, 38,00,41,00,2D,00,38,00,39,\
00,31,00,34,00,2D,00,34,00,32,00,66,00,64,00,2D,00 ,42,00,33,00,33,00,46,00,\
2D,00,36,00,31,00,39,00,36,00,38,00,42,00,39,00,41 ,00,41,00,42,00,33,00,32,\
00,7D,00,3D,00,50,00,43,00,4D,00,43,00,49,00,41,00 ,20,00,43,00,61,00,72,00,\
64,00,20,00,53,00,65,00,72,00,76,00,69,00,63,00,65 ,00,73,00,00,00,00,00
"Order"=dword:00000000
"Dll"="PCMCIA.dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BATTMGR]
"Ioctl"=dword:00000004
"Order"=dword:00000000
"Dll"="BattMgr.Dll"
"Prefix"="SPI"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WAPIMAN]
"Priority256"=dword:00000011
"Order"=dword:00000001
"Index"=dword:00000001
"Dll"="waveapi.dll"
"Prefix"="WAM"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"IClass"=hex(7):7B,00,41,00,33,00,32,00,39,00,34,00,32,00, 42,00,37,00,2D,00,39,00,32,\
00,30,00,43,00,2D,00,34,00,38,00,36,00,62,00,2D,00 ,42,00,30,00,45,00,36,00,\
2D,00,39,00,32,00,41,00,37,00,30,00,32,00,41,00,39 ,00,39,00,42,00,33,00,35,\
00,7D,00,00,00,00,00
"Priority256"=dword:00000010
"Order"=dword:00000000
"Index"=dword:00000001
"Prefix"="WAV"
"Dll"="BtCeIf.dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Ethman]
"Order"=dword:00000005
"Index"=dword:00000001
"Dll"="ethman.dll"
"Prefix"="ETM"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IrCOMM]
"Index"=dword:00000003
"Order"=dword:00000003
"Prefix"="COM"
"Dll"="IRCOMM.DLL"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IrCOMM\Unimodem]
"DevConfig"=hex:10,00,00,00,02,00,00,00,10,01,00,00,00,4B,00, 00,00,00,08,00,00,00,00,\
00,00
"FriendlyName"="Infrared Port"
"DeviceType"=dword:00000006
"Tsp"="Unimodem.dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\AFD]
"Entry"="AfdInitialize"
"Keep"=dword:00000001
"Order"=dword:00000002
"Dll"="AFD.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NDISUIO]
"Order"=dword:00000003
"Index"=dword:00000001
"Dll"="ndisuio.dll"
"Prefix"="UIO"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NDIS]
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"Order"=dword:00000001
"Index"=dword:00000000
"Prefix"="NDS"
"Dll"="NDIS.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SIP]
"Index"=dword:00000000
"Order"=dword:00000001
"Dll"="softkb.DLL"
"Prefix"="SIP"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\GSM610]
"Order"=dword:00000000
"Index"=dword:00000003
"Dll"="gsm610.acm"
"Prefix"="ACM"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TAPI]
"Order"=dword:00000001
"Dll"="TAPI.dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CODEC_GSM610]
"Order"=dword:00000000
"Index"=dword:00000001
"Dll"="gsm610.acm"
"Prefix"="ACM"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\ipv6hlp]
"Order"=dword:00000004
"Index"=dword:00000001
"Dll"="ipv6hlp.dll"
"Prefix"="V6H"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\ZeroConfig]
"Order"=dword:00000004
"Index"=dword:00000001
"Dll"="WZCSVC.dll"
"Prefix"="ZCF"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings]


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings\MediaPlayer]
"WindowName"="Windows Media"
"ClassName"="WMP for Mobile Devices"
"ExeName"="wmplayer.exe"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings\MediaPlayer\0xb]
"lparam"=dword:00000000
"wparam"=dword:00000000
"msg"=dword:000080CA
"action"=dword:00000001


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings\MediaPlayer\0x2]
"lparam"=dword:00000000
"wparam"=dword:00000000
"msg"=dword:000080CC
"action"=dword:00000001


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings\MediaPlayer\0x3]
"lparam"=dword:00000000
"wparam"=dword:00000000
"msg"=dword:000080CB
"action"=dword:00000001


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\AppC mdMappings\MediaPlayer\0x8]
"lparam"=dword:00000000
"wparam"=dword:00000000
"msg"=dword:000080D2
"action"=dword:00000001


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PendantBus\Curr entBindings]
"0x14"="MediaPlayer"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial8]
"FriendlyName"="Bluetooth Serial Port COM8:"
"Index"=dword:00000008
"Order"=dword:00000000
"Dll"="BtCeIf.dll"
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000008


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5]
"FriendlyName"="Bluetooth Serial Port COM5:"
"Index"=dword:00000005
"Order"=dword:00000000
"Dll"="BtCeIf.dll"
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000005


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC4]
"DeviceArrayIndex"=dword:00000004
"Prefix"="BTC"
"Dll"="BtCeIf.dll"
"Order"=dword:00000001
"Index"=dword:00000004
"FriendlyName"="Bluetooth Port 4:"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC3]
"DeviceArrayIndex"=dword:00000003
"Prefix"="BTC"
"Dll"="BtCeIf.dll"
"Order"=dword:00000001
"Index"=dword:00000003
"FriendlyName"="Bluetooth Port 3:"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC2]
"DeviceArrayIndex"=dword:00000002
"Prefix"="BTC"
"Dll"="BtCeIf.dll"
"Order"=dword:00000001
"Index"=dword:00000002
"FriendlyName"="Bluetooth Port 2:"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BTC1]
"DeviceArrayIndex"=dword:00000001
"Prefix"="BTC"
"Dll"="BtCeIf.dll"
"Order"=dword:00000001
"Index"=dword:00000001
"FriendlyName"="Bluetooth Port 1:"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtCeProfiles]
"Index"=dword:00000001
"Order"=dword:00000001
"DeviceArrayIndex"=dword:00000001
"Dll"="BtCeIf.dll"
"Prefix"="BTP"
"FriendlyName"="Shims to BtCeProfiles on BTP1:"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtCeStack]
"Index"=dword:00000001
"Order"=dword:00000001
"Dll"="BtCeIf.dll"
"Prefix"="BTS"
"DeviceArrayIndex"=dword:00000001
"FriendlyName"="Shims to BtCeStack on BTS1:"
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Bluetooth]
"DevConfig"=hex:10,00,00,00,05,00,00,00,10,01,00,00,00,4B,00, 00,00,00,08,00,00,00,00,\
00,00
"FriendlyName"="Serial Cable on COM0:"
"DeviceType"=dword:00000000
"Index"=dword:00000007
"Order"=dword:00000005
"Prefix"="COM"
"DeviceArrayIndex"=dword:00000005
"IoLen"=dword:00000024
"Tsp"="Unimodem.dll"
"Irq"=dword:00000018
"IoBase"=dword:B5600000
"Dll"="serial.Dll"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\AtmelUsb]
"Entry"="ATL_Init"
"Dll"="vnetusba.dll"
"Keep"=dword:00000001
"Order"=dword:00000003
"Prefix"="ATL"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FingerChip]
"ThreadPriority"=dword:00000064
"Order"=dword:00000000
"Dll"="FingerChip.Dll"
"Index"=dword:00000001
"Prefix"="FCA"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlshDrv]
"FolderName"="iPAQ File Store"


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SLR]
"Prefix"="SLR"
"Dll"="SLR.dll"
"Order"=dword:00000009
"Index"=dword:00000000

The btrez.dll is in English

If sameone canhost this files I will upload.

Please Daniel tell us what you are doing

[towa]

One more hint for TomTom:

Once you got it to work you should add in Software\Widcomm\BtConfig\AutoConnect\007 a new DWORD value

BtBrowserEnabled with value 0

This will disable the "Choose device" dialog and will always choose automatically the GPS once you have paired it.
Normally when an application accesses COM7 (Outgoing Serial) appears this dialog.

One more hint: To get the .cab files you need to install the update. Afterwards you will find them in program files\hp directory.
Don't worry that your PDA tells you that it can't install it.

[JoseF]

@towa

Please explain all the way you did :)
As far I have look at this topic you hare the only one that put this together :lol:

[orinoco]

ftp://www.shawus.com

username: hydrosphere
Password: 12345

Please provide instructions here, or upload a how-to file with instructions.

Many thanks.

Fernando

[towa]

I put a readme in ftp://www.shawus.com/thisoneworks

I also tried to upload the files but I got a message disc quota exceeded. It's 1.5B more or less.

Anyway I must remind you that you may use this software only if you have a valid license of the WidComm drivers.

[sweeney]

I put a readme in ftp://www.shawus.com/thisoneworks

I also tried to upload the files but I got a message disc quota exceeded. It's 1.5B more or less.

Anyway I must remind you that you may use this software only if you have a valid license of the WidComm drivers.

Just uploading the reg file (bt.txt) will give us all we need (providing we have the WidComm driver obviously)

Steve

[Roadster]

Oops after checking I am wrong it is not ms stack sorry :oops:

[towa]

Just uploading the reg file (bt.txt) will give us all we need (providing we have the WidComm driver obviously)

Steve

Done :wink: I uploaded the bt.txt file for you

BTW: I have the Rikaline BT GPS. It's really amazing. I'm living the highest floor and even in my flag I get a signal from 3 satelites. :D :D :D :D You can use it without any problem inside a backpack.

[ppcitaly]

Please boys, how can extract the right files from Widcom installer or iPAQ installer?
Thanks

[orinoco]

Towa,

Can you retry to upload the BT.ZIP file? I have freed some space from the ftp site:

ftp://www.shawus.com
username: hydrosphere
password: 12345

Thanks,

Fernando

[abo_khaleel]

Please boys, how can extract the right files from Widcom installer or iPAQ installer?
Thanks

- run the update. then cancel before installation.
- the cab file is in: C:\Program Files\HP\h2200 BT Driver Update Build 58

[ashby]

I haven’t got an XDA II yet. I am planning on buying one if the TomTom GPS Bluetooth issue has been resolved.

I have been using Nokia phones for 10 years and have no experience of MS Phone OS.

How difficult is it to bodge the XDA II for this to work? I don’t want to shell out £600+ and not be able to use it.

Ashby

[axbl]

rename 000SdkCE.011 SdkCE.dll
rename 000btrez.010 btrez.dll
rename 000vcard.016 vcard.2bp
rename 00BtCeIf.002 BtCeIf.dll
rename 00ISVDLL.999 ISVDLL.pdb
rename 00ReadMe.025 ReadMe.Txt
rename 0Blu_Bul.032 Blu_Bul.2bp
rename 0Red_Bul.026 Red_Bul.2bp
rename 0btcepan.035 btcepan.dll
rename BTBIZC~1.017 "BT BizCard icon.2bp"
rename BTBUSI~1.040 BTBusinessCard.exe
rename BTCEBC~1.001 BtCeBCSPTrans.dll
rename BTCEFU~1.036 BtCeFujiCF.dll
rename BTCEOS~1.003 BTCeOsif1.dll
rename BTCEOS~2.004 BTCeOsif4.dll
rename BTCEPH~1.014 BtCePhilipsCF.dll
rename BTCEPR~1.005 BtCeProfiles.dll
rename BTCESE~1.006 BtCeSendTo_Poom.dll
rename BTCEST~1.007 BtCeStack.dll
rename BTCHOO~1.008 BTChooserLib.dll
rename BTCONF~1.009 BTConfigCE.cpl
rename BTCONN~1.037 BTConnManagerCE.exe
rename BTDialer.033 BTDialer.dll
rename BTFILE~1.038 BTFileExplorer.exe
rename BTPANM~1.042 BTPanManagerCE.exe
rename BTTrayCE.039 BTTrayCE.exe
rename BTW-CE~1.000
rename BTWIZA~1.015 BTWizardCE.exe
rename BTWIZA~1.041 BTWizardProfiles.dll
rename BT_GLO~1.018 BT_Globe_icon.2bp
rename BT_ICO~1.019 BT_icon_Blue.2bp
rename BT_ICO~2.020 BT_icon_Gray.2bp
rename BT_PHO~1.021 BT_PhoneDialer.2bp
rename COMPAQ~1.013 Compaq3870Power.dll
rename COMPAQ~2.034 Compaq3970Power.dll
rename EDITPR~1.023 "Edit profile icon.2bp"
rename FOLDER~1.024 "Folder icon.2bp"
rename REFRES~1.027 Refresh_icon.2bp
rename SIGNAL~1.028 Signal_Strength_Green.2bp
rename SIGNAL~2.029 Signal_Strength_RED.2bp
rename SIGNAL~3.030 Signal_Strength_Yellow.2bp
rename STOP_I~1.031 Stop_icon.2bp
rename btwcehlp.022 btwcehlp.htm
rename wbtapiCE.012 wbtapiCE.dll

[axbl]

MyTry:
Took the Widcom-Install mentioned above.
Renamed all files in CAB (see last posting)
Deleted Registry enties as toda wrote (readme.txt)
Imported Toda's bt.txt into registry.
Made a link to autostart.
Reset.

A NEW BT-MANAGER !!! Thank's, Toda !!

Activated Bluetooth.
In Bluetooth manager, added paired device (GPS found, PIN required)
Menu BEw->Connect doesnt work.
In tomtom GPS tried wit "TomTom wireless GPS" and "BT-Port 7"
BT-Connection-Manager pops up.
Clicked on GPS-Device.
BT-Connection-Manager pops up.
Clicked on GPS-Device.
BT-Connection-Manager pops up.
Clicked on GPS-Device.

Does not work !!!!

Help, toda, what is wrong ???

Put my CAB-Files onto ftp-server (MyTry.zip) mentioned above.

[tbd@immigrantsong.de]

I looked at the Widcomm site and it seems that it doesn't support the HSET or HFREE profiles required for the headset.

Anyone have better information?? :?:

If its true, then the patch solves one problem but causes another - GPS or Headset!!! :evil: :evil:

[domloff]

I looked at the Widcomm site and it seems that it doesn't support the HSET or HFREE profiles required for the headset.

Anyone have better information?? :?:

If its true, then the patch solves one problem but causes another - GPS or Headset!!! :evil: :evil:

I've seen the 2210 (and I think the 5550) with headset on the davesipaq website where he used a 2210 with a CF GSM card, so there shouldn't be a problem pairing up. If you look at reg files above you can see a reg entry for 'headset'. I don't think it supports HFREE, but the MS BT stack doesn't support it either.

[orinoco]

Axbl:

I tried your procedure: deleted the registry entries provided by Towa; downloaded the mytry.zip, and copied all the files to windows; imported Towa's bt.txt into the registry; created the link for BTTrayCE in Startup; soft reset.

I get an error message indicating that some component, path or library is missing or incorrect.

Are you sure you put all the required files in the mytry.zip?

Thanks,

Fernando

[axbl]

orinoco:
I have prooved it, all files ok.
Have you delete the old link in the startmenu ?

towa:
do you use the widcom-setup or only the update fro hp or both ?

[Ian_Goulding]

:roll: Hi Guys, please see below the contents of an email recieved 20/11/03 from TomTom in the Netherlands regarding the Bluetooth problem on the XDAII

Hope this helps: Regards Ian

===============================================

Dear Mr. goulding,

Thank you for contacting TomTom E-Support and Services.

We apologies for the delay and thank you for your patience,

We are aware of the issue, to inform you shortly is seems that the Bluetooth software in this device is unable to create a serial or virtual comport that we need for transmitting the GPS signal.

Currently we are investigating this in cooperation with the manufacturers of the XDA / MDA / QTEK and the developer of the Bluetooth software.

Please watch our website for information regarding this.

Regards,

TomTom Customer Services
support@tomtom.com
http://www.tomtom.com
===============================================

[orinoco]

Thanks Towa and axbl.

Question is though: if I have to do a hard reset, it will go to the original BT stack, won't it? Is there any way to keep it?

Thanks,

Fernando

[axbl]

orinoco:

Does it work now for you ???

[JoseF]

Please let us know how you did

:wink:

[blinky99]

I've fixed MyTry.Zip file:

BTWizardCE.exe and BTWizardProfiles.dll have been renamed the wrong way round. Swap the names over. Then in BlueTooth Manager New-->Connect! now works! I've managed to connect my Fortuna GPSmartBT with TomTom Navigator 2. (Make sure to Connect to the GPS device after you have set it up).

Some problems i've had:
1) if bluetooth is switched on when i power off, i can't power back on
2) sometimes when I turn bluetooth on it says that there is not enough "Driver Memory" and that I must do a reset.

Anyone else had this??

[JoseF]

Hi,
Do you mean the file is good now? No need to swap the names?
It´s possibel to use bluetooth headset too? I don´t mean at the same time as GPS.
One more It´s possibel to get back the older BT profile?

Regards :)
JoseF

[blinky99]

err sorry :oops: I meant i've fixed it on mine. Could someone fix the .zip on the ftp site?

I haven't got a BT headset so I'm not sure about that. My guess is you can only connect to one device at a time (my mate with an ipaq says so..)

Anyone?

[svonk]

@blinky99

well i changed the names but the mistake does not disappear :-(
there must be some other mistake...
any idea?

[blinky99]

which mistake do you mean?

Have you tried running BTWizardCE.exe in the windows directory?

[svonk]

yes i did. i have this mistake:
something like "BTTrayCE" or another component could not be found..."

[svonk]

running btwizard develops this mistake:
"cannot load ressource"

[blinky99]

I simply copied all the files in the mytry.zip file to my /windows directory. Not sure what is missing.

Have you tried copying the files over again? (make sure bluetooth is off)
And you've added the bt.txt to the registry with TascalRegEdit?

Sorry I can't be more help

[domloff]

Well I tried the above installation and it does work!

You have to use the Tascal regedit program no other will work! Renamed the two files and copied them all over to the windows dir.

I can now pair and connect to the BT GPS!

Now the problems :

1) I have to manually go to the shortcut screen to connect the BT GPS.
2) Once I quit my GPS program the connection is lost and I have to connect again.
3) Sometimes the BT stack just dies and only a soft reset will bring it back
4) Pressing the tray icon can take >2mins to bring up the manager

and most important of all it does not recognise my BT headset! It comes backwith no valid profiles found :(

I am sure that there is a reg fix to make the 2210/5550 understand the headset profile I will have to have a dig around.

Dom

[axbl]

blinky99:

Thanks ! was my mistake with the wrong name. I checked all files now and found another Problem: ISVDLL.PDB is wrong, has to be ISVDLL.DLL (I think, my HEX-Editor says so)

I have deleted MyTry.zip on the ftp (Thanks to orinoco) and upped MyTry1.zip with the 3 files corrected.

Something I know:
- There will be an update in id of december for the MDA II for the bluetooth stack and perhaps for the memory problem

- T-Mobile Bluekit II doesnt work today wit TomTom - it works only with Navigate

- Using Bluekit II and Navigate you can use a bluetooth headset parallel

Something I hope:

- the new Bluetooth Stack (from microsoft) is able to support all the things that widcomm does


Does anybody know something about the Profile SPP that towa used in his readdme.txt on the ftp ????

[shire29]

CF GPS with back pack anyone :wink: ?

Cheers, Shire

[palmop]

Hey axbl, did you try the newest files from the 2210 BT patch? mytry.zip had files dated may and the new files have september. maybe that will fix the headset troubles and others.

I will try later on, I tried files from 5450, which had the latest patch, but it didn't work, I guess, I'll have to export and import that one's registry for proper use. With reg from 2210, I get always driver memory errors

[axbl]

bluetooth headset is not working with the widcomm stack in MyTry1.zip. Perhaps it is because there are no devices with phone from hp. Tried the Update from 2210 BT patch but had memory problems.

[domloff]

I found that adding a new dword to :

HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Appli cations\0009
"Enabled" = 0000001

Allows the XDA II to recognise the headset correctly (comes up as headset profile) , but I can't figure out how to get the phone to switch to the headset yet.

[blinky99]

I've managed to extract the widcomm stuff out of the latest bluetooth upgrade for the Ipaq 5400 series. Its version 1.4.1 Build 58. The little bluetooth icon now has a menu on it so you can turn bluetooth on/off, access bluetooth manager, and access bluetooth settings.

The crash when you turn off while accessing a gps seems to be fixed now. Another thing i've noticed with this version, there are now "Personal Network Server" settings (dunno what they are...)

Anyone interested?

[axbl]

blinky99:

>Sure ! How can I get it !

[blinky99]

Can I upload the files somewhere?


btw It still seems a bit flaky - looks like I need new registry stuff (my mate has a new Ipaq :) ) .

[axbl]

blinky99: send you a private forum mail . you could send me the file, I will upload it to the ftp

[domloff]

Look forward to trying this one out!

We'll need the reg extract for the 5400 (the same keys as previously),
as it may need different settings (I could be wrong).


Thanks

Dom

[axbl]

Upped blinkys files as NewBT.zip including bt_reg.txt to ftp !

[domloff]

I can't but think that it may well fix the BT GPS problems but the headset will still not work properly.

The file HeadSet.exe in the startup directory seems to me to switch the headset on when you use the phone. Haven't tried moving it out of the way (I will do), but if it does then it looks like we'll probably need some sort of reg update (I think thats all that is needed) to get it working.

Probably something simple like pointing the MS BT headset entries to the Widcomm headset entry, don't know.

[tadzio]

I can't but think that it may well fix the BT GPS problems but the headset will still not work properly.

I don't know if that helps, but at http://www.xscale.de/index.php there's a "Headset Enabler" for "HP PDAs" (probably iPAQs). In the description they mention that after executing it once, the files can be removed from the Pocket PC again, so I guess the Enabler just sets a few registry entries.

The site mentioned above is in German. Maybe some German speaking BT headset owner wants to have a go at it!?

Cheers
Daniel

[domloff]

In theory it looks like it may work.

Though I can't find where to download it, and I can't make head or tails what it says! :)

It probably just sets the headset key to 'enabled' which I've tried already.

Worth a go I supose!

[tadzio]

After having a closer look at it, I know now what the Bluetooth Enabler does:

- HKLM\SOFTWARE\Widcomm\BtConfig\Services\0005
"Enabled"=dword:00000001

- HKLM\Drivers\BuiltIn\WaveDev
"Dll"="BtCeIf.dll"

Interestingly, this is also what's in JoseF's registry settings posted on page 3 of this thread. In towa's settings on the same page, Services\0005 has an "Enabled" setting of 0.

Anybody with a Bluetooth Headset wants to give it a try? If it still doesn't work, we probably should have a closer look at JoseF's registry settings. :-)

Cheers
Daniel

[tbd@immigrantsong.de]

HEadset Issue:
I took a look at those registry settings and compared them to the "old" MS-Stack and noticed, that the WidComm isn't configured to provide the Headset-service. Look at [HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\BtConfig\Servi ces\] and compare it to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices] - the entry starting with 00001108 is the headset handler.

I have my BT_Headset connected and its connected with this service.

I would expect that this is where we need to look - haven't had time myself.

[Dumph]

Hi Guys - I am new to all this hexing and would love if someone could give me an idiots guide to connecting a bluetooth GPS to my xdaII - Surely there is some kind soul that would help this confused irishman!!
Many thanks in anticipation!! :?

[mrg2003]

Not any day soon. TomTom say they are waiting for O2 to fix BT stack. O2 say that they are not aware of any problem, and in any case only wired GPS is currently supported. Unless you want to load other stacks outlined here with meadicre success.

Mr.G

[ashby]

Hi Guys - I am new to all this hexing and would love if someone could give me an idiots guide to connecting a bluetooth GPS to my xdaII - Surely there is some kind soul that would help this confused irishman!!
Many thanks in anticipation!! :?

I agree, I would love to buy a XDAII safe in the knowledge that I was going to get TomTom nav 2 working

[Puff The Magic Wagon!]

O2 are aware of the problem & are "working on it" quote/unquote.

They have recently removed the statement that BTGPS was supported with the XDA2 from their website.

I am sure they monitor this website (hi guys!!) & will be aware of the problems & it will be an embarassment for them.

Admitedly a h@Xored BT manager is potentially not as good as an official release, but 02/HTC etc should have got it right in the first place.

As soon as they do 1) they will get more sales & 2) if it works properly & better, those that have made this modificiation will just update.

[blinky99]

I suppose that we shouldn't forget that the XDA is running a Microsoft OS and like all Microsoft products, will get released in a ropey state later to be fixed by patches etc.. (when O2 get their fingers out..)

Still it doesn't make it any better when you have just shelled out your hard earned on something that is only partially working :(

Thank god for sites like this one to replace "Customer support" :D

[Southern_Man]

Who's responsibility is it to make sure all technology works?

O2 to make sure TomTom, Socket and Navman work?

What happens if Navman or Socket say 'nope' - should they have not launched?

Just playing devil's advocate - is it Microsoft's responsibility to ensure everyone else's software will work on Longhorn, or will they delay it for 4 years while they wait for everyone else to get their ass in gear?

[Puff The Magic Wagon!]

Southern Man

As you're playing Devil's Advocate...

The XDA2 does not work with ANY BlueTooth GPS device, nor with ANY software that utilises BlueTooth GPS devices.

Therefore, its not a question of compatibility with 3rd party software houses/manufacturers of peripherals but of the suppliers (O2/HTC etc ) being too short-sighted or penny-pinching to do the job properly.

In this instance, its nothing to do with 3rd party suppliers as the openings are just not there for ANYONE to use.

I take it you work for O2 or one of their suppliers/subsiduaries?

[blinky99]

O2 surely, it is their new device. Even if it is not compatible with certain products it would be nice for them to own up to it from the outset. It seems that either they genuinely didn't know about the problems (lack of testing) or knew about it and kept it quiet (to get it released quickly). Yes I may sound a bit bitter but this is the third phone i've bought (all different makes) which have "issues" and spent time looking on websites for a fix.

[Darryl]

Tried connecting my grs receiver tothe xda2 and the xda tries to launch activsync, and then gives an error message, if you select ok then activsync will close and the gps software will launch and receiver is connected, Any idea plse gents why activsync launches and how can I stop it?

[stevew]

Thanks to everyone who has helped to work out this solution. I used the tomtom bluetooth gps to get home tonight, without problems.

Thanks again.

Steve

[RedBull]

Is anyone using a GPSmart?
When I link this to Navigator my position is 60-100m out!

[ashby]

Thanks to everyone who has helped to work out this solution. I used the tomtom bluetooth gps to get home tonight, without problems.

Thanks again.

Steve

Steve,

Any chance you can write a dummys step-by-step guide on how to get this working

Ashby

[axbl]

Attention: modified !!


One needs:

1. Resco Explorer http://www.resco net.com/explorer_dwn.asp
2. The Widcomm files ftp://hydrosphere:12345@www.shawus.com/MyTry2.zip
3. A Registry file for importing Widcomm.reg into the Registry (in MyTry2.zip on ftp see above)

Procedure:

1. Resco Explorer install
2. With the Resco file manager delete linkage "BTIcon" in \Windows\Autostart
3. Soft-RESET
4. Unzip the MyTry2.zip on your Windows-PC
5. Copy all files from the ZIP to your XDA/MDA in the Windows-Directory
6. Copy the file Widcomm.reg in "My document"
7. Import the file Widcomm.reg with Resco Registry
8. Soft-RESET
9. Make links to the files BTTrayCE.exe and BTIcon.exe to /Windows/Start Menu/Programs
10. If you want to use a headset start the BTIcon.exe and configfure as usuall
11. If you want to use Bluetooth.GPS start BTTRay.exe and configure your GPS
12. If you want to switch from Headset to GPS or back you have to stop all applications using Bluetooth (TomTom, ..) and to turn Bluetooth off.

Configure TomTom:
Start TomTom GPS , select "NMEA 0183v2 Bluetooth" as protocol and "BT serial interface COM7" as interface

Adding your Bluetooth-GPS:
1. Start BTTrayCE.exe
2. Switch Bluetooth on by tapping the Bluetooth-Icon on the right border of your today screen
3. Wait until the Icon changes to completely blue
4. Start the Bluetooth-Manager by tapping the Bluetooth-Icon on the right border of your today screen
5. Using Tools >Paired devices add your GPS (Add,Find-Icon,PIN)
6. Using New > Connect! find Bluetooth-Device, select service

Cause my english isnt good please correct this and add comments to help other users !!!!

[RedBull]

GPSmart works fine with memoryMap but not TomTom anyone?....

[axbl]

Please translate someone for everyone !!!
The Bluetootht stack in this setup is in german.

Habe zufällig folgende Datei gefunden:

ftp://hydrosphere:12345@www.shawus.com/BluetoothGPS.zip

Ist eine BluetoothGPS.cab drin, die man direkt auf dem XMDA II installieren kann.
Bluetooth/Headset sollte ausgeschaltet sein, ev. Softreset nach ausschalten durchführen.

Dann einfach installieren.
Links unten auf der Heute-Seite hat man dann beide Bluetooth-Symbole, das Microsoft (für Headset) und das Widcomm (für GPS).

Die anderen Fehler der MyTry3.zip sind wohl auch nicht mehr drin

Läßt sich übrigends auch wieder deinstallieren.....

[MarkJ]

GPSmart works fine with memoryMap but not TomTom anyone?....

Hi all firstly i would like to say THANKYOU :lol: to all who have made me a very happy GPS/XDAII user. I now have a connection with my Fortuna GPSmart unit and TTN works but my position is also 60-100 feet out, even with a nice 5 sat 3D lock :? .

[Puff The Magic Wagon!]

Property the coincidentally following file found: ftp://hydrosphere:12345@www.shawus.com/BluetoothGPS.zip Is a BluetoothGPS.cab in it, which one can install directly on the XMDA II. Bluetooth/Headset should be switched off, ev. After soft RESETS switch off accomplish. Install then simply. Left down on the hay width unit side one has then both Bluetooth symbols, the Microsoft (for Headset) and the Widcomm (for government inspection department). The other errors of the MyTry3.zip are not probably more in it Leaves itself uebrigends also again deinstallieren.....


From www.altavisat.com then translate....

[surur]

Whn I install this my menu is in german (which I dont speak). IS there any english version?

Also I get the error BtTrayCE Could not initialize properly after every susepnd wtih the power button. IS everyone getting it, or am I doing something wrong.

Thx

Surur

[Puff The Magic Wagon!]

I've just followed the instructions above for the MyTry2 and apart from the device selection in the GPS module being in german, everything else is English. Can't comment on the .cab.

What I can say is that it works perfectly - exactly as it says it would :D

So I'm now a happy chappy again as one of the points of getting the XDA2 for me was for my EMTAC. Just need to get a car charger now :roll: oh & a 128k SD card :D

Not worried about the phone side - I use a T39 on Voda for that with BT headset.


Many thanks to the guys who've gone out and sorted out the problem on XDA-Developers probably a long time before the "offical" one :D

[towa]

I'm currently developing a solution for the built-in (Microsoft Stack)
I already got it to work with my GPS. My GPS responds perfectly on COM4 with my device driver :D :D :D :D :D

I will add now a small GUI, who will ask if you would like to add a virtual COM once you added a BT device with SPP profile. Forget the WidComm solution, it is not necessary anymore. I suppose my plug-in will be ready on beginning of next week. This solution will be clean and easy to use. No more registry hacks are necessary anymore.

So be patient some more days.

Best regards,
Tobias

[axbl]

ftp://hydrosphere:12345@www.shawus.com/BluetoothGPS.zip

there is a new version ! (installtion perhaps in german, but bluetooth in english I hope)

[towa]

I'm currently developing a solution for the built-in (Microsoft Stack)


BTW: My plug-in will automatically detect your OS language and show the corresponding dialogs in English or German :D

[domloff]

Tobias

I think you can safely say that a lot of people are looking forward to your new device driver!

Thanks for all your hard work.

Dom

[JoseF]

@Tobias
Thanks for what you hare doing

JoseF

[tbd@immigrantsong.de]

@Tobias

Good Job! We'r all looking forward to it like MAD :lol:

[Ian_Goulding]

Towa

Many thanks, for your magnificent works to date, I can't wait to get my hands on the new MS Stack mods.

Regards
Ian Goulding

[surur]

Just one question: Can you use the GPS and headset at the same time?

Thx

Surur

[Justus_Cologne]

Hi all!

First all of thanks to all who let this forum stay alive. Great work.

One question:

ftp://hydrosphere:12345@www.shawus.com/BluetoothGPS.zip

I download this file. But what I have exactly to do, to get my TOM TOM BT GPS to work. I am not very much a profi. Could somebody explain me please step by step, what I have to do with this zip file?

Thanks a lot.

Justus

[axbl]

Download, unzip, copy CAB-file to pocketpc, open/execute CAB-file with filemanager on pocketpc starts install.
Automatic reboot.
Two Bluetooth icons on todayscreen.
One (the old microsoft) for headset.
Second(the new widcomm) for gps etc.
Enable bluetooth clicking on the new icon.
Start bluetooth-manager clicking on the new icon.
Bind your GPS to bluetooth
Connect to your GPS.
Start TomTom GPS.
nemea...bluetooth on port 7.
Works ???

[towa]

Just one question: Can you use the GPS and headset at the same time?

Thx

Surur

With my plug-in it will be possible :wink:

[axbl]

Hey towa, don't you read your pm ??

[kalex]

towa,

awesome. can't wait to use it. so with your plugin we can add serial profile to ms stack? is that correct? i don't really need gps, cause i have one in my car, but it would be nice to use with bluetooth access point at home to browse the web and stuff.


thanks

alex

[jrd31]

hi towa

is your fix ready yet, i would like to buy tom tom nav2 for bluetooth but won't until i know i can use it?

axbl

where did you download the files from?

thanks

jase

[towa]

hi towa

is your fix ready yet

I suppose I will be ready on next monday. I have already a release candidate for the driver part but the dialgos for the setup are still not ready.

[JaToAc]

more reasons to get a xda, my girlfriend will hate me :P goodbye spv, xda2 here i come...

[axbl]

Good news !!!!!!!

towa was so nice to allow me to test his solution !

It W O R K S !!!!

Bluetooth Navigation and Headset at the SAME time !!!

Great towa !!!!!!!

[tbd@immigrantsong.de]

@towa

Why don't you post the beta somewhere?

After axbl's rave, I'm sure you'll get blasted with requests and won't find time to finisch the final.

[kalex]

excellent. can't wait. (beta would be nice :)

[Justus_Cologne]

Download, unzip, copy CAB-file to pocketpc, open/execute CAB-file with filemanager on pocketpc starts install.
Automatic reboot.
Two Bluetooth icons on todayscreen.
One (the old microsoft) for headset.
Second(the new widcomm) for gps etc.
Enable bluetooth clicking on the new icon.
Start bluetooth-manager clicking on the new icon.
Bind your GPS to bluetooth
Connect to your GPS.
Start TomTom GPS.
nemea...bluetooth on port 7.
Works ???

I have done all the above. But it dont work. I have the TOMTOM BT GPS and the MDA II. At the GPS Software which is delivered with TOM TOM NAvigator i can setup a lot of different GPS Mouses. Which I have to choose: TOMTOM Wireless GPS or NMEA 0183v2 BT or annother one ???

Should I chosse BT Serial COM 4 or Com 7???

Is there anybody who can help me?

If you sent me your phonenumber maybe I can give you a call. That would be very nice.

Thanks a lot.

Justus

[Zzr]

Hi All!

The newest XDA II ROM (1.52.00) now support Bluetooth Serial profile!
:D

[JoseF]

Hi,
Please where to download?

JoseF

[NickP]

Hi All!

The newest XDA II ROM (1.52.00) now support Bluetooth Serial profile!
:D

Don't suppose it will support Bluetooth Hands Free profile as well will it?

[domloff]

Good news !!!!!!!

towa was so nice to allow me to test his solution !

It W O R K S !!!!

Bluetooth Navigation and Headset at the SAME time !!!

Great towa !!!!!!!

Now we're talking! Looking forward to getting this baby installed ....

[lukasz]

@Zzr @ towa

Hmm, I have the ROM version 1.52.00WWE dated 10.23.03 with radio ver 10513A0 but the bluetooth serial profile DOES NOT work with this veresion - I am testing one of the few devices for the one of the GSM networks in Poland . Zzr can you provide detailed description how to enable it?? maybe I am doing something wrong....
btw I have installed mytry2.zip and it works ok with Socket GPS. Ms stack works with Nokia HDW-2 headset but it is disconecting and there is no information what is the current situation - it should be some icon on the top bar informing the user that it is connected or not.

Dear TOWA is there any chance for your beta release? if yes please email it to me lpiechowski@ebs.net.pl

[mrg2003]

Instead of everyone asking for a copy. Why not one person with permission of towa post to a web server, maybe with password.

MR.G

[axbl]

@justus_cologne:
you have to yuse NMEA 0183v2 BT with port 7.
Dont forget to bind it, then connect.
If you are from germany, send me a PM and I can help you in german (much easyer for me !!)

@ ALL:
Please, dont send towa so much requests. I have got many quetsions for the widcomm solution. many of you know much about CAB, registry, reset, ...
But there are also many people which don't know what the registry is.

So I think it is better to let towa do his job and he will make a perfect (i hope) installer.

From my good contacts in germany I heard that there will be an update for the MDA II on 5.12.2003. It will fix the memory/task problem and make a com-port available for GPS.

I think, without people like towa,... the manufacturer of XMDA II would provide their online navigation solution until next cebit.

So, thanks to all !

[Puff The Magic Wagon!]

axbl/towa

Many thanks for the work that you have done.

I for one will be waiting patiently until next week, because the solutions you have already made available work & I can be patient for a few days ;)

8)