balonie2 wrote:1. I did a reset, but it still gives the same error :(
I thought this would happen, because with the old map, it also said the map was patches, but it still doesnt work.
2. So now what?

1. A reset was not necessary.
2. Take a screen shot of the contents of your unit. Uploaded it somewhere & PM me the link.

Razorblatter wrote:Get your meta code in the same format as in the archive.

Formating is not a big deal. It can be like this:

; Greece v905.4754
E0 3A 26 6D CD 18 F4 D9 C6 AE 28 E0 E2 07 E9 EB Greece-710.meta

or like this:

Greece v905.4754
E0 3A 26 6D CD 18 F4 D9 C6 AE 28 E0 E2 07 E9 EB Greece-710.meta

or like this:

E0 3A 26 6D CD 18 F4 D9 C6 AE 28 E0 E2 07 E9 EB Greece-710.meta ; Greece 905_4754

or even like this:

E0 3A 26 6D CD 18 F4 D9 C6 AE 28 E0 E2 07 E9 EB Greece-710.meta

They all work.

Dear tendriver and downunder,

(Thanks for your invaluable corrections above. You are and will always be our guru's)

I just discovered that a false meta code in meta.txt (and with the correct one not being present in FA) does produce a confirming message of a created .meta.dct.
Seemingly confirming that the map has indeed been cracked !

But that's not the case if the meta code is wrong so TT gives the dreaded "can not use this map" error.

In short: Garbage in FA causes garbage out!
No problem, but good to know...
Make no mistake, the (new) FA is a wonderful tool with splendid options. Very client friendly!

So can it be that the wrong format (the missing ";") used by balonie causes the error?
Assuming that the meta code for Europe_1GB_West is correct of course.

Am i talking baloney or what ?

Check post #27 ;)

Yeah, I did.

But can you confirm that my statements #33 are correct without, please, beating about the bush?

I just never encountered it because all my meta codes from NT are always correct...

Razorblatter wrote:Dear tendriver and downunder,
So can it be that the wrong format (the missing ";") used by balonie causes the error?
Assuming that the meta code for Europe_1GB_West is correct of course.
Am i talking baloney or what ?

You are talking baloney! Also see post 32!!

Haha, but then I fail to see the relevance of downunders #27.

Razorblatter wrote:Haha, but then I fail to see the relevance of downunders #27.

That is for Downunder to answer.

It seems, tendriver, that your remarks about the format of the meta code are correct.
As far as I know now the minimal format is this:

E0 3A 26 6D CD 18 F4 D9 C6 AE 28 E0 E2 07 E9 EB Greece-710.meta

But I also found out that FA will always give a positive result and create a .meta.dct file if the meta code used is nonsense like this:

BL AH BL AH BL AH BL AH BL AH BL AH BL AH BL AH Benelux-746.meta

Of course, this will not work within TT.
That was the point I wanted to make. That FA is not discriminative for the quality of a meta code.
Might be logical for you guys, but one might pull one's hair out when you got a faulty meta code.
No baloney there !

Now, I hasten to say, normally this is no problem whatsoever if you got a self-cleaning, quality forum like NT.

To be honest, your discovery is of no real application value. We have been doing this for years. In that time, I have only seen 3 maybe 4 "fake" meta codes. All other meta code issues have been unintenional user errors. With the vast number of satnav forums, a meta code problem has a very very short lifespan. When a problem is found, it is corrected, reposted & redistributed around the system in a very short amount of time.
Bottom line: meta code problems have never been a lingering or burning issue.

Exactly !
Precisely what I have been saying!

I was only presenting it as 'my' discovery which could be an explanation for other users if FA keeps resulting in .meta.dct's on which the TT device keeps choking itself.
Because if all fails, one might be wise to double check the meta code to see if it contains more than BL AH BL AH...

Problem solved! My TomTom works again! Razorblatter helped me privately and now it works!
The solution was to do a total reinstall of the TomTom: delete every file except the maps, connect to TomTom HOME and install the updates, then insert the new map in the TomTom (map from 910 thread) and then use FA option 2 and 3 to patch the maps and NC. And now it works!
Thanks everyone for all your effort.

Yeah, did not steal him away from NT but, both being Dutch was to good for him to resist.

I don't know what was his problem but Europe_West could not be activated.
Because the NC showed some signs of some modification, I thought it best to start clean and reinstall original NC via TomTom Home.
That worked pretty painless.

Balonie2 also wanted to give a big, warm thanks to Tendriver for his assistance.
And I second that !

Razorblatter wrote:1. I don't know what was his problem but Europe_West could not be activated.
2. Because the NC showed some signs of some modification, I thought it best to start clean and reinstall original NC via TomTom Home.

1. The Europe_West map was activated.
2.Doing it this way left balonie2 with a 8.XXX navcore & old icons. The TT team strives to take our members to a higher level on their older 32MB units.

Granted, I do agree with you.

However:
- although a .meta.dct was created the TT did not accept the map even though the map appeared to be patched. This was causing stress and a feeling of extreme disorientation, demotivation and distress within the subject.
- the device was intended for use on shortest term for Australian guests in the Netherland so I though it best to keep it a clean and straightforward as possible.
- I did inform him about (especially) Downunder's modded NC's
- Due to TT One 3rd Ed.'s limited storage of 1GB, one has little option in maps. Only 910_4852 for Europe regions.

The subject balonie2 appeared happy and content when he got a gps fix on this new map and I left him alone wishing him and his parent's guest happy days.
I'm sure he will have a good memory of NT and will know where to return for further options.