Universal Naming Convention: Difference between revisions
Jump to navigation
Jump to search
(Created page with " <!-- Universal Naming Convention is a Microsoft(/IBM) standard of referring to remote network share paths, introduced as something Explorer could do around WinNT/Win95. It amounts to: \\<server>\<sharepoint>\<path> Where server can be * IPv4 address * server name * IPv6 address https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/62e862f4-2a51-452e-8eeb-dc4ff5ee33cc https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-path...") |
mNo edit summary |
||
| Line 25: | Line 25: | ||
\\.\ | \\.\ | ||
: prefix will access the Win32 device namespace instead of the Win32 file namespace, which is how you can get some things ''beyond'' a standard file API. | |||
: also used for \\.\COM56 | |||
:: COM1..COM9 happen to work only because the filesystem API actually FORBIDS files be called that (so that it can kick you over to the device namespace?{{verify}}) | |||
\\?\ | \\?\ | ||
: tells windows to ''disable'' string parsing and send the string right through the filesystem. | |||
:: as almost a side effect, this also bypasses MAX_PATH lengths, but this is a reason for some yses. | |||
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectdfrom=MSDN | |||
https://stackoverflow.com/questions/21194530/what-does-mean-when-prepended-to-a-file-path | https://stackoverflow.com/questions/21194530/what-does-mean-when-prepended-to-a-file-path | ||
Revision as of 16:45, 4 April 2024