solved - no error [TC 11.03] Possible misconception in TC help for wincmd.ini

[petermad]

In The Help for wincmd.ini parameters I see:

SizeStyle1000=0 0: Use binary units: 1k=1024bytes, 1M=1024k, 1G=1024M, 1T=1024G
1: Use decimal units: 1k=1000bytes, 1M=1000k, 1G=1000M, 1T=1000G
Note: Doesn't affect "Properties" dialog, which is part of Windows and always uses binary units.

The statement about Windows properties using binary units seems to be wrong - it is only after setting SizeStyle1000=1 that TC and Windows shows approximately the same sizes (for example total space on the disk).

[ghisler(Author)]

I cannot confirm that. When I press Alt+Enter on a file with, say, 9645 bytes, then
- Total Commander shows 9.41 k
- Alt+Enter shows: 9.41 KB (9'645 Bytes)
This is on Windows 11, and as you can see, the Properties dialog (Alt+Enter) clearly uses binary 1024 multipliers.

[petermad]

2ghisler(Author)

Yes - I was thinking of drive space - try and right-click on the C: button in the drive button bar and choose "Properties" - you will see numbers that are pretty far from the values in TC's "Free space on drive" bar. If you then set SizeStyle1000=1 then the numbers will be much closer to each other

[tuska]

Hi,
That's what I see here:

Code: Select all

Difference/Bytes     ADMINISTRATOR + HS files*	Available Free Disk Size (330 GB) - drive C:
---------------------------------------------------------------------------------------------------
         225 280     with    SizeStyle1000=1	Total Commander shows LESS free space than Explorer
	 376 832     without SizeStyle1000=1	Total Commander shows MORE free space than Explorer
       2 666 496     with    SizeStyle1000=1	Total Commander shows LESS free space than Explorer
	  20 480     without SizeStyle1000=1	Total Commander shows MORE free space than Explorer

Code: Select all

Difference/Bytes     USER + HS files*		Available Free Disk Size (330 GB) - drive C:
---------------------------------------------------------------------------------------------------
          65 536     with    SizeStyle1000=1	Total Commander shows MORE free space than Explorer
	   4 096     without SizeStyle1000=1	Total Commander shows MORE free space than Explorer

Code: Select all

________________________
*  ✅ Show hidden files
   ✅ Show system files

Pictures:
2024-09-05_wincmd.ini - SizeStyle1000 - 1_83687_ADMIN.png
2024-09-05_wincmd.ini - SizeStyle1000 - 1_83687_USER_without Admin.pngt

The values for drive C: have changed continuously (even with the Internet switched off).
For this reason, I have endeavoured to make the hard copies as quickly as possible.
That was certainly one of the reasons why, in my view, there were minor differences.

With a total ‘free memory’ of 330 GB, these differences between Total Commander and
Windows Explorer are negligible for me and I stick to the default setting, i.e.
NO entry in wincmd.ini [Configuration] of SizeStyle1000=1

---

Windows 11 Pro (x64) Version 23H2 (OS Build 22631.4112) | TC 11.03 x64

[ghisler(Author)]

I cannot reproduce that. What size format do you use for headers/footers (Configuration - Options - Tabstops/Data Formats?

[tuska]

I cannot reproduce that. What size format do you use for headers/footers (Configuration - Options - Tabstops/Data Formats?

I'm not sure if you are referring to me.

I have the following settings:
- Header/footer: bytes
- Size display:  bytes

[petermad]

What size format do you use for headers/footers (Configuration - Options - Tabstops/Data Formats?

If you are asking me: kbytes

See:
https://tcmd.madsenworld.dk/SizeStyle1000=0.png
https://tcmd.madsenworld.dk/SizeStyle1000=1.png

This is on Windows 10, and can also be reproduced with a fresh ini-file.

There is almost a 12 Gb difference (out of 490 Gb) between the Capacity reported by Windows and TC when using SizeStyle1000=0

If I set SizeStyle1000=1 and SizeFooter=1 I get exactly the same disk capacity in TC as in Windows properties.

[Dalai]

2petermad
I don't see a problem here and certainly no missing gigabytes. Your picture with SizeStyle1000=0 shows 478,869,764 KiB - that's Kibibytes. Multiplying that number with 1024 gets bytes, and the resulting number matches the number shown in the Windows properties window exactly (490,362,638,336 bytes).

With SizeStyle1000=1 the number of bytes is divided by 1000 to get KB (no Kibibytes in this case). The 490,362,638,336 from Windows properties dialog divided by 1000 is 490,362,638 which TC shows. Note that the number in TC is three digits shorter because the unit is KB instead of bytes.

[tuska]

Unit Converter (German) -> Byte (B): 490362638336 <enter>

[petermad]

[/mod]2Dalai

You are right , I was erroneously comparing TC's header set to kbytes with Windows' properties bytes - when I set TC to show x.k/M/G and use SizeStyle1000=0 I get the same size in G as the GB shown in Windows' properties.

Moderator message from: petermad » 2024-09-07, 12:08 UTC

Moved to "Total Commander (English)" from "TC11.x bug reports (English)"