GPSFileDepot.com
 

News:

Welcome to GPSFileDepot!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - adrienqa66

#1
Hello,

I followed the step-by-step instructions to install the California Topo map on my Macintosh and then on my Garmin Nuvi 660.

I have the MapInstall software.

I downloaded from the web, the "28-5234-California_Topo.tgz" file and then extracted it to get the "California Topo.gmapi" file.  Then, as per the web instructions for the Macintosh, I went to MapInstall (I didn't double-click the file itself), and I selected the SD card as the place of installation and then the California Topo map name automatically showed up on the left corner of the screen with the screen showing the map.

I elected to select the entire map and then I proceeded to install it.

After installation was completed, I turned on my Garmin (which had been connected in data-transfer mode) and then went to the Tools icon and "Map" and then "Map Info" and there were three maps showing, one was the Garmin Nuvi branded "base" map (2009), and then there was the California Topo map; but it was listed twice.  I checked the Nuvi and there's only one file listed.

So I don't understand why there is a duplicate.

What I've done now is erased the map from the Garmin through my computer, then deleted the file I downloaded, plus the extracted "California Topo.gmapi" file it generated in the same directory (downloads from my browser automatically appear in the Downloads folder and so do extracts when I double-click the file to be extracted.  (tgz file extracted to gmapi file).

I checked my Garmin and no trace of the Topo maps is found (good).  Then, I downloaded the file from the web again and followed the instructions given on this website for the Macintosh.

I am now in the process of installing the map on my Garmin again, hoping that the duplicate issue won't happen again.

I was wondering if other people have had this happen to them.

Is it a known "bug" that is minimal that people just ignore?

Thank you.  I will reply to let people know whether it happens again after I complete the install.