Does Ctrl-L use Everything?

[Hacker]

petermad,

The difference could be due to caching.

Yes, however, there is still the question of the 6 minutes using TC 64-bit. Perhaps an antivirus program.

Roman

[tuska]

tuska,

the shortcut ALT+ENTER is already taken for "Show property sheet."

I guess that was the point - to use Alt-Enter instead of Ctrl-L if one does not want to use Everything for space calculation.

Good guess
(the General tab of that property sheet shows for a folder: Size, Size on disk, Number of folders, Number of files )

Ahh, thanks for that.

[Hacker]

TesterTC has uploaded four comparison videos:

FreeCommanderXE.wmv - 0:04
DoubleCommander1.0.0.wmv - 0:03
TotalCommander64bit.wmv - 6:54 (sped up 2x on video)
TotalCommander32bit.wmv - 0:58

According to TesterTC, antivirus was disabled and the times are reproducible several times in a row, so no caching involved or it does not change the outcome.

Roman

[petermad]

I suggest that TesterTC tries TC x64 with a clean ini file.

[Hacker]

petermad,
Indeed, I should have suggested that as the first troubleshooting step

Thanks
Roman

[NotNull]

tuska,

I would like to keep CTRL+L in its current form (TC method).

What is the advantage?

- The required space on the destination drive is also displayed

Don't rely too heavily on Total Commander for this, as TC reports wrong sizes for small files.

Normally there is some extra room per file in the MFT (Windows' file "address book" ) and smaller files ( typical <800 bytes) are stored there (in the MFT) if there is room left and don't occupy a cluster on disk. Win10 reports the correct size-on-disk (use Alt-Enter )

[Usher]

2NotNull
Do you know that zero byte file can occupy a cluster on disk?

[petermad]

Don't rely too heavily on Total Commander for this, as TC reports wrong sizes for small files.

Not really, but you have to make sure that the settings for showing hidden and system files is the same in TC and Explorer, and you have to disable TC's ignore list, because files that matches the list are not calculated by TC.

If I do that, I get the same results - here for my entire TC-directory. including subdirectories: https://madsenworld.dk/tcmd/usedspace.png

[NotNull]

Not really, but you have to make sure that the settings for showing hidden and system files is the same in TC and Explorer, and you have to disable TC's ignore list, because files that matches the list are not calculated by TC.

An experiment:
- Create HELLO.txt with content "Hi!" on your C: drive.
- In TC, press CTRL-L on this file.
- In TC, press ALT-ENTER on this file.

2NotNull
Do you know that zero byte file can occupy a cluster on disk?

No, I didn't know that! Under what conditions?
(or do you mean through a named datastream?)

[petermad]

An experiment:
- Create HELLO.txt with content "Hi!" on your C: drive.
- In TC, press CTRL-L on this file.
- In TC, press ALT-ENTER on this file.

The result depends of under which OS you do it:
Under Windows XP: https://madsenworld.dk/tcmd/usedspace5.png
Under Windows 7: https://madsenworld.dk/tcmd/usedspace2.png
Under Windows 8.1: https://madsenworld.dk/tcmd/usedspace4.png
Under Windows 10 1909: https://madsenworld.dk/tcmd/usedspace3.png

As you can see Windows 10 and 8.1 obviously shows the wrong value for used diskspace - since a 3 byte file cannot occupy only 0 bytes of the harddisk,

[NotNull]

As you can see Windows 10 and 8.1 obviously shows the wrong value for used diskspace - since a 3 byte file cannot occupy only 0 bytes of the harddisk,

Please re-read my original message:

Don't rely too heavily on Total Commander for this, as TC reports wrong sizes for small files.

Normally there is some extra room per file in the MFT (Windows' file "address book" ) and smaller files ( typical <800 bytes) are stored there (in the MFT) if there is room left and don't occupy a cluster on disk. Win10 reports the correct size-on-disk (use Alt-Enter )

[petermad]

smaller files ( typical <800 bytes) are stored there (in the MFT)

You got a point there. I just tested under Windows 10 on a FAT partition and here Windows reports a whole cluster (32768 bytes) used for the HELLO.txt file.

[Hacker]

TesterTC tested using a fresh .ini, after 4:40 only 1 GB was counted and he gave up.
Perhaps of note is that the counting wasn't interruptible by Escape and he had to kill the TC process.
Video here.

Perhaps create a Process Monitor log?

Roman

[Usher]

The result depends of under which OS you do it:

Wrong. The result depends on filesystem.

[Usher]

2NotNull
Do you know that zero byte file can occupy a cluster on disk?

No, I didn't know that! Under what conditions?
(or do you mean through a named datastream?)

Use the Force of NTFS compression, Luke!
MS never fixed filesystem drivers to not compress small files (or files already compressed).