New packer API wrong file size display

[TrePe]

EDIT: This has been reported before and Mr. Ghisler had in plan to fix it (I do not understand German very well, though...) http://www.ghisler.ch/board/viewtopic.php?p=60568#60568
Maybe it is time for TC 7 to correct it?

Hi. I am in the process of modifying DiskDirExtended to support > 4GB files.

I found strange behaviour of TC when the plugin's reported file size (using UnpSize and UnpSizeHigh of tHeaderDataEx) is:
4294967295 (0xFFFF FFFF) the file size is displayed as [face=courier]?[/face]
4294967294 (0xFFFF FFFE) the file size is not displayed at all

For all other file sizes (that I tried, not for all 2^64 possibilities ) it works correctly, i.e. the displayed file size is correct. It works even for
4294967293 (0xFFFF FFFD)
4294967296 (0x1 0000 0000)
8589934591 (0x1 FFFF FFFF)

To be fair, the two mentioned file sizes (4294967295 and 4294967294) are displaying the same (i.e. wrong) even in TC 6.55.

[ghisler(Author)]

Indeed these two numbers are used to encode unknown size (?) and empty size field. It's planned to use two high 64 bit numbers for that instead, but not all parts of TC are 64-bit enabled yet, so it will take time...

[ghisler(Author)]

This should be fixed now. The unknown size should now be encoded by FFFF FFFF in BOTH upper and lower 32-bit variables. Please check that! I had to make a lot of changes to make this work, so you may get wrong display in some cases. Please let me know if you encounter such a case!

[ghisler(Author)]

BUMP - Anyone can confirm that, please?

[Flint]

I checked it with DiskDir Extended 1.55, displaying is now correct (as well as in TC itself, as I wrote here). But there is another problem, and I'm not sure if this is DiskDir or TC that has the bug... Reported here.

[ghisler(Author)]

Great, thanks!