Author Topic: Understanding avast4.ini file  (Read 433354 times)

0 Members and 1 Guest are viewing this topic.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #15 on: November 03, 2003, 03:41:05 PM »
[VRDB]VRDB Settings



MergeIcons0Merged VRDB and Main icon = 1; Splited (2 icons) = 0



LastFileempty



FullCompleteemptyThe value is the result of the time() function, i.e. representes the number of seconds elapsed since midnight, January 1st, 1970 until the end of VRDB generation



Disabled0Enable VRDB generation = 0; Disable VRDB generation = 1



ScreenSaverOnly1Generate VRDB only when screen-saver is running = 1; Generate VRDB only when computer is idle = 0



RunInterval30240Time in minutes between to runnings of VRDB. Default: 60 x 24 x 21 in minutes (21 days).



IdleMeansSeconds8



ShowTaskbarIcon1Show the VRDB system tray icon; Hide icon (suppress) = 0



TagDontShowNextTime0



[Splash]Splash Screen Options



KeyUsage0If avast! is already registered = 1; if not (first run) = 0



iNews_Days7Number of days on which avast! iNews will be displayed after release. Default = 7. Repeated on [Simple] section.



ApplicationChestashChest.exe Default: ashChest.exe in Home version and aswChest.exe on the others.



ApplicationEnhancedashEnhanced.exe Default: ashEnhanced.exe in Home version and aswEnhanced.exe on the others.



[iAVS]Update (Conections) - Details Settings



RunningModeSilent* Normal or Silent



Progress1* Show update progress = 1; Do not show = 0



TrayIcon0* Show icon in task bar tray = 1; Do not show = 0



AskReboot1* Ask for reboot when needed = 1; Do not ask = 0



Push1* Enable Push iAVS (Professional Edition) = 1; Disable = 0



AddInfo1* Add information about performed action into e-mail = 1; Do not add = 0



« Last Edit: November 11, 2007, 06:15:55 PM by Tech »
The best things in life are free.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #16 on: January 11, 2004, 10:47:19 PM »
[Scanner] Decompression bomb protection.



MaxFileSizeToExtract_Scanner500000The maximum size of the file extracted from an archive. If the file in the archive exceeds the value it will be skipped. Note: a message with such a file will be treated as mail bomb. Default means 500Mb. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



MaxFileSizeToExtract_Resident100000The maximum size of the file extracted from an archive. If the file in the archive exceeds the value it will be skipped. Note: a file with such a file will be treated as file bomb. Default means 100Mb. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



MaxFileSizeToExtract_Mail30000The maximum size of the file extracted from an archive. If the file in the archive exceeds the value it will be skipped. Note: a message with such a file will be treated as mail bomb. Default means 30Mb. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



MaxCompressionRatio_Scanner90Maximum compression ratio, i.e., ratio of the unpacked file length to the length of the packed file in the archive. If the ratio exceeds the value, the file will not be extracted and therefore will not be checked. Note: a message with such a file will be treated as mail bomb. Default is 90%. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



MaxCompressionRatio_Resident90Maximum compression ratio, i.e., ratio of the unpacked file length to the length of the packed file in the archive. If the ratio exceeds the value, the file will not be extracted and therefore will not be checked. Note: an archive with such a file will be treated as mail bomb. Default is 90%. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



MaxCompressionRatio_Mail90Maximum compression ratio, i.e., ratio of the unpacked file length to the length of the packed file in the archive. If the ratio exceeds the value, the file will not be extracted and therefore will not be checked. Note: a message with such a file will be treated as mail bomb. Default is 90%. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



CompressionCheckThreshold_Scanner10000Maximum file size inside archive, beginning from which the maximum compression ratio will be checked (if enabled by MaxCompressionRatio switch). Default means 10Mb. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



CompressionCheckThreshold_Resident10000Maximum file size inside archive, beginning from which the maximum compression ratio will be checked (if enabled by MaxCompressionRatio switch). Default means 10Mb.If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



