dr.bob

I just purchased a Garmin Colorado 400. I love all the features, but I cannot read the screen MOST of the time, and I hate having to use the backlight in daylight. The ancient GPSr I purchased 8 years ago is much easier to read, and I wish I could find a modern GPSr that is as readable. I have tried putting a white background, as suggested, but still the screen is still next to impossible to read in indirect sunlight (shade) or under artificial light (indoors). I can only read it clearly with sunlight shining directly on the face. Any suggestions?

When I use bmgpx, it works great. But when I try to use the resulting .gpx file with gpx2html, it only processes about 1/4 of the benchmarks. Now what's with that?

I guess I was looking for an answer that did not involve using more outside programs. The basic problem I'm describing is an incompatabilty between .gpx files from geocaching.com and ExpertGPS: the .gpx files define 'symbols' that are not accepted by ExpertGPS. This incompatability doesn't show up until I download waypoints to my GPSr, but the issue is between those two entities. I thought that geocaching.com and ExpertGPS have cooperated in formulating compatable files, but in this instance, they are not compatable. I believe that this issue would best be solved by either geocaching.com or ExpertGPS changing their file/program, and not by having to involve 3rd party conversion programs.

Ever since GPX files have come out, I've had a problem transfering Waypoints to my GPSr. I am using the latest beta version 121b2 of ExpertGPS, and a Magellan Meridian GPS. The specific problem is this: Unlike the .loc files, the .gpx files have the "Symbol" field blank; the .loc files gave it a value of "Default". If this field is not blank (as with the .loc file), it will download into my Magellan Meridian just fine. However, with a blank "symbol" field, the download fails. I can manually change the symbol field to 'default' for each waypoint, and then download to my GPSr, but that becomes quite tedious. Is there some other way to get around this, or can the .gpx files be set to have the 'symbol' field non-blank? [This message was edited by dr.bob on February 12, 2003 at 01:15 PM.]

I saw that problem . . . I simply got out my pocketknife and cut the power button flush wish the face. It works fine now.