- Reaction score
- 1,248
- Location
- Charente, France
In fact, there is no ideal scenario for restore. The less bad is first to attempt to restore to original path then create let's say a D subfolder in "My Music" folder if D is not writable. The problem would be that if the tech is using an external drive that has the D letter on the new system: the files will be restored straight to the tech's drive... Another pain to solve hereA question that just appeared somewhere in the cerebral cortex is this: I presume at the moment you back up files from the Library path found in the registry and restore to the Library path found in the registry. The paths don't have to be the same. It doesn't matter. However, in the scenario where the source Library has multiple paths, how would you handle the restore?
1) Would you attempt to recreate the paths and restore to multiple paths so that the original Library configuration is restored? What if the restore target system doesn't have a D: drive (or whatever), ie not possible to recreate a path?
2) Or maybe just restore everything to the new "Save Location"
3) Pop up option dialog, "User libraries have multiple paths. Do you want to recreate the paths or merge into one path?"
I know the idea of popups in the middle of a restore is contentious so maybe something like this. This will attempt to recreate the library paths but if that can't be done then the paths are merged.
rem restore library pseudo code
for each library
for each path in librarynext library
if the path is the old save pathnext path
change to new save pathelse
attempt to create the pathif path is writable
if creation fails
change path to new save path
restore files
Last edited: