-=(GEO)=-

1) Magellan Meridian Platinum + 64 Meg SD card, Gecko 201, Mapopolis on a Pocket PC (to find places to place caches and sometimes for navigation). 2) GPXSonar (of course! ) on my iPaq 1945. 3) I'm set for the time being.

I've been extremely happy with my iPAQ 1945. It runs Pocket PC 2003. To keep it secure in the field, I use an Otter Box case (Armor 2600) which is waterproof, crushproof and dustproof. My 2 cents.

CacheGear.com

Vacman... Hue!?! I have no idea what you're talking about. Sorting works fine on all columns and if you use the preferences to eliminate columns, they are no longer visible in the grid. Something else is up... Email me directly and we'll troubleshoot this. Regards, Fabien.

My MeriPlat does not loose lock that easily in those Pacific NW forests that you speak about. I would highly recommend it.

DrSearch... Get the update for v1.0. I had a bug in the filters that I've fixed since the release (which is what this thread is about btw )

Dr Search... Yes, with 'List Options\Filters\Cache Attributes' -> 'Hide Found Caches'. You may want to check the online help for a description of the other options. It's not 100% up-to-date, but close. Regards, Fabien.

Renegade Knight... About 'flipping things around': there are 'power toys' available for the PPC that do that sort of stuff. It's really outside of the scope for GPXSonar.

Renegade Knight... Check the 'Preferences'. You can remove columns. Regards, Fabien.

The release version had a bug in the filters causing invalid result sets to be returned. Also, the 'Search' dialog would appear after selecting the 'Country' filter. Both problems have been fixed. This update applies to the PPC 2002 & 2003 versions of the program. Sorry for the inconvenience. Also, GPXSonar is now available on Handango Check it out and add your own reviews. Regards, Fabien.

Capt. Jack... Sounds like you've run out of memory. Try this: using the File/Tools/Performance menu option, switch GPXSonar to 'Use Less Memory'. This should solve your low memory woes. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

I'm French, living and actively caching here in the US. Everytime I read cracks about the French in these forums, I just find it amusing. I have to say that the joke 'Their ammo cans are still full' was pretty funny But more on topic, France is behind mostly because of the cost of the GPSrs: I saw my MeriPlat in a REI-like store in Paris for $585! Even the cost of the Yellow eTrex was insane. Oh and btw, I have one of the few 'real' caches in Paris. Turns out that only non-French people have found it so far in almost a year. Amazing. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

Yep, that's it. I double checked the code and the file is indeed opened r/w instead of r/o. My bad. I'll have a fix available for the next release. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

DrSearch... Ah! I think I know what the problem is. Try this: before you copy the GPX file over to the SD card, change the file attributes on your desktop to Read / Write as opposed to Read-Only. Then try to open the file w/ GPXSonar. I'll look at the code tonight and will try to reproduce this scenario. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

DrSearch... Unless your memory is really low, the size of your GPX file is not the issue here. I run my tests as I develop the app with GPX files that are nearly 3 Megs and I've never seen the symptoms that you describe. Please zip up the GPX files that your trying to open to no avail and email them to me. I'll gladly try to reproduce the problem. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

TheCookieCrew... I am glad that this version is working well for you I had fixed the crash problems in BETA 2 though... You may not have seen it. Next time you have a problem, email me or post to this forum. I take the stability and the performance of the app very seriously and I'd like to know when/if it fails so that I can fix it immediately. But I can't do that if you just 'ditch the app' Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

DrSearch... Weird. I don't know what to tell you at this point. I always load my GPX files from the SD card and I've never experienced this problem. If you find out the cause of it, please email me. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

Phantom... Are you using the release version? If you are, I am very surprised that you're still seeing those “â€ä” sequences: I've added a meta tag to the generated HTML cache pages to let Pocket IE know that the pages may contain UTF-8 escape sequences. I am beginning to wonder if PIE on PPC 2K2 understands UTF-8 or the meta tags. I know that some meta-tags are ignored by this browser. In any event, I'd appreciate it if you could zip up and email me your GPX file so that I can run some tests with it. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

DrSearch... It sounds like you have installed GPXSonar to the memory card. This is not supported. Instead, install the app to the main memory. However, you -can- load GPX files from the memory card. Just place the files in a directory first. I hope this helps. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