CompressionCheckThreshold_Mail10000Maximum file size inside archive, beginning from which the maximum compression ratio will be checked (if enabled by MaxCompressionRatio switch). Default means 10Mb. If the user do not declare the variables, default values will be used. Using 0 like their values, decompression bomb checking will be disabled.



« Last Edit: November 11, 2007, 06:16:22 PM by Tech »
The best things in life are free.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #17 on: January 12, 2004, 01:32:14 PM »
[WebScanner]



AutoRedirect1



HttpRedirectPort80*Port number to monitors the HTTP traffic.



LoadIsapiFilters1



ISAPIFilter1ashWsFtr.dll



IgnoreAddressempty



IgnoreLocalhost0



OptIn1The default value 1 means that the avast OptIn process is to be used and the unknown avast list and any extra user specified inclusions are to be scanned by the WebShield. The value Optin=0 means that that the WebShield will just scan all HTTP accesses by all processes. But, this way, for instance, WebShield will handle HTTP interface for fetching emails and if a virus is found, the WebShield virus dialog with the "Abort Connection" button won't work in this scenario. Clicking that button simply aborts downloading of the email (or all emails), even in the successive attempt to grab email (until WebShield is stopped, or the offending message is deleted from the server, possibly from another machine). That's why Alwil do not include mail clients to the default OptIn list.



OptinProcessempty



IgnoreProcessavast.setup



