Computer people: advice on virus checker
Monday, 14 June 2004 20:06![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
This is one for my computery friends:
I use an AVG virus checker, which I update once a week and which runs automatically once a day. I've been used to it taking about 20 minutes to run its daily test (of the whole C drive), or more if I am using my computer at the same time.
However, for the last couple of days it has suddenly been taking only about 10 minutes to run the same test. Nothing significant has changed about my C drive, so why might this be? And should I be worried: could it means there are parts of my C drive which now aren't being checked for some reason?
Everything else seems to be in full health, by the way.
Hope someone can help!

I use an AVG virus checker, which I update once a week and which runs automatically once a day. I've been used to it taking about 20 minutes to run its daily test (of the whole C drive), or more if I am using my computer at the same time.
However, for the last couple of days it has suddenly been taking only about 10 minutes to run the same test. Nothing significant has changed about my C drive, so why might this be? And should I be worried: could it means there are parts of my C drive which now aren't being checked for some reason?
Everything else seems to be in full health, by the way.
Hope someone can help!

no subject
Date: Monday, 14 June 2004 17:50 (UTC)My company uses AVG, and at last count it was taking ~30mins to do a complete scan on my workstation with it's gob-smackingly enormous *irony bell* 9Gb HDD, whle this (my own) PC with the 240Gb drive takes ~10mins; used to take bloody ages. I figure they've just honed what file types are being checked.
Anyway: if the guy I work for is happy to use AVG, I'd trust my life to it (he's so anal about security it hurts to watch). More news if it happens.
no subject
Date: Wednesday, 16 June 2004 07:33 (UTC)However, what people forget is that the way to prevent viruses entering a system is to prevent them being *written* to the disk, rather than prevent them being *read* from the disk, that way there is no chance they'll infect you. If that were possible, virus scanning of this nature would be unnecessary.