XPost: comp.mobile.android, alt.comp.os.windows-10   
   From: marion@facts.com   
      
   Below is both a clever suggestion - and - a quizzical question.   
      
   Here's the problem set (which I experienced myself, recently):   
   A. You're a typical Android/Windows/editor owner with a 64GB sdcard   
   B. Most of your editing data is kept on that 64GB portable memory card   
   C. But then you need to double your memory (to 128GB, which costs ~$10)   
      
   What happens?   
   Well, for most people, they lose many editing associations to the files.   
      
   Why?   
   Because for many editors, they don't "search" for file associations.   
   Coupled with the filespec having changed between the 64GB & 128GB sd cards.   
      
   Huh?   
   You need to know that every sdcard comes with a "volume name".   
    An example volume name could be, for example, "A1B1-C1D1" (or whatever).   
    Another example volume name could be, for example, "A2B2-C2D2".   
      
   The point is that every sdcard comes with an (almost) unique volume name.   
   So?   
      
   Well, the old card filespec to your data is now *different* than the new!   
    OLD: /storage/A1B1-C1D1/{editors}/{files}   
    NEW: /storage/A2B2-C2D2/{editors}/{files}   
      
   OK. That sucks. So now you have to manually re-establish the filespec.   
   For every modern editor. For every file that the editor associates with.   
      
   Why did you insert "modern" editor in that sentence?   
   Are you being sneaky?   
      
   Well, a good editor will save its own files wherever you want them to be.   
   Some editors are good (such as map editing programs, for example).   
      
   Those good (aka modern) editors will access your files on the sdcard.   
   Just like cameras do (but cameras have another trick up their sleeve).   
   Cameras will *find* all their "media" files, so they don't have this issue.   
      
   But many editors do have this issue - particularly map editors.   
   And GPX editors. And PDF editors. And text editors. (and so on)   
      
   So what's the trivially simple (yet devilishly clever) solution then?   
   Heh heh heh... it's so simple - it should be outlawed as too simple.   
      
   Simply format your new sdcard to the same volume name as the old sdcard.   
   Yup. It's that simple.   
      
   STEP 1: Determine the old 64GB sd card volume name (e.g., 0000-0001).   
   STEP 2: On Windows, quick format the new 128GB sd card to the same name.   
   STEP 3: On Windows, copy all the old data to the new 128GB sd card.   
      
   That's it!   
   You pop in the new sdcard and everything works exactly as it should.   
   Ask me how I know that this concept of "portable memory" just works.   
      
   Now... for my quizzical question, where the problem set is similar:   
   A. You're a typical HP Stream owner with a permanent 32GB C: drive   
   B. So you've added a 64GB portable memory card as the D: drive   
   C. But then you need to double the D: drive (to 128GB, which costs ~$10)   
      
   Does the same trick of formatting the volume name work in that scenario?   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)