Symbolic links and junction points are nothing to do with Sonar and don't care what is in the directories. So you can use them with any directory, whether it contains programs, samples, 32bit things, 64bit things, whatever.
 
The important thing is that this is a 2 part process:
1) Move a directory from its original location to a new, preferred location
2) Create a link with EXACTLY the same name in EXACTLY the original location that points to the new location.
 
Tom's screenshot won't work because he has mistyped "Files" as "Fies". But if that was corrected, AND he has already moved the whole directory "C:\Program Files\Cakewalk\Studio Instruments" to "V:\Cakewalk\Studio Instruments" (ie. he went into C:\Program Files\Cakewalk\ in Windows Explorer, cut the 'Studio Instruments' folder, then navigated to V:\Cakewalk, and pasted the 'Studio Instruments' folder there) then yes, it will work. Any program in future that tries to look at C:\Program Files\Cakewalk\Studio Instruments will be automatically redirected to V:\Cakewalk\Studio Instruments and all is well.
 
The process is reversible, too: remove the link, then move the targeted directory back to where it started. (Make sure you have a backup though, because if you get this wrong you might delete the directory with all your data rather than the link. Better safe than sorry.)
 
 

Kylotan
 The process is reversible, too: remove the link, then move the targeted directory back to where it started. (Make sure you have a backup though, because if you get this wrong you might delete the directory with all your data rather than the link. Better safe than sorry.)

Thanks for this Ben.  Where does this "Link" reside?
 
Paul

Actually I couldn't make the C:\Windows\system32> go away.
So it is "moot".
Thanks Ed.
T

DOS commands
So do I cd or not cd, that's the question?T

*bookmark*

Bristol_Jonesey

scook
The assumption in my initial post is data already exists in the folder on the C drive but it does not matter. What does matter is prior to issuing the mklink command, the path on the C: drive must not exist and the path on the D: (or whatever drive is actually storing the data) must exist. This is why in the example above, the first step moves the "C:\Cakewalk Content" folder to the D: drive.
 
The process for a new install where "C:\Cakewalk Content" did not exist is
1) create "D:\Cakewalk Content"
2) Run cmd.exe as administrator and type:
mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content"
Then when installing, the installer will think it is writing to "C:\Cakewalk Content" but the OS actually writes everything to "D:\Cakewalk Content." When SONAR starts up it will use the "C:\Cakewalk Content" default setting but the OS actually reads the data from "D:\Cakewalk Content."
 

i think the bit I've put in bold is the most important part of using mklink.
 
It's no good just to copy (or cut) your files across, the path on the C: drive must not exist, so you have to delete it once you've moved your files.

 
Actually, the destination directory of a junction in fact MAY "not exist";
but the link is inoperable UNTIL the destination directory is created...
you can pre-setup a junction(s) and create the directory from a backup
as needed.
 
Mel