fpb

Did you ever find out what was the problem? The same thing happens to me, I need to wait a lot of time before the unit finishes whatever it is doing after the transfer. I have a similar problem while recording the current track or a portion of it... It takes forever to recover after saving it. This last issue disappears if I remove my geocaches .ggz file or if there is only a small number of them. I usually have around 30k geocaches loaded as a single .ggz file. I tried splitting the caches into several .ggz files but it takes more than 15 minutes to load them when they change... Frustrating!

Hi! I believe the problem is with the buggy firmware in Colorado/Oregon devices. Does it crash in ever chache or just in certain ones? my Oregon crashes on some (always the same) caches. The solution I found was to convert the .gpx files with a program that I wrote. The program removes every problematic HTML tag that Garmin's firmware doesn't like. It produces a new .gpx file that I can use without the unit crashing. if you are interested in the program (i have both Windows and Mac versions) feel free to send me an email at: fernando dot birra at gmail dot com Have fun fpb PS. If the problem happens when you try to acess the cache description that it most certainly is the same problem I have.

Now I have faith that the problem will be solved...

It may not be a big problem but in the field, with limited time, having to remove the batteries and not being able to do this cache is really annoying. If you try the program let me know if it solved that particular cache. I ended up incorporating the program into my pipeline. I export the caches with GSAK and filter the .gpx files before loading them to my Oregon. Never had to remove the batteries after Have fun

I also have the same problem. Everything was fine until 3.42b. At least 3.30 and 3.41 didn't have the problem. I solved the problem by writing a small program that loads the original .gpx files and creates new ones, without troublesome HTML tags inside. I have versions for mac and windows. You can grab the programs here: OregonGPXFilter I hope it will fix your problems.

No on my OR300 with 3.6. This firmware seems really stable, apart from a issue I have with HTML processing on a lot of cache pages. My unit crashes on several cache description pages since 3.42b like this one: - GC1WBBP and it breaks text display on others, like this one: - GC1PJWF I know that this is not a bug that affects everyone but I also know that it is not just me. I ended up solving my problem by writing a small program that removes most of the useless HTML formatting tags from the .GPX files. Oh, and one more bug. My compass seems to hang for long periods of time. I solve it by calibrating it again.

It means you don't live in Europe How come? I live in Europe and sometimes (and only sometimes) I get D over the sat bars... So, I guess EGNOS is really working (sometimes at least)...

Perhaps when they say: * Corrected issues with GB Discoverer maps. They don't mean ALL issues but just a FEW... I too have a problem although a different one. On some cache descriptions the unit hangs up and I have to remove the batteries. This appeared in 3.42b and what worries me most is that it doesn't happen in all units, so it will be harder to have this one sorted out. I must say that Garmin has done a good job in putting new features in this devices. It is just too bad that that the firmware is still so buggy. I wished we all had a channel where we could discuss the issues with the developer's team...

Ok, I think I know how to solve the missing magenta line problem. After playing around with the profiles I noticed that in the recreational profile the line was drawn correctly. My suggestion is to do this: 1. Backup your profiles folder 2. Choose every profile and mark which ones exhibit the missing magenta line problem 3. Connect the unit via USB 4. Delete all the name.gpf files in the profiles folder for every profile that showed trouble in 2. 5. Disconnect and turn the unit on 6. Choose a valid profile (hopefully you will have one where the magenta line appears. If not I can send you one for the Oregon x00 series). 7. Go to setup profiles and duplicate the profile as many times as needed and change their names to replace the deleted ones. 8. All you have to do now is to configure each and every bit of your new profiles to suit the specific needs. Of course, an old backup of your Garmin unit might be a more straight forward way To answer the questions above: - It affects both on-road and off-road navigation - Independent of maps chosen and type of display (north, automotive, track up) - routes correctly but no line, only white arrows in auto mode - Compass works ok. There is only one place where I could still see the magenta line: Active route and then choose the first maneuver. You will be taken to a kind of roadbook representation where the line is visible. By the way, to show you how Garmin really made a mess with this upgrades, take a look at my compass screen at some stage (Oregon 300, don't forget): After a restart it finally ended up correctly, like this. Later, after trying to reinstall the software using Updater and FW 2.50, I got the same old thin arrow we are used to in the x00 series. But this proves one thing: Other arrow types are available, its just Garmin being nasty on us...

No Magenta line on my Oregon 300 either. Also, the unit crashes on the following cache description pages (just a few as an example): GC1WBBP GC1GD56 GC20KEK Finally, the unit also crashes while trying to access the diagnostics from the sat screen (Keeping the top left corner pressed for 5 seconds while on the sat screen). The strangest part of all this is that the behavior is not consistent among different units. I guess this will be a really nasty set of bugs for Garmin to solve...

Not really related but I've been using 3.20 for a couple of weeks with no major problems. After upgraging to 3.30, in just 1 day, I've experiencing lockups too, specially at startup. The last one was really nasty. I had chosen a route before shutdown. After waking up I got a route error, followed by a restart. After restarting the unit did a kind of hard reset, asking me which language I wanted. All my profiles were reseted and my geocaches had gone. I had to manually update the timestamps of the files for them to showup again. I'm thinking of going back to 3.20... fpb