|
Scotter, I don't know about a "Second Compatibility Update." Getting all the important Updates was the very first thing I did after installing XP. And when I check now, my system is up to date. So I most likely have that "Second Compatibility Update," unless they're parking it somewhere that I don't know about.
This may be pertinent: I do run NAV 2002; and I also have APC's updated (for XP) software for my Back-UPS Pro 500 installed. I followed ZA's instructions about uninstalling very carefully, and that didn't cure the problem. At the time, I did not have a Ghost image of XP that didn't have ZA in the system; so, later, when nothing else fixed the problem, I reinstalled XP, got everything back up to speed, working fine (without ZA), then made a Ghost image of XP that had no trace of ZA anywhere in its system. Having that, you can feel brave. So, once again, I installed ZA to this cleansed system.
This time, it functioned beautifully, with this one exception: ZA wouldn't start at Startup, even though it was checked to do so (read my above posts). Now, strange thing is, this problem didn't occur with previous installs of ZA. I suspect this could be happening on some other user's systems, and they don't realize it, simply because they never shut their computers off as I do -- every night, and sometimes several times in a day. That problem is no big deal, and sure, I could live with it. But not knowing what really causes it haunts me. So, once again, to hell with ZA. This time, I just restored my Ghosted Image that didn't have ZA on it. And, for now, at least, I'll just use XP's built in firewall. But thanks, anyway, Scotter, your input is truly appreciated.
jaded
jaded
|