XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows   
   From: arlen_holder@newmachines.com   
      
   On Fri, 04 Sep 2020 21:37:04 GMT, MajorLanGod wrote:   
      
   > I assume there is a way   
   > to examine that name without too much trouble.   
      
   Thank you MajorLanGod for your purposefully helpful suggestions.   
      
   The first experiment that worked for me was the aforementioned   
   script that identifies the flash drive by filespec.   
      
   However, to your point, it certainly would be nice if someone   
   posts a script that solves the problem using the volume name.   
      
   Bear in mind, I also will be solving this problem for Linux.   
      
   Given these three newsgroups were added for explicit purposes:   
   a. alt.msdos.bat (Windows batch experts)   
   b. alt.comp.os.windows-10 (Windows 10 experts, no dejagoogle archives)   
   c. alt.comp.microsoft.windows (for the dejagoogle archives)   
      
   You'll note I did not ask this question of Linux experts,   
   even as the setup I'm devising _also_ will work on Linux   
   (given all my machines are generally set up as dual boot).   
      
   Hence, I simplified filespecs to limit this question to Windows.   
   o And I simplified the explanation of the overall problem set.   
      
   I limited the question to Windows for the purpose of this thread.   
   o To clarify, there is one flash card, and multiple dual-boot machines.   
      
   To that point, when I plug in the USB stick to any of my computers,   
   (only some of which are Windows, while others are booted to Linux)   
   what's "unique" about that USB stick is the "volume name", and   
   the file hierarchy on that specific system software USB stick.   
      
   For example, the USB stick variables are threefold:   
   o %SW_DRIVE%:\%OS%\software\%MACHINE_#%\syslog.txt   
   1. The software drive can change upon every insertion.   
   2. The OS will be either Linux or Windows at any given time.   
   3. The machine will be any number of dual-boot PCs.   
      
   To your purposefully helpful suggestion of identifying the flash drive by   
   its volume name, that was certainly possible (and viable).   
      
   If anyone has a batch script that replaces the one I proposed,   
   which uses the volume name instead of a filespec to identify the drive,   
   that would be a very useful actionable addition to this thread.   
   --   
   A tutorial, if it's not actionable, is just a pretty story.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)