Maybe this has been discussed before, and last post I saw said something like "Process Guard would still be doing it's job, because it was there first". I have to comment on this, saying "precisely, but not really". I'll explain. I installed Tiny Firewall Full professional, and Process Guard 2.000 Full was still installed. Tiny would contantly crash, and I read inumerous violations in ProcessGuard 's Window's Log. After a million of crashes of tiny, for "privilleges error", I manages to add all the "required" files of Tiny into Process Guard, so they'd have access onto explorer and drivers, so Tiny could implant his rootkit. 1 restart later I noticed right away: ProcessGuard's Driver was not loaded. Is this the consequences of rootkit preventing adicional kernel drivers ? Or is this some anti-ProcessGuard conditions on Tiny Firewall. I know Tiny firewall as good as I know Pg, so I didn't forget to add file, driver and system privileges from Tiny to ProcessGuard. I event tryed with Tiny *personal* Firewall (with exactly the same configuration) and it worked fine. Why doesn't Tiny 6 (Tiny Firewall) cooperate with process guard. Any one noticed this ? Ps. Sorry for the long doubt and long post.