Hello,

I have read almost my eyes out on this, and tried loading over 10 navcore 9 versions on my device, but got only one working. And that one seems more like navcore 8 then 9 to me.

My device: a TomTom One XL (first generation) with SD Card.
I have the latest maps (Benelux 880.3856) working on this navcore SE_Navcore.9.160.567967_32mb_devices.

But The GUI seems exactly the same as with navcore 8 ?
This is my info:
SE 8.417.1255 x30
App 9.160.567967.2 OS 563271 (5006, 24-8-2010)
32MB RAM (available 4.2 MB)
GPS v1.20 Boot 5.5250

Someone an idea ?

All the other navcores (extracted over a working navcore 8 installation) give me a device that hangs after boot at hte TomTom logo.
Tried:
SE_Navcore.9.205.547817_32mb_devices
X_Navcore.9.205.547817.1.Basicpack with X_ttsystem.9.205.547817.1
9.205.rider3.CAB-navcore-RIDER with X_ttsystem.9.205.547817.1
...
And Fastactivate as well as autoactivate (thanks you guys !)

I would be very thankful

Wimme

The Xl always is a bit tricky and stubborn when it comes to using new Navcores.
A V9 Navcore does not really give a benefit over the "old" V8 except for the 3 pane status bar and that you can use maps with the HNR feature.
I know it gets frustrating after a while if you can't get anything to work, but unfortunately that is what happens often on a XL.
I suggest two solutions:
1. if you don't really need a V9 Navcore, stick with the good working V8 ones
2. if you do need a V9 Navcore, make it a bit easier for you and use the DSA tool to install and try different NC versions. The tool downloads the NC diretly from TT and patches it for your device.
With a V8 Navcore you could be able use the "MB" (memory boost) option which can result in over 10mb of free ram on a 32mb device - but only works with a V8 NC.

wimmme wrote:All the other navcores (extracted over a working navcore 8 installation) give me a device that hangs after boot at hte TomTom logo.
Tried:
SE_Navcore.9.205.547817_32mb_devices
X_Navcore.9.205.547817.1.Basicpack with X_ttsystem.9.205.547817.1
9.205.rider3.CAB-navcore-RIDER with X_ttsystem.9.205.547817.1
...

We have had many users successfully load 9.205 on their ONE XL, using the .CAB, X_ttsystem.9.205.547817.1 & setconfig.txt configed for emu 40 or emu 50.

Downunder35m wrote:The Xl always is a bit tricky and stubborn when it comes to using new Navcores.
A V9 Navcore does not really give a benefit over the "old" V8 except for the 3 pane status bar and that you can use maps with the HNR feature.
I know it gets frustrating after a while if you can't get anything to work, but unfortunately that is what happens often on a XL.
I suggest two solutions:
1. if you don't really need a V9 Navcore, stick with the good working V8 ones
2. if you do need a V9 Navcore, make it a bit easier for you and use the DSA tool to install and try different NC versions. The tool downloads the NC diretly from TT and patches it for your device.
With a V8 Navcore you could be able use the "MB" (memory boost) option which can result in over 10mb of free ram on a 32mb device - but only works with a V8 NC.

It was for the statusbar and the smoother lines that I want the NC9. I will try the DSA tool anyway, I Like tools

tendriver wrote:We have had many users successfully load 9.205 on their ONE XL, using the .CAB, X_ttsystem.9.205.547817.1 & setconfig.txt configed for emu 40 or emu 50.

I did not use nor touch setconfig.txt, maybe that can do the trick for me ? Will try this evening, need my Tomtom to be functional for a drive within an hour.



Thanks for the repsonses anyway. I will update this thread later !

If you don't use the config files on device like yours than it explains why you had so much trouble ;)
I suggest you check the tutorials for the switchfiles and if the DSA tool can't offer what you want or you want to do it easy try Tendrivers suggestion.

Downunder35m wrote:If you don't use the config files on device like yours than it explains why you had so much trouble
I suggest you check the tutorials for the switchfiles and if the DSA tool can't offer what you want or you want to do it easy try Tendrivers suggestion.

Config files, switchfiles etc are not needed on a ONE XL & 9.205. Just the .CAB (overwriting the current navcore), X_ttsystem.9.205.547817.1 & setconfig.txt configed for emu 40 or emu 50.

tendriver wrote:Config files, switchfiles etc are not needed on a ONE XL & 9.205. Just the .CAB (overwriting the current navcore), X_ttsystem.9.205.547817.1 & setconfig.txt configed for emu 40 or emu 50.

Will try that this evening for sure !

the setconfig was what did it. there I found also the changedtext (SE 8.417.1255 x30) which got me on the wrong track ...
Thanx all you guys !!!

wimmme wrote:the setconfig was what did it. there I found also the changedtext (SE 8.417.1255 x30) which got me on the wrong track ...
Thanx all you guys !!!

Congrats. The TT Team sez, "You are Welcome". Enjoy.

@ Tendriver: Thanks for clearing the switchfile thing, but I was under the impression that the setconfig.txt is in fact a part of the switchfiles as outlined by TTUSER in his original SE -Navcores.
To my knowledge the switchfiles are the term for all files modifying the emulations and appearence inside the the config folder (or the root as it makes no difference).

Downunder35m wrote:@ Tendriver: Thanks for clearing the switchfile thing, but
1. I was under the impression that the setconfig.txt is in fact a part of the switchfiles as outlined by TTUSER in his original SE -Navcores.
2. To my knowledge the switchfiles are the term for all files modifying the emulations and appearence inside the the config folder (or the root as it makes no difference).

1. You are correct. setconfig.txt is in fact a part of the switchfiles, but in this case, it is being used as a standalone file.
2. You are again correct. switchfiles is the term for all files modifying the emulations and appearence inside the config folder. In this case we are only using 1 file & no folder.
The same results could have been achieved, if wimmme had been instructed to use a model.txt file to set emu 40 or 50.