Garmin also says that units such as 260/W, 370, 680 and 780 are compatible with NTU when clearly they are not. That list supplied in the 'Compatible Devices' tab of EUU page is a load of rubbish. Whoever cobbled it together at Garmin US was either seriously hungover or didn't care about accuracy. I wonder if Garmin would give a refund if i bought an EU unicode for my 260W only to find myself unable to properly search by address when on the ground? My guess is no, because they don't list it as the recommended map for a North American 260W in the 'Maps' tab for 'Europe'/'On the Road'. Only the NTs are listed:
Code:
Please Login or Register to see the links
The arguments about NTU compatibility/non-compatibility/partial-compatibility seem to never end and it appears that its mostly down to personal anecdotal experience in particular areas, and in some cases how you're searching, language, text etc. In nuvi series for example, it's obvious some have at least partial compatibility [nuvi 2x5/W, 465, 500, 7x5 for instance], there's almost compatibility in 1xxx, but only 2/3xxx have full compatibility. In my opinion anyway, 2x0/W, 3xx, 6xx and 7x0 for instance are near useless with NTU.

Units with complete compatibility not only have unicode string references in their firmware, but also specifically have 'UnicodeMaps' in their GarminDevice.xml. Less compatible units have it in firmware but not in the xml. Non-compatible units have it in neither. My take on this is that if this reference is not in the GarminDevice.xml then it's not fully unicode compatible:

[Only registered and activated users can see links. ]

If that's not in the XML but it has 'UnicodeString' in the firmware then there's probably some compatibility. If it has neither then don't bother even trying.