Charged headlong into this one.
I'm not too irked about it, but here's the issue:
1) Installed Windows 7 onto 128GB SSD.
2) Initialized 3TB drive as GPT (which Windows cannot be installed on).
3) Found out later in Intel Rapid Response Technology that I needed Windows installed on a drive other than the SSD.
I was hoping to split the SSD between a ~64GB Windows 7 volume and a ~64GB cache volume and put the bulk of my software on the 3TB (backed up externally, of course). With what I currently know, I don't think this can be done.
However, since I run many so many programs, I doubt I'd see much of a SSD cache boost. Instead, I'm going to use the SSD to capacity on core professional software (and non-steam games that I want to run more quickly) and keep Steam, other games and non-essential media on the 3TB drive.
Steam really does need to step up and allow people to select drive location for specific game installs. This has been an issue since 2004 and low-capacity Raptor hard drives.
I'm not too irked about it, but here's the issue:
1) Installed Windows 7 onto 128GB SSD.
2) Initialized 3TB drive as GPT (which Windows cannot be installed on).
3) Found out later in Intel Rapid Response Technology that I needed Windows installed on a drive other than the SSD.
I was hoping to split the SSD between a ~64GB Windows 7 volume and a ~64GB cache volume and put the bulk of my software on the 3TB (backed up externally, of course). With what I currently know, I don't think this can be done.
However, since I run many so many programs, I doubt I'd see much of a SSD cache boost. Instead, I'm going to use the SSD to capacity on core professional software (and non-steam games that I want to run more quickly) and keep Steam, other games and non-essential media on the 3TB drive.
Steam really does need to step up and allow people to select drive location for specific game installs. This has been an issue since 2004 and low-capacity Raptor hard drives.