One thing I've been wondering for the longest time is why ClamAV and ports such as this must require us to update the entire thing every single time. It's not as bad on a GOOD linux system (like Debian and distros based on it for example, but some others as well) where you can just run the package manager and it updates almost automatically (I don't like 100% automatic either, but I like the way it's handled on Ubuntu for example.) But some distros have the same problem as Windows due to staying far behind in the package system, and that problem is that the user must manually update the entire thing by hand every single time. If ClamAV and ClamWin updated at normal intervals, this wouldn't be so bad, but, basically every single time I run ClamWin it informs me that I need to update the client as it's badly out of date.

So what I'm wondering is why it can't be more modular or something. Some sort of system where it can update not just the virus definitions, but the client itself when you tell it to check for updates. Even if no modular kind of thing is possible or reasonable, in the past I've seen some AV programs in the past simply queue up the update and change the client over as soon as the user exits (or answers yes when it asks to restart after aquiring the update.) Couldn't ClamWin do this?

there is already an update system, it was tested by some users, but now clamwin will redirect you to an incremental updater (~200kb) yes it's not fully automated but still useful

The problem isn't getting to the update exactly. The problem is the fact that you must essentially reinstall the actual program every time a major update is released to keep from falling behind (and the thing is that you really need to stay as up to date as possible since its the newest viruses that are the most likely to infect you usually.) With ClamWin (and ClamAV) these major updates that change the main program occur maybe as often as once or rarely even twice a month, so to always stay up to date one must essentially reinstall the program completely once per month.

Also though, I must admit that it bugs me a little on principle that the update option isn't always actually updating since it will leave the job incomplete at times. IMO that's the hallmark of a faulty update system if it can't always actually update...

I think we all make the same mistake of wanting it "yesterday," but it's generally more important to keep the signatures updated than to update the program itself the very second a program update is available. You still have pretty good protection even if you are using the previous ClamWin "model."

Now, I would like to have Version 1.0 yesterday!

Regards,