(XPH, 512 MB RAM, Athlon XP 2000+ CPU)
I've been testing several AV packages and one thing that caught my eye was the commit charge total (from XP's task manager) on my machine. For those who don't know, the commit charge total refers to the total amount of physical and virtual memory the computer is using at that moment.
After a reboot, the following commit charge totals were noted:
(with Avast 4.6.691 as the only AV) 155 M
(with AVG as the only AV) 132 M
(with eTrust EZ AV as the only AV) 124 M
(with Nod32 as the only AV) 120 M
Any ideas as to why the commit charge is relatively high when AVAST is running ?