plgpat's dashboard

Export configuration work again for me! :) I fix the "Error generating digest for the config file." message!

Try to remove ALL diacritics chars from Names of Connections in Network Security/Trusted area/Description column and also remove all diacritics chars from Description in Network Security/Applications/Packet filter.../IP Groups/Group name column.

Tested on Sunbelt Personal Firewall version 4.6.1861 with spf.cfg file copied from previous version 4.5.916.
Export configuration was also malfunctioning in version 4.5.916. Probably for the identical reason.

Before diacritics removing some high (100%) CPU load by SbPFCl.exe was observed...

I added this csv exclusion and it works! No slow anything. Thanks for finding and posting this! – Darren, on October 23, 2008 12:44

Hi, plgpat.

NOD32 -> Setup tree -> Real-time file system protection -> ThreatSense engine parameter setup -> click Setup button -> type CSV in Extensions -> click Add button -> click OK. – Bog, on October 23, 2008 10:51

witch files exactly? nod32 ThreatSense can exclude specific files
with threatsense ( in advanced options : tools/threatSesense advanced configuration ) – plgpat, on October 22, 2008 22:14

it would be caught on-execute

You're great, Ventura!... but a question still remains: what if a virus is hiding itself under a .csv file?

Thanks for the workaround! – Bog, on October 22, 2008 18:26

Hello Guys,

NOD32 checking lots of *csv files which is created by CS 3.1, and that cause the problem. Add csv extension to the NOD32 exclusion list in NOD32, after that the problem disappear.

Kind Regards
Peter

There is definitely something wrong then. I think it would be best to contact us here in support directly. We can help you get it working.
support@sunbelt-software.com – Mike Williams, on September 17, 2008 18:50

Mike - even with NOD32 and Comodo disabled, and then CS reinstalled and launched, I still can't get passed the CS splash screen - even after 8 minutes of waiting. – gwp99, on September 17, 2008 17:42

Hi, Alex, good to hear that. I'm sure you will make it, good luck! – Bog, on September 17, 2008 17:32

Bog -- I do want to mention that by design, it is our intention that CounterSpy and NOD32 co-exist peacefully. Our developers are researching these reports and we do take them seriously.

Darren, of course I have the latest versions of CS V3 and NOD32, and set the two things you mentioned above. I’ve noticed no significant improvement in either CS “deep scan” or CS and Windows startup, which are all very slow. No wonder, as long as NOD32’ “ekrn.exe” eats 35-40% out of CPU. With NOD32 disabled CS is flying!
I think one doesn’t pay for a product to make compromises. When I chose to purchase CS a few months ago, I searched the net for eventual issues with NOD32 and I didn’t find any, but now... it’s very frustrating.
Using CS as a stand-alone (like CS team tries to suggest) is ridiculous, any professional antispyware tool should live well alongside an antivirus and a firewall program.
So, Darren, let’s not make illusions to CS developers that all is well and let’s hope they will find solutions to these issues in a future upgrade. Until then, I will disable “SBAMSvc” service in Administrative Tools to receive a red icon reminding me CS is not functional. – Bog, on September 17, 2008 10:54

Hi Qwp99,
If you are unable to open CounterSpy, try doing a uninstall reinstall. Disable NOD32 while doing the reinstall, to make sure that it doesn't block or corrupt any of the files.
After reinstalling, remember to run only one of the active protections to avoid a conflict.
Here is a direct link for CounterSpy 3.1

http://go.sunbeltsoftware.com/?linkid...

Just tried the latest (today's) update and still the same issue... – gwp99, on September 16, 2008 16:48

Well, I don't know then. For me they have been running together fine since I upgraded to CounterSpy v3 two weeks ago. I also updated my Eset to latest build 3.0.672 (I had 3.0.669 before).

Two things to check:
- disable "Check files when they are opened or copied" in CounterSpy
- NOD32 turn of Scan on File open in the Real-time file system protection setup.

CounterSpy Scans work fine:
Both Quick Scan and Deep Scan work well. ekrn.exe mainly used up to 40% CPU during the initial startup of the scan with occasional small CPU spikes during scan. You may have scan appear stuck scanning System Volume but briefly disabling Eset and straight away enabling it gets through it, but my scheduled full scan last Sunday completed on it's own. Scheduled Quick scans run without me even noticing.
A full scan with Eset turned off wasn't that much quicker, so for me at least, turning off Scan on File open in Eset helped a lot.

Other things:
It does take one minute to open CounterSpy. It also does take longer with History Cleaner (even shows not responding for two minutes but when Eset ekrn.exe cpu use goes back down,it always works). So with these ones just a little patience. I can live with these and the PC Explorers being a bit slower, it's the scanning I mainly care about.

I could tune Eset further but apart from the File open real-time setting I prefer keeping my protection optimal.

I am happy with them both running together now. (Main problem apart from this one I had to solve was getting CounterSpy working with Comodo firewall which was disabling CounterSpy at the end of scanning! - again, it's all about compromise and what you can live with) – Darren, on September 16, 2008 13:13

Same issue here with v3 and Nod32 - however, I cannot open CS to adjust any parameters - it hangs at the splash screen even when CS disabled and no scan running. Even with nod32 disabled, I cannot open CS gui to get at the parameters.