Total Commander

Hallo
I found interesting anomaly.

Screenshot are capped from TC 11.01 but same anomaly/bug hapend at 11.03

See screenshots of disk size:
If i use dynamic x.xx k/M/G/T, disk have more free space then showed disk capacity.
https://ibb.co/wzShbCT

If i use dynamic x.xx k/M/G is everhyting OK
https://ibb.co/Wzmnf2Y

Its no problem, only cosmetic anomaly, but seems weird to have more free space then disk actually have showed in TC in first settings x.xx k/M/G/T.

Thanks

Did you set "SizeStyle1000=1" under [Configuration] section?
If not then everything is OK - binary 0.9 TB > 906 GB
NO BUG.

Not a bug. 931 GB = 931/1024 TB=0.909 TB, truncated to 0.90 TB.

truncated to 0.90 TB.

why not mathematically converted to 0.91Tb?

ghisler(Author) wrote: 2024-10-11, 09:54 UTC Not a bug. 931 GB = 931/1024 TB=0.909 TB, truncated to 0.90 TB.

I was thinking about the numbers, thei are rounded off and shortened or something like that.
Thanks for explenation
But seems wierd if free space is biger then actual disk size.
I have startet using x.xx k/M/G only

Gral wrote: 2024-10-11, 00:48 UTC Did you set "SizeStyle1000=1" under [Configuration] section?
If not then everything is OK - binary 0.9 TB > 906 GB

No i didt set this in config.
Thanks for tip

Can be closed

TB=0.909 TB, truncated to 0.90 TB.

As AntonyD also says - why truncating instead of rounding?

Because MS do truncate.
To be more serious, you should never show more free space than it's really available. Otherwise you will get annoiyng copy errors.

petermad wrote: 2024-10-11, 20:49 UTC why truncating instead of rounding?

(or->of: misspelling corrected)

Usher wrote: 2024-10-11, 21:51 UTC To be more serious, you should never show more free space than it's really available.

That's it.

why not mathematically converted to 0.91Tb?

I will consider it.

Moderator message