Windows Mobile 6.1 trouble

[Markus Humm]

Hello,

is there any resource on the net which lists the API differences between
Windows Mobile 6.0 and 6.1? Especially in regards to the MS Bluetooth
implementation?

My problem is: we developed some software which communicates via
Bluetooth. On Windows Mobile 5.0 and 6.0 it runs fine but on 6.1 it's a
complete failure! Our software does the asigning of a com port to the
available SPP services of our devices on its own, because MS one day in
the past decided to only show one of those SPP services available for
any given device. They claimed customers reported to be confused if more
than one SPP was shown. If I'd be MS I had rather opted on clear
education of users in such cases than to drop this UI part.

Via API one can detect all those SPP services (we require it) and can
select which one to assign a COM port. Since our app. also supports
other BT stacks and real RS232 ports the way via com port seemed us the
most natural one. So are there any differences in that area? Or is it
manufacturer specific (HTC Touch Diamond and HTC Touch Pro but always in
their T-Mobile flours...)

Another thing which could help me diagnosing this problem: does anybody
know which Bluetooth Stack the new HP iPAQ Data Messenger or iPAQ Voice
Messenger have? Did HP stick to Broadcom (what I hope) or did thhey
switch to MS? And: are tey already available in Germany? Or supplier
doesn't yet list them...

Greetings

Markus

 

[Peter Foot [MVP]]

There should not be any differences in the way you assign a virtual COM port
using the Microsoft Bluetooth stack on WM6.1. As you have guessed there are
occasionally differences between devices, also the number of available ports
varies widely between devices.

Regarding HP devices in my recent experience the Standard Edition (e.g.
Voice Messenger use the Microsoft stack). I'm not 100% sure but those based
on Professional Edition may still use the Broadcom stack. I don't know about
availability in Germany sorry.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
peterfoot.net | appamundi.com | inthehand.com
APPA Mundi Ltd - software solutions for a mobile world
In The Hand Ltd - .NET Components for Mobility

 

[Markus Humm]

There should not be any differences in the way you assign a virtual COM
port using the Microsoft Bluetooth stack on WM6.1. As you have guessed
there are occasionally differences between devices, also the number of
available ports varies widely between devices.

Regarding HP devices in my recent experience the Standard Edition (e.g.
Voice Messenger use the Microsoft stack). I'm not 100% sure but those
based on Professional Edition may still use the Broadcom stack. I don't
know about availability in Germany sorry.

Peter

Hello,

according to HP support the new ones have the Broadcom stack. They'll be
available start of december.

I'm organizing currently a Palm Treo WM 6.1 testbed to see if it's not a
problem of the HTC Diamond and Diamond pro.

Didn't yet find other WM 6.1 models our IT dept could/would easily get
me a testbed.

My developper says it's a problem at the point the com port is assigned.
We have to do this ourselves as our device has 2 SPP services but the MS
BT setup can only deal with one so we're using directly the APIs. That
worked fine for WM 5.0 and 6.0. But my developer also says those binding
APIs are declared as deprecated, but I don't want to go through all the
hassle to change this code to using sockets.

Greetings

Markus

Greetings

Markus

 

[Markus Humm]

Hello,

seems we've used two now deprecated API functions.
But: introducing them in WM 5.0 and deprecating them already in WM 6.0
is a bit of Joke, esp. when one of those was replaced with another one
doing afaik the same thing but only with a different name... ;-)

Greetings

Markus

 

[Chris Tacke, eMVP]

Which APIs are you using that were deprecated?


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

 

[Markus Humm]

Hello,

ok we found out meanwhile that it's not because of those 2 APIs but
rather the way we're checing for the BT stacks available. We changed
that and it works now again.

Reason for this seems to be that some required DLL was put into ROM and
somehow hidden in Wm 6.1 at least on those devices we own. Let's wait
and see how those other devices look I've ordered as test bed.

Greetings

Markus

 

[Brad]

How do you properly check to see which BT stacks are available? I'm wanting
to do that too but am not sure of the best way.