EnableLogging0Disable logging. Set 1 to enable. Restart WebShield provider (or whole computer in case of Win98). After troubleshooting, turn the logging off and restart WebShield otherwise the logs will grown indefinitely (they're not automatically deleted). Log files are: C:\Program Files\Alwil Software\Avast4\Data\log\ashwebsv.ws and C:\Program Files\Alwil Software\Avast4\Data\log\ashwebsv.log.



ZoneAlarmCompatibility1Turns on the compatibility WebShield with ZoneAlarm Professional version, i.e., disable the web shield transparent proxy mode with ZoneAlarm firewall because the cookie blocking features of ZoneAlarm is being used. The default is 0 (the value even exist in the default avast4.ini file) in order to turn off the compatibility mode with ZoneAlarm, i.e., the user has ZoneAlarm free firewall and WebShield works transparently. WebShield should be restarted (or whole computer in case of Win98) if this value is manually changed in avast4.ini file.



ModifyVistaSocketAutoTuning1 The current version of ZoneAlarm has a bug in Vista that is causing 1 second delay for each new connection (if avast! WebShield is active). So, this will indeed (subjectively) slow down browsing a lot. This is perfectly reproducible in Alwil lab. They have tried to contact ZA team many times. As usual, they never really acknowledged the problem (even though we clearly showed that the problem is not limited to the WebShield scenario). Changing the setting to 0 could help ZA users.



IgnoreLSPemptyUsed for troubleshooting blocked connections due to an interaction between the dll (name of the dll as the value of this entry) and WebShield provider. On Windows 98 or Me you'll need a boot. On 2k\Xp\Vista, maybe just restart the WebShield provider.



[Chest]



MaxSize256 Limit of the Chest in Mb. The computer must be restarted for any changes in the limit to take effect (at least on WinNT/2000/XP).



« Last Edit: January 02, 2008, 12:43:36 PM by Tech »
The best things in life are free.

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #18 on: March 01, 2004, 03:25:14 PM »
[AntiRootkit]



Exceptions<path> Path of the files to be excluded from the rootkit scanner.



WaitOnStart480 Time in seconds to compare processes and discover malicious hidden ones.



[SelfDefense]



ShowMoreInfo1



SelfDefenseEnabled1



IniChangeConsentProcessesNotepad.exe Processes allowed to change avast4.ini file. Separate values with commas (without space, e.g., IniChangeConsentProcesses=notepad.exe,youreditor1.exe,youreditor2.exe



[Admin]



RebootAsk Ask, No or Auto*/. In Auto, number means timeout in seconds to reboot machine



SvcAccount



ScheduleBoottimeScan0



[Admin.upd]



[WWWAccess]



ScreenWidth800



[SQL]



[WHS]



StartClient1Set if avast (on the workstation) should initialize the WHS
communication layer (for the communication with the WHS) or not. By default, the value is 1 (i.e., it does initialize it, if the WHS connector is installed on the machine). Sometimes, for troubleshooting purposes, it may
be useful to set it to 0.



ScreenWidthAll other entries in the section are either local data (a cache or so) or a "log" that something actually happened (e.g., that the firewall rules have been created). So, these settings are not really useful because they're "read-only" (changing them don't make any sense).



« Last Edit: September 09, 2008, 11:03:11 PM by Tech »
The best things in life are free.

Max M.Wachtel III

  • Guest
Re:Understanding avast4.ini file
« Reply #19 on: April 29, 2004, 04:22:59 AM »
I saw this in newsgroup anti-virus  -max

Can somebody tell me how to configure AVAST free version to scan inside .zip files?

yep, but I think you must hack a bit - Here is a text-file I found
(in addition I have added "LHarc" to the list as well
If on-access, yes, avast by default doesn't look for viruses in packed
files. However, it can be enabled. Look at the "deftasks.xml" file in
 the avast folder - all you need to do to enable scanning of archives
 on-access is to add the line

<STANDARD--ScanPackers>EXE;ZIP;MIME;RAR;ARJ;TAR;GZ;CAB;ARC;ACE;ZOO;BZIP2;Win
Exec</STANDARD--ScanPackers>

after the line

<STANDARD--InvalidEntry>1</STANDARD--InvalidEntry>

When you have saved the changed "deftasks.xml" file, reboot the system
to make the change permanent

skylynx

  • Guest
Re:Understanding avast4.ini file
« Reply #20 on: May 01, 2004, 11:36:14 PM »
Okay you sweeties, Avast loyals all.. I do realize the pesky blue box is just doing it's job to keep me informed of updates and missions accomplished...but PLEASE not every durn time I turn on the PC. It parks its little self right on top of my Favorites List so I can't  go anywhere until it takes its good ole time to leave! So, I go into Notepad and look up the Avast4 files. I open up DATA. Several dozen files come on, but not one of them is labled Avast ini. That's the file you say I need to look into, but I don't see Avast ini anywhere. Have any of you actually done this?  Please, Which one of those little file boxes has Avast ini. in it?  

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48512
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re:Understanding avast4.ini file
« Reply #21 on: May 02, 2004, 03:10:52 PM »
skylynx,
If you install the program to the default directory, then this is where you will find it:
C:\Program Files\Alwil Software\Avast4\DATA\avast4.ini
I hope that helps :)
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48512
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re:Understanding avast4.ini file
« Reply #22 on: May 02, 2004, 03:15:41 PM »
Section and KeysValuesNotes and value description
[InetWD] Define which Internet connection do you have
UpdatePeriod360Time (minutes) for update checking
UseRAS1If you have a dial-up = 1; If you have a permanent connection (DSL) = 0
AssumeAlwaysConnected0If you have a dial-up = 0; If you have a permanent connection (DSL) = 1
AlwaysConnectedWaitSeconds30Number of seconds to wait before attempting to update. The default is 30 but it may not be enough in some DSL systems. In this case, you can try increasing this e.g. to 60 (1 minute). That should be enough.

Dear Technical just thought you might like to know that when I increased my wait time to 60, it resolved all of my issues with some of the icons not showing up in the system tray.
Thanks for doing such an excellent job. :)
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #23 on: May 03, 2004, 03:44:08 AM »
Dear Technical just thought you might like to know that when I increased my wait time to 60, it resolved all of my issues with some of the icons not showing up in the system tray. Thanks for doing such an excellent job. :)

Oh, the excellent job was made by Alwil Software...
I just compile the informations posted in the forums.
Thanks.
The best things in life are free.

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48512
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re:Understanding avast4.ini file
« Reply #24 on: May 03, 2004, 02:57:07 PM »
Quote
Oh, the excellent job was made by Alwil Software...
I just compile the informations posted in the forums.

Technical,
You forgot to finish your statement with  " And clarified anything that required further explanation."
It's fine to post the technical info but without the interpretation, it's useless to most of us novices.
Again,
Thanks on an excellent job and please continue to be here and keep us informed. :)
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

