BetaMan

Well, I have a Garmin 60CSx, a Colorado 300, and Oregon 400t, a StreetPilot 2620 and a StreetPilot 2820. For GeoCaching, I use the Oregon 400t (with 2010 NT Maps installed) For driving, StreetPilot 2820

For me, it's not the "latest" bug. It has ALWAYS been like this on my Oregon 400t, REGARDLESS of what firmware I have installed on it. It has ALWAYS frozen up when attempting to do a Wherigo. In fact, I've NEVER been able to complete 1 single Wherigo with it. When I had my Colorado, it worked fine.

I just transferred (in both directions) between my CO and OR running 2.98. The first transfer took a little longer than I remembered (15-20 to connect) but it did finally go through. Ditto. I was sending / receiving both fine with 2.98 last weekend. While at GeoWoodstock, I received a cache wirelessly from a Colorado 300 without issue, although it took a little longer than it did when I used my Colorado to Colorado wirelessly. Now if they could fix the Wherigo aspect so it would work without freezing up. There was a Wherigo at GWS and several people asked if they could use my Oregon 400t to complete it if I didn't want to do it. I told them, it's NOT that I don't want to do it, it just doesn't work well at all on the Oregon yet. Maybe soon...

Went caching yesterday and found 39 caches with 2.98b. Accuracy was off about 40 feet on most caches and they were placed by various users so it rules out 1 user's GPS being the culprit. Unit turned off again for no apparent reason also. Hmmm...

I have a friend that has the Oregon 200 and his NEVER displays arrival alerts. I was envious. He and I went on a cache run 2 weekends ago and found 292 caches. Mine popped up the arrival alerts EVERYTIME, when I got within like 350 feet and again when I got within 100 feet (approximate). His NEVER popped up! Maybe the Oregon 200 doesn't have that "feature" (annoyance, actually). I have the Oregon 400t.

Also, I know this isn't the place for this question, however, does anyone know what the feature is called that, when routing to a cache and getting close, the unit will beep and say "Arriving at location" for a few seconds is called? I want to DISABLE IT!!!

Well, I found about 165 this weekend at GeoWoodstock and the unt performed pretty well with 2.98b installed. However, the unit turned off several times for no apparent reason again, just as it did with 2.97b installed. It only got me to ground zero a couple of times, but each time, it got me pretty close, even under tree cover, which was a nice surprise!

Going to GeoWoodStock later this afternoon and I hope to do a lot of caching in the area. (as well as log my 3000th find! I have more than 300 caches yet to log. Sandbagging, you know...)

I was caching this weekend in Upper Tennessee and lower Virginia and found 292 caches with version 2.97b. The unit just cut off for no reason several times. Other than that it performed pretty well with drift about 4 times (over about 25 hours of caching!). I wish I had THIS version with me though. I loaded it yesterday but haven't had a chance to try it out yet. I hope the unit doesn't just shut off with this version. (I haven't logged my 292 fines yet... I'm 'sandbagging' to get to 3000 before a friend of mine does... ;-)

I'm with you! Hey, I'd be happy with an "älpha" version for our Colorado. Anything....... anyone, anyone, Beuller? I almost spit coffee on my screen! That's funny!

Seems sucky because the Colorado appears to be able to do Wherigo's perfectly well. What's up with the Oregon team?

I tried to do a "Wherigo" Saturday and it locked up repeatedly. A friend was using a Colorado and it worked perfectly. This is the 3rd Wherigo I've tried with the Oregon and all three locked up repeatedly, regardless of the ROM version. Anyone have any ideas? Also, a friend of mine was with me with HIS Oregon 200 (Mine is an Oregon 400t) and HIS was locking up repeatedly also!!!!

I tried to do a "Wherigo" Saturday and it locked up repeatedly. A friend was using a Colorado and it worked perfectly. This is the 3rd Wherigo I've tried with the Oregon and all three locked up repeatedly, regardless of the ROM version.

I'm glad Garmin jumped on this one. I was stoked about the new features (especially the Waypoint Averaging) and was bragging to some of my 60CSx buddies that we now have this function only to have to ditch the update. Now we have it back! Can't wait to test it out today! Way to go Garmin!

I DID downgrade to 2.95 simply because I couldn't USE 2.96 due to the map freezing constantly. I hate that too because we FINALLY got waypoint averaging!

Well, I switched to 2.85 and let it aquire satelites. Then I reinstalled 2.96 and it worked fine until I started down the road. The map screen froze and I zoomed in and out and it just disappeared! I never got the map back! I pulled off the interstate and installed 2.95 and all was well the rest of the way home (about 60 miles). I quess 2.96 doesn't like my 400t for some reason... I tried it 3 times with map locking up every time.

Well, it did it again! Today the map just disappeared! Very strange. I am using City Navigator 2009 NT and it has always worked perfectly until now. Never had this problem before. Gonna flash back to 2.95 and then see if I have maps again. If so, I'll flash back to 2.96 and see if it was just a bad flash....

Thanks for the reply. I checked it and it waslocked down tight. It appears to be working now though. Just a momentary glitch that hasn't happened before on ANY ROM update. Thought it might be a new bug or something, but maybe not.

Yesterday, shortly after loading the update on my 400t, I restarted the unit and it worked like it always has only WITH new features. I navigated to a new cache and found quickly. I then turned the unit off for a little while due to work. After work, I turned the unit back on and the map screen and had a beige background only. It was blank completely. Moving it around did nothing. Restarting it did nothing. Hard Resetting it did nothing. Taking the batteries out did nothing. I turned off the unit for a while and when I turned it back on, the map showed back up! What gives???? This never happened with any other firmware for me...

Ooops! Double post!

The link worked for me. It took me to 2.96 However, I see no mention of any fixes on this release. No mention of accuracy and WAAS improvements. No bug fixes. Just looks like they added some features. FINALLY added waypoint averaging!!! Will give it a go today!

I had a good day today as well with my Oregon 400t and 2.95 installed.

Yep! It's working perfectly! Must have been a bad flash or something! Now to go grab some caches!

Well, this is strange! I flashed BACK to 2.85 and the satellites picked up perfectly! I then flashed back to 2.95beta and the satellites are in full force! Strange...

I just went back to version 2.94 with the same result. Then I went back to 2.85 and all works perfectly! What's up with the new GPS firmware? Does it take FOREVER to build a new almanac?