5 ms·
260 is the typical limit. NTFS allows for 65535 per filename and I think up to 65535 deep on directories (I could be wrong on the second one). Win32 on the ot
by sumtechguy 5y ago
260 is the typical limit. NTFS allows for 65535 per filename and I think up to 65535 deep on directories (I could be wrong on the second one). Win32 on the other had usually caps everything at 260 total (MAX_FILE_LIMIT). Most of the docs and examples out there use that. I would bet that it is some sort of FAT limitation.
This can be annoying if you move a drive between differing OS's and the NTFS bit on the other side does interesting things. NTFS is also case sensitive. But the win32 layer 'hides' it mostly, there is a flag to turn it on. Unless you do something like write from a linux box and you can end up with 2 files named the 'same' but different case. It is also possible to trick windows into doing it but it is tougher.
- colejohnson66 5y ago> Win32 on the other had usually caps everything at 260 total (MAX_FILE_LIMIT). Nitpick: It’s MAX_PATH :) Also, there is a way around the limitation: prefix all (absolute) file paths with \\?\ https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd https://docs.microsoft.com/en-us/windows/win32/fileio/maximu...
- sumtechguy 5y agoDoh! I should have got that. I should not have messed that one up.