Update: in June 2006, Rollback Rx was buggy as hell:
http://www.wildersse...ollback+firstdefenseThose problems seems to be gone.
And it seems that version 8, to be released march 2007, will be really nice.
The only reason I wanted to avoid FDISR is that it takes forever to create a new image, and I want to recover fast from a bad install. For that, RB rx seemed better suited.
However, I found this method to use FDISR as an 'bombproof uninstaller' (from
http://www.wildersse...5235&postcount=4):
I have pared down to a simple setup. I do a lot of imaging in conjunction with FDISR. Also I am a single partition person. My objective was first ability to recover or undo an install. Speed of both FDISR and imaging is very important. Speed for imaging, implies keeping the drive space minimized.
Also I don't care about going back to yesterday, the day before, etc. So....
On my c: drive I have my Primary which of course has everything I run. Then I have a secondary which is a stripped All it contains is Windows, and enough to feel safe online. It's only purpose is to provide a bootable snapshot.
I also keep an Archive on my primary, both on my second internal drive, and one on my external drive. These are update frequently. Update time is around a minute. I also keep an archive of the secondary snapshot
So if I want to test a program, I first update my archive, and then install in the Primary. If I don't like it I boot to my secondary and update my primary from the archive. I
This setup also means that even if I have to restore from the image I took when I bought the system(which has FDISR), I can load the secondary from the archive, boot to it, and the bring the primary update from the archive.
I have thoroughly tested this approach and it works beautifully. Also if i want I can keep several different configurations in archives and switch back and forth easily.
Pete
So I'm going to go with FD I think.