QUOTE (Ilya Rabinovich @ Jan 2 2007, 04:41 PM)

Well, in fact, both of the product are, mostly, driver-level. GUI need to get logs and to control. Both GUI need admins rights to operate in full effect.
Right now you may protect your settings with limited user account. I may create driver-based gates to allow people operates under limited-user account, but this will break this defense. Within DefenseWall 2.0 there will be parental control for it. So, I'm in a little doubts...
ok, thanks! I imply from your reply that driver-level protection continues with DefencePlus from a limited user account, the limited user simply cannot access the GUI... or I'm not 100% sure since you say GUI needs admin to operate in full effect. As long as DefencePlus continues to perform and block from limited user, sure ok, unless inability to access GUI would muck up operation. just checking. let it be as is, and certainly do not want to break the defense. in past, I used DCS Process Guard and from a limited account there was no GUI in systray, so limited user could not turn off PG, but PG GUI would temp pop up to allow/deny a process that was not in PG's database.
give me a few days to see how computer reacts to DW & DF and I'll register both. so far so good.