Difference in speed and time.

[Nagan]

I unzipped a zip file containing say 2000 "MUTED" samples with three real time file (ACTION) settings.

1.Repair & DO nothing.

2.Repair , Move to Virus chest , Do Nothing.

3.Repair , Delete.

While unzipping 1 seemed to be very quick. 2 and 3 very very slow.

I have been using a competitor in another of my computers , which performs all the 3 choices  with the same (VERY FAST)speed and time. I wish AVAST looks into this.

Also why are the alert sequences only till 51 and another set of alerts. Why can't the alerts go on building till all the files are listed in that time gap.

[DavidR]

Why are you creating this new topic when it is related to the topic you already have on the go, http://forum.avast.com/index.php?topic=69231.0.

Igor one of the Avast developers has replied in that topic.

Not to mention your other related topic almost a duplication of the last link I gave above, http://forum.avast.com/index.php?topic=68680.0.

Creating multiple related topics just confuses the issue and duplicates effort for those trying to help.

[igor]

The difference in speed is caused by the fact that for repair, it just tries to repair (and probably fails) - while for removal actions a registry/autostart cleanup of associated items is also performed, which is kinda slow.

Again, your test is not a real-time scenario, so yes, it's probably slow... but I don't think we'll look into this. In the command-line scanner it's possible to disable the registry cleaning.

[Nagan]

Why are you creating this new topic when it is related to the topic you already have on the go, http://forum.avast.com/index.php?topic=69231.0.

Igor one of the Avast developers has replied in that topic.

Not to mention your other related topic almost a duplication of the last link I gave above, http://forum.avast.com/index.php?topic=68680.0.

Creating multiple related topics just confuses the issue and duplicates effort for those trying to help.

With due respect to you , they are entirely different.
The first link talks about hanging while taking action on detected files.
The second link is about an incompatibilty encountered in a earlier version which seems to have got corrected in the later versions , which I had written there.

The difference in speed is caused by the fact that for repair, it just tries to repair (and probably fails) - while for removal actions a registry/autostart cleanup of associated items is also performed, which is kinda slow.

Again, your test is not a real-time scenario, so yes, it's probably slow... but I don't think we'll look into this. In the command-line scanner it's possible to disable the registry cleaning.

Thanks for the reply. Agreed it is not a real time scenario.Well you can also take it as a  suggestion if not a priority now. By the way the competitor AV which I use is able to do that (all the three choices mentioned)without any fuss!Might be it is the method adopted.....if you can take it in the right spirit...