No programming, it is a command line instruction. If you can play an instrument, you can handle the DOS command line. But it would require some reading and playing around with the command to get comfortable with it.

Cool i will do that
I think i understand the link concept - getting a program to look for the files it needs in a different place from where it expects to find them? So i can keep the files on my HDD and set up a link so that programs that need those files follow the linked path.....

Yes, the /d and /j switches let you link entire directories instead of individual files. For example, to relocate the Rapture multisample directory from "C:\Program Files\Cakewalk\Rapture\Multisamples" to "E:\Cakewalk\Rapture\Multisamples" move the folder then issue the DOS command:
 
mklink /j "C:\Program Files\Cakewalk\Rapture\Multisamples" "E:\Cakewalk\Rapture\Multisamples"
 
This creates a link in "C:\Program Files\Cakewalk\Rapture" called Multisamples pointing to "E:\Cakewalk\Rapture\Multisamples". Rapture still looks in C: for it's data because the registry is unchanged but picks up the data from E: because it follows the link.

scook
Yes, the /d and /j switches let you link entire directories instead of individual files. For example, to relocate the Rapture multisample directory from "C:\Program Files\Cakewalk\Rapture\Multisamples" to "E:\Cakewalk\Rapture\Multisamples" move the folder then issue the DOS command:
 
mklink /j "C:\Program Files\Cakewalk\Rapture\Multisamples" "E:\Cakewalk\Rapture\Multisamples"
 
This creates a link in "C:\Program Files\Cakewalk\Rapture" called Multisamples pointing to "E:\Cakewalk\Rapture\Multisamples". Rapture still looks in C: for it's data because the registry is unchanged but picks up the data from E: because it follows the link.

Thanks for explaining this!!!!!! I never knew how mklink worked.
 
As to the original issue, it's been alluded to but here's a more complete explanation.
 
When you install a program that has lots of content, the install will typically default to placing everything on the C: drive because it doesn't know what drives you have. However, there will usually be an option during installation to place the content somewhere else. For example I have a 3TB drive that's dedicated solely to content. When given the opportunity to install content, it all goes on that drive. When you specify this location during installation, the program will "point" to this location to look for samples. 
 
Most programs that depend on lots of content also allow you to specify a new file path if you change the location of the content. The principle is similar to Sonar's "Folder Locations" preference.
 
 

Scook thats excellently explained i feel confident in doing this now. :)
Thank you very much its much appreciated.
Anderton thats very helpful excellent advice too im pretty sure my problem will be solved by a combination of everyones input.
Thanks again everyone :)