... Which might than be the cause of other software (which installed Gator)
Better notify the user that your app refuses/cannot work as long as it's
(Gator) there, and leave the decision to the user ...
If you do work for a company then if you can get the users to use your
software you should be able to get them to run a scan every so often
using the aforementioned tools. If the users are too daft, to stupid,
or too ill-behaved to do that then you have a problem.
So, if you're still gonna do it yourself, does Gator have a UI (a
window) with a constant title? If so, you could use an API call to
locate a window (FindWindow, check the API viewer or
MSDN.microsoft.com) and check every few seconds for that window. Not a
perfect solution 'cause God only knows what that malware crap has done
to your system in that couple of seconds. Besides, that's gonna be a
system drain checking for that window, I bet.
If they don't have a UI, or if the title of the window changes from
time to time or instance to instance then you'll have to look for a
running process on the system and I don't know what API calls would be
involved in enumerating the currently running apps on a system, but if
it's NT, 2K, or XP you're gonna have to sweat permissions, I think,
before you can swat a running process, which means you'll either have
to have your users running under and admin account or you'll have to
try to run your app with a separate security account (rots o' ruck,
:-/ Dunno how much help any of that is, hope some is.