sduck

Call garmin. Sounds like something they'll definitely replace.

Actually, the change in the tracks behavior was new to 5.80, but people are only starting to notice it with this update, which followed the 5.80 one fairly quickly. Agreed about the montana thing.

This is incorrect. You're misunderstanding the issue. I've tried to explain this clearly, and everyone else seems to be understanding it except you. Perhaps you should back off from this issue since it doesn't even apply to you.

It's not hard - but be aware that you'll lose all your user settings. Your current saved waypoints, geocaches and such, installed maps and tracks will still be there, so it's not like completely starting from scratch - for me it just means changing 4 or 5 settings to my preferences. Instructions below are for the x50 version of oregons. BTW back up all your old stuff just in case before doing this! Go to this page - http://garminoregon.wikispaces.com/Versions+x50 - and download the one you want - use ones that have (gcd) next to them, like the 5.50 one - here's the direct link for that - http://www.garmin.com/software/Oregonx50_WebUpdater__550.gcd - then you'll need to rename that file to gupdater.gcd, then move it onto your oregon into the device memory (not the sd card) into the /garmin directory. Then unplug from the computer, and restart the oregon - it'll ask you about installing an older version, are you sure, all that, click yes, and your done!

Aha - that thread is here - http://forums.Groundspeak.com/GC/index.php?showtopic=300841 The "solution" there is a workaround to a recently introduced bug. A bug that garmin fixed before, and that hopefully they can fix again. It's just a matter of the firmware placing a stop mark at the end of the current track upon powering off, and upon powering on starting a new track (recorded in the same current.gpx file) once a decent location fix is achieved. If this is done successfully every time, no lines! This workaround requires 3-5 extra steps (depending on which page the track manager is on) to perform the same job that the unit used to do automatically. Fo some people this workaround may be an ideal solution - for my useage in saving many separate tracks from many driving trips to google earth it's just too many steps, both while out recording the tracks and later, transferring them all. An easier solution is to just revert to firmware version 5.50 - if you don't need or want the new "features", it's an excellent solution!

Because oregons used to NOT create the straight lines by default. My first garmin gps was a gpsmap 60c, and I later upgraded to a 60csx. Both of these kept beautiful track logs - never a straight line between stop and start points if the gps was started up in a different location. The software knew to shut down the track on power off, and restart once a position lock was attained on power up. When I upgraded to the oregon, at first it had the straight line problem, but as of software 4.30 (I think) it was fixed, and worked wonderfully until version 5.80, where the lines started appearing again. Hence, this is a bug that garmin needs to fix, and should as soon as possible in my opinion. You've mentioned that there is a fix for this, but I've searched, and can't find a thread with the name you've stated twice now. I've also PM'd you - hope you got it! If this is a fix, and not a workaround, I'd love to hear it. I've searched all the settings in my oregon and can't find anything that relates to this.

Could you provide a link to that thread? The search function isn't finding it. Or better yet, paste the workaround or fix here. Apparently it's a pretty big issue for a lot of people, and I for one have never heard of a fix for it.

Yes, usb support in winebottler is iffy. If you can live without it, it's still an excellent alternative. With my oregon, I just export gpx files from gsak to the desktop, and then load them to the oregon from there.

Sorry - didn't know that. Does that mean you can install CNNA maps directly from basecamp, or do you still need to use a separate piece of software?

I don't think basecamp has map install capabilities. You probably need garmin mapinstall - get it from garmin.

