I tested some alpha or beta version of comodo 3, awhile ago (dec 2007 or jan 2008), and did not have any of these problems with it.
Am using windows xp sp2 x86.
1, cant restart windows xp (thus i cant properly shutdown winxp)
after unchecking all defense+/d+ monitor settings, I still cant reboot.
With d+ disabled, I can reboot ok.
My guess is that d+ hates Stardock’s Logon Studio program with a passion. (i am using it)
it seems there is no d+ setting the user can toggle to tame d+ in this specific area.
I use a open source console program called ‘Console’. Much better than using cmd.exe.
For some reason, I cannot start the console program (it errors out saying that it could not create a new tab), even after unchecking all defense+/d+ monitor settings.
However with d+ disabled, it works fine.
What is d+ doing exactly that I cannot disable from the comodo GUI? …
GuiTest Perl module
Win32::GuiTest::SendKeys is broken, but works fine after d+ is disabled.
I use SendKeys to automate various things, and for some reason the keys aren’t being sent with d+ enabled.
Basically SendKeys can automate everything or many things that can be done via keyboard.
I can see d+ being a great security feature, but its a shame that its configuration seems to be somewhat lacking in options.
I hope the comodo dev team will expand upon what a user can enable/disable for defense+.
at mods/admins: if you think of any of these problems will be fixed in some future build of CFP, then great!
but if not, then why not?