- what does this mean? Does this mean that sandboxes will be written/stored/operated on [C:]? Because that's the opposite of what I want. Or does it mean that the whole [C:] drive will be sandboxed so that when I install Steam/TF2 onto my secondary drive [D:] it won't actually change Windows?Set Container Folder > C:
buppus wrote:I see, so you're saying it virtualizes in [C:], but is actually taking place in [D:]?
buppus wrote:In light of already having a 13GB Steam folder with all of my application data, shouldn't I start by migrating that data to the actual [D:], then running Steam sandboxed w/ set container folder > [D:]?
buppus wrote:By junctioning the folders, will that allow the sandboxed Steam client on [C:] to forward permanent updates to D:/...steamapps?
buppus wrote:Can you give me some info on how to implement the folder junction?
buppus wrote:I just realized how incredibly useful this junction tool is
buppus wrote:So with the LSE utility, just select "Pink Link Source" on C:/....steamapps and then "Drop Here > Junction" on D:/...steamapps ... is that right?
buppus wrote:As for the sandbox on Steam, are there any particular settings I should change (like restrictions or resource access?), or should I just use the default?
MichaelS wrote:No. You need to create the junction from D to C, from source to destination.
MichaelS wrote:Yeah. First time I used it was to junction folders on RAM Disks.
buppus wrote:Do I have to remove the original steamapps folder from C:/...Steam before creating the junction? (just right click inside the steam folder to drop as junction?)
buppus wrote:Do you think it's worth it to set up a RAM disk for internet cache and temp? or is it unneccesary with the new capabilites of this generation SSD?
Users browsing this forum: No registered users and 2 guests