OSM maps in Win 7-64 vs XP

Former Member over 13 years ago

I just tried to post this but when I hit Submit it disappeared, so if this ends up being a duplicate please ignore or delete it.

I have installed the latest BaseCamp on two computers one running Win 7 64b and the other XP Home and get very different behavior.... On the XP I downloaded a map from the web and put it in a folder My Garmin \ Maps. I am able to see this map in BC without my Oregon 450 or SD card plugged in. Not so with the Win 7 computer - In order to see the maps I must have the 450 plugged in. How do I make the Win 7 perform like the XP?

It would seem logical to me that an application such as this should be able to use maps from any source - hard drive, flash drive, sd card, dvd/cd, or GPS.

0 Former Member over 13 years ago

Put the maps into C:\ProgramData\Garmin\Maps on your Win 7 machine.

0 Former Member over 13 years ago

Tried that - no luck :-(

0 Former Member over 13 years ago

Put the maps into C:\ProgramData\Garmin\Maps on your Win 7 machine.

Well this is curious indeed. I download a new different OSM Street Map and installed it to your suggested directory and it WORKED. Then I tried installing my TOPO map to the same directory and it did NOT work. Tried installing to C:\Garmin\Maps - nope! C:\Program Files(x86)\Garmin\Basecamp\Maps - nope! C:\Program Files(x86) - yup!

Does this make any sense?

I also tried to install a small trail map from the same supplier and it will not work no matter where I put it (but the single IMG file works great on the SD card in the Oregon 450). And when I connect the 450 to the computer the trail maps appear in BaseCamp.

0 Former Member over 13 years ago

Most third party maps, and some old Garmin maps (those that use IMG files) need the Registry to find the folder the IMG files are stored in. These maps are generally furnished with an installer that edits the Registry. I suspect that when you are successful loading the map into a folder, the registry has already been set so BaseCamp looks in that folder. It's more complicated than this with OSM maps, because some OSM map providers use the same Family ID for all mapsets they compile. This would mean that the new mapset you installed would probably overwrite the earlier mapset with the same FID.