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

I've tried changing the stack to CSR - useless utility. Then BlueSoleil and finally the Toshiba stack, which seems to be the best of them. But the problem persists - during pairing, Nokia displays one code, but Win7 displays another one, and there's no way to change it.

windows bluetooth pairing is a ****ing joke
i have a microsoft bluetooth mouse, every time i connect it, i go through this stupid wizard, it lets me click "my device does not need a code" and it works finally. any time the battery dies and it looses the pairing, i have to remove the device from windows as well, otherwise to reconnect it, the only option is to enter the 4 digit code, even though there isn't one. </rant>
so yeah, anyways, i'm not sure wtf you are doing there, i thought the idea is you either get the code from the device or the computer, and then enter it on the other one. it's not supposed to "match" any codes between them on your screen. you have to type it in!

I would say the BT technology is a f... joke by itself. I cannot understand how they screwed up such a simple thing so much. In A2DP, why use some ugly codec instead of directly filestream mp3 to the headphones for them to decode it? Instead, they wire BT chip to the analog output of the device, and use very lossy SBC low complexity codec. Ogh, yeah, they saved 1$ per licence to mp3 tech owners owners... and arguably increased battery life. That's very important, since every new phone receives a worse battery - forts 1500mah, then 1200, now they are around 1000mah. Dumb again, since the processor clock is increased, and they already have a 1500mah developed.

Well, you thought wrong. Recently, SIMPLE SECURE PAIRING v 2.1 was introduced. I dunno why on earth is there any need to simplify dumb enough procedure of "see digits on one device screen, enter them on another". Anyway, the code is now noneditable.
In my case, the PC gives one code, N900 gives another, and there's no freaking way to change it.
See the picture.

I know I'm not helping, but I'm at my 2nd BT dongle and am about to toss it. Simple things simply don't work, things that other BT do. Laptop BT, e.g., works like a charm. Pair is fine, it remembers pairing, send to works.

The PC dongle is a nightmare. Took me 4 hours to finally get a driver that (kinda) worked, it supports 15 protocols and none work as they should. I need to dance for rain to get a file pushed to N900 (it randomly works) and there is no way in heck I can do it the other way around.

I ended up installing SMB on N900 for file transfer. Also, SMB on Windows in case I need the other way around and I'm not near PC. And VNC both ways.

But I simply wish I could right click a file and just send to phone, like I did in the old days. Or drag it to the device. Oh well. SMB kind of does that.