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.