[9.50] FAT32 message for 4Gb+ files not displayed with custom copy methods

[Flint]

Tested in 9.50β10 32- and 64-bit.

1. Go to Settings - Copy/Delete, untick the "Use standard copy method" checkbox. (Optionally, you can switch to "Also use big file copy mode".)
2. Try to copy a file >4 Gb to a FAT32 drive.
3. Instead of showing the new message about being unable to copy such large files, TC starts copying, and when 4 Gb is reached, it displayes the gold old "Disk is full".

In standard copy mode the new message is displayed, and copying does not even start, which is the correct behavior.

[ghisler(Author)]

This is intentional and will not be changed. Why? There is no reliable way to determine whether a drive supports files >4GB or not. Some Linux network drives report themselves as FAT32, some as NTFS, although they are neither and may or may not support files >4GB. When using the default copy method, CopyFileEx will fail immediately if the file is too big for the file system. This doesn't happen when copying with ReaFile/WriteFile.

[Flint]

Why not allocate space first, and copy data later? Then it would fail early.
Actually, I thought TC already did that. Or was it just the CopyFileEx behavior? It's worth adding to other modes, because it also helps to keep fragmentation at lower level when copying many things in parallel.

[Usher]

Maybe add user defined list for drives always using standard copy method?

[ghisler(Author)]

Why not allocate space first, and copy data later?

I already do this. But it's not a reliable way to determine that the drive cannot hold the entire file: The user may delete large files while copying the new file.

Maybe add user defined list for drives always using standard copy method?

Just for a changed error message? That would be overkill, sorry.

[DrShark]

There is no reliable way to determine whether a drive supports files >4GB or not. Some Linux network drives report themselves as FAT32, some as NTFS, although they are neither and may or may not support files >4GB.

Even if such info is not reliable, at least for "FAT32" drives the dialog with message like "Tagret filesystem detected as FAT32, copying files over 4 Gb may fail. Are you sure to continue? Yes / No"' with ReadFile/WriteFile method will be a time-saver for user.

[Usher]

Maybe add user defined list for drives always using standard copy method?

Just for a changed error message? That would be overkill, sorry.

For more flexible drive management. I want to decide for which drive standard copy method is used. Or maybe "standard copy method" is the same as "compatibility mode"?

[Hacker]

Usher,

"standard copy method" is the same as "compatibility mode"

Yup.

Roman