I’ve downloaded 2.2 and it fixes the problem with forgeting rules, but the process cmdagent.exe is sucking up about 30% of my cpu. What does this one do, cause the cpf process takes more memory but hardly any cpu, and are there any known problems with Comodo running aside prevx1? I installed the both around the same time, and I’ve noticed longer startup time on my pc and a bit slower internet speeds…
edit: Comodo seems not to like running with my Desktop Weather program from the Weather channel, as soon as it’s closed, cpu usage is fine again…
Ok, the new installer works for me. My first impression of CPF is good. Some of the things I noticed
after using for ten minutes:
I don’t like the small fonts used when in some of the windows. Be nice if one could adjust this.
Beta doesn’t integrate with Security Center. SC is telling me that Kerio FW is not running, even
after uninstalling it completely. I was hoping that Comodo would get integrated in SC. I guess the KERIO
uninstaller did not do a complete job. Par for the course for most uninstallers. Is there a reg
tweak to fix this so SC recognizes CPF instead of Kerio?
The LaunchPad is fine for integrating the other Comodo components, but ther should be an option
to only bring up the components separately… To get the firewall, I have to right click LP -->>FW–>
Open.
When I open the CPF, it doesn’t remember my window settings. I prefer it to open maximized
instead of upper left corner. It does remember If I resize, but not if I maximize it. No big deal.
If this discussion should go to another forum, please let me know.
Just wanted to say that I’ve been putting v. 2.2.0.11 through its paces. I’ve accessed all of my internet apps, and have switched on the component monitor from the learning mode. All has gone very well so far. I think that it’s fair to say that several pay-for applications are going to be in trouble!
Hi there… I’ll answer what I can in the 4 minutes I have available
CPF is SC-enabled. However, other SC-enabled software can often be a little “lazy” in their uninstallation routines, leaving rubbish in the WMI databases that confuses Windows Security Center. Rest assured, this is not a Comodo issue. For some steps on how to perform the cleanup yourself, have a look at this post, especially the last bit… That should help.
3. The LaunchPad is fine for integrating the other Comodo components, but ther should be an option to only bring up the components separately.. To get the firewall, I have to right click LP/FW/Open.
What you suggest has been suggested previously and I believe Comodo are looking into providing this option (bless 'em!)
Ok, excellent instructions concerning wbemtest. Now, I need to know how to get SC to recognize CPF. I hope I won’t have to reinstall since I have already created quite a few rules and would like to avoid applying them again. When’s the “Save Your Settings” going to be implemented?
I see it’s in pending, but if you folks keep cranking out new releases, then I would hope this would get some priority. Should be a no brainer right?
Thanks for the support. At last I can give Comodo some plus points
Al
SC does recognize CPF after logging off and back on again. Should have tried that before posting.
Sorry. Might want to add that bit of information to the wbemtest post.
I tried using the new settings for the AVG programs with no change
My setup is a cable modem with Cox Cable and two mail accounts, one with ATT Worldnet and one with Cox Cable. The ATT account uses a secure connection because it is going through Cox Cable and has never had any problems. The Cox Cable account does not use a secure connection and I have never been able to use it without disabling the e-mail scanner in AVG. I never had any problems using Sygate Personal Firewall.
As an update to my previous post I finally got everything working with AVG and CPF
After further poking around I found that the rules changes I had made in the Application Rules section of the Security tab did not overwrite the previous rules Changing them in the Application Monitor section of the main screen and rebooting fixed the problem.
