Tomtom one updating maps
Mapping is unit specific, therefore it is important to know which Tom Tom sat nav you have so that you buy the correct map. Tom Tom ONE 1st or 2nd (New) Edition, however these have since been discontinued.The only current option is to download new maps or map updates from Tom Tom (see below).When you buy a GPS Unit from Tom Tom, it comes with Canada/USA/Mexico maps pre-loaded.That's great, but they also include something nice called a "30 Day Latest Map Guarantee".This sounds great - you can download the most recent map from Tom Tom via their "Home" software, and it will install itself on the GPS device, giving you the most up-to-date maps possible.In theory, this is a great idea, and solves the need for Tom Tom to supply a DVD with maps on it inside the shipping box, etc. The "Home" software downloaded the maps no problem, worked like a charm, and only took 10 minutes or so for approx 1.6 Gb of files, pretty sweet.The issue occurred when the software attempted to copy the downloaded maps onto the GPS device itself.The copy failed within 5 minutes, claiming that there was a "write error", something to this extent: ERROR: Home Base/IO: Error writing file: K:\USA_Canada_and_Mexico_P\@ .\portable\cfile.cpp(1947)Now, if you've got a degree in Computer Science, you can see this is some sort of I/O error, and it's being thrown from a C file that is internal to the "Home" software's IO module...?!?!!
The ONE 3rd Edition doesn't even have an SD card slot, which is required for installing new or updated maps when buying maps from us.
The one annoying thing with Tom Toms is that you have to keep up with the latest changes to speed cameras and routes.
To do this, you'll need a subscription to Tom but Tom Tom Home can make things a bit smoother.
And now for a chapter in the "Don't ever do this if you run a software company" magazine... Tom Tom's "Home" software to update the Map software on the Tom Tom One 140 GPS Unit is a huge magical "epic fail" of Quality Assurance proportions.
This is so terrible I figure I'd blog about it now that I have a solution, and hopefully others can benefit from the research I just did figuring out how the heck to fix this.