I wonder if any of you experienced BT guys can shed any light on this ...

I have given up on the Vodafone v1640 because it doesn't actually work, as I
suspected. The BT problems are unique to that machine. I have told them but
they are not listening.

I have given up on Symbian because the development system doesn't actually
work. I have told them but they are not listening.

I have laid my hands on a MS stack BT device (a datalogic Jet) which DOES
work, however it's configuration utility for BT is strange, even though it's
CE5. There doesn't seem to be any way it will let you publish the serial
over BT service, even though it works fine with incoming. It appears to use
COM5 for both incoming and outgoing serial comms.

Is this common, or should I look for (yet) another device?

TIA

Unc

Re: More Bluetooth anomalies by Peter

Peter
Tue Apr 03 10:30:56 CDT 2007

For Windows Mobile 5.0 the creation of virtual COM ports is managed through
the Settings > Connections > Bluetooth applet, but for generic CE 5.0
devices this will be implemented differently and can vary between devices.
Windows Mobile devices prior to 5.0 also had OEM implemented control panel
items for virtual COM ports so there wasn't a standard approach.
I'm not familiar with your specific device, is it generic CE 5.0 or a Pocket
PC?

Peter

--
Peter Foot
Device Application Development MVP
www.peterfoot.net | www.inthehand.com

"Uncle Marvo" <paul.r@deletethisbitfortescue.org.uk> wrote in message
news:57f3igF2ctc4gU1@mid.individual.net...
>I wonder if any of you experienced BT guys can shed any light on this ...
>
> I have given up on the Vodafone v1640 because it doesn't actually work, as
> I suspected. The BT problems are unique to that machine. I have told them
> but they are not listening.
>
> I have given up on Symbian because the development system doesn't actually
> work. I have told them but they are not listening.
>
> I have laid my hands on a MS stack BT device (a datalogic Jet) which DOES
> work, however it's configuration utility for BT is strange, even though
> it's CE5. There doesn't seem to be any way it will let you publish the
> serial over BT service, even though it works fine with incoming. It
> appears to use COM5 for both incoming and outgoing serial comms.
>
> Is this common, or should I look for (yet) another device?
>
> TIA
>
> Unc
>
>
>


Re: More Bluetooth anomalies by Uncle

Uncle
Wed Apr 04 03:20:38 CDT 2007

In reply to Peter Foot [MVP] (feedback@nospam-inthehand.com) who wrote this
in 26AA0CCF-EC84-46C4-936E-1EACAB7C4824@microsoft.com, I, Marvo, say :

> For Windows Mobile 5.0 the creation of virtual COM ports is managed
> through the Settings > Connections > Bluetooth applet, but for
> generic CE 5.0 devices this will be implemented differently and can
> vary between devices. Windows Mobile devices prior to 5.0 also had
> OEM implemented control panel items for virtual COM ports so there
> wasn't a standard approach. I'm not familiar with your specific device, is
> it generic CE 5.0 or a
> Pocket PC?
>
It's a CE 5 machine (I believe) which I have to program with eVC4 (because
the SDK won't let me use VS2005). It's a ruggedised job, very sweet machine
but the BT "utility" is not the MS one, it's a bespoke piece.

I will try to contact their techies to see if it can be done, but I'm not
very happy with these "specific" implementations - I wish these
manufacturers would leave well alone!