-
Notifications
You must be signed in to change notification settings - Fork 714
Doesn't appear to support "long paths" #357
Comments
The binaries provided here do not yet contain this functionality, but a release, see #356, is on the way. |
No, I didn't download the source. |
Unfortunately the result was the same. |
Have you tried my binaries ? If it is not working, please report in detail what are trying to do:
|
Are you comparing the length of the new name with MAX_PATH(260) in the rename (F2) operation? |
No. Please provide a description what you are trying to do by following the instructions in my last comment. |
|
I looked at #356 and looked it up. |
GeneralNTFS suports path + filename up to 32767 utf-16 characters, but each individual component (subfolder/final-file) has a limit of 255 utf-16 characters Your CaseWinfile supports path + filename up to 1024 utf-16 characters. You are trying to create a single file with more than 256 characters, which violates the general NTFS limitation above. Winfile and no other tool can overcome this. A small test to prove that Winfile works with long path up to 1024 utf-16 characters according the NTFS spec can be found here |
I got it |
@craigwims: please close |
I'm looking for a rescue tool for the "long path" error.
but it truncates it to 259 characters.
Are there any setting items other than the above registry settings?
Environment: Windows 10 Pro 22H2, WinFile 10.1.4.0
The text was updated successfully, but these errors were encountered: