Posted: Sun Sep 12, 2010 1:18 am Post subject: Operate my GO error "calling method on NPObject!"
Hello all. I haven't been on here for a while (the Tomtom has been working!). I now have a problem and I apologise if it has been dealt with elsewhere on the forum - I did a search and couldn't find anything relevant.
A week ago I was offered an update of Tomtom Home to 2.7.6.2056 (not sure what it was before but it was the previous version). I was also offered a map update from Australia 845.2661 to 855.2884. I then tried to use "operate my GO" from Home and got the message "Error calling method on NPObject!". Here is the full error:
Code:
ERROR: Error: Error calling method on NPObject!
in chrome://tthome/content/ui/subtask/emulator/emulatorPage.js:232
Stack:
0. function startup_navigator("M62357B05413","8-351-9982-1.dll","22","Latin-1","H:") unknown
1. function () chrome://tthome/content/ui/subtask/emulator/emulatorPage.js:232
dataFolder);
2. function ([object XML]) chrome://tthome/content/ui/subtask/emulator/emulatorPage.js:148
this.initEmulator();
3. function ([object XML]) chrome://tthome/content/logic/util.js:79
return func.apply(obj, arguments);
4. function () chrome://tthome/content/logic/comm.js:442
this.successCallback(this.resultXML);
5. function (true) chrome://tthome/content/logic/comm.js:430
this._doneCallbacks();
6. function ([object ProgressEvent]) chrome://tthome/content/logic/comm.js:277
this.request.onload = function() { me._done(true); }
Time: Sun, 12 Sep 2010 00:10:34 GMT
While my immediate assumption was that it was caused by the updates, I am now less sure. I had not used "Operate my GO" for a week or so previously. Indeed, I've tried reverting to an earlier version of Home (2.6) and the previous map, and got the same.
All this is on a laptop running XP, which I wish to continue using as the machine on which I manage the Tomtom. I do have access to another machine running Win 7 which has not previously had Home installed on it. I installed Home on that and found that "Operate my GO" worked normally on that machine.
I logged a support job with Tomtom and they suggested a couple of fairly generic processes (deleting the Tomtom directory in "My Documents", and when that did not work, a much lengthier one involving deleting and reloading the Tomtom application on the device, which did not work either). Now they are just saying "something wrong with your computer, not our problem".
Searching the web for references to this error show that it is not limited to Tomtom - it seems to come up in the context of Java or Javascript (that might be evident from the error message but I am not an expert).
I would be very grateful for any suggestions.
edit: I should have said that I have downloaded and installed the current version of Java.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
