I have my apps on C: and my libraries on E: I want to replace E: with a new drive. I've copied all my libraries to the new disk and I'll give it the same drive letter as the old disk so all the paths to the libraries will be the same.
 
My question is, will I get caught out by something else, like the true disk ID or the fact that the new disk is bigger? Can anyone think of any reason a straight swap as described above, wouldn't work?
 
Thanks - rev

CW has a thread (you'll have to find it yourself) about the format needed on 'new' drives in order for them to 'work' with the CLSID registry system. It has to do with the 8.3 file name format being required but no longer a standard HDD format for new systems. I've had bunches of problems with this. In fact, SPro still throws CLSID errors routinely when loading projects, even for things like CW's Zeta. I stumbled across the CW note on this by accident. Converting the HDD format was not trivial (but didn't require a full low level format at least) and it did not completely resolve the issues, but CW still seems to need it to operate correctly.

This doesn't affect newer projects saved since we revised the CLSID system a few versions ago - X2 IIRC.
AFIK however older projects saved with the older system could still end up with missing plugins if the File system doesn't support 8.3 names.

Oh dear, what does all that mean? I'll look for the thread Letcher mentioned and come back if I have questions. I had a feeling it wasn't going to be quite that easy...

I changed the drive letter and everything seems to be working perfectly. No problems with plug-ins or plug settings whatsoever, and I have plenty of plugs in each project so I'm sure I would have triggered an error by now if there was going to be one. 

I've seen CLSID errors before from Sonar plugs but all you have to do is remove the existing plug and insert the new or correct version.
 
I'll continue opening projects for a while, until I'm absolutely sure but this has to happen so if I have to fix the occasional error so be it. It looks as though it's going to work perfectly.

Yes as I mentioned it should work fine with newer projects saved in X3 or higher since this issue was addressed some years ago.You shouldn't need to do anything to mess with your file system settings.
BTW the old thread you were looking for is here if you want to read up on the history. 

>Yes as I mentioned it should work fine with newer projects saved in X3 or higher 
I'm on Sonar 8.5.3 - so I figured that would mean my projects are before the issue was addressed. Either way, I'm happy and thanks for the thread.