Here is the Beta version of CPF 2.3 :-) [closed]

When I tried to install the adaptec ASPI driver. CPF or CLP could not properly close during reboot and finally it locked the pc. I had to manually reboot. When I manually closed CPF and CLP and the installed the ASPI I had no problem rebooting.

Also I saw that even if I disable- close CPF, programs that are not included at the rules are blocked. Does this mean that CPF is on even if it is closed? ???

If properly closed, there should not be such an issue. But if somehow it is killed, rules will remain effective.

Just installed the 2.3 beta after uninstalling 2.2.0.11 and have been receiving popups as shown in the two attachments. I had OSMODE=3 and have reset it to 0. Note that this type of warning doesn’t allow for “remembering” permissions. Any suggestions welcome.

Thanks.

Bob

[attachment deleted by admin]

I get a similar popup with a newsreader I use, NewsBin Pro, when I have OSMODE=3.

I also got it one time when I logged in as a different user. That time it mentioned an AVG module. I forget which one.

Going back to OSMODE=0 does eliminate the messages.

Hi Bob,

Make sure you restart your PC after changing the OSMode value.

Egemen

nod32 email virus scan is not working. (with thunderbird)

also, I’m getting weird error with hkSFV, showing bad files that are not bad… very odd!

Working fine here…

Hi egemen,

rules remain effective even when CPF is properly closed not killed. Maybe it has something to do with OS3.

I had to return to the CPF version 2.2.0.11 because after installing the adaptec ASPI driver 4.7.1 windows could not turn off, log off, or reboot. The problem is that sfter installing ASPI CPF cannot close itself.

One last comment on the Cisco VPN. We still have a crash if we use the VPN option to disable the firewall. Those files I listed have to be removed.

Still getting the same type of popups, viz., Cryptographic signature has changed since last time and OSMODE=0. Willing to try something, anything, to fix this since it’s irritating me to distraction.

Thanks.

Bob

Hi,

Any ideas when the final of 2.3 will be released? And will the High Performance mode be finished in the official 2.3 release?

we are aiming for 2nd week in july.
yes High performance mode will be there too (along with other features :slight_smile:
Melih

Could you list any of the other new features that may be there, or are you going to make me wait :wink:

~Justin

If OSMODE=0 is standard and OSMODE=3 is high performance, what is 1 and 2?

Ewen :slight_smile:

I believe he said that modes 1 and 2 were for internal testing only. Of course that could change with a final release. :wink:

(B) Lee

Hi Ewen,

They are used for internal purposes. Related to operating system version etc.

Egemen

ta. just curious.

ewen :slight_smile:

Any word on the problems I have had with with Windows 2003 and the beta? I can gladly test it on the OS. I only use Windows 2003, so no other version of Windows is an option for me.

Benn running the Beta on two Pc’s for a couple of days now with no problems to report so far. Will there be updates to the beta posted here to allow testers to try out the “fixes”?

Just thought I recap the problems I am having with CPF 2.3 beta. Please note that the first two problems are only present when using OSMODE=3.

  1. When I click on a file with the extension of NZB, which is associated with my newsreader Newsbin Pro 5, I get a popup stating that there was a failure of NBP to communicate with CPF. Something to that affect. There is no checkbox to remember this so I always get this popup. OSMODE=0 does not produce this popup.

  2. A CPF message is always issued during shutdown of Windows when OSMODE=3.

  3. Not unique to 2.3 beta but to 2.2 as well. My Temporary Internet Files are NOT being cleared automatically when my browser closes (IE6) even though I have specified the Internet Option to do this. If I kill CPF.EXE then it works. Appears CPF has a lock on the TIF folder which prevents the automatic clearing. Manual clearing does work however so the problem appears to be a little more involved then just a lock on the handle IMO.

Other then this I’ve had no problems with 2.3beta other then what seems like a gazillion more popups then I ever got with any other firewall.