Software update: TomTom Navigator 3.01 build 409

TomTom has released an update in the form of 3.01 build 409 for its Navigator software. The industry 3.0 was announced early this month and presented at CeBIT 2004. The first update of the new 3.0 series is available for download as a zip package and executable† What the changes are in this release can be read below:

What’s new in Tom Tom Navigator 3.01 (409/2)?

• This upgrade provides improved itinerary navigation. When you are approaching an intermediate destination, TomTom Navigator gives a warning signal. This can be turned off in the advanced settings.
• This upgrade includes several improvements to the route planning algorithm.
• On some devices, turning the device on and off caused the application to crash. This upgrade is more robust.
• In a single case, reading the TomTom Navigator 2 settings resulted in a crash. This issue has been resolved with this upgrade.
• The Great Roads of Europe map could not be opened with TomTom Navigator Scandinavia and TomTom Navigator for Spain and Portugal. This issue has been resolved in this upgrade.
• Under certain circumstances, scheduling from city centers or stations could cause the application to crash. This issue has been fixed in this upgrade.
• Some saved Itinerary locations were shown as disabled after loading and attempts to enable the location resulted in the message “This location is not on the map”. This issue has been fixed in this upgrade.
• Improved Itinerary view: Itinerary items had the same name if the street name was the same but the city name was different.
• When driving on a road that is closed to traffic, TomTom Navigator replanned the route immediately after a route calculation. This issue has been resolved in this upgrade.
• When planning the route in the Itinerary view, the original route did not take into account intermediate destinations and detours. This issue has been resolved in this upgrade.
• Under certain circumstances, the application could crash when using the schematic navigation view. This issue has been fixed in this upgrade.