I just got a space warning on update about my c drive, but I always put stuff audio related on my D drive, but obviously the new installer has thoughts of its own. How do I correct this so my precious C drive doesn't get overrun with new install info? I'd hate to have to delete all my keyboard cat vidz to make room. :-)
 

Only way is to not use the Command Centre and go manual

I should add, while you can direct the CCC to download the files to an alternate non C:/ drive location when unpacked by the CCC the files will still install to their default C:/ drive locations.

Hence the need to download the files from your account as in the past and then do an advanced install on each installer file and make your installation path choice then.

Yeah, this C:/Cakewalk Content folder has been slowly building an empire on my hard drive. 

The easiest way to move "C:\Cakewalk Content" is using a directory junction. For example, to move the folder to D:
1) Using Windows Explorer move "C:\Cakewalk Content" to D:
2) Run cmd.exe as administrator and type:
mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content"
and you will not have to worry about Cakewalk Content again, at least not until the D drive fills up

scook
The easiest way to move "C:\Cakewalk Content" is using a directory junction. For example, to move the folder to D:
1) Using Windows Explorer move "C:\Cakewalk Content" to D:
2) Run cmd.exe as administrator and type:
mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content"
and you will not have to worry about Cakewalk Content again, at least not until the D drive fills up

Whoa!  Can you expand a bit on this.  Sounds like a solution.  Is it really that simple Scook?  Thanks!
 
Paul

Not much more to say. It is that easy. Once the folder is moved to the new location and the directory junction is created (the mklink command), SONAR and all subsequent Cakewalk updates will not be aware of any change to the PC, the OS will use the new location to read and write Cakewalk Content.
 
The same technique may be used to relocate practically anything such as Cakewalk sample content folders (ex. dimPro, Rapture, Session Drummer multisamples folders) or content from other vendors.

Thanks Scook... I am going write this down. What about things that are already installed on the C drive, is there any need to do anything with them or is this a one stop fix?
Heck, I am printing this thread! edit> I just copied posts 5 and 7 and pasted then to Notepad and saved them as "CCC Drive and folder fix" and saved it to my desktop... so I can use it on my DAW, I am SO glad that I have not put much on it yet... this is a REALLY helpful post and should be written up and made a "Sticky", IMO. A lot of us really don't know much other than "turn that knob", "press that button", "move that slider".. and as far as a DAW, I just do what I am told and hope it works. Maybe it's just me, but I doubt it. I think people who really know their way around a computer and a DAW just assume that most others do too but, like I said.. as for me, not so much. IT is ALL hard for me but this takes a LOAD off my mind.
Really... Thank you for this!
 
J

I'm contemplating using junction points for the whole freakin Program Files" and "Program Files (x86)" folders when I set up my new system from Jim in order to keep stuff off of the OS-only SSD drive. It's a bit scary to do, but since it will be a brand new system, I might as well try it and see if there are issues. Worst case I need to nuke and pave if I break it.
 
But it will have separate application and sample drives, so not sure how to separate those so that I can use C3 and do the installs. Maybe I should put the junction points a bit deeper to make them more targeted in order to separate apps/samples.
 
Maybe to help all of us that need stuff to not be on the C drive, but want to use C3 for simplicity, we can document the folder structure showing where various files are located. This way it becomes clear how to set up the junction points. I can go and dig through the Program Files folder and try to figure it out but I recall some people knew the layout pretty well.

SilkTone
I'm contemplating using junction points for the whole freakin Program Files" and "Program Files (x86)" folders when I set up my new system from Jim in order to keep stuff off of the OS-only SSD drive. It's a bit scary to do, but since it will be a brand new system, I might as well try it and see if there are issues. Worst case I need to nuke and pave if I break it.
 
But it will have separate application and sample drives, so not sure how to separate those so that I can use C3 and do the installs. Maybe I should put the junction points a bit deeper to make them more targeted in order to separate apps/samples.
 
Maybe to help all of us that need stuff to not be on the C drive, but want to use C3 for simplicity, we can document the folder structure showing where various files are located. This way it becomes clear how to set up the junction points. I can go and dig through the Program Files folder and try to figure it out but I recall some people knew the layout pretty well.

At the risk of sounding ignorant (well, about this I AM ignorant, not stupid, I can learn but def ignorant!)... any elaboration will be appreciated. Like "documenting and junction points for dummies". Really, I assume that you mean to just write down where you/I put everything associated with a particular VST, that makes sense.. but if all MIDI and audio associated with instruments goes in subfolders on D drive, under VST Audio and Midi and you direct the .dlls that are on the C drive to their sub folders on the D drive, shouldn't everything work? Then wud I need to set Sonar to just scan the VSTPlugin folder on the C drive? Then C would have a lot of small folders with the big stuff on D drive... or am I not understanding? Would I need to also set to scan the folder on D drive or all the subfoders with audio and midi on D drive?
I hope that makes sense.. 
Thanks you!!
 
J