🚀 go-pugleaf

"poojo hackma" <poojo.com/mail> wrote in message
news:45c257c5$1@newsgroups.borland.com...

> If AutoRun.exe can detect that CustomSetup.exe is
> running, it can close CustomSetup.exe ... or itself.

Have both CustomSetup.exe and AutoRun.exe (and optionally MainApp.exe
as well) create a mutex with the same name when run, and release it on
exit.  GetLastError() will return whether the mutex already existed or
not.  This way, CreateSetup.exe can detect whether AutoRun.exe is
already running, and vice versa.

> I'd like to use EnumWindows and GetWindowThreadProcessId
> within AutoRun.exe to find and close CustomSetup.exe
> (using WM_CLOSE)
>
> How can I find the CustomSetup.exe process?

You don't need to.  Just have AutoRun.exe (and MainApp.exe) exit if it
detects that CustomSetup.exe is already running.  Maybe
CustomSetup.exe is installing a new version of AutoRun.exe and
MainApp.exe (or recovering a previous install), so they shouldn't be
running in that situation so that CustomSetup.exe can overwrite the
files.


Gamit