apersson850

Were you sitting up at midnight watching?

Has anybody tried changing the file attribute to read-only? If it still works then, you can do that. Then at least it will ask once more if you want to delete it.

I don't know where you live, but if it's somewhere where the 24 hour system is used, it's easy to get confused by the illogical 12 hour system. As a note, there is no 24:00 really. Maybe it will show that, but that's then just some erroneous state, before it switches to the correct 0:00.

Considering the discussion above, it's probably: "White man strange, Cut 1 foot section off blanket sew back on other end. Blankets still same size"

Which once again supports my theory above, i.e. that this is a timing problem for signals between some circuits in the unit. If you have such a timing problem in a design, then not only may different units behave differently, in spite of being from the same batch, but the same unit may behave differently from one time to another, due to random variations, temperature drift etc. Software changes can sometimes fix these hardware problem, by simply reacting appropriately. If you know some signal may not be stable at some time, then you may be able to wait for it a little longer, or you may reset some circuit at some time and ignore its signals before that or whatever. There are several possibilities, besides a redesigned hardware. Such software fixes may of course suffer from not fixing the problem in all units, if there are tolerances to components, that makes the problem slightly different in different units. Finally, all this is pure speculation, based on my experience from nearly 30 years of electric and electronic systems design. But Garmin exists in the same universe as the rest of us, so...

Anyone looking at the history of firmware updates for various Garmin models would notice that if there is something that's regular, then it's the irregular interval between the publishing of these updates.

The coordinate matching is a method preferred by those who haven't comprehended the value of the magnetic compass when you come close to a cache. Units equipped with magnetic compasses, like the Colorado, provide a more intuitive method of zeroing in on a certain spot.

Regarding the missing translations (Dutch) above: The translations are in a specific file for each language. When Garmin issues updates, where new text strings are needed, these strings have to be added to the translation file to work. If they are missing there, it will use English instead. That's why there are some translations missing, as the translations files haven't been updated yet. They can be updated separately from the firmware. This is done automatically by Webupdater. Monday as the first day of the week has been an international standard since the early 1970's, but it hasn't made it into the American's minds yet.

There are two advantages with pre-programmed cards: You can move them to any GPS (one at a time) that has a suitable card reader. You don't need any computer to get going. If you are participating here, the last advantage is probably a moot point. It could be understood above, but I want to stress that maps on a pre-programmed card works from that physical card only. You can not buy a 2 GB pre-programmed, then get a 4 GB blank card, move the maps to the 4 GB card and use the rest for MP3. That's not any point for the Colorado, but could be if you have, say, a nüvi too. What could be a point is that you can probably not add any other maps to the card either. For most units, the file structure used will allow only one map file on a card, which then means you are limited to the map that's on the card to begin with. No maps can be added to that file, so you can't install whatever you are interested in on the card at the same time. Now on a Colorado, you can probably have that other map in internal memory, so it may not be any significant problem either.

No. Rate of descent is how fast you are falling down. Glide ratio is how much a line from where you are to where you are heading is sloping. Glide ratio to destination is the same, but not to where you are heading now, but to the destination you have entered. So Glide ratio will depend upon how you actually move, but Glide ratio to destination will show what Glide ratio you need to reach your destination. If you are moving along a certain line, the Glide ratio is the same, regardless of your speed. But the rate of descent is proportional to your horizontal speed, as long as you follow that same trajectory. Besides, it's called the 60 CSx, not Csr.

I assume you mean on the map screen? There the Colorado can have only two, not up to four. On the other hand, the Colorado can show any data in these fields, not just "short" data. Also, the Colorado can show a map only screen, something that's missing on the 60 CSx.

How do you define "simple" backlight?

It doesn't take much time. Just set it to record data always, then check after power on at some later time if you have any pressure curve recorded.

Ha-ha, that was a good one. As jotne already have put it, the obvious next question is how the alarm clock is supposed to work, then? Jotne, does your unit collect barometric pressure data at 15 minute (I think it should be) intervals, when the unit is off? Provided you set up the altimeter to do that, of course.

Not at all more durable, but the 3600a (aviation version) is much more: Expensive. Rare. Suited for off-road navigation. The last item is of course due to that it's intended for aviation as well, and they rarely fly along the roads. Hence the off-road routing capabilities are much better than for the automotive iQue 3600.

Well, if the clock doesn't run, you don't expect the date to advance either, do you? It seems the Colorado now and then thinks the current time is corrupted, which causes it to go back to the last known time stored in the unit. Sometimes, that's more than one day back.

Search near is what I meant by changing the reference point. But you can't set the reference point on the map, that's correct. Well, if you save the (part of the) track you are interested in, then use Where to? -> Tracks -> the track in question, you can follow it at a later stage. That's how the Colorado handles following a previously recorded track. Selecting which part to save, from a full active log, is so bad that you can say it's equivalent to not functional at all. Transfering the track to Mapsource, select what part you are interested in and send it back to the Colorado works much better.

If you just pull the plug on the Colorado, it powers off anyway.

They store the basemap in the file gmapbmap.img.

But now, as the Norwegian came to rescue, I'll simply delete all this mess, and ask you to read on.

I think I wrote somewhere before that I can confirm that under certain circumstances, you will get non-consecutive drive lettering in Windows. It depends upon what else you have defined.

Try renaming both Colorado drives to something consecutive, further up in the alphabet. Like M: and N:. Chances are good it will stay there then.

Whatever I do with these track files is easier with the current implementation, where they merge up to 10000 files in the archived logs. Why can't those who necessarily need these files separated by date, not by location, use a GPSmap 60 Cx instead? If that's the main reason they have it, it should be good enough.

Same here. Took me 14½ days to figure out that it was probably a typo. But I'm not sure.

Close that window and open the drive the Colorado appears as using the file explorer instead.