I have been running CMF 2.0.4.20 for a few hours now [WinXPSP2 on x86; CFP 3.0.15.277; BOClean 4.25; AVG Free 7.5.5.16; WinPatrol Plus 12.1.2007.0]. The issue with the tray icon appears completely resolved.
Software conflicts still exist. I summarize here what I have found; some reported in other threads.
DropMyRights.exe must be added to the exclusion list; the applications it starts are all protected.
%windir%\system32\dumprep.exe must be added to the exclusion list.
%CommonProgramFiles%\Acronis\CDRecord\cdrecord.exe must be added to the exclusion list; without it, Acronis TrueImage 7 will not work; this likely applies to later versions of ATI as well. This issue may be related to the next item, since the same folder contains a copy of cygwin1.dll.
I have the Cygwin API installed to allow running Linux-like commands. Every executable (e.g., ls.exe, pwd.exe, grep.exe) must be added individually to the exclusion list; there are over 200 of these, so the task is unreal!
Without the additions to the exclusion list mentioned, any of these applications hangs, consuming essentially all of the available cpu time. Manual termination of the application is required, often through Task Manager. The Linux commands seem to produce their expected output to the command prompt before hanging.
The effects on the Linux-like applications could be mitigated with the possibility for CMF to use regular expressions (e.g., ?*.exe) or folder names in the exclusion list; the latter would exclude all procedures in the subject folder.
I have a problem: if i start the EAC application on installed CMF, the WINXP OS is freeze. Any earlier CMF versions is same situation generate on my machine.
What shall i do? :-\
I found a small bug in the interface, or maybe its something bigger. At the lower left corner CMF is telling me that the driver is not active and to reinstall CMF. But I already did that, could this just be an interface bug or it really is not working. :-\
I installed the new memory firewall, waited a bit before i switch off the computer. It was like 10h just before i switch the pc back. Seems CMF just took the cpu time away, both cvtres.exe instances got somehow the same high cpu usages (random, both below 50%): this is below 100% but definetly something abnormal (they won’t drop cpu usage to 00%). I’ve terminated the processes through taskmanager and just launched the “COMODO Memory Firewall” link from Start Menu but the interface must have some problems at me cause i only saw the four clickable buttons (see attached picture). I got no graphical problems with any other softwares (nor with games), ideas?
Part1: I killed the processes from taskmanager to avoid the cpu usage. Awaiting for futher ideas…
Tried CMF latest version and getting this error after rebooting: “Windows Command Processor Has Stopped Working”. It kept popping up several times on the screen.
Processor 64bit
Vista Ultimate X64
CFP 3 and Avast Free Edition
Installed CMF and after reboot the problem started to occur.
Killed the process and had to uninstall to fix the problem
cvtres.exe is not a CMF process. It is part of the .net 3.0 installer which microsoft ■■■■■■■ up so it can’t install properly unless done manually. It also effects shutdown if it tries to install then it will take forever to power off.
Perhaps you should add cvtres.exe to the CMF exclusion list. I have had to add several items to this list on my system (see my post earlier in this thread). The main symptom of the need for this is high cpu activity, approaching 100%. In each case where I have encountered this issue, adding the offending executable to the CMF exclusion list solves the problem.
Windows Vista 32bit. Running alongside Comodo Firewall Pro latest and Symantec AntiVirus 11. Instances of cmd.exe will not close when supposed to. They remain running and eating 100% CPU until closed manually. Rven as much as going to start → run, typing “cmd” and then “exit” from the command prompt is enough to trigger the glitch. Batch files using the command prompt do the same. However, the command prompt works just fine until it is closed. Adding cmd.exe to the exception list or shuitting down either CMF or CFP3 will not solve the issue. Only uninstalling CMF fixes it.
I’m starting to think its just a UI bug, I got the red light again telling me the driver was not active. After I rebooted though, it turned green again.
