When TC7 release ?

[sas2000]

 
2sqa_wizard

Ok, thx for the explanation.
  

[sqa_wizard]

De nada

[karlchen]

In the German forum a severe problem was reported which may lead to the loss of (random) folders on the drive to which %temp% points.

This problem may occur under a very specific set of conditions:

+ if you unpack a RAR archive which holds a folder structure and
+ if unpacking is done using external (WIN)RAR and

Translating - Christian's message:

"+ if you re-archive such a (Win)RAR archive into another archive directly (simply unpacking is not enough) and
+ if you are inside a subfolder stored in the RAR archive and
+ if you mark 1 or more subfolders in the current subfolder for re-packing
+ if the marked subfolders themselves do not have subfolders

If all of the above listed conditions are met the error will occur"
(translation done to the best of my knowledge, not absolutely literally)


What causes the error? And which damage may be done?

Again translating another message by Christian:
"When the batchfile is built which is used to unpack the marked subfolders the contents of the %TEMP% variable may be changed. In the worst case, only the drive letter is left. TC unpacks the files to a subfolder of %TEMP% and repacks them to a new archive and finally deletes the temporary subfolders. As a consequence of the incorrectly modified %TEMP% variable, some random folders may be deleted instead of the temporary folders."
(translation done to the best of my knowledge, as best as I could)


So the message should be:
Do not try to reproduce the error deliberately.
Wherever possible use the T.C. internal RAR unpacker.
Do not re-pack RAR-archives into another archive directly using T.C. and external (Win)RAR until Christian has fixed the bug.

But do not panic either. Very specific conditions must be met to get struck by the bug (see above). - It can happen, though. -

Karl

[frenky]

2karlchen
Thanks for the translation!

[ghisler(Author)]

Correct - I issued no warning because the danger is much higher if someone tries to reproduce this bug (although told not to do so!) than hitting it by accident. A warning will be sent out with the release of TC 6.56.

[karlchen]

Good evening, Christian.

v6.56 has been released, file dates 01-01-2007, hm...

TC7 users should be careful until pb3 fixes the bug for them, too, I assume

Cheers,
Karl

[ghisler(Author)]

v6.56 has been released, file dates 01-01-2007, hm...

The program has been available to beta testers since then, therefore the delay.

TC7 users should be careful until pb3 fixes the bug for them, too, I assume

Correct. PB3 is planned for next week.

[karlchen]

Thanks for the fix and thanks for the explanation.

If I had taken the time to read your announcement of TC 6.56 completely I might have known without asking.

Karl

[karlchen]

Hi,

as you all know TC6.56 fixed the bug.
As Christian explicitly confirmed here, the bug has been fixed in TC7pb3, too.

So now we can all sleep well again.

Karl