Since the updates are cumulative, once avast detects several days (don't know how many) with no updates, when you actually let avast attempt an update (once a week) it will be forced to download the whole database, instead of just the little chunks.
Maybe once a week is not enough to trigger this behaviour (as mentioned, I don't know). My point is that updating at least once a day (change the setting from 240 minutes to 1440 minutes), it would be less than 4MB in 1 week. Against that, updating the complete database is 44MB.
I certainly would like much more flexibility in updates for the future avast 7, but updating once a week is so simple (tray icon, update), that seems a little "too lazy"
. Of course, the goal is not to forget about it, but then update every 1440 minutes (once a day) and really forget about it.
[OT, but not much]
@
igor,
BTW, for avast 7, it would be nice if there would be some "schedule" and "rules" so to allow/block updates' attempts. For example, "don't attempt to update if the connection is not one specifically already selected"; or "allow updates' attempts between 8:00 - 12:00 only"; or "do not let updates' attempts between 15:00 - 18:00 and between 5:00 - 10:00".
An example of "schedule" allow/block could be something similar to the schedule rules of utorrent, just to give an example.
The utility of rules for specific connections is useful when using notebooks (and alike), so to allow updates under certain specific (high bandwidth, low cost) connections only, but block the attempt (as if it were set to "manual") if currently connected using a different (expensive) connection.
Just to be clear, "schedule" and "connection rules" mentioned above are not the same thing, but complement each other.
[/OT, but not much]