Sorry, if it has been mentioned. There is a problem with the HIPS.
See the picture attached. There should be buttons ALLOW and BLOCK (or sth. like that) on the form. Ideed, there were the first 2 or three times, it appeared. After that the buttopns disapperared and I could not remove the form!
That is why, I had to disable the HIPS.
yes I got same experience. The culprit was the GUI display, DPI setting in my case. When it set to 96 dpi (normal) everything is OK. When I set to 120 DPI then no allow or cancel button.
It said that they will correct this GUI problem, but later (no priorities…?)
Thanks
fhkh
* Windows XP (SP2) / Windows 2000 (SP4 or later)
* 50 MB available space on your hard drive
* 128 MB RAM
* Intel Pentium 300 MHz processor (or equivalent)
Note - Not compatible with Windows 9x systems
Now here is the kicker
Windows Xp Professional Sp2 really requires at least 256mb of ram to run at a snails pace. A Good rule of thumb is to remember that application requirements fall on top of the pre-existing requirements of your Operating system, as your OS will be running various processes that will require active use of allocated memory. It is in my opinion doubtful that your system will ever be able to run Comodo faster then it already is. The requirements listed on the website in all likely hood are the requirements of the scanner and the scanner alone and not the requirements of the interface and windows UI components. Keeping in mind that those requirements are for Version 1.1 and not the current Beta Builds which include new features that can further tax a system that already struggles to meet the minimum requirements of the OS that is running. I know the box says 128mb, but when you add service pack 2 you added the need for an additional 64mb of memory to account for the added systems and features that run as services after the installation of sp2.
OK Thanx for your advice, have bought some more memory and things are looking up
One other problem, I can’t submit the safefile list to Comodo, I keep getting “Cannot connect to FTP server” message, is this a firewall problem or a bug?? I’m using the inbuilt windows XP SP2 firewall.
Note to Dev Team: This occasionally occurs even with 96 DPI, so it’s not just related to this. I have primarily noticed it when installing new software, if I forget to disable HIPS before exiting CAVS (since the HIPS will still be running).
I ran the “Bootlog XP” program to see why my system was still booting slow after upgrading the RAM up to 384 mB, and I discovered that CAVS tries to launch its submit program (CAVSUBMIT.EXE) an impressive 17 times during the startup, but still won’t send the user profile database that was created during a on-demand scan (I think it contains about 3000 files).
This action is causing my cpu to run at a continuous 100% for about ten minutes after the boot cycle should have finished. And it still says “Cannot connect to ftp server”. Grrr.
Check out the log file which BOOTLOGXP created and you will see what I mean.