[mswlogo]

Originally Posted by BooDaddy

I still have the lag when I use the settings the OP had in his first thread. Dont notice it while driving as bad, but if your walking, the GPS doesnt have a high enough update resolution to be useful. You have to walk about 30-50 feet before the gps chip updates your position. I have also tried using GPSgate with GCz and still have the lag.

GPSgate is simply a program that GPS applications can use to "share" the gps chip at the same time. Its also used if your application cant "talk" with the gps chip throught the windows gps api. Its not a be-all-end-all lag reducer. Its an intermediary app used to share out the output from the GPS chip.

I hear ya. I don't notice any difference in lag between Diamond and TP2. Even driving around the block in a residential area. I will try walking with both Diamond and TP2 and see if I notice anything.

If folks say one application works and another doesn't then it's NOT the chip.

Your description of GPSGate is correct and it basically allows COM based apps to use the WM GPS API. Which is what the built in "Intermediate Driver" (aka External GPS applet) is supposed to do. But if you use that you will see HUGE lag (way more than 30 feet).

I think the types of lag are getting confused.

Perhaps it (the chip) changed from 1 sec to 2 seconds to save battery in the chip and folks navigating by car didn't notice a problem but folks walking do. But that only confused the normal bogus Microsoft GPS COM Port emulator lag that has been around for a long time.