My boot time seems to have gone up. After the desktop is put up and before the startup music, the disk now crunches for a bit. WHen I look at the taskmgr, I see something called AVAST.SETUP (along with the other AVAST processes like UI). I would say there seems to be an additional 5-6 sec now from when the DT displays and when the startup music plays and the system completes booting. I went from the last major release to 1289 using the UI update. I have XP SP3.
The avast.setup is the avast update process, when you have an internet connection present it will check for updates.
Essentially this update check hasn’t changed, it is still done when an internet connection is detected.
-
In avast5/6 you need to edit (using notepad) avast5.ini the [InetWD] section of the C:\Documents and Settings\All Users\Application Data\Alwil Software\Avast5\avast5.ini (XP file location).
If you did a clean install of avast6 the folder names are slightly different, \Avast Software\Avast\ instead of \Alwil Software\Avast5\ other than that it is the same procedure. -
Broadband connections, add this line:
AlwaysConnectedWaitSeconds=120 and
AssumeAlwaysConnected=1 if not present (or edit AssumeAlwaysConnected=0 to AssumeAlwaysConnected=1)
[InetWD] AssumeAlwaysConnected=1 AlwaysConnectedWaitSeconds=120When complete save the changes, avast's self-defence module will ask for confirmation, etc. answer Yes.
The figure is seconds and the above equates to two minutes, you could try that and adjust upwards if required, 180, 240, etc.
I have broadband but do turn on/off my computer during the day and it’s off at night. My AssumeAlwaysConnected was 0 so I changed to 1. My UpdatePeriod was 240 and I changed to 120.
That portion now is:
AssumeAlwaysConnected=1
UpdatePeriod=120
Can you quickly explain what this did please? Does this simply delay the update check until 120sec after BOOT?
Update period has nothing to do with delaying the update you need to add the AlwaysConnectedWaitSeconds=120 line as I said in my post.
The update period is how frequently the updates are checked for (after having first checked), the default is 240 (every 240 minutes every 4 hours).
[quote author=DavidR link=topic=84353.msg686007#msg686007 date=1315430788]
“Update period has nothing to do with delaying the update you need to add the AlwaysConnectedWaitSeconds=120 line as I said in my post.”
Thanks so much for this little bit of info–I had just written to the support folks about making the ‘invisible’ update visible/dis-able(abul?) ???;stoppable, postpone-able–whatever–make it wait till AFTER I’d loaded my email!
Like jcoltrane above, I too, “have broadband but do turn on/off my computer during the day and it’s off at night”, and this has always been a major annoyance for me. Now I know how to make it do what I want! But shoot, shouldn’t HAVE to go edit the file–should be on the icon or a pop-up bubble or, at the VERY least, in the settings somewhere. Not all of us are ‘avast! Übertechnical’! Thank goodness, YOU are! ;-*
It doesn’t matter if you constantly turn it on and off, this is about delaying the update check when you turn on the computer, taking it out of the early stages of the boot. This for some systems, depending on resources and what you have loading automatically on boot can be a busy time.
I would suggest checking what actually starts on boot as many programs want to start on boot when they really have no need, media players are a common one that you don’t need until you double click a media file. So only essential applications should be allowed to run on boot, basically, windows processes and security applications.
So the point is to delay that check during a busy time, essentially you should only do this is it is actually causing a problem, which in most cases it doesn’t and that is why I believe it isn’t a UI setting. Thankfully avast has the avast5.ini file to fine tune configurations.