Loading maps to internal memory on Colorado 300

[gallet]

Is it safe to send maps to the Colorado internal memory without destroying the basemaps or causing any other problems?

 

Can I back up all the data on my internal card and recopy it back in case of something going awry?

[+Red90]

Yes on both questions.

[gallet]

Thanks,

 

The reason I was puzzled is because there is a 'Garmin' folder on the Colorado and I thought if I send maps that they normally get sent inside a 'Garmin' folder that overwrites any other 'Garmin' folders.

[+DavidMac]

Yes, you can load other maps into the internal memory. On the Colorado 400, the preinstalled topo maps are contained in the file called gmapprom.img. There may also be a file called gmapbmap.img. Don't touch these two files, and you should be okay (I recommend backing them up to a safe place just in case). When you upload other maps to the unit, they should be stored in a file called gmapsupp.img.

[gallet]

Oh, I get it now. Mapsource looks for a folder called 'Garmin' and just replaces the enclosed file, I was under the impression that it replaced the 'Garmin' folder. Thanks.

[gallet]

One last (probably) question. I have a 300, I presume the 384Mb of internal memory includes the 90Mb basemap, leaving approximately 290Mb.

 

My question is, if I send a map file to the internal memory and it is slightly too big, does it say so before attempting to install, or does it just stop when it runs out of room.

 

Also does it matter if the internal memory is filled with maps. Can tracks and waypoints still be saved to their own protected memory?

[+g-o-cashers]

One last (probably) question. I have a 300, I presume the 384Mb of internal memory includes the 90Mb basemap, leaving approximately 290Mb.

 

Nope 380MB is what is free after you take away space for the basemaps and other preloaded software.

 

My question is, if I send a map file to the internal memory and it is slightly too big, does it say so before attempting to install, or does it just stop when it runs out of room.

 

I don't think Mapsource checks this ahead of time, but I'm not 100% sure.

 

Also does it matter if the internal memory is filled with maps. Can tracks and waypoints still be saved to their own protected memory?

 

I've never really tried this. Tracks and waypoints do have internal storage you cannot mpact, however, when you plug the CO into your computer all of the internal data (tracks/waypoints/routes) is dumped into the current.gpx file. I'm not sure what would happen if the drive became full when this file was written. Similarly the CO uses space to archive track logs on the internal drive. In any case you are probably wise to leave 30-50MB free for this type of stuff.

 

GO$R

[+Crid]

You can also have a map file in internal memory and a map file on SD card and swap between the two. I have a City Navigator SD card (which can route along roads) and OpenStreetMap map in internal memory (which can't route along roads, but does have a lot more footpaths, bridleways, etc). It's really neat that I can use City Navigator to drive to the starting point and then swap to OSM maps to go for the cache itself, without having to swap SD cards. Just pick Options on the map page and turn one map on and the other one off.