Personal computing discussed
Moderators: renee, morphine, Steel
Airmantharp wrote:You're assuming that ~240GB is enough for anyone- and that everyone wants to deal with a Revodrive, let alone OCZ.
It may not be typical, but I know that my Steam directory exceeds 180GB. And then there's Origin, and Blizzard games; the reality is, until SSDs get quite a bit larger and cheaper at the same time, most people are still going to be splitting stuff between a smaller SSD and a larger HDD.
DiMaestro wrote:"Deal with a RevoDrive"
I'm assuming by your response, you have one? If so, what's been it's negatives for you? I'd own this if it had been on sale two weeks ago when I bought my Corsair 240GB SSD.
Origin & Blizzard games. They exceed 180gb in space? ****, the D3 install is what, 7.6gb? Wow Maxed out on expansions is what? 33gb? Once again, how many different games do you play in a week?Airmantharp wrote:You're assuming that ~240GB is enough for anyone- and that everyone wants to deal with a Revodrive, let alone OCZ.
It may not be typical, but I know that my Steam directory exceeds 180GB. And then there's Origin, and Blizzard games; the reality is, until SSDs get quite a bit larger and cheaper at the same time, most people are still going to be splitting stuff between a smaller SSD and a larger HDD.
Mr Bill wrote:Thanks for the tip Airmantharp! I had no idea mlink existed. I use Adobe Lightroom for my photography. It insists on keeping a set of files on the system drive that grows larger as I add more photos and my system drive is a puny 80GB Intel SSD. So, my question is... If I use mlink to link that directory to a new drive, will new additions that Lightroom makes go to that new drive seamlessly? Or, is this a static arrangement for files that never change?
Edit: Also, does doing this impose an overhead to file access similar to that when you map a directory as a network drive and then refer to the network drive?
SuperSpy wrote:Mr Bill wrote:Thanks for the tip Airmantharp! I had no idea mlink existed. I use Adobe Lightroom for my photography. It insists on keeping a set of files on the system drive that grows larger as I add more photos and my system drive is a puny 80GB Intel SSD. So, my question is... If I use mlink to link that directory to a new drive, will new additions that Lightroom makes go to that new drive seamlessly? Or, is this a static arrangement for files that never change?
Edit: Also, does doing this impose an overhead to file access similar to that when you map a directory as a network drive and then refer to the network drive?
If you link the directory (it has to be empty), it will seamlessly use the link target.
Technically there is some overhead involved, but I'd bet it's near zero, as the entire link mechanism takes place in the NTFS driver, unlike network mapping which has to dive all the way through the SMB stack and most of the way through the networking stack.
Waco wrote:For Steam I just tell it to install to whichever drive I choose (it'll create a SteamLibrary directory there). Why mess with all the linking (at least for games)?
Airmantharp wrote:This is almost four years old- and I still use it, but only for games on Origin (BF4, Dragon Age).