I am sending this as an open letter in hopes of persuading TomTom management to test the current incarnation of the install script for the Safety Camera applet, for reasons described below.
[1] As a justification for my request to TomTom to test the install script for the safety camera applet, I am going to describe a totally mind-blowing experience which clearly indicates that TomTom's software team is not always following proper testing of application install scripts. Specifically, I found a glaringly careless error in the script that updates HOME version 2.7.3.1894 to version 2.7.5.2014, when run under Windows XP.
During installation, the script halted and said::
"Error opening file for writing: C:\Program Files\TomTom HOME2\xulrunner\nspr4.dll.
Click Retry to try again or Cancel to stop the installation".
I went and looked for this nspr4.dll file and found it existed already, and that the script writer had failed to handle this (should have either erased it or given overwrite permission).
So I erased nspr4.dll and said retry and yes, a new version of nspr4.dll was installed.
I had to do the same thing for 8 other files in the /xulrunner/ folder before the installation would complete without errors. The files in the xulrunner folder that needed to be erased or overwritten were:
nspr4.dll; nss3.dll; nssutil3.dll; plc4.dll; plds4.dll; smime3.dll; softokn3.dll; sqlite3.dll; ssl3.dll
Clearly, the script writer (or his/her supervisor) committed the cardinal sin of assuming the script would work without actually testing it. This is unbelievable carelessness and someone deserves a thorough wigging… possibly some exec who was pushing for too much too fast or skimping too much on programming resources. Maybe the script worked on one OS but not another. But my OS is XP, which is surely popular enough for testing to be mandatory.
[2] I have had another unpleasant experience that I suspect may also be the result of sloppy script writing. When I try to download the “Safety Camera” applet to my TomTom 540 XXL TM I get the following error message: "The internet server had an internal error. It may be a temporary problem. Please try again later."
Note the words "internal error". This clearly implies the problem is on the TomTom server and not on my PC. I strongly suspect there is an error in the installation script. I have already posted a request to TomTom support asking for a programmer to test the script on a TomTom 540 XXL to see whether the script reliably works. I should have added that the test should be across all popular OS’s.
[1] As a justification for my request to TomTom to test the install script for the safety camera applet, I am going to describe a totally mind-blowing experience which clearly indicates that TomTom's software team is not always following proper testing of application install scripts. Specifically, I found a glaringly careless error in the script that updates HOME version 2.7.3.1894 to version 2.7.5.2014, when run under Windows XP.
During installation, the script halted and said::
"Error opening file for writing: C:\Program Files\TomTom HOME2\xulrunner\nspr4.dll.
Click Retry to try again or Cancel to stop the installation".
I went and looked for this nspr4.dll file and found it existed already, and that the script writer had failed to handle this (should have either erased it or given overwrite permission).
So I erased nspr4.dll and said retry and yes, a new version of nspr4.dll was installed.
I had to do the same thing for 8 other files in the /xulrunner/ folder before the installation would complete without errors. The files in the xulrunner folder that needed to be erased or overwritten were:
nspr4.dll; nss3.dll; nssutil3.dll; plc4.dll; plds4.dll; smime3.dll; softokn3.dll; sqlite3.dll; ssl3.dll
Clearly, the script writer (or his/her supervisor) committed the cardinal sin of assuming the script would work without actually testing it. This is unbelievable carelessness and someone deserves a thorough wigging… possibly some exec who was pushing for too much too fast or skimping too much on programming resources. Maybe the script worked on one OS but not another. But my OS is XP, which is surely popular enough for testing to be mandatory.
[2] I have had another unpleasant experience that I suspect may also be the result of sloppy script writing. When I try to download the “Safety Camera” applet to my TomTom 540 XXL TM I get the following error message: "The internet server had an internal error. It may be a temporary problem. Please try again later."
Note the words "internal error". This clearly implies the problem is on the TomTom server and not on my PC. I strongly suspect there is an error in the installation script. I have already posted a request to TomTom support asking for a programmer to test the script on a TomTom 540 XXL to see whether the script reliably works. I should have added that the test should be across all popular OS’s.
Last edited: