It occurs me with making or copying some files (folders) some warning message in TC about lenght of string .. BUT:
NTFS: limit of file (name) is 255 bytes
limit of lenght is 32767 unicode !!!
bug - length of"path" with copy
Moderators: Hacker, petermad, Stefan2, white
re
I found sdimilar thread:
http://ghisler.ch/board/viewtopic.php?t=30170
BUT:
you say: total path length (including drive letter any any subdirs) becomes longer than 259 characters, because that's the maximum ******most Windows program***** can handle
And I say (in doubt) there is not reason in windows not to allow total path lenght extend it up to 32767 characters
http://ghisler.ch/board/viewtopic.php?t=30170
BUT:
you say: total path length (including drive letter any any subdirs) becomes longer than 259 characters, because that's the maximum ******most Windows program***** can handle
And I say (in doubt) there is not reason in windows not to allow total path lenght extend it up to 32767 characters
Maybe you should read about Windows limits in more detail before asking.
Look here!
The "Overlong" paths (i.e. > 259) are only possible on modern NT systems and
from in there only when an Unicode function is used. For all other API functions we're
still stuck to MAX_PATH, which is 259 characters.
For individual file and folder/directory names (not the resulting path!), we're
limited to 255 Unicode characters(not Bytes!) on all occasions,
no matter if NT or not or which file system or API.
TC warns for a good reason: There are tons of older programs out there which didn't support
paths > 259 when they were written and you'll get problems then.
If you don't like the warning:
There's an ini option "LongNameCopy" which you can modify for your desire.
Look here!
The "Overlong" paths (i.e. > 259) are only possible on modern NT systems and
from in there only when an Unicode function is used. For all other API functions we're
still stuck to MAX_PATH, which is 259 characters.
For individual file and folder/directory names (not the resulting path!), we're
limited to 255 Unicode characters(not Bytes!) on all occasions,
no matter if NT or not or which file system or API.
TC warns for a good reason: There are tons of older programs out there which didn't support
paths > 259 when they were written and you'll get problems then.
If you don't like the warning:
There's an ini option "LongNameCopy" which you can modify for your desire.
re
thank you for explanation
may I have last question ? as you said ."only when an Unicode function is used." - How can I force in my win 7 and TC to be properly used Unicode encoding (characters) so that no problem with longer paths characters ?
Unicode is too hard to understand for me in http://en.wikipedia.org/wiki/Unicode
may I have last question ? as you said ."only when an Unicode function is used." - How can I force in my win 7 and TC to be properly used Unicode encoding (characters) so that no problem with longer paths characters ?
Unicode is too hard to understand for me in http://en.wikipedia.org/wiki/Unicode
Re: re
Simply: You can't, because this has nothing to do with your settings, but with the API functions used by the program.trevor12 wrote:How can I force in my win 7 and TC to be properly used Unicode encoding (characters) so that no problem with longer paths characters ?
The developer fixed the functions at compile/build time, you can't alter that behavior.
This is not your responsibility but the developer's.
Nevertheless you can look for newer/updated versions of programs which fully support long paths,
(should be most common programs by now) but in general it's best to keep the paths simple and short.
When you can't avoid a very long path use a recent program to work with files in these.
TC can work with them since version 7.50.