diamond owners please read

DieterR

Member
Licensed User
This thread is waiting for an answer since a long time ...
The problem should be solved with B4P version 6.5 that now generates the correct .exe.config for QVGA devices.
 

agraham

Expert
Licensed User
if the diamond has the same GPS issue as the P3300 and the TYTN2
I recently acquired a Diamond for the explicit purpose of getting GPS working using the GPS Intermediate Driver, included in WM5.0 and later, on devices that exhibit this problem.

I wrote and tested, on the Diamond, the code that is at the heart of the official release of the new GPS library for such devices http://www.basic4ppc.com/forum/official-updates/3268-new-gpsdriver-library.html so you should be OK getting one :)

I have also released this http://www.basic4ppc.com/forum/additional-libraries/3319-gpsdrivernmea-library.html which returns NMEA sentences from the GPS Intermediate library and this http://www.basic4ppc.com/forum/additional-libraries/3327-gpsserial-library.html#post18685 which provides the same facilities as the new GPSDriver but for serial port GPS devices.

The original problem appeared to be an incompatibility with the .NET SerialPort class and the internal GPS of some HTC devices, not limited to Basic4ppc but for any .NET 2.0 application that used SerialPort. I originally blamed HTC for this but having worked on it I suspect that it is actually a Microsoft problem with the .NET SerialPort class not liking the virtual serial port that the Microsoft GPS Intermediate Driver provides for legacy applications that don't know about the Intermediate Driver API.

EDIT :- I just noticed how old the original post is - I bet he's bought it by now!
 
Last edited:
Top