XPost: comp.mobile.android, alt.comp.os.windows-10   
   From: janis_papanagnou+ng@hotmail.com   
      
   On 31.01.2025 18:48, Marion wrote:   
   > 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. [...]   
      
   (I probably shouldn't engage in this thread - and not only because it   
   got aggressive recently - because it seems (partly?) a Windows issue,   
   given the mention of 'C:', 'D:' and such crap later in this thread;   
   but I'm curious...)   
      
   First, the above mentioned IDs have a purpose, I think; to uniquely   
   *identify* a hardware device.[*] (Please correct me if I'm wrong.) -   
   So it therefore sounds strange to change that ID in the first place.   
   And therefore it wouldn't appear to me to re-label that device and   
   even less to reformat the device just to change its "label".[**]   
      
   What I typically see as "solution" - but which is rather more of a   
   "concept" - is to use generic path components where you want them;   
   on Unix-like systems you'd create for example a symbolic link like   
     /storage/generic -> /storage/A2B2-C2D2   
   and generally access the files only through the generic link   
     /storage/generic/{editors}/{files}   
   If you want to replace the storage device just re-link the generic   
   link to the new device (and without any necessity to change device   
   identity).   
      
   (I'm not sure this is "clever" or "helpful" (as your suggestion is,   
   according to your subject), but it appears much more sensible to me.   
   Isn't that possible on Windows and Android to preserve portability?)   
      
   Janis   
      
   [*] I, and the OS, should actually have an interest to know whether   
   there's another (or new) device in the system.   
      
   [**] A quick browse of the Net shows that you could [on Windows] also   
   just simply change that label by context menu 'properties'.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)