I'll try that Client Security v2.0 update from Symantec too.
I'll try that Client Security v2.0 update from Symantec too.
The update went fine. It asked me to insert the CD-ROM and then the update started. Now the version numbers are Client Firewall 7.1.0.1400 and AntiVirus 9.0.0.1400
And... The Windows Security Center now shows the status.
Thanks. Very helpful thread.
one of the 450 reasons I Will never install that piece of shit SP2 again
must be the beverly hills version.Originally Posted by {I}{K}{E}
yes, yes, i know where the door is.
aside from my from idiocy, how is it i have version 9.0.3.1000 (not installed mind you, but i dloaded a few days ago
Last edited by Mïcrösöül°V³; 02-01-2005 at 12:23 AM.
And I thought I was anal, when it comes to my computer!
9.0.3 seems to be the latest version (didnt know that thnx)Originally Posted by Mïcrösöül°V³
I found that 9.0.3.1000 version myself and downloaded it. As an expirament just for giggles and yuks, I copied my share of SCS v2.0 to my harddrive and replaced the previous 9.0.0.338 files with this newer versions. I compiled the new share and installed it upon another computer. SCS installed correctly without error, however the anti-virus version still reads 9.0.0.338. SP2 failed to monitor it's status as well until I patched it. I wonder if I did something wrong during the file swap or if something else alittle more out-of-my-league is going on?
Out-of-curiosity: what exactly are the changes between these newer versions and 9.0.0.338 . Being that they are all essentially "9.xx" at heart, I cannot imagine that it could be much.
did you reboot after installing?Originally Posted by Izagaia
I previously had the original, un-altered copy of SCS installed. I un-installed that completely (I did not remove any of the usual crap often left behind such as program folders or registry keys though) before my attempt with my self-compiled copy. Rebooting of course each time for the un-install then install.Originally Posted by {I}{K}{E}
I will try this again on a freshly formatted system soon.
Now that you posted your results it has reminded me of why I thought (previously in this thread) that installing the later version "on top of" wouldn't work.
I had tried the same thing as you, Izagaia. Except that I tried to integrate the 9.0.2.1000 files into the installation (removing the ...338). The ...338 showed up after my test setup also. I then tested it on a fresh Windows install and guess what... the 338 was still there.
I have no idea where or how it got the ...338 version.
Bookmarks