Understanding avast4.ini file

[Lisandro]

What do the following items mean?

Section [InetWD]
1. Sleep (Default: 40000 (40 seconds))

Section [UserInterface]
1. ErrorDlgTimeout (Default: 10000)
2. RespondTimeout (Default: 30)
3. VRDBBalloonShown (Default: 1)
4. ScrollResults (Default: 1)

Section [AAVM]
1. SuppressExpirationWarning (Default: 0)
2. NeverShowInfo  (Default: 0)
3. LogDiskChanges (Default: 0)
4. LogStart (Default: 0)
5. GradientStepMsg (Default: 20)
6. GradientStepInfo (Default: 50)
7. EventLogAnalysed (Default: 1)

Which are the values for the old [ODBC] section that are still working?

Thanks for the one which have patience to fill up this 

Igor, please, don't pretend you're not looking at this one 

[hyjaxltd]

Sorry, for posting twice im a lil retarded 2day.  I definitly appreciate your help and btw I pulled up the GUI and did it.  To many things to get running smooth b4 my moms PC willl be automated while im away   So is your post above for anyone or r u asking someone particular?

[hyjaxltd]

nevermind, can see why you need them!!!

[Lisandro]

or r u asking someone particular?

I'm asking to Alwil team programmers...

[igor]

Well, it's not as easy as you might think... I have to search all the sources for the occurrences, then find out where it's used and then try to guess what the hell does it really do   So, don't take my answer for 100% correct.

Section [InetWD]
1. Sleep (Default: 40000 (40 seconds))
- The interval of pinging the updating servers (to detect internet connection)


Section [UserInterface]
1. ErrorDlgTimeout (Default: 10000)

- some timeout for error dialog... have honestly no idea if/where it's used

2. RespondTimeout (Default: 30)

- not used

3. VRDBBalloonShown (Default: 1)

- specifies whether the initial VRDB baloon (shown once after the installation) was already shown

4. ScrollResults (Default: 1)

- corresponds to Enhanced User Interface setting: "Scroll session results"


Section [AAVM]
1. SuppressExpirationWarning (Default: 0)

- not used in avast! Home/Pro

2. NeverShowInfo  (Default: 0)

- suppresses display of (some) info messages, I think (silent mode for updates?)

3. LogDiskChanges (Default: 0)

- seems to log drive add/removal into event log, if set

4. LogStart (Default: 0)

- logs resident protection start into event log, if set


5. GradientStepMsg (Default: 20)
6. GradientStepInfo (Default: 50)

- didn't find any "GradientStepMsg" or "GradientStepInfo" occurrence, only "GradientStep", which has something to do with the color gradient of avast! info messages


7. EventLogAnalysed (Default: 1)

- not used anymore

Which are the values for the old [ODBC] section that are still working?

- none, I guess

[Lisandro]

Many thanks Igor... as far I have some spare time, maybe on weekend, I'll update the avast4.ini file thread...

Section [InetWD]
1. Sleep (Default: 40000 (40 seconds))
- The interval of pinging the updating servers (to detect internet connection)

Very useful to ones that are paranoid about pings...

3. VRDBBalloonShown (Default: 1)
- specifies whether the initial VRDB baloon (shown once after the installation) was already shown

I thought there was another setting for this one...

5. GradientStepMsg (Default: 20)
6. GradientStepInfo (Default: 50)
- didn't find any "GradientStepMsg" or "GradientStepInfo" occurrence, only "GradientStep", which has something to do with the color gradient of avast! info messages

Hmmm... I won't be able to discover who told me about that settings...

7. EventLogAnalysed (Default: 1)
- not used anymore
Which are the values for the old [ODBC] section that are still working?
- none, I guess

I'll remove them from the available settings.

Thanks again. Step by step will get all of them

[Snagglegrain]

Which value must I edit in the avast4.ini file in order to change the update frequency of the VRDB? 

I am thinking that weekly (rather than every three weeks) might be a good idea.

And a related question, does this VRDB file eventually grow quite large in size?

Thank you.

[DavidR]

That will possibly give you less repair potential. The VRDB keeps information on the last three generations of the VRDB, this spans 9 weeks, your plan would span just 3 weeks.

If a file becomes infected and it is one that the VRDB has in its database it will use that to repair the file, if that to fails (infected) then it uses the previous one and if that too fails (infected) it would use the final third version information to attempt the repair.

So if there is a previously undetected virus on your system, when it is included in the avast virus signatures then it will be detected, that duration could be greater than the VRDB Generation of only three weeks that you would have, effectively making it potentially unrecoverable. The three week interval is there for a good reason.

Having said that I do a manual Generation of the VRDB every other week as part of my weekly system maintenance, but I don't schedule that I prefer to do it at a time of my choosing.

If you still choose to do it, the VRDB RunInterval information is in page 2 of this Topic http://forum.avast.com/index.php?topic=1647.msg10271#msg10271

[Lisandro]

The 'files' (rather than file info) into VRDB are always clean.
The one-week period could be that much if you don't install many programs frequently. But, it won't harm that much too.

[DavidR]

Not if the file/virus is an undetected one at the time the VRDB is generated as I said, the generation would include information on a file that was already infected. I believe this was previously mentioned by Vlk or Igor.

[Lisandro]

Well, if Alwil team has a timetable of three weeks to add a signature, well, we must be worried about that period. I wish they have a better speed update time...

[Snagglegrain]

The three week interval is there for a good reason. ... Having said that I do a manual Generation of the VRDB every other week...

Looks like you think along my lines.

If you still choose to do it, the VRDB RunInterval information is in page 2 of this Topic

I have opened avast4.ini in notepad ,and the example you directed me to does not show there. Literally, "RunInterval" does not appear anywhere, under [VRDB] or anywhere else, in my avast4.ini file.

[Lisandro]

I have opened avast4.ini in notepad ,and the example you directed me to does not show there. Literally, "RunInterval" does not appear anywhere, under [VRDB] or anywhere else, in my avast4.ini file.

It's ok. When the option is not there, you should (could) add it.
Look the blue text here: http://forum.avast.com/index.php?topic=1647.msg10233#msg10233

[Snagglegrain]

It's ok. When the option is not there, you should (could) add it.

Great!  So I can add the line: "RunInterval 10080" if I desire a one week VRDB update, correct?

And what is your opinion on update intervals?  Three weeks?  Two?  One?

[Lisandro]

So I can add the line: "RunInterval 10080" if I desire a one week VRDB update, correct?

Yes.

And what is your opinion on update intervals?  Three weeks?  Two?  One?

Do you install software frequently? If so, three is better.
If you do not install software very often, you can set one week.
Two will be in the middle