XPost: comp.mobile.android, alt.comp.os.windows-10   
   From: marion@facts.com   
      
   On Sun, 2 Feb 2025 15:44:38 +0100, Janis Papanagnou wrote :   
      
      
   > You again stirred my curiosity - since I don't know about the Android   
   > and its file-editors peculiarities... - How does Android recognize the   
   > path with the (arbitrary) "A1B1-C1D1" and "A2B2-C2D2" path components   
   > but not a generic (a fixed) one?   
      
   Well, I wish I understood why *some* Android file managers show those   
   cryptic identifiers, and yet other Android file managers show '0000-0001'.   
      
   There must be someone out there who understands why, but it's not me (yet).   
      
   Take a look at these screenshots I made for you to illustrate the question.   
      
   0. We're starting with an sdcard which was formatted to 0000-0001   
      Then we test only the 1st 4 file managers in my homescreen "file' folder   
         
      
   2. Notice the first file manager (OwlFiles) shows both the cryptic label   
      and the user-defined label (for reasons completely unknown to me).   
         
      
   3. The second file manager (Round Sync) is completely fooled by the label!   
         
      
   4. The third file manager (Mix Explorer) is almost completely fooled.   
         
      
   5. The fourth file manager (ZArchiver) isn't fooled in the least.   
         
      
   I wish I understood those results.   
   But I don't.   
      
   Does anyone?   
      
   Why do some file managers show 0000-0001, while others show both, and yet,   
   still others only show the cryptic volume label & not the 0000-0001?   
      
   I openly admit that I'm befuddled by those results.   
   Does someone know more about this than I do?   
      
   If so, please explain why we're seeing what we're seeing above.   
   That would add value for sure.   
      
   TIA   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)