For some unknown reason, when I opened nRoute this morning, I received a message that I had a registry error, and I should reinstall the program (sigh).

Well, I reinstalled the update to no avail.

Uninstalled the nRoute from my PC and tried to restart from a fresh install from ''nRouteFrench_24.exe'' to built up to a newer version. All this to receive the same registry error message.

I decided to completely uninstall nRoute, and go back to my original package from my GPS 10 setup disk, which installs nRoute 2.1, with the hope to correct whatever problem. This attemp whas not successfull, I still have the registry error.

I went in regedit and found a complete entry called nRoute. I am tempted to delete the whole thing to get rid of whatever registry problem there is, and be able to start from scratch.

Any suggestions ?

tcassidy

What was the registry error message? Was it to do with a map or something else?

Terry

RJW

Allen, I had the same issue, I did remove all listings for nRoute in the registry.
Reboot then reinstall nRoute and it worked.

AllenMaloney

Which version of nRoute did you install ?

AllenMaloney

Quote:

Originally Posted by tcassidy

What was the registry error message? Was it to do with a map or something else?

Terry

No map related type message, just that there was an error with the registry, re-install

RJW

Version 2.7.6.

AllenMaloney

Got it to work, but I had to start from nRoute 2.1 and built it up from there.
Had problem to get the bluetooth link working, but everything is resolved now.
Thanks a lot !
Allen

kiwitonita

Does nRoute work OK with the latest City Navigator maps?

The reason I ask is that on my XP computer I've tried several times to install nRoute. I have MapSource and BaseCamp running OK. Even tried deleting everything "nroute" out of the registry and starting again from nRoute version 2.1 and working up through them all to the latest 2.7.6.

So then tried a friends new Windows 7 computer: Installed BaseCamp then MapSource latest then nRoute276 then the free Open Project NZ street map. nRoute worked fine.

Thanks for any tips to get nRoute working without bringing up the registry error.

Boyd

You cannot use nRoute with the new maps. A number of years back, Garmin brought out City Navigator NT which used compression to store more map data in a smaller file. nRoute isn't compatible with the NT maps. For awhile, Garmin continued to sell the non-NT version of City Navigator, but they completely pulled the plug almost two years ago.

So unless you can find an old non-NT version of City Navigator, you are out of luck. 2009 is the final version of City Navigator that would work on nRoute. Garmin no longer sells it, but maybe somebody still has it in stock (although I doubt it): https://buy.garmin.com/shop/shop.do?cID=280&pID=8465

tcassidy

Get a copy of MapReverseConverter and you can use the later versions of CNNA NT with nRoute.

Terry

Boyd

Ah, perhaps you're right, I haven't tried that. I know that Mapreverseconverter does not allow you to use NT maps on GPS units that aren't compatible (like the StreetPilot 2600 series). But those units use a compiled gmapprom.img file, whereas nRoute uses the raw map tiles installed on your computer.

If you convert your maps, does that cause any issues with current versions of Mapsource or Basecamp and their ability to transfer City Navigator to a GPS unit?

tcassidy

Just keep both versions and you won't have to worry about that as I can't say for sure. Ken says that having both versions active does not affect MapSource. It sees the original via the .gmap folder at a location in the Users folder for Win7 and the other version by the link in the registry. nRoute only sees the converted one linked in the registry.

Terry

Ken in Regina

Hi Boyd,

Just for the [technical] record, nRoute has no problem using NT maps. It's quite happy to use them.

The problem is not related to NT vs. non-NT compression. The problem is related to where/how the maps are installed on the PC.

In the nRoute and Mapsource pre-6.14.x days, the maps were installed into the Windows Registry. The more recent map distributions don't install the same way. They also come in a different folder/file layout than they used to. This all happened long after the switch to NT compression.

MapReverseConverter takes the new folder/file layout and converts it to the older style and creates the corresponding older style Registry entries so nRoute and Mapsource 6.13.7 and older can find the maps.

Once they can find them, they use them just fine. I have City Navigator North America 2012.20 - the very latest update - working in Mapsource 6.13.7 right now. Anything that Mapsource 6.13.7 can see and use will work in nRoute.

...ken...

Ken in Regina

More for the [technical] record...

The problem with your Street Pilot and other older units is that the device itself does not know how to deal with NT compression. Mapsource, even older versions, will happily compile an NT mapset for one of those older devices, like my iQue 3600. But the device will refuse to use it because it doesn't understand it.

It has nothing to do with the fact that nRoute (or Mapsource 6.13.7) are using the uncompiled map files. The uncompiled distribution .IMG files are all compressed with the NT compression method so they have to understand it to display the maps for you (and they do). The compilation that Mapsource does simply takes the .IMG files for the tiles you have selected and combines them all into a single mapset file for the device to use.

As Terry said, having both the original .GMAP version of the maps and the converted registry version of the maps does not have any effect on either Mapsource or Basecamp. I have duplication of at least the last three City Navigator North America updates (because I have lots of disk space and I'm too lazy to clean things up) and no problems.

And just for final [technical] clarification, the "conversion" that MapReverseConverter does does not alter the original Garmin/Navteq files. It simply puts them into the older folder/file layout and creates corresponding Registry entries for them so older programs can find and use them.

...ken...

Boyd

Cool - thanks, I stand corrected.

I have just started to get interested in Garmin's new map storage format, because it's the same on both the Mac and Windows. As a mapmaker myself, I would like to find a universal format for distribution of map files, and there are advantages to not messing with the Windows registry. For example, Win 7 64 bit has registry-related issues with maps that some of us have posted on GPSFiledepot. These same maps work fine on Win 7 32 bit and other versions of Windows.