skylynx

  • Guest
Re:Understanding avast4.ini file
« Reply #25 on: May 03, 2004, 04:07:27 PM »
Thanks so much for the info Captain Bob.  I did finally find the Avast 4.ini file and will work on removing the Avast all-too-frequent notifier.  Good thing I'm not in charge of the Enterprise, huh?  You may be an old fart, but you sure beat Cap'n Picard in the looks department!!  Happy warp drivin, all a ya. :-*

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48512
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re:Understanding avast4.ini file
« Reply #26 on: May 03, 2004, 05:46:08 PM »
Dear Skylyx,
Thanks for the compliment and yes, flattery WILL get you anywhere. :)
I think I'm even older than he is ;D
« Last Edit: May 03, 2004, 08:55:17 PM by bob3160 »
Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #27 on: June 05, 2004, 03:59:17 AM »
Just to explain that my study about the avast4.ini file:

Not all the configurations are by default, you can add the lines of specific configurations.

You can add the settings for both Home and Professional version without any trouble. If you have Home, maybe some Professional features won't be activated but, after all, you won't harm your installation.
The best things in life are free.

rloschmann

  • Guest
Re:Understanding avast4.ini file
« Reply #28 on: July 15, 2004, 11:12:18 AM »
Here is the message Igor sent me concerning the default values for colors :
Quote
Hello!

After some digging in avast! sourceshere are the default values of the AAVM message colors. When I checked them, I discovered some errors in the "high priority" and "fatal" messages (the colors were read from an incorrect key) - it will be fixed in the next version.

Note that the default colors may change in the future (unlikely, I'd say, but possible).

MsgTitleBkgColor1: RGB(0, 84, 227)

MsgTitleBkgColor2: RGB(61, 149, 255)

MsgTitleTextColor: RGB(255, 255, 255)

MsgInfoBkgColor: GetSysColor(COLOR_INFOBK)

MsgInfoTextColor: GetSysColor(COLOR_INFOTEXT)

MsgHighBkgColor: RGB(0, 0, 0)

MsgHighTextColor: RGB(255, 255, 255)

MsgFatalBkgColor: RGB(255, 255, 0)

MsgFatalTextColor: RGB(255, 0, 0)



InfoEmergencyTitleBkgColor1: RGB(200, 0, 0)

InfoEmergencyTitleBkgColor2: RGB(255, 0, 0)

InfoEmergencyTextColor: RGB(255, 255, 140)

InfoNormalTitleBkgColor1: RGB(0, 84, 227)

InfoNormalTitleBkgColor2: RGB(61, 149, 255)

InfoNormalTextColor: RGB(160, 255, 255)

InfoTitleColor: RGB(255, 255, 255)

Thanx Igor !!   8)

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67197
Re:Understanding avast4.ini file
« Reply #29 on: October 22, 2004, 06:30:10 AM »
Section and KeysValuesNotes and value description
[VRDB] VRDB Settings
MergeIcons1Merged VRDB and Main icon = 1; Splited (2 icons) = 0
LastFile
FullComplete1066508931Time of the end of VRDB generation
Disabled0Enable VRDB generation = 0; Disable VRDB generation = 1
ScreenSaverOnly0Generate VRDB only when screen-saver is running = 1; Generate VRDB only when computer is idle = 0
RunInterval30240Time in minutes between to runnings of VRDB (default = 21 days = 60*24*21)
Hi Technical,

I'd raised the question about interval between VRDB updates a while back, and you answered me briefly there and also steered me here.

The "RunInterval" line isn't in my ini (4-Home) -- do I simply add a new line for it?  And if so, does it matter where in that VRDB "paragraph" it goes, relative to the lines already there?

Thanks and best,
Mike


Mike, the changes on avast4.ini file could be done without a 'specific' paragraph order. You must be sure to enter the line in the correct 'section' of the file.

You must boot the system for some changes have effect.
Hope this help. Come back in this forum with certain frequency because more and more 'secrets' of avast! are being posted and discovered.  ;)
The best things in life are free.