Results 21 to 30 of 44
-
9th March 2019, 02:22 AM #21
Certainly nothing from TT as they've basically dumped/EoL'd all these older devices but maybe someone will come up with an SE version of this 9541 for 32 MB units?
Possibly for now, after a full windows backup, try the LE version direct from here or an EE Simba version from here and see following posts after that too
AND, please remember to report back once done or dumped!
SPAM HUNTER/KILLER
Please do not just post "thanks" but use the "thanks" button bottom/right or the reputation star "*" bottom/leftS i m p l e s
-
9th March 2019, 02:01 PM #22
The EE Simba version works great on the TT One v3.
I only removed the start/shotdown screens and media.
-
The Following 1 Users Say Thank You to Jorre2220 For This Useful Post:
- [ Click To Expand ]
-
biggerdave (9th March 2019)
-
10th March 2019, 03:36 AM #23TomTom Expert
there is and you get it from the tomtom site directly. just becareful that you have saved all your stuff first though. since it affects nav core, me careful you still use an update here to make sure it is not blocked. fastactivate will sort that out, as I just askes the ones that know. Newer versions, less than 10 or so years old will not be affected. your smart phones will not be affected either. It is a lot like the milleniem bug really. the better manufactures know this in advance, and the poor crappy ones have not.... need I say more really?
One day, someone might make things work perfectly before release. Sadly not in my or your lifetime. At least by finding problems and sorting them, we are still alive.
-
10th March 2019, 04:01 AM #24TomTom Expert
A long time ago, before many of you were even borm or thought about I was coding in COBAL and I was told to use YYYY in any dates used. I know many were not, but with mellenium, those poor coders using YY just would have problems, just as a few of us know time was only 4 digits for time . hence 9999 on April 6th. smart ones use 09999 etc. not hard, but I met they did not think that years ago. Hence the problem. it is binary. 9999 is 10011100001111. 10000 is 10011100010000 that is one digit too large for a computer date (not going to explain why) as I know your maths does not matter (why should it?)
That is the reason for April 6th problem. All you need to know is most will be fine and old stuff, will need an update maymbe.... We can or TT will do for you. Basically, do not worry. As Dave and many others know, I am or was a senior coder in maths. not bragging, but I told them about the error in the light and other going faster error. think 28m earth moves in the time. simple. blame a cable connection if you want too, but how you justify that? quess what my email return was?One day, someone might make things work perfectly before release. Sadly not in my or your lifetime. At least by finding problems and sorting them, we are still alive.
-
10th March 2019, 05:07 PM #25Tomtom Master
Supporter
I'll believe it when it happens.
I'll never forget some years ago the first time I left my TomTom at home and used my Phone.
TomTom tried to get me to miss my plane and get fined for crossing the Dartford Crossing at the wrong time.
The TomTom 1.4 app does not respect daylight saving time.
In practice that means in summer as you arrive at your destination TomTom tells you you are arriving an hour ago.
Great for "Tardis" owners everywhere.
-
14th March 2019, 03:02 PM #26
Navcore problemen na April 2019
Geacht forum,
Dear Mira,
I don't know if you've noticed, but this is a forum that uses English as the main language by default
Above the website that indicates that problems will arise in April 2019 with older TomTom systems (read this site firsta.u.b.). I myself have a Medion 350 with a Navcore7.910 version (patched) that works excellently because I always provide my system with the current maps. As you may have read, TomTom says that you have to update the system, but the Navcore7.9xx and 8.xxx versions do not provide them as an update and in addition, my Navcore with FastActivate patched and cannot be linked to the TomTom site for an update. My question now is whether anyone is at the Forum with sufficient know-how to solve this problem and possibly "automate" the solution through an extension with an additional function in the software toolFastActivate. Basically it is about resetting the correct memory cell somewhere in the Navcore application.
Thank you for thinking along.
mira
No hard feelings and have a very nice day also on behalf of the crewLast edited by pe1agp; 14th March 2019 at 03:22 PM. Reason: Wrong language
-
14th March 2019, 03:26 PM #27
To answer your question if someone with sufficient knowledge is present, I can answer you with a simple YES.
But first, let's wait and see what will really happen after April 6, if it goes like this with the millenium bug, then we can just continue racing after our TomTom.
-
25th March 2019, 04:12 AM #28
Talking to someone who knows a lot more than me about GPS and this "possible" problem... and he tells me that what TT are saying is probably a load of rubbish !!
Apparently the end of the epoch Week Number Rollover is exactly what it says ... it is a WEEK NUMBER rollover ... so the only devices that are affected are those that use/calculate "weeks" and utilise the "week number" index !!
As most SatNavs don't even use even date/day information but simply use "time" then they will NOT be affected !!
He sent me to this site to show me that he wasn't talking rubbish, and sure enough, down the bottom is this little crumb of information ..
"This situation won’t affect a receiver’s ability to navigate and/or calculate precise time, but it has the potential to create week, month and year timestamps that are wildly wrong. Applications which rely on GPS data at that level may be seriously affected."
I have a strong feeling that April 6th will be a "non-event" for my GO700
-
The Following 4 Users Say Thank You to Entwood For This Useful Post:
- [ Click To Expand ]
-
Alfred_ML (27th March 2019), biggerdave (25th March 2019), iannic52 (26th March 2019), pe1agp (25th March 2019)
-
3rd April 2019, 05:56 AM #29
I received an email from TomTom stating my XXL540 9.510 YOUR SATNAV’S STATUS
After 6 April 2019, your satnav will continue to navigate, but will not be able to show the correct time and the estimated time of arrival. Fortunately, this is easily fixed with an update we have ready for you below.
As far as I'm aware it's 2014 model and has not received an update from TomTom since 2015-16 I don't think the serial number matches any more!
HELP... what should I do
-
3rd April 2019, 10:56 AM #30
-
The Following 1 Users Say Thank You to pe1agp For This Useful Post:
- [ Click To Expand ]
-
biggerdave (3rd April 2019)
2023.Q2 Here Australia,New Zealand
Australia New_Zealand HERE 2024.Q2 please