My life with this pc upgrade is upside down.
 
I finally got a mobo that will house my RME pci card and the new cpu/fan kit in my rackmount box.
I've got it up to Win 10. It works. Nice.
 
But when I loaded the rest of my drives back into SATA 3 ports, the drive letter for audio changed to D from F. I didn't do that. No matter which SATA 3 I'm in, it's F. What was my G: Samples 1 drive is wiped and known as F - I plugged all in with pc off and regulated supply turned off, too. My H: Samples 2 drive is now known as G. All my projects refer to the F audio drive, and the soft synths refer to G and H for streaming. Every project I've ever done.
 
Does anyone know how to fix this? I know I have to reload the samples that were on my wiped drive, but I don't want to do that until I fix the drive letter debacle. I don't want to load Sonar back in until I get it right as well. Thanks, Shep

http://windows.microsoft.com/en-us/windows/change-add-remove-drive-letter#1TC=windows-7
works for Win10.

I appreciate this. It worked. The last time I tried this, it was on a freshly formatted new drive. It made the drive RAW, and I had to start again. Hopefully now I can start rebuilding my  Samples 1 drive to the tune of about a 1/2 TB. I can't wait to get see how this system performs once I'm fully reloaded in a couple days.

FWIW, the project drive and path assignment should not matter, if you are using per-project audio folders in their default locations under the project files. The projects use relative paths to the audio folders. If using the global audio folder, updating the preference in SONAR can also handle drive and path changes. The only case a drive or path change is an issue is if per-project audio folders are not in the default location. This results in projects storing fully qualified paths to the audio.
 
Still I can appreciate maintaining historic drive letter assignments to avoid learning a new layout.

I don't use default locations under project files. So, while a guess - I'm guessing getting these drives tidied up is a good thing for my sanity.

Drive letters are an abominable relic from the pre-DOS CPM file system. Internally, Windows uses object identifiers (see https://technet.microsoft.com/en-us/sysinternals/winobj.aspx ).
 
I wish MS would remove these.
 
Be that as it may, the order that things get assigned are the order they enumerate from the Plug and Play subsystem which is based in BIOS and Motherboard issues.
 
In fact, there are cases where the drive letters may enumerate differently from Boot to Boot (see https://support.microsoft.com/en-us/kb/937251 ).
 
You can force the assignment of drive letters as shown above and you can mount drives without drive letters, but as folder locations, as like Unix mount points using the Computer Management -> Disk Management (Change Drive Letter and Paths...).
 
I have 8 physical drives made into 14 volumes and I have encountered lots of issues with this.
 
By the way, you can use drive letters A and B nowadays, as I do. They are no longer reserved for Floppy Drives.
 
When I mount ISOs, like when installing NI Komplete, I can run out of drive letters. You can't use UNICODE letters for Drives (but you can for folder names, if you want to get into trouble with the many programs that don't support Unicode). Also UNICODE naming sorts in weird ways, not lexically or in binary order.
 
 

I just added a new 7,200 RPM HD to one of my systems, and split off a bunch of stuff to now go live on the new HD.
 
I had to go back and change a bunch of path pointers for multiple releases of Sonar, and some other software, and it made me think back to having to do the HD drive-renaming shell game a couple of months back, due to a hard drive failure on another system, and a couple of expansion drives that were added to that.
 
I just took drives that had assigned letters I didn't want for them, and assigned new drive letters, like from D: to X:, E: became Y: and so on.  Then, I could rename the new drives back to the old drive letters, and populate things as desired, and then lastly went in and updated any path info for content for applications such as Sonar.
 
It was actually not difficult at all. Hope that is of any help, or at least calming. :)
 
Bob Bone