Process Lasso and NIS 2011 problem!

[airborne]

My log on Nis 2011 shows how Process Lasso are being blocked. The reports never ends. So many are there!
I read some where that this was an solved issue in 4.00.34 but this seems not to be the case.

Kind Regards

[hanemach_gt]

Add Process Lasso to exclusions' lists in NIS 2011 and exclude Symantec processes in Process Lasso.

[airborne]

And where is the option in Process Lasso to exclude NIS 2011!

Kind Regards

[hanemach_gt]

Go to: Options > Configure ProBalance ... > Configure excluded processes ... and add entry cc*.exe

Should work as Symantec processes (especially these of Norton) start with 'cc'.

[airborne]

Thank you! adding Nis 2011 to Process Lasso exclude list is enough to make it stop!
The interface is a little confusing when you havent use the program before, so thank
you for the help.

kind Regards

[hanemach_gt]

The problem is that both Process Lasso and Task Manager don't see ccSvcHst.exe, you can see it using command-line utility tasklist .

[airborne]

Hello!

ccsvchst.exe is shown both in Process Lasso and Process Explorer.
On my computers any way.

Kind Regards

[hanemach_gt]

Ah, I forgot you are running Vista, I have Windows 7. At least I have Norton's processes invisible.

[Jeremy Collake]

This is fixed entirely in the new *beta* version (or is supposed to be, correct me if wrong). The last final only partially fixed it, it turns out. When the GUI is minimized to the tray, you should see no new events though... for what that is worth. Sadly, simply 'Trusting' Process Lasso within NIS does not stop it from logging the crap out of Process Lasso every time Process Lasso dares look at its process. So, I had to avoid that process entirely, which required some new code, and so had to be done in the beta. The fix in the more recent final actually substantially decreases the number of log events you see in Deep Guard. Very sorry for inconvenience. This is one of many reasons I am trying to get v4.1 on finished. While I could back-port this fix, the totality of it is quite risky, so I'm better off just finishing the new version!

Thanks for the report.

[airborne]

Is it possible to have this fixed in the next release!

[Jeremy Collake]

I will look into it and get back to you. That should be possible. Now that the web server migration is complete, I can get back to 'real work' ;o

[airborne]

Okay great!

[airborne]

Do the latest beta have any fixes regard the Nis 2011 problem.

Kind Regards

[Jeremy Collake]

It has not been released YET, but it will address this. It is (almost) the next thing on my agenda here. The last week was terribly distracting, I do apologize for the wait.