XPSP2 Bluetooth + Activesync

[stevetooth]

I have installed XPSP2 on my laptop, and replaced my original widcomm bluetooth stack with the proprietary microsoft one. My only problem is that from this point simply nothing works. The laptop can discover services nicely on other bluetooth devices, but no other device (my mobile phone, SE T610, iPAQ 4155, and an other PC using widcomm stack) can discover anything on my XPSP2 laptop. I also donno how to initiate an activesync connection over bluetooth from my PDA. Naturally I cant reinstall Widcomm drivers once XPSP2's own driver installed.

HELP!!!

[Jereboam]

Hmmm I have the same thing...my iPaq 5450 discovers a single service on my laptop which is helpfully labelled "p" and is a gears icon.

At which point the whole process is pretty pointless.

OBEX works fine, for once, though.

I was excited about the new Bluetooth stack in SP2 because the old one on my Vaio was notoriously bad, and never worked with Activesync anyway.

Very boring. I haven't the time, energy or inclination to beta test anybody's crap anymore, at least not when it is not my conscious choice to do so. As I get a little older I really just want stuff to work, as advertised, and paid for.

J'bm

[freitasm]

Hmmm I have the same thing...my iPaq 5450 discovers a single service on my laptop which is helpfully labelled "p" and is a gears icon.


Completely broken. This happened to me with RC1. Sometimes other devices can't find the Windows computer, sometimes can't find the services, and sometimes all work like a charm.

I reported this "p" thing to Microsoft, but of course nothing was done. Bluetooth seems to be as broken as before.

Also the serial port needed for ActiveSync is not created by default. Open the Control Panel, find the Bluetooth icon and then create an Incoming port there. Take note of the number and check this number on ActiveSync.

