B
Bill Sanderson
I can understand your frustration. I'm not clear myself on what happens
with the expired code---I've managed to update all my machines before the
year-end. I believe you should get a notice at the time of a scheduled
scan, and I also believe that on startup, it should do an update cycle that
should invoke the automatic download of the new code version. However--it
doesn't sound like either of those happened for you.
The beta1 code is largely unchanged from the third-party product Microsoft
bought a year ago. Beta2, which is expected soon, will be developed by
Microsoft to their standards. It will be significantly different from
beta1.
My take on what is left behind after an uninstall is that it is
conservative--i.e. if you do an uninstall and reinstall, you retain current
definitions, custom settings, access to quarantined items, etc. Perhaps
there should be a "REALLY uninstall" option--but there isn't.
I've gone through a year of this beta without looking into what is kept in
the registry by the beta1 app--so far, registry fixes haven't proved
necessary for the general run of newsgroup questions here--although there is
a large class of "install" issues which I've stayed clear of lately because
I don't feel I have a solid answer to any of a number of "numbered error"
install issues. Perhaps some of these might be resolved through work in the
registry, but I'm not comfortable with advising about that in a forum with
the mix of novices and experts we find here.
There are more than 18 million users (counted by machines taking up
definitions) of this beta. If a large proportion of that audience were
having the problems you've seen, we'd be swamped here. I can attest to
having successfully updated via the Microsoft link--individually, largely,
on perhaps 4 dozen machines in various offices and homes. I can also attest
to having seen the wrong code downloaded--including, I believe,. once via
the autoupdate mechanism, which was a real surprise. The load balancing and
dns mechanisms involved in the download site are complex, but this download
has been out there since November 21st. I suspect there is more to the
story than simply a rogue server at Microsoft's end--but I've never managed
to pin the problem on anyone else.
--
with the expired code---I've managed to update all my machines before the
year-end. I believe you should get a notice at the time of a scheduled
scan, and I also believe that on startup, it should do an update cycle that
should invoke the automatic download of the new code version. However--it
doesn't sound like either of those happened for you.
The beta1 code is largely unchanged from the third-party product Microsoft
bought a year ago. Beta2, which is expected soon, will be developed by
Microsoft to their standards. It will be significantly different from
beta1.
My take on what is left behind after an uninstall is that it is
conservative--i.e. if you do an uninstall and reinstall, you retain current
definitions, custom settings, access to quarantined items, etc. Perhaps
there should be a "REALLY uninstall" option--but there isn't.
I've gone through a year of this beta without looking into what is kept in
the registry by the beta1 app--so far, registry fixes haven't proved
necessary for the general run of newsgroup questions here--although there is
a large class of "install" issues which I've stayed clear of lately because
I don't feel I have a solid answer to any of a number of "numbered error"
install issues. Perhaps some of these might be resolved through work in the
registry, but I'm not comfortable with advising about that in a forum with
the mix of novices and experts we find here.
There are more than 18 million users (counted by machines taking up
definitions) of this beta. If a large proportion of that audience were
having the problems you've seen, we'd be swamped here. I can attest to
having successfully updated via the Microsoft link--individually, largely,
on perhaps 4 dozen machines in various offices and homes. I can also attest
to having seen the wrong code downloaded--including, I believe,. once via
the autoupdate mechanism, which was a real surprise. The load balancing and
dns mechanisms involved in the download site are complex, but this download
has been out there since November 21st. I suspect there is more to the
story than simply a rogue server at Microsoft's end--but I've never managed
to pin the problem on anyone else.
--