4 ms·
I think I read somewhere that Microsoft were investigating ways in which to get rid of the FAT32 backward compatibility issues with NTFS like the 255 character
by hashhar 10y ago
I think I read somewhere that Microsoft were investigating ways in which to get rid of the FAT32 backward compatibility issues with NTFS like the 255 character path element limit and the character limits in filenames. You can manage such files using the NTFS way of addressing them, "\\?\C:\Example\file:with?illegalstuff"
- nitrogen 10y agoIs there an official name for those kinds of long paths in a single namespace? I found UNC, but it seems to apply only to the network variety. https://en.wikipedia.org/wiki/Path_(computing)#Uniform_Naming_Convention https://en.wikipedia.org/wiki/Path_(computing)#Uniform_Namin...
- thoth 10y agoI'm not sure Microsoft gives an official name for "\\?\". The closest I can find is "To specify an extended-length path, use the "\\?\" prefix." (from https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...). So maybe it is the "extended-length path prefix".
- cataphract 10y agoYou can also use that prefix to access volumes that have no mount point, as in \\?\Volume{<UUID>}, among other things like UNC paths (\\?\UNC\...). So that's not a good name.