I've also had problems loading Topo Norwegian Topo Pro maps which I've reported earlier and now tested with firmware 2.4:
The Topo Pro maps in Norway are divided and sold in 20 maps:
Topo Pro cd 1 - Stavanger
Topo Pro cd 2 - Kristiandsand
-
-
Topo Pro cd 20 ....
When I download 9 or more norwegian topo pro maps to my Colorado 300 (sd card) the GPS perfoms a auto shutoff when I select Map/Options/Select Map. (Sometimes also auto shutoff when I select map)
Other experiance exact the same problem. For those who understand norwegian see:
http://www.gps.no/mbbs2/forums/thread-view...004&posts=3
It seems to be a limit in numbers of maps that the GPS can handle. After what I can see this a serious matter in the firmware. I have used the latest firmware and different kinds of 2 gb SD cards. ( I've have also tried these sd cars and maps on my Nuvi 660 without problems! 9 Norwegian Topo Pro maps is less than 1gb.)
I loaded my Colorado 300 with a set of fresh alkaline Duracell Ultra m3 batteries, firmware 2.4.
kl 15.00 I turned the gps on using no backlight.
kl 19.00 the gps turned off, batteries low.
Is this 15 houres?
Still, when I download 9 or more norwegian topo pro maps to my Colorado 300 (sd card) the GPS perfoms a auto shutoff when I select Map/Options/Select Map.
The Topo Pro maps in Norway are divided and sold in 20 maps:
Topo Pro cd 1 - Stavanger
Topo Pro cd 2 - Kristiandsand
-
-
Topo Pro cd 20 ....
When I download 9 or more norwegian topo pro maps to my Colorado 300 (sd card) the GPS perfoms a auto shutoff when I select Map/Options/Select Map.
Other experiance exact the same problem. For those who understand norwegian see:
http://www.gps.no/mbbs2/forums/thread-view...004&posts=3
It seems to be a limit in numbers of maps that the GPS can handle. After what I can see this a serious matter in the firmware. I have used the latest firmware and different kinds of 2 gb SD cards.
A few times when I have panned the map, suddenly the screen has gone black and the unit has turned off by itself. It is not the batteries. Is this a known issue??