Suggestion: ramdisk image loading options
Posted: Fri Aug 27, 2010 3:29 pm
I would like to be able to have that image loaded at boot, but *not* saved automatically at shutdown. I can either select a manual save while in Windows, or perhaps a prompt at shutdown that asks if I want to save the image (with a timeout to accept the default the user specified).
I store my Windows profile on a ramdisk that is loaded/saved to an image at boot/shutdown. If it was loaded but not automatically saved each shutdown, this would allow me to always have my registry and profile in its pristine condition at each reboot, and undo any nutty stuff I or a program did during the last session. It would almost be like restoring a VM snapshot.
2) I would also like the ability to do a manual reload from image, and browsing of image files. I have several applications that are very disk intensive in reading/writing their home dir (and they are rally doing a lot of writes and using up the lifetime on my SSD).... but all of them combined are too large for a ramdisk. I could set up a ramdisk, say on X:, of 1GB, which is big enough to handle any one of the apps, install an app to X, and save the image. Then clear the disk, and install the next app to X:, and clear it.... and so on. Then when I wanted to run ABC, I could load the ABC image to the ramdisk, and run ABC from X:. When done, I can load the PDQ app image to the ramdisk, and run PDQ.
I store my Windows profile on a ramdisk that is loaded/saved to an image at boot/shutdown. If it was loaded but not automatically saved each shutdown, this would allow me to always have my registry and profile in its pristine condition at each reboot, and undo any nutty stuff I or a program did during the last session. It would almost be like restoring a VM snapshot.
2) I would also like the ability to do a manual reload from image, and browsing of image files. I have several applications that are very disk intensive in reading/writing their home dir (and they are rally doing a lot of writes and using up the lifetime on my SSD).... but all of them combined are too large for a ramdisk. I could set up a ramdisk, say on X:, of 1GB, which is big enough to handle any one of the apps, install an app to X, and save the image. Then clear the disk, and install the next app to X:, and clear it.... and so on. Then when I wanted to run ABC, I could load the ABC image to the ramdisk, and run ABC from X:. When done, I can load the PDQ app image to the ramdisk, and run PDQ.