I loaded the map on my HCT HD2 activated it and it worked fine. Then I removed it again to replace it with the downloaded Europe 900.4600 only to find out that no meta was available for this map.
I deleted that map, reloaded Europe_South, ran Fastactivate as before got no error messages and it showed the map in the log but when I try to select it in TomTom it tells me that it is not activated. What can I do?
The log:
..:: FastActivate 15.12.2012 ::..
________________________________________________________________________________

Voice(s):
Map(s):
South_Africa_Swaziland_and_Lesotho-248.meta => .dct OK!
Southern_Africa-513.meta => .dct OK!
Europe_South-667.meta => .dct OK!
Fuel prices:
Speed cameras:
________________________________________________________________________________

BIF File......R:\TTNAVIGATOR.BIF
KeyGen Type...8

Application...7918
DeviceID......XXXXX XXXXX
Press any key to continue . . .

1. Never post your DeviceID!!!
2. Once a map is patched, it never needs repatching, as long as it is used on the same device that it was patched for.
Removing & restoring it does not make any difference.
3. An attempt to repatch can cause problems with the original patch. Delete the Europe_South-667.meta.dct file & then do a clean repatch.

When i delete the Europe_South-667.meta.dct file than fastactivate does not recognise the file anymore. I copied the map from my TT GO 700 as I did the first time. I did not make a copy of my patched map (wish i had). After restoring the original Europe_South-667.meta.dct to the map fastactivate recognises the map but the end result remains the same the map does not get patched.
I replaced fastactivate with EasyDCT II and managed to get my map patched

If would have worked the first time with FA if:
a) you would have deleted the the DCT file from the copied map and
made sure the meta for the map is included in FA or in the meta.txt you can create yourself
b) if you would have followed the previous instructions in post 2.

Reason is simple: FA does not create a new new DCT file if one is already present, so if you copy the map from a different device the activation is invalid.
Depending on the release date of a map it makes sense to create a meta.txt with codes needed for the map(s) one wish to activate.

In addition to Downunder's comments, ALWAYS check for the latest version of FA. FastActivate Premium 1.8.9.0 Updated 24.12.2012 is current.

Somehow I'm misunderstanding or misreading your instructions as the results do not turn out as expected. In the end I did get the map activated with EasyDCT.
When deleting the dct file I dont see the map in FA's log so it apparently needs a dct file.

janm wrote:Somehow I'm misunderstanding or misreading your instructions as the results do not turn out as expected. In the end I did get the map activated with EasyDCT.
When deleting the dct file I dont see the map in FA's log so it apparently needs a dct file.

The Europe_South-667.meta, needed to create the Europe_South-667.meta.dct is included in the FastActivate Premium 1.8.9.0 Updated 24.12.2012 Integrated meta.txt

The Europe_South-667.meta was not the problem I created it myself. I did try to duplicate the problem with Europe_Central-667 created the meta (a copy posted in v900 maps) and activated with v24.12.2012 and could not repeat it. I deleted the map copied it again from my TT and it activated fine, no need to delete any dct files. It must have been a glitch in the 15.12.2012 version.

OK, time for a quick review.

1. All maps have a .meta file.
2. In order to use a map that wasn't purchased, the map must be patched with the patching tool of the user's choice, creating a .meta.dct file.
3. In order to create a .meta.dct file, a meta/blowfish is required. The purchaser of a map can easily create a meta/blowfish. (Europe_Central-667.meta for example, which is much appreciated!!!)
4. To actually patch a map, the user must have the map in a folder, a copy of the ttgo.bif file from the device that the map will be used in & a patcher with the meta/blowfish for the map being patched. If all of these requirements are met, the patcher will patch a map everytime without fail!!
5. Once a map is patched, it never needs repatching, as long as it is used on the same device that it was patched for. Removing & restoring it does not make any difference. A patched map can be used in another device, if it is repatched for that device.

All of the above is and was clear to me. The reason I went through this procedure was that I did not have a copy of the patched map to restore. Why it would not activate the original map (not a patched version) with FA version 15.12.2012 a second time is still not clear to me as it would be the same as loading and patching a new map. Version 24.12.2012 does not show that behaviour, having said that, I did not go back to the previous version to retry so whether it was a glitch in 15.12.2012 or something happened to the original map I dont know. With 24.12.2012 all works as expected including loading an original map again after deleting the patched version and activate it the regular way. I'm happy with that

janm wrote:All of the above is and was clear to me. The reason I went through this procedure was that I did not have a copy of the patched map to restore. Why it would not activate the original map (not a patched version) with FA version 15.12.2012 a second time is still not clear to me as it would be the same as loading and patching a new map. Version 24.12.2012 does not show that behaviour, having said that, I did not go back to the previous version to retry so whether it was a glitch in 15.12.2012 or something happened to the original map I dont know. With 24.12.2012 all works as expected including loading an original map again after deleting the patched version and activate it the regular way. I'm happy with that

Version 15.12.2012 did not have the required meta/blowfish needed to patch the map in question. Version 24.12.2012 does. The only change in new versions of FastActivate is an updated meta file.

If you re happy, then the TT Team is happy.

Happy New Year!!