3rd party map "Locked" after update to 3.0.1

Former Member over 15 years ago

G'Day,

I use the 3rd party map product OZtopo V2.1 which consists of three separate maps (Contours, Roads and Contours+Roads combined). All of them worked flawlessly in BaseCamp 2.1.1 Beta.

Today I updated BaseCamp from version 2.1.1 Beta to version 3.0.1 and now I get this message box:

when I launch the application. :mad:

In the Map Info message box, the status of OZtopo V2.1 Roads shows Locked, while the status of OZtopo V2.1 10m Contours shows Unlocked:

As mentioned above, both maps belong to the very same product and use the same unlock code?!

This attachment:

shows the Map Info message box under BaseCamp 2.1.1 Beta. As you can see, both OZtopo maps are Unlocked. And that's the way it should be in version 3.0.1 also!

When I select OZtopo V2.1 Roads under BaseCamp 3.0.1, BaseCamp seems to fall back to the Global Map.

Could you please fix this problem? Or is there some workaround?

Cheers,
juliet11

PS: I have reinstalled the OZtopo V2.1 Roads map twice via MapManager, but that didn't help. :(

0 Former Member over 15 years ago

I'd think your oztopo is a locked map made with cgpsmapper.

any FID above 2200 will be locked if there is no .gma unlock file.

Also the new firmware of the oregon will be locking the maps.

Contact the maker of oztopo, he need to redraw his map with a lower id.

0 azdrmn over 15 years ago

Contact the maker of oztopo, he need to redraw his map with a lower id.

What he said. Some third party maps are made with a family ID that was reserved for a new way of unlocking maps. As such, the original provider will need to rerelease to be unlocked on the unit and in BaseCamp. Sorry for the inconvenience.

0 Former Member over 15 years ago

juliet11 OZtopo has a forum, I would suggest you make this issue known as quickly as possible since the same problem happened with Feb release of MapSource. They are advising everyone to downgrade their Garmin Software. I doubt they will pleased to hear about this.

http://gpsoz.freeforums.org/oztopo-f3.html

MapSource Problem:

http://gpsoz.freeforums.org/mapsource-v6-15-10-or-v6-15-11-do-not-upgrade-t375.html

0 Former Member over 15 years ago

Thank you all very much for your replies!

@ GPS-INFO_NL: I googled a little bit and had a closer look at the map itself. The FID of OZtopo seems to be 5027. And I do not have a .gma unlock file. My unlock file is called UnlockCodes.ucx. Also, it would appear that the OZtopo Contours map is not a locked map after all, which would explain why it's still usable under BaseCamp 3.0.1 while the OZtopo Roads map is not.

@ azdrmn: I don't think they will re-release the current version (2.1) with a new ID as they are about to ship version 3 of that product. It would be too much of a hassle for them. Whoever is to blame for this problem, one thing is for sure: For us customers this is an extremely annoying situation.

@ AMEMAIN: Thanks for the pointer to the OZtopo forum, but I am already a registered user over there ;). (Although I use a different nick in that forum, which wasn't available here anymore.) Having said that, for some reason I totally missed the thread about the MapSource problem. Looks like this is exactly the same issue. I will let them know about the BaseCamp 3.0.1 / OZtopo 2.1 incompatibility.

Thanks again,
juliet11

0 azdrmn over 15 years ago

@ azdrmn: I don't think they will re-release the current version (2.1) with a new ID as they are about to ship version 3 of that product. It would be too much of a hassle for them. Whoever is to blame for this problem, one thing is for sure: For us customers this is an extremely annoying situation.

If OZTopo had released their maps using Garmin's OEM tools, they should not be having this issue. This is one reason that Garmin frowns on 3rd party maps that don't go through Garmin; customers are ultimately the one that will suffer.