Two ideas if you need gsak functionality on a mac - I too have tried crossover, vmware, bootcamp, etc. The bootcamp solution works the best of those, but it's also a pain to set up and switch between. I currently run GSAK in a native mac os app, that lives in my dock, and works mostly similar to a native mac app. How - winebottler. I don't recommend this to anyone who isn't fairly technically proficient, as it takes a bit of trial and error (and/or web sleuthing) to get it set up, but once you do, it works really nicely. It's not a complete solution, - all kinds of little parts of the complete gak experience don't work right, depending on how able you are in setting up wine extensions, but for basic use it works well. I can load up a big collection of pq's, perform all kinds of filtering and sorting and such, and output a nice little gpx file I can load on my oregon easily. Another native mac app that has a quite a bit of gsak functionality is iCaching - find it in the app store. It takes a bit of getting used to, as it works in different ways, but seems to be fairly complete, and still has an active developer - it's not abandonware yet, like so many mac geocaching apps.

I don't see why one would go to all the bother of making a substandard cache container slightly less unuseable than it normally is when there are so many other really good cache containers readily available. Probably for free, available in your house right now. Just because a lot of people have used peanut butter jars (or altoids cans, or film cans, or mentos tubes, etc) for cache containers doesn't make them acceptable.

And don't use a phone that has geotagging built in to take the pictures, especially if it's a puzzle cache - you could be giving out a spoiler without even realizing it!

That fixed it - thanks!

Now if only my statistics page reflected this change - maybe it takes a while for that page to update? Everything else has updated itself nicely - just that line I cut and pasted in my previous post is still there.

Thank you kind sir!

Thanks for the reminder - I've been meaning to clean up my dupes for ages. Way back in the dim early history of caching, at various events it was fairly common practice to hide pocket caches, or event specific caches, that instead of going through the whole cache page and approval process, you'd find them, and then just log the event cache multiple times. I guess it seemed like a good idea at the time. The last time I remember doing this was at geowoodstock 2. Anyway, thanks for the hint about using gsak to find the dupes - that'll make it a lot easier. Ok, mission accomplished, sort of. I still have this - You've found 2711 caches (2704 distinct) since your first cache find on 07/23/2002. I eliminated the dupes I could, but still have 7 extra ones on a locked geocache - GLDV11R - I can't delete the extra logs on this. Any ideas on how to fix this? I suppose I could contact an approver or such for this, but is it worth the extra bother?

iCaching seems to work ok. I've used it a bit, and while its limited compared to gsak, it can be made to work. And it's not abandonware yet, unlike several other mac geocaching related apps. Another idea which I've used for years is running gsak as a native mac app with winebottler. Takes a bit of technical skill to get it going, and also has some limitations, but again, it can be made to work.

ICaching looks nice - hadn't heard about it until now. I'll give it a spin later. Glad to see an involved developer! This probably won't be of much use to most people, but I've been using gsak on my mac using winebottler for a long time - runs like a native app, works well, and fast! Takes a bit of work to get it working right, and upgrading versions is an iffy process.

The keeping them as unpublished listings idea is Very Bad Form - while it might possibly work, depending on the reviewer in your area, you'll be squatting in areas that could be used for active geocaches, preventing them from being published as long as your unpublished hides are there. If you just want to keep them online somehow, use a blog page on tumblr or something.

I hate it when I reluctantly hunt a cache hidden by someone who's known only for lame micros under lamposts, but at least it'll be an easy smiley - and it ends up actually being a really cool walk in the woods to a beautiful location, and a really well hidden ammo can.

First post here by a 10 caches found so far cacher. Hopefully Trinity's link will point the OP in the right direction - hint: use the geocaching.com map once you get to the linked page, you should be able to figure it out pretty easily from there. Looks like a cool park - full of caches!

I was kidding. I'm never serious.

One way to get good ftf numbers is to specialize in one particular area of geocaching. Like only ftf'ing webcam caches, or perhaps 5/5 caches. Me, I only ftf event caches. I have over 400 ftf's at event caches, including most of the geowoodstock ones. Sometimes I'll show up and log them days before they happen just to beat the others! In fact I've already logged geowoodstock X, so you all can back off that one.

How many more RCTs and reviews will it take before quacks throw in the towel? Unfortunately, they never will however compelling and overwhelming the evidence against their claims are. As James Randi would say, they're unsinkable rubber ducks.