I don't think it was a case of avast fowling ZA but the bug in ZA when run under Vista as mentioned by Vlk.
Now with ZA running under Vista for some reason the transparent functionality of the web shield proxy was disabled. So it wasn't scanning anything, even when you stopped it running on boot there are as Tech said some virtual device drivers loaded in the registry legacy keys.
avast may well have seen those and disabled the transparent proxy, but that is speculation on my part. Or when asked about the compatibility question you answered incorrectly for the ZA version you had and that would disable the transparent proxy, I think this is the more likely reason.
As for double click issue, it would get past the web shield if the transparent proxy wasn't enabled then nothing was being scanned by the web shield.
Whoa dude I run Xp pro.
I have come to realize the problem is with ZoneAlarm Pro 6.5.737
One person I recommended Avast! to is running ZA Free 7.x. in Xp Home. She does not have the same problem I did.
My son's computer has XP Pro with Zonealarm 6.5.737 free. He does not have the same problem.
I don't remember Avast! asking about ZoneAlarm during the installation. If it had I know what version I have.
(I have big issues with ZA Pro. Another topic maybe.)
I did not mention before that I removed everything Avast! from ZA permissions list and rebooted.
ZoneAlarm should have asked about for new permissions for at least two Avast! services on startup and it did not.
So I uninstalled Zonealarm pro. Then tried again at eicar.org and Avast! worked as it should on the HTTP download it did not work on the HTTPS download. Can not have everything. I am glad I found and fix the problem.
I think Tenny should look at his software firewall.
Who is vlk? And why is he/she accusing me of running Vista
.