[Bug?] Internal RAR unpacker does not detect corruption.

[Flint]

In some rear cases there is a situation possible, when a corrupted archive file is not detected by TC as corrupted: it is shown just as empty archive, unpacking gives no effect, test archive function shows no errors. But WinRAR can find errors in this archive and reports that the archive is incorrect.

Here are the links to the example original and modified archive (the original one was just opened in Notepad and some part of code was cut):
Original archive
Corrupted archive

I think, TC should report about even such incorrections, else user may think that the archive is really empty and remove it, while the archive could be repairable it and the user could save some data from it.

[ghisler(Author)]

This can happen if a file header contains data which TC doesn't understand. Such headers are skipped because they may contain data for newer versions of RAR.

[Flint]

ghisler(Author)
Hm... So, maybe, it's better to show some message box, that the header cannot be recognized? So that user could distinguish such archives from the usual empty archives.

[Clo]

2Flint
Hello
- Odd, I've the usual error message "Error in the packed file…" for your two samples… ???
• Both have exactly the same size = 4250 bytes
• I dowloaded them alright from the links you give above.
Under Win 98 SE.

Kind regards,
Claude
Clo

[Flint]

Clo
This is strange, I've just tried to download them both - and got the same files that I uploaded. The original archive - 2829 bytes, the corrupted one - 1591 bytes.
I packed both archive files into one archive and placed it on the webfile.ru service, please, try to download it from there: http://webfile.ru/276062

[Clo]

2Flint
This works like you told with the new samples !
- So, I can confirm now : I did NOT get any error message for the corrupted RAR, and nothing more occured…
- The "Original" archive is unpacked normally…

 Kind regards,
Claude
Clo

[Flint]

2 Christian:
So, what about implementing such message box? In TC 6.53 there are still no messages in such cases...