Blacksmith
Joined: 10 May 2010
SWITERZRLAND-Zurich-Watt | | Files who's drive & path & filename & extension are longer than 256 (?) characters will result in a 'skipped file'(Source - The system cannot find the path specified)
I do think I read (sorry, I was not able to find this right now) long time ago that there are windows limits for
#1- drive & path (or maybe only path) <=(?) 256(?) chars
#2- filename & extension <=(?) 256(?) chars
#3- drive & path & filename & extension (or maybe path & filename & extension) <=(?) 256(?) chars
I do think the problem is, that it is possible to have valid limits for #1 + #2 but break #3. Astonishingly this works flawless for Explorer, NFTS and so on, BUT not some API-function seem to crash when the limits get exceeded.
While I suppose this is a problem of Windows (hmm, maybe only WinXP and earlier?) we should still be able to copy those files securely.
A tool I wrote once used as a workaround to map a drive letter if the path(es) became too long. |
|
