My God, it's full of stars...
Dark Knight PC had a surprise for me Before Coffee.*
It's still in the process of doing updates to catch up with two years' development, but given how fast the drive is I hadn't noticed until I got a caution from Windows that it may need to be restarted after the next batch... of 87. So I shrugged and launched the update process before brewing some coffee.
I make coffee with a French press, and between boiling the water and the actual brewing process it takes me about 12 minutes to brew a pot. In that time, Windows had installed roughly a gigabyte of updates. Yep, it was done before the coffee was.
Right now Microsoft Security Essentials is sweeping through checking that nothing unsavoury snuck in during the process, and the only way I can tell is by checking the CPU usage (18%) as there's actually no impact whatsoever on web browsing. Contrast this with my positively-ancient workstation at the office, wherein its virus sweep** takes over an hour and renders the system practically useless for much of that time.
-- Steve's gratified that the fix seems to be working quite well, but there's more to do as soon as he can work up the ambition.
* Yes, I'm very late waking today... I woke up at about 3am with abdominal cramps and spent until 4am in the "reading room" making a dent in Vinge's Children of the Sky and the population of my intestinal flora. After that brain-and-lower-body workout and a glass of water, I guess my body decided it wanted a real night's sleep.
** Admittedly the office uses "Snortin' Norton" the Resource Hog, so this isn't an entirely fair comparison. MSE has a much lower profile, plus it actually has a slider on it letting users dictate how much of the system's resources it's allowed to use so you can trade a longer scan time for lessened impact on that system; for instance, on my tablet I have it set to use no more than 25% and any slowness resulting is indistinguishable from network lag when browsing.
It's still in the process of doing updates to catch up with two years' development, but given how fast the drive is I hadn't noticed until I got a caution from Windows that it may need to be restarted after the next batch... of 87. So I shrugged and launched the update process before brewing some coffee.
I make coffee with a French press, and between boiling the water and the actual brewing process it takes me about 12 minutes to brew a pot. In that time, Windows had installed roughly a gigabyte of updates. Yep, it was done before the coffee was.
Right now Microsoft Security Essentials is sweeping through checking that nothing unsavoury snuck in during the process, and the only way I can tell is by checking the CPU usage (18%) as there's actually no impact whatsoever on web browsing. Contrast this with my positively-ancient workstation at the office, wherein its virus sweep** takes over an hour and renders the system practically useless for much of that time.
-- Steve's gratified that the fix seems to be working quite well, but there's more to do as soon as he can work up the ambition.
* Yes, I'm very late waking today... I woke up at about 3am with abdominal cramps and spent until 4am in the "reading room" making a dent in Vinge's Children of the Sky and the population of my intestinal flora. After that brain-and-lower-body workout and a glass of water, I guess my body decided it wanted a real night's sleep.
** Admittedly the office uses "Snortin' Norton" the Resource Hog, so this isn't an entirely fair comparison. MSE has a much lower profile, plus it actually has a slider on it letting users dictate how much of the system's resources it's allowed to use so you can trade a longer scan time for lessened impact on that system; for instance, on my tablet I have it set to use no more than 25% and any slowness resulting is indistinguishable from network lag when browsing.