HI - I have a barebones (no MS updates or SPs) Win XPPro machine I am trying to get operational.

I want to backup my 'vanilla'  state prior to  moving forwards and I iniitally installed Acronis, but then decided to use Shadow Protect instead.

I de-installed Acronis.  Used JV16 Power Tools (last free version) to get rid of 'acronis' and 'trueimage home' entries - cleaned out pre-fetch - rebooted.

Attempted to install Shadow Protect desktop.  Error - about snapman.sys still exisiting.

Looked at Storagecraft kb doc about BSOD and snapman and Shadow.  Followed the KB directions - looked a the registry entries it said to look at - where snapman.sys was supposed to be listed.  None of mine listed snapman.sys.

I assume that my previous registry deletions got rid of the referecnes to snapman.sys, and now all I have to do is delete the driver.

I want to get Storagecraft's opionion before I go ahead though -  I'm having enough trouble getting this machine up, without another setback with a BSOD due to  ACRONIS.

Help is very much appreciated. deb
 

Hi Deb,

I know you said you uninstalled ATI and used JV16 to clean out the registry.  Here is a link to a posting by Nate a few months ago that might help.

http://forum.storagecraft.com/Community/forums/p/358/1517.aspx#1517

Hope this helps...

Thank you Bob.  The thread you refer to contains the same steps as the KB article that I followed.  None of the keys I checked contained snapman.  My guess is - by using jv16, I already de-registered snapman - and the only step I actually have to perform is  the physical removal of the driver.  I'll cross my fingers and give it a go.

Bob, thank you.  The thread you refer to contains the same steps as does the KB artilce that I found, and I did look at all the registry entries it mentioned.  But none of mine had snapman listed anymore.  My guess is that by using jv16 I got snampman correctly de-registered as a PHP filter - but the only thing it did not do was actually physically remove the snampman.sys driver.  I wanted some corroboration that I wouldn't be facing a BSOD - but I guess I'll cross my fingers and give it a try.