Yes, this is a serious question. I have dropped all other methods and been trying what I am about to describe for a few months now. I really just wanted some input from others as to why or why not this would work for them. Yes, I understand some have specific needs or desires. But put that aside, and consider that you were using this method. What would you see as it's pros and cons. I ask because I like it so far, but I also realize I don't always think of everything, so others input can help to bring to light things I might have overlooked. First, I have 3 harddrives and a local file server with additional removable hdds/mem stix. I have a new hdd with my data I wish to keep on it, and usually rotate a new hdd in place every 3 years. I also have data backed up to optical or removable hdd if it is really important. So from the stand point of data integrity, this proposed setup is not one of 100% data integrity, but more for the small amount of data not currently backup up yet and for the convenience of having most of my stuff on a local hdd. So I have been using Macrium Reflect personal to make my images and Sandboxie along with SRP as the only forms of security. I am running as Administrator only because I do admin actions all the time and being a User is not conducive to what I do on a computer (other than playing games). I will lay out what I have done. 1. I always make my c: drive/partition small, usually <100gb, but lately only 20gb. I install XP here and customize it, installing only small softwares, nothing large like games or program suites. Just the basic everyday stuff. 2. I make an 'baseline' image of a normal install to 2nd hdd. 3. I put SRP rules in place for browsers, email clients, media players, and essentially any normal application that I might use that goes online. 4. I make a new image, something like 'srp ready'. 5. I create a few special folders that SRP applies to for downloading items into and testing. I install SBIE and force much of the same programs I use SRP on, along with those download directories. 6. I make another image titled 'net ready' or something. 7. I now have my basic images. As I add new settings or applications, I will fresh load one of these images, install the new features, then make a new 'current' image. The images I archive on a 1tb hdd, so I can go back and forth between images if one is not quite to my likings. I never store anything of value on the c: other than in very specific locations (download and storage folders) so that before I re-image I know right where to look for things that I might want to keep permanently (as imaging will remove those). 8. I install programs into c:, and copy/paste thier contents to storage drive and export thier registry entries if needed. Now when I restore an image most of my software actually live on d:\program files, and this keeps them across image restorations and I normally do not have any problem with this method. This way large programs can be installed there. 9. I have created a BartPE image that sits on c: , and there is an entry in the boot.ini that allows the boot option to start BartPE in ram. This way, when I want to restore an image to c: , BartPE boots in about 30 seconds, I start the Macrium plugin, choose my image file etc, and restore the image. The whole process takes about 5 minutes. This is largely due to the fact that my image is only about 4 gb because large programs are not installed into c: . It also means an average of 3 minute to create a new image. At this point, I have no firewall (but do use a router), no AV, no AS/AM, no HIPS. My browsers and other network apps are both (for the most part) restricted to User level and forced into a sandbox that is fairly restrictive. I have done some other things like take user rights away from some directories and registry keys. So, that is it. Nothing really fancy. A virus could attack, a malware could install. I might not even know it (except for the fact that I know what processes run etc etc). It is thus far been the most pleasant security setup I could have. I reimage when I want because my c: does not have anything really to lose in it. What would you think about running this? Good or bad? Sul.