PDA

View Full Version : ATI Removal conflict with Rollback?


Baldrick
October 25th, 2008, 03:57 PM
Hi

I have ATI 11 installed (used for imaging) but now that I have installed Rollback Rx I am thinking of uninstalling ATI (especially since I believe that the two installed together may be the reason for an increased system boot time since Rollback was installed...snapman.sys may be the culprit).

Question is therefore do I have to uninstall Rollback before I uninstall ATI given that both delve into and potential change the MBR. Or can I just uninstall ATI as normal (and then manually remove the dregs, ie, snapman.sys) ???

farmerlee
October 26th, 2008, 06:28 AM
No you shouldn't have to uninstall rollback.It should simply be a case of doing a standard ATI uninstall. You could always just rollback to a snapshot before you installed ATI (assuming you installed rollback first of course :)).

Baldrick
October 26th, 2008, 09:19 AM
-{ Quote: "No you shouldn't have to uninstall rollback.It should simply be a case of doing a standard ATI uninstall. You could always just rollback to a snapshot before you installed ATI (assuming you installed rollback first of course :))." }-
Thanks, will give it a go (after taking a full image with Rollback...of. course;) )

Aaron Here
October 26th, 2008, 12:27 PM
-{ Quote: "....Question is therefore do I have to uninstall Rollback before I uninstall ATI given that both delve into and potential change the MBR. Or can I just uninstall ATI as normal (and then manually remove the dregs, ie, snapman.sys) ???" }-
When I removed ATI with EF active, it seemed to uninstall ok but I have since noticed that there are several 'Acronis' registry entries that were orphaned and can't be removed (they produce an error on any removal attempt)! :-\

Jo Ann
October 26th, 2008, 04:21 PM
-{ Quote: "When I removed ATI with EF active, it seemed to uninstall ok but I have since noticed that there are several 'Acronis' registry entries that were orphaned and can't be removed (they produce an error on any removal attempt)! :-\" }-
Aaron,

The problem you will usually run into with such difficulties is one of permissions. Once you have found the entry in regedit, try right-clicking on it and setting the permissions to 'full control'. That may do the trick. ;)

JA

Baldrick
October 26th, 2008, 06:32 PM
Thanks for the replies Both

Decided to do some 'trawling' on this subject and cam up with the following:

http://www.wilderssecurity.com/showpost.php?p=1120006&postcount=4

This may be of assistance Aaron re. seeing if and how it handles those Registry entries that you referred to.

I plan to do a normal uninstall using the uninstaller provided and then double check the instructions provided to make sure that all is removed.

;D