I have had quite a time with GPS's lately. I am a long time Garmin user. My 5 year old Nuvi bricked on me while driving cross country. Stopped at a Walmart and picked up a newer model. After an hour, it crapped out too. Disgusted, I decided to give Tom Tom a try and picked up a Start 50TM. It worked like a champ the rest of the trip and got me home. It took a little getting used to the differences between the Tom Tom and Garmin interfaces but I caught on pretty quick. The first thing I noticed was that the Tom Tom does not change time zones automatically. That is very annoying and would seem to be a simple thing to do.
Anyway, the reason for this post is to share my nightmare trying to update the maps after I got home. I run Windows 7 64 bit. Tom Tom HOME installed just fine, I entered my coupon codes and thought I was good to go. After what seemed an eternity, it gave an NS_ERROR. After trying a complete reinstall of HOME, a reset of the GPS unit, turning off my firewall/antivirus, it did the same thing.
I took the GPS to work where I have a Windows XP machine. The map update still took an eternity but was successful. I can only come to the conclusion that HOME is not compatible with Windows 7 64 bit. I have a support ticket in with Tom Tom and just got a response. Their solution is to run in compatibility mode, or download version 2.6. I will give it a try. This seems strange as 64bit Windows is not new.
Anyway, the reason for this post is to share my nightmare trying to update the maps after I got home. I run Windows 7 64 bit. Tom Tom HOME installed just fine, I entered my coupon codes and thought I was good to go. After what seemed an eternity, it gave an NS_ERROR. After trying a complete reinstall of HOME, a reset of the GPS unit, turning off my firewall/antivirus, it did the same thing.
I took the GPS to work where I have a Windows XP machine. The map update still took an eternity but was successful. I can only come to the conclusion that HOME is not compatible with Windows 7 64 bit. I have a support ticket in with Tom Tom and just got a response. Their solution is to run in compatibility mode, or download version 2.6. I will give it a try. This seems strange as 64bit Windows is not new.