To see screenshots of Bluetooth ActiveSync, check our Bluetooth Guides (http://www.geekzone.co.nz/content.asp?contentid=449)

[stevetooth]

Hmmm I have the same thing...my iPaq 5450 discovers a single service on my laptop which is helpfully labelled "p" and is a gears icon.

At which point the whole process is pretty pointless.

OBEX works fine, for once, though.

I was excited about the new Bluetooth stack in SP2 because the old one on my Vaio was notoriously bad, and never worked with Activesync anyway.

Very boring. I haven't the time, energy or inclination to beta test anybody's crap anymore, at least not when it is not my conscious choice to do so. As I get a little older I really just want stuff to work, as advertised, and paid for.

J'bm

Yeah, I found that mysterious service "P" too.

But now I figured out how to activesync: its not enough to pair the laptop with the PDA, you have to separately add an "Incoming COM port" in the COM Ports tab of the bluetooth config window (because the automatically added one during the pairing process does not work. also the port should be COM1-9, otherwise activesync cant use it), and then set this port as default com port in the activesync connection setup window. If this is done, then you can find the service "COMx" using my ipaq's built in widcomm BT manager, and also u can use the PDA's New/ActiveSync via Bluetooth option.

I still dont know that how can other computers initiate connection to the network access service and file transfer service of the XPSP2 machine, it seems like the XPSP2 box can only initiate such connections, not accept them.

[freitasm]

I still dont know that how can other computers initiate connection to the network access service and file transfer service of the XPSP2 machine, it seems like the XPSP2 box can only initiate such connections, not accept them.

SP2 still doesn't offer the Network Access (LAP or PAN). You should really stick with Widcomm.

[Jereboam]

Also the serial port needed for ActiveSync is not created by default. Open the Control Panel, find the Bluetooth icon and then create an Incoming port there. Take note of the number and check this number on ActiveSync.

I discovered that...ticked the box for the serial port service, waited, made a cup of tea, had a bath, went out for a drink, caught a movie, came back and it had just about decided what it wanted to do with itself...

But still didn't actually assign a port, merely suggested that now an Incoming port was a possibility, if the moon was in the right phase and I sacrificed my children to the Norse god of wirelessness.

OBEX decided it wanted to use COM 13 for file pushing...

Activesync wants to use ports 3 or 4, and brooks no argument.

I give up. Almost.

J'bm

[Jereboam]

SP2 still doesn't offer the Network Access (LAP or PAN). You should really stick with Widcomm.

Can you upgrade to SP2 and retain your original Widcomm stack? I had thought not...

J'bm

[freitasm]

If you are upgrading, yes. If you try to install the Widcomm AFTER the SP2 then things get complicated.

[stevetooth]

I still dont know that how can other computers initiate connection to the network access service and file transfer service of the XPSP2 machine, it seems like the XPSP2 box can only initiate such connections, not accept them.

SP2 still doesn't offer the Network Access (LAP or PAN). You should really stick with Widcomm.

Well, there is BT PAN in XPSP2, and it works great, but its one way only: the XPSP2 can connect to existing bluetooth netowkrs, but you cant create one. Its a silly thing, because for instance if i wanna quickly create a network between two laptops (lets suppose, these laptops dont have WLAN) on the go, I simply cannot, because although both can join a bluetooth network, none of them can create one. lol.

[freitasm]

One way only, when all computers in the house are using the same software, is not very good. It's almost the same as nothing, really.

[Jereboam]

I'm not quite sure why Microsoft have incorporated Bluetooth in SP2 with such damaged functionality...why bother?

The bluetopian dream of having devices in proximity talk to each other easily and with a minimum of configuration keeps getting pushed just out of reach.

It's disappointing, especially when the tech has been around for donkeys and there are very complete and defined standards for it.

J'bm

[stevetooth]

I'm not quite sure why Microsoft have incorporated Bluetooth in SP2 with such damaged functionality...why bother?

The bluetopian dream of having devices in proximity talk to each other easily and with a minimum of configuration keeps getting pushed just out of reach.

It's disappointing, especially when the tech has been around for donkeys and there are very complete and defined standards for it.

J'bm

Yeah. I hope that m$ or a third party firm will update this otherwise great implementation with the required features. I think m$ bluetooth integrates into windows much better than any other implementation (widcomm for example), its user interface is nicer, and (should be) easier to use. The most important lacking features are:

- Create bluetooth PAN / offer bluetooth PAN service
- Offer File Transfer service (not just file receive), share folders for bluetooth sharing
- Ability to browse other devices' shared folders
- Support of bluetooth audio (audio gateway, headset, handsfree profile)
- Some kind of PIM synchronization ability

these are the most important.

[Darius Wey]

Yeah I had that "P" issue since I had SP2 in its beta days. I didn't think it was that big an issue because I mainly used my BT for ActiveSync which I established by noting the incoming COM port, and PAN which I enable in Network Connections. Sure it was more of a hassle than when I had 3rd party drivers installed, but for basic functionality, the SP2 BT functions should be sufficient for your needs.

[Jereboam]

Got Activesync working, but had to juggle port numbers....so don't know what else I have broken yet!

Grrrr...

J'bm

[Badandy]

Hey guys. I have a question.

I got a Dell with built in bluetooth. I recently got bluetooth to work with my phone and pda again because my harddrive failed, and they shipped me a new one. So, what happens now? If I install SP2 and DO NOT uninstall "Dell Bluetooth Software" that is listed in the Add/Remove Programs, will it still work? Do I need to uninstall it first? If I do uninstall it, can I get it working with dial up networking? I like my software, do I need to use microsofts, or do I just not uninstall it?



Thanks

[stevetooth]

Hey guys. I have a question.

I got a Dell with built in bluetooth. I recently got bluetooth to work with my phone and pda again because my harddrive failed, and they shipped me a new one. So, what happens now? If I install SP2 and DO NOT uninstall "Dell Bluetooth Software" that is listed in the Add/Remove Programs, will it still work? Do I need to uninstall it first? If I do uninstall it, can I get it working with dial up networking? I like my software, do I need to use microsofts, or do I just not uninstall it?



Thanks

hi,

if dell software is installed prior to sp2 installation, then the bluetooth settings will remain unchanged. however, if u install sp2 with dell bluetooth software not installed, sp2 bluetooth will be automatically installed, and u cant (or hardly can) install dell software afterwards. or at least i think so.

steve

[Badandy]

Thanks, I'll just keep it installed. I have it working perfectly now.


Has anyone experienced bad performance when upgrading to SP2? Does it slow everything down?

[Jereboam]

No, quite the reverse actually. My laptop was getting sluggish to the point I was thinking of doing a recovery disc back to a virgin state, especially seeing as I knew SP2 was coming up.

That's a lot of work though to reinstall everything so when I found the "admin" SP2 was out I decided to give it a go.

Although still needing a general tidy up, I'm pleased to find my machine genuinely responding much faster.

J'bm

[Badandy]

Cool. I think I'll give it a go.