riffraff9000

Different types of batteries have different discharge rates. Selecting the proper setting allows for a more accurate battery meter.

This "Rugged" horizontal phone case fits the eTrex 10/20/30 perfectly. Ninety-degree detents, slip-on or belt-through holders available. This was too large for my clamshell cell phone, but I'm glad I kept it, as it works GREAT with my eTrex 20.

So, I notice that there's an option for PQs, GPX 1.0 and GPX 1.0.1. Try searching for it. Even quoted as "GPX 1.0.1", the silly search engine here renders that as "GPX 101." So I get a bunch of beginners' threads. How do I find out the difference between the two GPX formats, 1.0 and 1.0.1? And why is the search engine here so incredibly lame?

Nope, won't charge whilst connected to a computer, but I'm pretty sure your batteries won't drain while connected...the unit is then powered via USB.

Heh, I can spend $30 in gas in one day geocaching, if I'm not careful.

WAAS accuracy really doesn't have anything to do with how high you are (unless you're north of Alaska, perhaps), or high fast you're moving. If you are using WAAS, your maximum civilian lateral accuracy is 0.9 meters. Everything else being the same, maximum civilian lateral accuracy without WAAS is 2.5 meters. Either one is easily good enough for geocaching. I leave WAAS on. As John "Bluto" Blutarsky said, "It don't cost nuthin'."

I believe that would be the trade-off in fixing the "sticky."

My eTrex 20 did that when I tried to update with the 2.61-beta firmware. Luckily, I loaded it to a microSD card, and was able to pull the batteries and delete the update from the card in a card-reader. If yours loaded to the device itself, as I suspect the WebUpdater does, you may have to send the unit in to get its mind erased.

I wholly understand the decision to drop Google Maps. What I don't understand (and this prolly isn't GS's fault) is how ANY map maker worth his salt could possibly fail to include a scale bar his map/API. It just wobbles the mind.

My guess is that they lost that functionality when they dropped Google Maps. I. too, wish there was a scale bar.

I installed 2.70 on an eTrex 20 and tried it out yesterday afternoon. We hit about eight caches in varying terrain and cover, and eTrex worked fine. No "sticky" behavior was observed, and accuracy to the caches seemed fine. Even seemed better under trees. So far, so good.

I believe you have to export those to your GPSr via MapSource or BaseCamp. Edit: ...or MapInstall. I forget.

Meh. No software is ever 100% "bug-free."

If you're getting an I/O error on your SD card, the file system might be corrupt. Can you write a small text file to it? If you get the same error, try running chkdsk (assuming windoze) on it. I've had to do this twice on a Garmin eTrex 20 file system.

Some cameras detect how they are held when the photograph is taken, and embed that info in the pic. Then it's up to your display software to rotate it automagically. Sounds like the Oregon doesn't add this flag, or the web site you're uploading to doesn't recognize it.

Okay, the non-beta 2.70 firmware is out, at least it's available via the "webupdater" program; didn't see it on the "my.garmin" web site dashboard, yet. The loader worked this time around, although the verifier sat at "0%" for quite a while...I was starting to get nervous! But all is well, 2.70 is installed. Now to test.

If you keep your GPX files on your memory card you can fix it easily in the field. Remove memory, boot GPS, shutdown, replace memory, boot GPS and caches are back. Good idea. I hadn't thought of that. I shall have to try that. Thanks!

Nice. Well, I guess I was lucky it didn't happen whilst in the field.

Nope, they were the weekly PQs I had already downloaded and saved to my computer.

So, I've been playing with adding (free) maps to my new 8GB microSD card, and suddenly all my geocaches are gone on my Garmin eTrex 20. This unit has worked fine for 3 months, but now suddenly all the caches are gone. I doubt the maps had anything to do with it, as they are saved on the card, and all the caches (mostly pocket-queries) are on the unit itself. Anyway, plugging it into either a windoze machine or a Linux box showed that all the PQs were present. I was able to write to the file systems on both the GSP and the card, from both boxes. Finally I just over-wrote the pocket-queries, and that fixed it. Very odd. So, just a quick note to document this strange occurrence. If your PQs disappear, try reloading them, even if they look fine, file-wise.

Yeah, Cuckoo Cachers' last post in this thread was Jan-11-2008. His last visit to this web site was July-25-2011. I wouldn't hold me breath.

Probably need someone who has one to chime in, but from what I've read, I don't see how a GPS watch would be applicable to geocaching. https://buy.garmin.com/shop/shop.do?pID=11039#owners

Well, the software gives you the option of the GPS device itself, or the SD card, or, if you don't have the GPSr attached, to any recognized card-reader (as long as it has a "Garmin" folder on it). My assumption would be that if it HAD to be installed on the device itself, the software wouldn't give you the other options, and more importantly, it would ignore the file on the SD card. The etrex sees that file on the card, and tries to boot from it. The only fix is to remove the card. If that glitch (if it is) happened on the device itself, I'd be sending it back to Garmin to be resurrected. :-/

I've tried to load the new beta software for my etrex 20, but it always locks up and flashes, "Loader Loading..." until I pull the batteries. This is after multiple downloads of the software zip file (they are always the same size and same checksum), and I've tried this from two different microSD cards (one brand-new), with the same result. Is everyone loading it to the GPSr itself?

Bummer. Thanks for the info.