From: ldo@nz.invalid   
      
   On Fri, 8 Aug 2025 01:09:57 -0400, Paul wrote:   
      
   > On Fri, 8/8/2025 12:05 AM, Lawrence D'Oliveiro wrote:   
   >>   
   >> This contrasts with DOS/Windows, where “drive letters” like A, B, C etc   
   >> are used both to refer to the device and to the mounted volume. This kind   
   >> of scheme does not scale.   
   >>   
   > https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats   
   >   
   >    In addition to identifying a drive by its drive letter,   
   >    you can identify a volume by using its volume GUID. This takes the form:   
   >   
   >    \\.\Volume{b75e2c83-0000-0000-0000-602f00000000}\Test\Foo.txt   
   >    \\?\Volume{b75e2c83-0000-0000-0000-602f00000000}\Test\Foo.txt   
   >   
   > I believe it is also possible to call CHKDSK with an identifier   
   > similar to that, instead of C: or D: .   
      
   Only CHKDSK? Not other Windows software?   
      
   And don’t forget the nonsense over “reserved” Windows file names ...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)