This post is totally irrelevant to BOINCstats or BOINC, but since I spend a big part of a day on this and the information needed is hidden very well I thought I might help some people by posting this. And Google will bring people here that will normally not visit this forum: welcome to you!
A few months ago I bought a TomTom Go 910 with RDS-TMC receiver because I had it with the traffic jams on my way to and from work. I soon discovered that this combination didn't know about all traffic jams, or at least not in time. So when I was waiting in another unexpected traffic jam I experimented with the TomTom plus traffic services and it told me right away I was in a traffic jam, while the receiver was still telling me to go 120km/h faster.
Since my mobile-contract didn't have a GPRS budget and the cost would be sky-rocketing (and it is a company phone) I took a new mobile contract with unlimited internet access and a new bling bling phone.
This new phone is the HTC S710 and it comes with Windows Mobile 6 installed. I played with it and as a real man I was as happy as a child with all the gizmos on it (MSN, email, Internet Explorer, games etc).
Then it was time to pair it up with my TomTom. The TomTom found the phone and reported it found hands free and phonebook functions.... Hey, where is my wireless data connection functionality?? I went through all the settings of the phone, re-paired it with TomTom, tried again, more settings. Nothing. On to the internet. After searching for an hour and trying numerous search phrases I found out a few things. The wireless connection TomTom uses is called Dial-Up Networking (DUN for short) and none of the HTC phones is supported by TomTom. After more searching I found a page (
link) explaining that Microsoft had decided to pull native DUN support from WM6 in favour of PAN.
So here we have the problem: the biggest GPS company uses DUN and the biggest software company dropped support for it (expect a GPS system from Microsoft soon).
Not willing to give up, I went on to the dark side of the internet. Finally I found a .cab file that would restore the DUN functionality. After installing it and a few reboots I re-paired the TomTom to the HTC and guess what: it found the wireless data connection. YES! Success!
But not really. TomTom tried to establish a connection to the internet but it failed. I spend a few hours searching and trying every possible connection option and setting. No luck.
Back to the dark side. More searches brought me a new .cab file. I installed it, rebooted the HTC, and re-paired with TomTom. The wireless data connection was found and the same questions (country, provider) were asked. Then it hung for over a minute (or so it feels) at the 65% progress where all my other attempts failed. But this time it went to 75, 90, 100%. Connection established! Wow, it seemed to work. I tried getting the latest traffic information, and yes, it definitely worked!
So, if you found this page because you need a DUN connection but you have a Windows Mobile 6 (WM6) phone that doesn't support it, here is what you have to do:
1: find and download the file "WM6_BT_DUN.cab"
2: copy it to your phone
3: install it (by tapping on it/entering on it)
4: click yes on all the warnings!
5: reboot (offered by the installer)
6: enable Bluetooth and Bluetooth discovery
That's it.
So where to get that cab file? You can download it from
here. You have to register there. If you are unable to download it, send me a PM and I'll send it to you.
Thanks to AX3L from xda-developers for creating the cab file.
If you are not from the BOINC community and have found this information useful and want to say thank you, then consider reading up a bit on BOINC and maybe start using it.
(I could've made this guide a hell of a lot shorter by only posting the six steps required, but I felt the need to write off my frustration.)
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.