This would be a lot easier if CW wasn't so dependent on the registry and provided log files of installation locations. The whole registry thing (as it works today) precludes separate 32b and 64b Sonar installations since they share the same preferences rather than using their own log files. I mention this because even if I used mklink for both all the CW program and support dir's to get them someplace convenient, I'd still need to do a C: drv backup to ensure the registry and file systems include the Sonar updates. For instance, this FB DL currently in progress to help C3 cache installations is very likely keeping that cache in the registry and on a different drive than any other CW data after using mklink. I tend to sort things out eventually, but I'm not as patient as I used to be and this is way more hoops than any other tool I use. 
 
Just my comments with an intent to help make things better.
 
I clearly am "comfortable with their computer management and maintenance methods." It's just that the current Sonar path isn't helping at all.

I have no use for a current version of 32bit SONAR. If I needed 32bit SONAR for legacy projects, I would use an older version since it would be completely separate from the current 64bit installation.
 
The registry is another reason I use mklink. No need to mess with the registry.

Not raining on anyone's parade here, but I'm not afraid to make comparisons. Sonar and my assorted CW VSTs (and only CW VSTs) still seem to use the registry in ways that my other DAWs/video,etc don't have problems with. I'm a long time user and have 'crafted' (shall we say) structures, libraries, and indexes for RaP,Z3,DP,Z2,etc. Near as I can tell Sonar uses these links along with their CLSID's when locating them. I believe I've got everything 64b, but ...
 
And I do not want to hijack this thread. There are a lot of things going on in the registry for CW relative to other programs for keeping routine data specific to a certain program (which then attempts to go obsolete asap, say Project5). I haven't seen anything resembling a description, and definitely do NOT want to see such a thing of magical registry. The reg is not localized or relocatable from the C: drv. I worry about re-storing a 3 month old BU to a failed C: SSD and potential conflicts with CW's current records, etc. 
 
Per the OP: Please make it stop. Pretty please?
 

Let's face it the big data consumers on a drive are samples. The quantity and size of other files pales into insignificance by comparison.
The other thing that's nice to have is organisation from the point of finding files and for the purpose of backing up those files where required.

The decision we face is to use defaults and suffer the space consumption on precious C:/ drives or make a change.

I can tell you now that the first CCC update won't solve everyone's issues. Go read the sticky thread in the Features/Ideas forum. There are new features already defined along with things that will definitely not yet be added and may be added later.

Mklink doesn't impact on the registry so anything you've changed already won't be effected. As far as programs are concerned the files are still where they were.

Anyway it's a personal choice. I chose to take care of a simple problem with a simple solution that is working now and doesn't rely on how much Cakewalk do or don't do in terms of making installations and file locations more flexible.

mudgel

KPerry
I'm going to tout this again http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html which allows you to do the mklink (and more) from within Explorer.

You say tout it again so I must have missed it the first time. Must check it out. Thanks Kevin.

First edit:
Checked it out and it looks daunting with all the pics and documentation compared to just a few lines in the command line to use mklink. More reading required.
Second edit:
I've now read quite a bit of the documentation that comes with LSE. It's seems worth creating a thread espousing its value to Sonar users and providing the link back to the original website.

What do others think?
I didn't mean to hijack your thread WilliamCooper but it's pretty much where you're heading I think. Let me know.

LSE seems way cool...
gonna have to DL this one.
 
Mel

jih64

mudgel

What do others think?

What I think is the whole mklink, and above mentioned utility thing, shouldn't even be necessary, just like it isn't necessary for the other 99.9% of the software I/we own, which actually goes where we tell it to, and has the options readily and easily available to do just that.

The man has a Point...
However I refuse to hold my breath when a simple, reliable(if you make sure you understand it)
annnnd NATIVE fix is so readily available.
I stopped stamping my foot when I was three.
 
Perhaps  the Bakers SHOULD/will shortly make all these issues a distant memory but it's
nice to know I'm not screwed if they have older,(just not in the face, please) more important(in their view)
things to contend with.
 
Mel

Another associated problem I have is my SSD does not appreciate massive read/writes period, so the unpacking/installing (i.e. temp folder usage) makes it highly irate - unpacking these massive installers to the SSD will cause a BSOD before the installation can complete (e.g., X2, Dim Pro, et. al.) ... and researching this seems to point at a simple heating issue (one site recommended an auxiliary fan just to blow on the SSD for such things).
 
As I just rebuilt this machine and knew this was coming, during the SONAR installs (only) I reassigned the temp directories to a folder on my HDD (and switched them back when done). It would also be beneficial to allow the user to assign an alternate temp directory in the installers themselves because of this. I checked the directory I used after reinstalling Platinum (all piece parts) and 3GB of "residual material" had been left in that folder.
 
[To reassign temp directories - Win7]

1. Right click computer, select "Properties"
2. In the pop up, select "Advanced System Settings" on the left.
3. In the next pop up, on the "Advanced" tab, click "Environmental Variables"
4. There you can edit both the "TEMP" and "TMP" directories to a new folder (default is "%USERPROFILE%\AppData\Local\Temp" for each).
5. This is not something to leave re-assigned, as other installers (especially Windows) assume that is the primary drive and will begin to write protected files on it that shouldn't be there).

KPerry
I'm going to tout this again http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html which allows you to do the mklink (and more) from within Explorer.

I'm hoping one of our very helpful, (and much smarter than I), forum members will make an instructional video for this utility as it would be used with Sonar.  I haven't read all the way through the documentation yet but for me, (at least), it's going to take some head scratching.  Thanks to whomever developed this.
 
Paul

Quick and easy instructions...you only need to use one function of it.
 
1 - Browse to the folder you want to link to
2 - Right click on it and select Pick Link Source
3 - Browse to the folder where you want to paste the link
4 - Choose Drop As, then Symbolic Link in the submenu
 
Done!
 
You might be prompted for admin privileges depending on where you're creating the link.  You can also rename the link you've created after the event if you'd like to.

To understand why we are in this position to begin with, we have to understand Cakewalk's own viewpoint on this issue. Which goes something like this:
 

Willy Jones (Cakewalk) 
Because it adds a layer of complexity between a new user making music right away. I'd hate to burst your bubble here - but you are in the minority. The vast majority of users don't specify custom paths. Muddying up the first time/new user experience because Steven doesn't like it is a poor design choice and counter-productive to one of C3's major goals: remove obstacles to firing up a project and making music fast (herein referred to as goal 1).