long filename and path support

[SimonSecond]

NTFS supports deep and long filepaths since years but only since Windows 10 1803 there is Explorer support to use them. But even the Windows Explorer and the TotalCommander have still some problems. Especially with VSS recovery or "invalid" characters. A space at the end of a file or foldername is a hard problem for windows.
If FreeCommander could support this, it would be a dream.

Kind regards,
Simon

[klausisbruch]

I have the same problem/request

I have a build system for java programming, and java is notorious in working with veeeery long path/filenames, by creating many subdirectories.
Quickly, the current length limit of the latest FreeCommander donor version is exceeded, especially if attempting to copy or move the whole directory tree to some folder, which also already sits several subfolders deep.

Funny thing is, I can walk down such a veeery long directory tree in FreeCommander, but I cannot use FreeCommanders copy or move functions to get files there.

The request for FreeCommander is to support the path/filename length supported by the file system, which is 32.000 characters for NTFS, for copy/move/delete/zip/unzip/find,... etc.
Thanks, Klaus

[Marek]

Long path support is improved in the release 813.

[klausisbruch]

@marek: Thanks Marek.
BUT, I just downloaded v826, and I again could not delete a file with path length > 1024.
Would it be possible to have another look and support NTFS path length of 32.000?
Thanks, Klaus

[Marek]

For long paths you must define "Use FreeCommander" for delete operation https://freecommander.com/fchelpxe/en/S ... neral.html
and you must use File->Delete and not e.g. Delete from context menu.