Hello,
The newest City Navigator NA 2009.1 for Mapsource has the same new format and new installation approach as City Navigator 2009 Europe.
How to make it work with Nroute?
For City Navigator 2009 Europe, a similar problem has been solved in here
City Navigator 2009 in Nroute
Is there a solution for City Navigator NA 2009.1?
Thanks.
The newest City Navigator NA 2009.1 for Mapsource has the same new format and new installation approach as City Navigator 2009 Europe.
How to make it work with Nroute?
For City Navigator 2009 Europe, a similar problem has been solved in here
City Navigator 2009 in Nroute
Is there a solution for City Navigator NA 2009.1?
Thanks.
Yes. If you download GMapTool and if you are technical enough to understand the instructions for converting the CN Europe files, you can edit the batch file in the "convertCNE" folder so that it will do the same thing for the CN North America update files.
...ken...
...ken...
Quote:
Originally Posted by Ken in Regina
and if you are technical enough to understand the instructions for converting the CN Europe files, you can edit the batch file in the "convertCNE" folder so that it will do the same thing for the CN North America update files...
It requires very little understanding of Garmin conventions and nothing you should not be able to figure out, as I did, from an analysis of the batch file and the directory structure of the CNNA 2009_10 update files and the "Families" section of the registry for the 6.13.7 maps of your original CNNA 2009NT installation.
Mostly it's just the tedious work of substituting the appropriate file names from the North America update file structure into the batch file in place of the Europe equivalents. You must take care to not make typing errors when doing that. You can use a lot of cut/paste to avoid typos if you have something like the Send To Powertoy. The "Send To Clipboard (as Name)" is the feature you need. It allows you to right-click on any file or folder in Windows Explorer and send the full path to the clipboard so you never need to type it.
It is simple and tedious, but critical, that you find ALL of the corresponding North America equivalent files and substitute ALL of them. Everywhere there is a filename of the Europe mapset in that batch file, the equivalent filename from the North America files must be substituted.
The only spot that requires any understanding of Garmin map stuff is at the end where the registry keys are being built and I already told you that in the North America keys you use 396 instead of 378 in the Family names. And that's not critical. It will work even if you leave the keys named as they are, as long as you don't have the Europe product installed.
The only thing I didn't mention, and this is important, was in the very first key that's being built there is a hex value of 7A01 in the binary key value. That is reversal of the two bytes needed to express decimal 378 (eg. x017A). The correct value to substitute there will be the reversed two bytes for the hex value for decimal 396 (x018C, or 8C01 in the appropriate line of the batch file instead of 7A01).
It matters that you make sure to understand and follow the instructions in the readme-here.txt file. The batch file is designed on the assumption that you will place it in the directory where you want the 6.13.7 map files to end up. That will typically be in something like C:\Garmin\CNNANT2009_10 (you have to create it, obviously).
You can actually comment out the first third of the batch file instead of trying to convert it ... the parts that are there only for the purpose of trying to figure out what directory you are running the batch file in. If you run it with the command line example that shows up after the line containing "echo Please supply source directory!" you can comment out everything before that line.
...ken...
Mostly it's just the tedious work of substituting the appropriate file names from the North America update file structure into the batch file in place of the Europe equivalents. You must take care to not make typing errors when doing that. You can use a lot of cut/paste to avoid typos if you have something like the Send To Powertoy. The "Send To Clipboard (as Name)" is the feature you need. It allows you to right-click on any file or folder in Windows Explorer and send the full path to the clipboard so you never need to type it.
It is simple and tedious, but critical, that you find ALL of the corresponding North America equivalent files and substitute ALL of them. Everywhere there is a filename of the Europe mapset in that batch file, the equivalent filename from the North America files must be substituted.
The only spot that requires any understanding of Garmin map stuff is at the end where the registry keys are being built and I already told you that in the North America keys you use 396 instead of 378 in the Family names. And that's not critical. It will work even if you leave the keys named as they are, as long as you don't have the Europe product installed.
The only thing I didn't mention, and this is important, was in the very first key that's being built there is a hex value of 7A01 in the binary key value. That is reversal of the two bytes needed to express decimal 378 (eg. x017A). The correct value to substitute there will be the reversed two bytes for the hex value for decimal 396 (x018C, or 8C01 in the appropriate line of the batch file instead of 7A01).
It matters that you make sure to understand and follow the instructions in the readme-here.txt file. The batch file is designed on the assumption that you will place it in the directory where you want the 6.13.7 map files to end up. That will typically be in something like C:\Garmin\CNNANT2009_10 (you have to create it, obviously).
You can actually comment out the first third of the batch file instead of trying to convert it ... the parts that are there only for the purpose of trying to figure out what directory you are running the batch file in. If you run it with the command line example that shows up after the line containing "echo Please supply source directory!" you can comment out everything before that line.
...ken...
Ken,
Thanks a lot!
But is a little too much for me at the moment. Let's wait until some kind person does it and post a batch file for us.
Thanks a lot!
But is a little too much for me at the moment. Let's wait until some kind person does it and post a batch file for us.