vlado08

Er .. yes ... that is exactly what you would expect! 12-hour clock starts at 12:00 am (midnight) and goes to 12:01 am, 12:02 am ... 12:59 am, 1:00 am .... 11:58 am, 11:59 am, 12:00 pm (midday), 12:01 pm ... 12:59 pm, 1:00 pm, 1:01 pm ... 11:58 pm, 11:59 pm, 12:00 am (midnight). 24 hour clock starts at 00:00 (midnight at start of day), and then goes to 00:01, 00:02 ... sand so on in an ever-increasing sequence until 23:58, 23:59, pausing instantaneously at 24:00 (midnight at end of day), which is equivalent to 00:00. Hope this helps! Thanks Julianh. I feel so stupid.

Have any body noticed what the clock shows at 00:05 o'clock? I have Co 300 and it showed 12:05 am. And after switching to 24 hour format it showed 00:05. Returned to 12 hour format and it showed 12:05 am again.

That's what manuals are for. Granted, the Colorado manual is pretty poor but to expect the unit to use up storage for documentation that one will only need initially, while a new owner familiarizes themselves with a unit ... that just seems like a waste of storage. It's better to ask Garmin to improve their user manual. I don't think it will use a lot of memory it's just text info. And it will be useful for things you are not using very often. And after some software change there may be discrepancy between manual and actual menu. I have this in my GSM why not have it in my GPS? And also not every thing is for every one there are people that won't need this feature but there are people that will appreciate it.

To g-o-cashers Can you add this to your list: It is good in option menu to have in the end something like help Well this is not an issue but I think it is good to have it. In pages where you can change settings you can see in the help what each entry is if you need to. Of course this is not priority number one but still they should consider it.

My Colorado 300 has this clock problem after software v 2.40 alarm is working properly but when switched on the clok is not correct which leads to slow locating of the satellites. So this are my thoughts: If the alarm is correct and it is set on or off by software. Then this should be a software problem but there are people without this problem and this is very strange?? May be there are different hardware versions and they behave differently but I've heard that units with close serial numbers behave differently???? And I cant understand how many people have this problem and know about it and how many have it but do not know. I understood about it after slow locating of the satellites. But with v. 2.40 some people may not understood that they have the problem. Also many people without the problem don't write in the forum. So it is difficult to understand how wide the problem is.