Broadly speaking, yes. But some jcv files are tailored for certain units e.g. the 4x/5x series jcv are specific as you probably know and i don't think there is any EU NT jcv files for them, only NTU.
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
[Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
There is not going to be a problem since NTU devices support both latin characters and others (cyrillic, greek, etc)
NT supports only latin characters.
JCV will function if it is loaded together with its matching map file.
NTU capable devices like 3790 were reading NT maps and their additional files before the first NTU map was released so you shouldn't have any problems there. The thing is to find the right NT JCV file for your unit or you may have poor display results and i believe that's what Neil is trying to point out if i understand correctly.
Additionally Neil just wants to say there is no NT JCV for certain unit series.(40/50) So if you load a NT map ,you wont find a working JCV for them.
You have to navigate to get to the good.
Galaxy S5 Kitkat 4.4.2 / Nuvi1200->1250 / Nuvi3790T->34xx / Nuvi 2200 / Nuvi 66 / Oregon 600
I don't think 1xxx should be added to the list of compatible units. Garmin made it, Garmin says it's not compatible. Case closed. It seems 1xxx series reportedly handle unicode better with the latest firmware, however mileage reports vary. It is however a device designed and released before unicode maps were introduced by Garmin. The EU map supplied by Garmin for 1xxx is the non-unicode version.
When the non-uncode EU was issued 4 times a year contemporaneously with the unicode version any debate about 1xxx compatibility was moot. Now that the non-U is down to 2 updates per year it has more relevance and ppl should balance the distinct possibility of search problems in U with the faint possibility of map data deficiencies and associated sub-optimal routing in non-U. Personally, for 1xxx I'd take the risk with EUU, but officially recommend for others to use 2014.40 EU and wait until August for 2015.20 rather than use 2015.10 EUU.
Everyone should just make up their own mind about the alternate risks of course, so in taking that on-board the debate is again moot.![]()
'Thanking Posts' are banned. To thank someone, and/or to see hidden links and content, use the [Only registered and activated users can see links. ] button below left of the helpful post then refresh your browser [F5 key]. 'Thanking Posts' are banned.
Please don't spam. Posts serving no purpose other than to thank or to ask about hidden links are trashed or deleted, it's GPSPower's policy. Please don't spam.
[Only registered and activated users can see links. ] should make their first post as a new Intro Thread in [Only registered and activated users can see links. ].
Garmin nuvi 250W SW 7.60
Work fine with CN Europe NTU 2015.10
I from Latvia![]()
So is the Garmin Edge 800 compatible?
Bookmarks