The final release of GPXSonar 1.0 is out for PPC 2002! Here's what's new in this version: New Feature: Smileys in log entries are now represented as bitmaps. Bug Fix: It was possible to export more than 500 waypoints to the Magellan Meridian. This is now limited to 500 which is the GPSr's limit. Bug Fix: Invalid characters are properly filtered out when exporting waypoints to the Magellan Meridian. Bug Fix: When showing 'Found Caches Only', the caches marked with a green checkmark are now also included in the result set. Bug Fix: Caches without hints would still look like they had hints in the generated HTML page. This is now resolved. Bug Fix: Hints formatted with HTML breaks are now properly displayed in the hints viewer and the ROT13 converter. Bug Fix: Actual coordinates in Field Notes reports are properly formatted. Bug Fix:Log entries containing breaks are now properly formatted. Bug Fix: Cache pages containing UTF-8 escape characters are now properly displayed. Bug Fix: The 'Bearing' column is now accurate. Bug Fix: In case of an XML parser failure, the offending line # is properly calculated. Bug Fix: In BETA 2, bad characters in GPX files could still cause the XML parser to fail in some specific cases. Bug Fix: In BETA 1, some GPX files containing cache pages with very large description would crash GPXSonar and/or cause a hard reset of the device. This problem has been resolved. New Feature: A 'Search' filter has been added allowing exact or partial text searches on cache waypoints, names and owners. The search on these three columns is done automatically. New Feature: It is now possible to view unencrypted hints directly on the cache page. However, the hints are only visible when they are highlighted by the user. New Feature: It is now possible to generate a report on the caches bearing a field note. After a report is generated, GPXSonar also offers the option to delete the field notes. New Feature: GPXSonar now automatically re-sorts the cache list when the center coordinates are altered either by making the selected cache the center or by manually entering coordinates for the current location. New Feature: A green checkmark appears in front of the name of every cache that has already been found. Bug Fix: GC.com has added 2 new cache log types. One of them being a 'camera' type of log. The other one is still being investigated. Bug Fix: GC.com sometimes produces Pocket Queries containing invalid characters which cause the parser attempting to read them to fail. GPXSonar tries to filter such characters out as the GPX file is being read. New Feature: GPXSonar automatically saves the configuration of the application and any user-supplied data automatically every 30 seconds if alterations have been made. Bug Fix: In some instances, the code generating the caches pages would produce malformed HTML. Bug Fix: A new 'Performance Management' option has been added which allows the user to control how GPXSonar utilizes memory. By default, the performance option is set to 'Use More Memory' in order to be faster. The other option makes the program consume less memory but is slower to load GPX files. New Feature: A 'Preference' option has been included which allows to eliminate columns from the display. Also, the width of the columns is now preserved between runs. Bug Fix: Once again, the icons representing the caches have changed on the geocaching.com web site. GPXSonar has been updated accordingly to provide the same look and feel. New Feature: It is now possible to search on cache 'Owners'. This is a side effect of the 'Search' filter. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

The final release of GPXSonar 1.0 is out for PPC 2003! Here's what's new in this version: New Feature: Smileys in log entries are now represented as bitmaps. Bug Fix: It was possible to export more than 500 waypoints to the Magellan Meridian. This is now limited to 500 which is the GPSr's limit. Bug Fix: Invalid characters are properly filtered out when exporting waypoints to the Magellan Meridian. Bug Fix: When showing 'Found Caches Only', the caches marked with a green checkmark are now also included in the result set. Bug Fix: Caches without hints would still look like they had hints in the generated HTML page. This is now resolved. Bug Fix: Hints formatted with HTML breaks are now properly displayed in the hints viewer and the ROT13 converter. Bug Fix: Actual coordinates in Field Notes reports are properly formatted. Bug Fix:Log entries containing breaks are now properly formatted. Bug Fix: Cache pages containing UTF-8 escape characters are now properly displayed. Bug Fix: The 'Bearing' column is now accurate. Bug Fix: In case of an XML parser failure, the offending line # is properly calculated. Bug Fix: In BETA 2, bad characters in GPX files could still cause the XML parser to fail in some specific cases. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

Finally figured out the problem Turns out that an old file generated by GPXToMaplet buried somewhere on my SD card was screwing everything up. That file was being picked up automatically by Mapopolis and was crashing the app w/o any explanation. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

Trippy... I'm not getting -any- message. The apps quits as soon as I pick any option on the main menu other than help. I am only trying to load 1 map which is about 4.5 megs. The behavior is identical whether I click on the map icon to launch it or if I start from the app itself. I've got about 26 megs of free memory. Mapopolis is the only app running during my tests. Any more ideas? Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

EarlyMorningHours... I downloaded and installed the full app (a few times in fact). Nada Everything should work but doesn't. Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net

I just purchased Mapopolis 4.29S for PPC 2003 with a set of Platinum maps. Everytime I try to do anything with Mapopolis other than view the online help, the app quits on me. For the record, the demo version was running fine until it expired. I emailed tech support about the issue and still have no response after 3 days Has anyone experienced this issue before? Regards, Fabien. Got a PPC? Check out GPXSonar @ http://gpxsonar.homeip.net