About Home Edition

Avast Free Antivirus / Premium Security
1

Hi,

I saw in the Pro Edition that all the packers wasn’t selected.

In Home Edition, the packers are selected by default or how can I know wich are selected?

Thanks

2

You mean in the on-demand or on-access scanner?

Please be a bit more specific.

Thanks
Vlk

3

I mean on-acess, but you can tell about the on-demand too :wink:

4

?

5

The settings in Home and Pro are identical. The difference is that in Pro, you can customize them. On Home, you can’t.

6

With your reply, I can conclude that the Home Edition doesn’t have all the unpackers enable, right?

7

For the on-access scanner, you are right.
In the on-demand scanner, you can enable all supported packers by the checkbox “Scan archive files”.

8

OK, thanks for your info :wink:

9

We, shgoh and I, tried a lot to ‘solve’ this issue… I mean, the deftasks.xml could do it right? But, it is reloaded after boot and all the customization is lost… :frowning:

10

Maybe a deftasks.xml automatic generator could be created ?

Someone interested ? ;D

11

Le Doc, each boot, a ‘new’ deftasks.xml file will be ‘created’ according to the defaults of the program. Any changes will be lost…
Do you mean an automatic generator of the ‘default’ file? I think it won’t be possible as it is defined somewhere ‘inside’ avast code.
Of course, I can be completely wrong as I am not a programmer ::slight_smile:

12

Hey, as I said about 10 times already, the changes in the deftasks.xml do get lost but the ones in the actual configuration storage DO NOT. These are of course persisted!!

Please re-read my original post… :slight_smile:

13

Don’t get angry with us, please 8)

I do not found your original post but I’m confused: what is ‘actual configuration storage’?
For me, the configuration are stored into Windows Registry, avast4.ini and deftasks.xml file… What am I missing?

Excuse me, Vlk, I really do not understand deftasks.xml. Sorry boring you, but I tried :-\

14

I believe the actual storage is the Avast4.mdb file when Database=ODBC (and probably Avast4.xml for Database=XML? just guessing…)

15

I’m not angry. It’s just that no matter how hard I try to explain I don’t quite seem to be understood… a bit frustrating, gotta say… :slight_smile:

Here’s the original explanation: http://forum.avast.com/index.php?board=1;action=display;threadid=5492;start=msg40916#msg40916

The " Configuration Storage" is indeed the avast4.mdb in case of Database=ODBC and avast4.xml in case of Database=XML. In short, the file where avast stores its current configuration (besides the ini file).

16

We’re lazy and stupid… Now we don’t understand this you posted before:

The reverting-to-the-original-version thing you're seeing is a consequence of the fact that deftasks.xml is normal part of avast installation and therefore the avast auto-repair feature always replaces it to the original version. However, this is not a problem as the "import" procedure from the modified version is already done at that moment.

Please, help me on my thought:

  1. avast loads
  2. the user changes some settings
  3. the user runs the repair function and deftasks.xml is ‘restored’ to original state
  4. boot
  5. What happens with the configuration?
    Between which step the configuration of number 2 was saved?

If I understand correctly, among the configuration stored in deftasks.xml are the archive file types to be scanned ‘on-access’, aren’t they?
On-demmand you can check ‘all’ archive files to scanned…
How to do it on-access?

See Igor’s post:

For the on-access scanner, you are right. In the on-demand scanner, you can enable all supported packers by the checkbox "Scan archive files".

Can you teach me? ;D

17

sorry vlk…it’s kind of misleading…but then now we all understand the the configurations in deftask.xml is passed on somewhere upon reboot :slight_smile:

but like what technical just mentioned above…it seems a little contradicting? :stuck_out_tongue:

18

In short, on-access is avast Home protected by default into all packers available? It seems not… You should change any configuration to achieve that but, after boot, things come back to default, ie, non protected.

Sorry if I’m mixing and messing things…
I just want to understand 8)

19

technical…from what i understand from igor and vlk…we definitely need to add those lines into deftask.xml in order to scan archives for on-access (home edition only)

but then after you edited the deftask.xml…because it’s part of avast installation…it gets back to its original…

the trick here is that before it gets back to its original state…the configurations from deftask.xml are passed onto some configuration storage…which is avast4.mdb in case of Database=ODBC and avast4.xml in case of Database=XML.

therefore…according to vlk…no settings is lost!!! ;D

so i assumed that only changes made to deftask.xml are transfered to the configuration storage…hence subsequent reboots does not cause the settings to be lost…

but then…just my curiosity…how do we revert those settings in the configuration storage? 8)

20

Isn’t it saved in the database? I have enabled all packers and stuff on my home edition. And even though it’s reset in the file they still are active in the Access database… I followed this info:

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

EXE;ZIP;MIME;RAR;ARJ;TAR;GZ;CAB;ARC;ACE;ZOO;BZIP2;WinExec

after the line

1

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