Re: GPS Application without using GPS Intermediate Driver

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Jan 16, 6:17 am, "obcd" <luc__c...@xxxxxxxxxxx> wrote:
I don't think this is the proper place to change the DriverInterface key
from GPDx to COM4. The active registry keys are created by the OS to give
you an idea of what drivers are active, and to show you how you can
interface them. You should find another registry key with that driver. If
you change the DriverInterface there, you will need to cold boot the device
so that it reloads it's drivers. You can check the active key to see if your
changes reflected to the driver.

"Raj" <pandeyra...@xxxxxxxxx> wrote in message

news:2f9646f2-d42f-42fe-bde2-6c220a693eb0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Hi All,

I am working on WM6 for some GPS Application that uses the GPS
Intermediate driver's virtual port i.e exposed as GPD9 in the
"DriverInterface" key in the registry settings.
And there is this Co-Pilot7 app from ALK that uses the physical port
directly as I don't see any options like GPDx/GPSy.
As far as I understand from whatever reading I have done from MSDN and
all other blogs,If at all any application wants to use the COM port
directly fr the GPS then no other app can use the same COM port.

And I checked with Co-Pilot guy and he said that Co-Pilot 7 does not
support the Microsoft GPS Intermediate Driver.So I need to bypass the
GPS Intermediate Driver and talk to the COM port directly.

I heard that changing the "DriverInterface" key to COMx port should
let the GPS App to use this port for the GPS data.
Please correct me if I am wrong.
::::::::
"I have changed the "DriverInterface" key to say COM4 and made the
changes in this key

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver
\Multiplexer\ActiveDevice]

to COM4 as well. And then tried to configure the GPS at COM4 using the
Co-Pilot App but it didn't configure."

Has anyone ever came across this issue?

I will appreciate any pointers for this issue.

Raj- Hide quoted text -

- Show quoted text -

Thanks for the reply.But as you know I am using the co-pilot 7 to use
the GPS for getting the data and it will use the COM port for that coz
it does not have any option like GPD.
And Co-Pilot does not support the MIcrosoft GPS Intermediate Driver.

I tried changing the driverinterface key and GPSID key but it didn't
work.I wonder if we need to change the source code for co-pilot to use
the GPS.

Raj
.

Relevant Pages

  • Re: Disabling Serial Ballpoint Mouse when GPS connected
    ... common occurance when this GPS is installed? ... > the 'found new hardware' Wizard requesting the driver for the new mouse. ... > connected to the serial port and to see if it's a mouse. ... > installing devices, but this would mean that the USB to Serial drivers ...
    (microsoft.public.win32.programmer.kernel)
  • Re: GPS intermediate driver compatible to old software?
    ... not working on real hardware COM port and you have an application using ... It's possible the underlying hardware driver ... apps calling into them however they feel like. ... I think in general the GPS intermediate ...
    (microsoft.public.pocketpc.developer)
  • Re: Delorme SA2006 vs MS Streets and Trips 2006
    ... >>with other GPS units. ... This was in the first USB ... it had a driver that did the USB to serial ... > port conversion. ...
    (rec.outdoors.rv-travel)
  • Re: USB to Serial converter
    ... You might try some of the driver here if those are not the ones that came with it: ... rate I selected for the port. ... Do you have a GPS receiver? ... Do it after the GPS receiver has a fix because many GPS receivers will not output NMEA data unless they have a fix. ...
    (sci.geo.satellite-nav)
  • Re: GPS intermediate driver compatible to old software?
    ... I think in general the GPS intermediate ... driver is a great idea. ... serial library can sometimes access the software COM port and sometimes not. ... won't work because most older apps are hard-coded to only support COM0-9:. ...
    (microsoft.public.pocketpc.developer)