Can someone please help, I have just downloaded australian Map 830.2352 to my ONE XL, what navecore should i be using, have installed 8.413.1237 but it does not like this Map ????

Thank you

Can someone please help, I have just downloaded australian Map 830.2352 to my ONE XL, what navecore should i be using, have installed 8.413.1237 but it does not like this Map ????

Thank you

"but it does not like this this map" is a poor description of your problem.

Can someone please help, I have just downloaded australian Map 830.2352 to my ONE XL, what navecore should i be using, have installed 8.413.1237 but it does not like this Map ????

Thank you

Did you use TTusers SE version? http://www.ipmart-forum.com/showthread.php?t=352844

There are some dumps of this around that may help.

Thanks for the reply BiggerDave, yes I am using the SE version and all works well on map 815.2059 but when I change maps to Australia_830_2352 tomtom says cannot use this map on this device :Australia-61 ????

Thanks for the reply BiggerDave, yes I am using the SE version and all works well on map 815.2059 but when I change maps to Australia_830_2352 tomtom says cannot use this map on this device :Australia-61 ????

Sounds like a map patching problem.

Thanks Tendriver, Map patching, how do I fix that ????

You fix by reading about how to use the keygen

Thanks Everyone, keygen work fine, Excellent

Thanks Tendriver, Map patching, how do I fix that ????

Download Ben's tool from this post:

http://www.ipmart-forum.com/showpost.php?p=2578233&postcount=1

Run "Map v8 KeyGen".

You need to download TTUsers Easytool keygen. This will have the latest meta.txt included so you can patch the map.

How you do that is easy. With the new map copied to your TomTom, it connected to your PC and Easytools installed on your PC, go to whatever folder you installed Easytools in and double click RunMeforDCT.cmd, select option 1 in the first menu and then option 2 in the second menu. Now choose the drive letter that was assigned to your TomTom when you plugged it in.

TTusers program will now have patched your map.

Mike

You need to download TTUsers Easytool keygen. This will have the latest meta.txt included so you can patch the map.

How you do that is easy. With the new map copied to your TomTom, it connected to your PC and Easytools installed on your PC, go to whatever folder you installed Easytools in and double click RunMeforDCT.cmd, select option 1 in the first menu and then option 2 in the second menu. Now choose the drive letter that was assigned to your TomTom when you plugged it in.

TTusers program will now have patched your map.

Mike

TTUser's Easytool is a dinosaur, compared to the newer tools available.

TTUser's Easytool is a dinosaur, compared to the newer tools available.

Just like a crocodile: you will loose each and every time.
I personally like the MS-DOS CLI tools: they do what needs to be done,
nothing less, nothing more.

i got the same error as mentioned earlier, map not recognised. i might just put this question to the keygen thread, but i figure its the same problem.

originally, i used ben's keygen 2009 2.1A with the meta, but now switched to 2.1B with the online updater.

keygen creates the map DCT part with no problems. it patches tthome, when patching the navcore, it says "Navcore ttsystem Problem... You need a genuine non patched file"

what files do i need to replace from the backup to have a 'genuine' navcore, that it can patch ??

(it occurs to me that i might need to change the original navcore to the SE v8.413.1237 version to run the v830 maps, i'll go through that tomorrow and see how that works.)

TTUser's Easytool is a dinosaur, compared to the newer tools available.

no friend

ttuser' easytool is the best
usefull and if you have a new meta.txt it will patch all maps. problemless.
proffesionals uses always it.. no colorised screen no icons no mouse but it works!!!!!!!. all i need
i tried all other patchers but allways problem problem problem....

thanks to ttuser for alll

SE worked ok. but i had some audio glitch in the middle of a bluetooth call, which stopped all the audio functions entirely until i rebooted, so, i restored back to v830, and instead of using the keygen, used the easytool & yDG patch, which also got the emulation working as well.

not sure why the 2.1B keygen didn't pick it up, and, i'll use easytool next map update, it just has more transparency as to what its doing.

thinking about the original problem, i think i might have updated my tomtom navcore via home a while back and not noticed it, since i used my original maps for the mapshare content, i never consciously noticed the update since it didn't complain about the maps.

duh.