Known Bugs in Gartrip Version 210d - fixed in version 210e

 Some GPX files are not read correctly. All coordinates are set to zero.
This bug came up when creading data from new Nüvi receivers but it may happen with other GPX files as well. Users are asked to update to version 210e if affected.

Known Bugs in Gartrip Version 210c - fixed in version 210d

 Some Garmin receivers with GPX file based data transfer cannot be accessed by the menu Garmin
Use the menu file instead of the menu Garmin, and search the receiver and its folder with GPX files.

 Error when reading long routes or tracks from some Garmin receivers.
Use version 210d.

Chart slightly distorted in full screen mode.
In normal screen mode, Gartrip forces the aspect ratio to be the same as for the printer. This is not possible in full screen mode, leading to some x/y distortion.

Known Bugs in Gartrip Version 210b - fixed in version 210c

 Overflow error message when opening a GPX file with big track
When opening a GPX file with a track segment bigger than 32767 track points, the process fails.

GPX file open error
There are GPX files from third party programs using the character ' instead of ". Although not a Gartrip bug, it is fixed here.

 GPX file open error
There are GPX or KML files from third party programs with nameless route points. These aren't assigned correctly to routes. Although not a Gartrip bug, it is fixed here.

 Track read error from Garmin Geko receivers
Some Garmin Geko receivers show the wrong calendar date and use this wrong date also for track time stamps. This bug appeared beginning of the year 2010. Extreme date jumps let Gartrip refuse reading the track. Although not a Gartrip bug, it is repaired now: At each extreme date jump the user is asked for the correct track date.

Please give me a note if you find a bug. Don't forget to tell me the program version number you are using, and your receiver type.

back home