Anyone know why it is that occasionally, for reasons I cannot figure out, BaseCamp seems to arbitrarily reload the GMAPPROM which takes maybe 8 to 10 minutes?
No updates have been done, nothing I know of has changed. Yet it makes me wait about 10 - 15 minutes sometimes just to use Basecamp while it reloads the gmapprom.
The device is connected btw.
Also, the current maps are already installed on the PC.
Just curious, if you have maps installed on the PC, why do you leave the device plugged in? In my experience, I do all route planning strictly in BC, and only connect the device when I want to load my trip to it, and it only stays connected long enough to do just that.
Just curious, if you have maps installed on the PC, why do you leave the device plugged in? In my experience, I do all route planning strictly in BC, and only connect the device when I want to load my trip to it, and it only stays connected long enough to do just that.
I plug it in to upload the routes and voila! It goes through the 15 - 30 minute gmapprom thing.
I would look to a loos connection. I observed with basecamp and a lot of maps on a USB Stick the following behavour: One map-file on the USB Stick was corrupt. When I connect the USB Stick the first time, all maps are loaded new (also the corrupted map starts to be loaded with such a green line but at the end this line switches very short to red and the map and green/red line disappear). When I separate now the USB Stick and reconnect it once more, the normal maps are shown immmediately, only the corrupt map is reloaded as described above. Therefor it may be, that a loose connection first had corrupted your gmapprom and second each time the connection is interrupted, the map is tried to be reloaded.
I am curious to know if you are letting the map finish it's indexing before you pull the device out of the computer. Once the device has been indexed, it won't have to do this again... In theory. It will do it if something under the hood gets corrupted. 4.3 has improved the indexing speed.
