ATI Echo Workstation Build 8398 SnapMan.sys Issue
Here's some real WEIRDNESS about this product install, on several machines. Let me cite just one example:
I have installed ATIW Build 8398 on a computer that previously had Build 8345 installed. Because of problems with that older build, I had to download and install modules from Article 1514, including a replacement for SnapMan.sys, named SnMan380.sys.
I then uninstalled the older build, and completely expunged all the files and registry entries left over from the incomplete install Acronis performs (including SnMan380.sys, tifsfilt.sys, timntr.sys, and the Log & Script folders). Then, I went to %windir%\inf and removed all files with "Acronis" or "TrueImage" (or "True Image") inside, and completely removed the %windir%\PreFetch cache. I then rebooted. There are NO remnants of ATI left on this computer.
When I installed Build 8398, it installed TWO drivers, both SnapMan.sys (v3.6.0.446) AND SnMan380.sys (v3.3.0.380) in ....systen32\drivers, and creates entries in the HKLM\...\Services registry structure for BOTH of them. And, when I inspect the running modules (using Security Task Manager), ONLY the older *(obsolete?) SnMan380.sys is running!
Except for the names of the executable driver files, there is NO difference in the two registry keys.
So, why is only the older version of Snap running, even though both are "active" under Services, where does the ATIW Build 8398 installer get that file, and what must I do to resolve this apparent conflict?

- Log in to post comments