Winterlight wrote:
At 12:05 PM 8/4/2008, you wrote:
On 4 Aug 2008, at 19:47, Winterlight wrote:
RAM drive for TEMP likely counter-productive.
running from RAM rather then a hard drive counter productive... why?
Because dedicating a chunk like that You're blocking ram that could be
used for caching on an as-need basis.
I don't think so. I have 4GB RAM installed. Lots of testing, in the
past, by Maximum PC has shown little, if any, performance increase above
2GB. It is only when RAM got so cheap that everybody, including Maximum
PC started installing 4 GB of RAM. So I have always used RAM above 2GB
for the RAM drive. But even so I can set up my RAM drive at any size I
want or even to run dynamically which mitigates that concern. It runs
as hardware in Device driver.
Mostly, I wanted the RAM drive to keep the temp file cleared out on
reboot in a secure way. I always install a RAM drive, even if it is only
a couple of hundred megs. I can put encrypted keys in there knowing that
when I reboot they are gone. I have been running it for at least four
years, and no problems.
However, most windows checks, updates, as well as firewalls =
zonealarm, large program installs, and probably games, are going to
use \windows\temp no matter what path you specify under Environment
Not true, I have no such folder since I long ago moved pagefile, %temp% for system &
users, %userprofile%, and %programfiles% to different volume from %windir%.
I can see the point under that implementation only comment would be I hope the
allocation is dynamic. Tried to do the more logical choice of encrypting the %temp%
folders with EFS but some brain dead apps don't know how to move their data out
correctly. currently considering whole-drive encryption using Truecrypt 6 to acheive
%temp% encryption and because I want a hassle crossing the border! ;)
