I must not have been clear enough. No one seems to have gotten my goal.
First, the File/rename/copy option in Library manager is for MOVE related changes (as is the wiki). None of the options will let you changed the DRIVE: referenced -- that's all. No moves, nothing else.
There's no problem changing the DOS drive letter assignment. I change that on the server to V:, then run MC and the library still has every entry pointing to the E: drive. As a result, all entries are 'missing' (cannot be found). I simply want to change the database's notion of the BASE DRIVE from E:\ to V:\. No moves, no copies, nothing else. But only that much can be changed, because there is a specific hierarchy below that that cannot be changed.
Thanks.
It's a very simple request that doesn't seem to be addressed in any way on MC.
subst and friend are windows operations which are unneeded since the drive ID is easily assignable already in Drive Manager.
By doing this, then network sharing the drive V: so other client machines will see it as V: and I can set that network drive on each client, to the V: drive. Now when a MC is run on a client, the database also shows V:, which agrees now with the exact path for the local location of each song.
Other ideas?
The problem from preventing the use of E: on my workstation is a W10 2004/H2 and up, bug which has not been fixed yet. One other machine I have had the same issue, but the solution for it was easy to find. On this workstation, there is no E: drive iassigned by the drive manager, and the position is not showing as used by any driver or device. "This PC" shows it as a CD/DVD drive, but right now other such drives are disconnected. You can't disable any device to make the phantom drive to go away (thereby showing E: available for reassignment. I've spent hours on this one thing, searching the net, searching microsoft, etc, lots of mentions of phantom E: drives in this version of W10, but no solutions that solve the problem on this machine.