Thread
:
Bluetooth pairing in WIN7 - pairing number mistmatch
View Single Post
KPAH
2011-01-31 , 07:53
Posts: 58 | Thanked: 22 times | Joined on Jan 2010 @ Snowierasha
#
1
Hi ppl.
It's frustrating how simple operations you've done hundreds of times in the past 10 years, suddenly become a challenge with advances of Android, Maemo, Xbox360, PS3 and other proprietary systems.
My new issue is the following.
I have two PCs - a laptop with a Broadcomm BT and a desktop with an external CSR bluetooth dongle. Both run Win7 x64. They both use Win7 native BT stack (MS).
From laptop, I can access N900 via BT. And after discovering that DUN somehow was forgotten (I had it working out-of-the box in my first BT-enabled phone some 5-6 years ago), and needed to be installed, I'm even able to tether.
However, the PC is another way. I can't pair N900 and its pretty much the dead end.
When I launch Win7 pairing mechanism, it discovers the phone, then shows some pairing numbers on screen, which should match the numbers on N900. Well, N900 shows numbers of its own. These numbers don't match, and pairing fails.
I tired installing Nokia PC Suite, MS BT hotfix (KB980396), tried searching alternative drivers for CSR BT dongle - nothing helps.
It's like you know, all those new and
shiny
products like Win7 or Maemo fail in common things I was able to do with Siemens phones and WinXP ages ago.
I'm almost ready to give up, any help is appreciated. Like on how to change Maemo pairing mode, or Widcomm stack for CSR or anything...
Last edited by KPAH; 2011-01-31 at
09:52
.
Quote & Reply
|
KPAH
View Public Profile
Send a private message to KPAH
Find all posts by KPAH