CPF was terminated?!

I use CPF 2.4. It seems like it was terminated somehow. Let me explain:

  1. I downloaded AutoCAD from Autodesk, as a 1.5 GB large ZIP file.
  2. I extracted this ZIP file on C, having only 1.8 GB free disk space left.
  3. Probably this disk space wasn’t enough, because an error message came up.

Now, this error message is the very key to this problem. Unfortunately I read it very fast and then clicked it away. But I remember it was something about Visual Basic, C++, and Comodo Firewall. Nothing about “low disk space”, as one would expect. Then the firewall tray icon disappeared. I couldn’t believe what I say so I started the task manager, and no cpf.exe was running.

I really don’t have a clue what happened here. BTW, there was no Windows warning message that the firewall was turned off (and the built in XP firewall is turned off). Could this mean that CPF actually was running anyway, even though I didn’t see the tray icon, nor cpf.exe in task manager?

EDIT: I think I’m going to try this procedure again, to see if the same thing happens, then I will record the details!!!

Now I quickly tried this procedure again, but this time no problem with CPF. Only low disk warning in tray (this happened the first time as well). By the way, I extracted with IZArc. Anyone has an idea why it is only possible from C, not from an other partition? The last weeks I’ve had a lot of problems in Windows, concerning installers. Now obviously zip archives too. :-\

Resurrecting this because I can find no better thread.

Randomly, (say 3 in 7) when booting to Windows XP Pro, I have a balloon in tray reporting that I have no Firewall protection. I acknowledge that and when I go to windows Firewall Centre the advice is that Comodo is protecting me. A couple of times I have got to that window to see that protection actually ‘arrive’ as it were!

This begs the question which I presently cannot see addressed here. Should one have both Windows and Comodo Firewall running or be content with the Comodo one alone?

In the past…other forums and before the arrival of Comodo…I believe the consensus was not to run the windows Firewall in unison with other firewalls, ZoneAlarm for example.

Is there a factor to be considered if one is connected via a router that has Firewall incorporated?

I just must add that Comodo seems the ‘bee knees’ (UK version of not at all bad!)

Welcome to the forums, Dragoon ~

I’ll refer you to the ***FAQs/Threads - Read Me First ***
https://forums.comodo.com/help/faqsthreads_read_me_first-t9364.0.html

for this section:

System Tray Icon Tooltip - Firewall Being Initialized https://forums.comodo.com/index.php/topic,2397.0.html https://forums.comodo.com/index.php/topic,7055.0.html https://forums.comodo.com/index.php/topic,7255.0.html

and

Windows (Security Centre) Doesn't Recognize Comodo Firewall https://forums.comodo.com/index.php/topic,211.0.html https://forums.comodo.com/index.php/topic,545.0.html https://forums.comodo.com/index.php/topic,1182.0.html https://forums.comodo.com/index.php/topic,2479.0.html

Those should provide some assistance. Not sure if it’s in there or not, but if you do an Advanced Search on “initialized” or maybe “initializing”, in posts by me, Subjects Only, you should find one where I give a detailed explanation of how you can verify that your firewall is indeed running, regardless of what Windows Security Center says, or whether the icon is in the systray. With that is also more explanation of why you see these alerts from WSC.

Hope that helps.

LM

…and I take the opportunity to inform you:

Correct me if I’m wrong, but cpf.exe is just the GUI and cmdagent.exe is the real firewall? Obviously I didn’t check for cmdagent.exe (if I did, I would have mentioned it above). So maybe, this whole story doesn’t mean a thing, unless cmdagent.exe was terminated too.

/LA

You are correct ~ cfp.exe is only the GUI. You can kill the GUI all day long (until the cows come home…) and the firewall will still be running. Provided of course that cmdagent.exe, the service, and the two drivers have not been terminated/disabled as well.

Chances are, the firewall was still active; you just could not interact with it because the GUI was crashed.

LM

Thank you very much Little Mac.

As I said, this is a random occurrence and always rectified, so I was not too anxious, just reporting really.

I notice the thread reference to creating Comodo as the standard firewall for windows to recognise, but admit a certain wariness about doing so. Am I being too cautious in thinking that at some point, there could be a Windows XP update directly affecting the Windows version firewall and a potential conflict could occur?

It is not for me to be suspicious about these things but there is a certain history with Microsoft and the ‘control’ element of the organisation. Oh dear…what have I said? Make that allegedly.

Regards

D

Dragoon,

Nothing should happen with Win XP FW as long as you have it turned off. Even if you did leave it on & it updated, it has not (to my knowledge) ever been shown to cause any conflict with CFP. Primarily because XP FW does next to nothing… :wink: Should I say, “allegedly?” Nah, it’s been confirmed by independent testing (ie, Matousec)… XP FW does next to nothing. There you go.

In fact, a lot of users completely disable/turn off Windows Security Center, as it really does next to nothing as well. They can tell if their security applications are running, they know if Windows Updates is turned On or Off, so they really don’t see the need for WSC to consume resources by constantly running and doing next to nothing.

LM

Hello LM (If I may be so bold)

Carefully noted.

Knowledge such as yours should not be ignored by anyone, least of all by me.

What a revelation this site is proving.

Thank you

D

I appreciate the compliment and I’m glad you’re getting something out of the forum, Dragoon, but please don’t put me on any sort of pedestal; there are many many folks here with far greater knowledge than any I might possess.

LA, regarding your unanswered questions about the GUI crashing out on you, I don’t know why that happened. It is possible that it doesn’t just relate to the physical drive space for the file, but RAM as well. We know Windows borrows drive space for the cache/buffer/swap to act as RAM, and I think I remember hearing that in some cases it may use RAM to cache things temporarily; this could factor in when unpacking an archived/compressed file like that.

I note that was in May; has the issue continued since then?

LM