John
Tue Nov 28 13:28:06 CST 2006
1 - Really, this is something that the user would need to do via the control
panel. Unfortunately some OEMs removed the control panel (see my blog
below).
2 - There's no real way to be sure (short of trying to hack around the
drivers key, but even this isn't fool-proof).
3 - If your GPS driver supports plug & play, then you do not need to set the
CurrentDriver="...". When you plug it in GPSID will automatically detect it
and start using it. To my knowledge no one has implemented the actual magic
to make a GPS PnP.
For (1) and (2), if there's no control panel app and you're using the
GPSOpenDevice() and friends my inclination would be for you to not try and
hook up the multiplexer at all lest you cause more damage via (2) and taking
someone else's port. If you have to get at the NMEA yourself for whatever
reason, one way would be prompting the user for which COM they want to use
from your app - certainly not ideal, but it could let them guess&check
themselves. The other is trying to open up COM ports and see what's open
but this has a ton of problems (namely some drivers may start doing
unexpected things if they're opened and closed right away, not that they
should but they will anyway :().
Even with GPSID control panel included, on WM we know this is too hard to
configure --
http://blogs.msdn.com/cenet/archive/2006/07/07/659306.aspx. I
know as more carriers integrate GPS directly into their devices you won't
have to deal with this ever again since I'm talking to them about
configuring GPSID right right out of the box. The HP device
(
http://laptopmag.com/Review/HP-iPAQ-rx5900-Travel-Companion.htm) is also
tied into GPSID (or so I was told) to make app dev easier. I know this
doesn't help you at all for the short-term but I hope there's some
consolation knowing MS is aware of this and is fixing it in medium term.
--
John Spaith
Development Lead, Windows CE
Microsoft Corporation
Check out the CE Networking Team Blog at
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.
<wilhelm.lundgren@gmail.com> wrote in message
news:1164277746.833827.103620@j72g2000cwa.googlegroups.com...
> Hello,
>
> I am currently developing GPS software for the PPC environment. I have
> some questions about setting up GPSID correctly:
>
> When lacking a GPSID control panel:
>
> 1. Who's responsibility is it to add posts to the multiplexer registry
> post? Is the the actual GPS driver software, or the GPS mapping
> software? I am aware of that the gps driver should setup CurrentDriver
> registry post and likewise create a key with the same name as
> CurrentDriver and add the subkeys needed in there. This will make GPSID
> to understand where to get data, but who will make GPSID understand
> where it should output data? I am talking about raw data streaming, not
> GpsOpenDevice.
>
> 2. How does one know what com port to setup in the multiplexer
> registry? If i just pick one, it might be occupied and then i dont know
> what will happen.
>
> 3. What will the Plug and play support actually do? It doesnt say
> anywhere what actually happens if my driver supports that.
>
> Hope someone knows!
>
> Regards
> Wilhelm
>