Eunos wrote:
That small size proved more than a little annoying when some sort of virtual memory file impolitely filled up about half the drive with a massive temp file. All attempts to remove it failed, including disabling the Windows page file altogether.
"Impolitely" indeed.
Using
nLite I created a custom install of x64 XP Pro which ended up taking only 1.1GB of the iRam's space- "Great!" I think...plenty of space for some apps with room to spare.
I moved the swap file to a second disk and all was well till, upon reboot, I saw the iRAM was filled to the brim with a 2GB virtual memory file.
Several attemps to tame this problem finally resulted in this approach...
Immediately after install set the page file size on the iRAM (C: drive) to 16MB/16MB- this is the smallest allowable size. You can set the real page file to whatever size you like on a separate drive.
Disable System Restore (it never works properly for me anyway and
nLite has this option available).
Finally, in the Startup and Recovery tab (Control Panel>System>Advanced>Startup and Recovery>Settings)
uncheck the three option boxes for "System Failure" and set the "write debugging information" to "none".
A few other observations-
-During install (or when first initializing the iRAM if it's added later as a second drive) DO NOT do a "full format", use the "quick format" option.
I don't know why but trying a full format always resulted in a hard lockup and system freeze for me.
-I tried running Bootvis just to see what effect it would have and that resulted in a system freeze as well because the trace files were huge and overfilled the iRAM's capacity. Installing the program to a separate drive should work but I haven't retried that experiment yet.
-Under Properties for your CD/DVD drive go to the "Recording" tab and change the location where the burning software will save the image of what it's working on...default is C: and that too can quickly overfill the capacity of the iRAM.
Basically, any program that creates temp file whilst running or saves a history (a major offender here is Internet Explorer which defaults to a ridiculous size for it's saved temp/history file) must be carefully pruned or installed to a directory off the iRAM or the puny 4GB of your C: drive will quickly be overwhelmed.
Although I bought the iRAM for the speed ( and it
is snappy- but not earthshaking compared to a Raptor RAID0 array) I've come to appreciate the silence even more.
It's eerie really and I'll definitely upgrade to the SATA2 version when it comes out.