From: nospam@needed.invalid   
      
   On Fri, 8/8/2025 11:42 PM, Lawrence D'Oliveiro wrote:   
   > 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 ...   
   >   
      
   type "\\?\Volume{c3bc5ab1-c5f0-4dae-838c-751ef868e237}\Recovery\   
   ogs\Reload.xml"   
      
      
      
      
        
   ...   
      
      
   I can dump the contents of a text file, on a hidden NTFS.   
   The "type" command is similar to "cat".   
      
   But to do that, I had to use "testdisk.exe" to be able to list   
   the partition and identify some candidate file and folder names.   
      
   And the identifier used, is not the same identifier that   
   "disktype" prints out, either.   
      
   Whether this is useful, is another question entirely, but at least   
   I can see the potential to read one file from each partition of   
   a max-partition GPT disk (128 partitions).   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)