Please uninstall previous version before installing it. But while uninstalling, you can choose not to delete the existing safelist databases. So, the previous rules applied by you will remain with new installation.
Thanks for your co-operation in building this product bugs free and stable. Please keep it up.
I disabled CAVS active scanners, enabled the active scanner of NOD32 and everything went fine.
Then just for curiosity wanted to test how my system would react with both CAVS and NOD32 enabled.
Made a little pray, reanabled all features of CAVS and a miracle happened. Both Antiviruses with maximum protection coexist.
I’m glad the AV beta doesn’t trigger a BSOD like the firewall. I like the AV. It is very simple to use. Although I’m not a newbie to computer security, I like programs with a simple interface. I also like the fact that you guys have a filesubmitter. It only did work always as it was supposed to in the previous beta. I hope this is solved in this one (I did used it yet). I’m also performing a full system scan. I’ll post later how much time it took to scan the entire system and possible false positives (if there are any).
Before trying it remember to deactivate NOD32. AMON is the most important and you must disable also its “automatic startup”. For doing this open NOD32 select AMON->Setup->Security-> uncheck “Enable automatic startup of AMON”.
If it gives you a BSOD after you reenable NOD32, you will need to reboot, enter in safe mode and then:
You’ll know what a BSOD is when you get to see one. After that, you’ll never forget what a BSOD is. You get one if something went wrong in windows (during boot, in windows, …). When you get to see that, windows stops working and you’ll need to reboot. The BSOD itself is a blue screen with a lot of information on it, such as technical info, …
Hi YANKEE,
This hal.dll isuue is not yet reproduced at our lab. We had put the log creation to find which process is deleting the dlls. Can you pls send/uload the troubleshoot log. You can get the log at %Documents and Settings%\All Users\Application Data\comodo\Comodo AntiVirus\TroubleShootLog\cavasm.log
Dear Kishor : I really whished I could help you out on this one but… I formatted my HD in an attempt to copy my other HD to it with CasperXp( also invain) … BTW how did you know it was that Hal.dll he asked for?
Here is what happened :
In a first reaction I did copy this hal.dll but after that he asked another dll (I believe it was something like “nto…”) after this I got into a panic and formatted the HD… and now I am in deep trouble : sorry again !!! :-[
It would be an ENORMOUS help to us if you would try the beta of CAVS again.
The “missing HAL.DLL” problem has, so far, only affected about a dozen users. I used to be one of that dozen, but I haven’t had a re-occurence of the problem since upgrading to the latest beta. As Kishor stated, Comodo have not been able to reproduce the problem in their labs and urgently need the “cavasm.log” file from an affected system to find out what is causing this.
Would it be too much trouble to ask you to reinstall CAVS, knowing that it could cause your system to crash again?
I’ll try to do my best this evening when I am home … but why doesn’t my crashed HD except a copy from my other HD ? I couldn’t accomplish it with neither CasperXp OR partition magic …something is holding them back! I find this strange because I formatted this crashed HD and there is nothing left on it ! Maybe I should try it in safe mode ??? Every help is welcome ! (:HUG)
