By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,529 Members | 864 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,529 IT Pros & Developers. It's quick & easy.

Running processes

P: n/a
Hi,

I have written a win32 console application(exname1.exe) which runs for
ten minutes.I am calling this exname1.exe from another exe named
exname.exe using shellexecuteex.Now from exname.exe coding i have to
check whether exname1.exe is already running or not.How to find whether
a win32 console application is already runing or not from another win32
console application.I need only one copy of exe has to run(for that i
have already used createmutex in exename1.exe.But now i want to know
from exname.exe whether exename1.exe is running or not).How to find all
the processes or particular exe running in the computer using vc++6.0

Regards,
Mani

Mar 23 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
> Hi,

I have written a win32 console application(exname1.exe) which runs for
ten minutes.I am calling this exname1.exe from another exe named
exname.exe using shellexecuteex.Now from exname.exe coding i have to
check whether exname1.exe is already running or not.How to find whether
a win32 console application is already runing or not from another win32
console application.I need only one copy of exe has to run(for that i
have already used createmutex in exename1.exe.But now i want to know
from exname.exe whether exename1.exe is running or not).How to find all
the processes or particular exe running in the computer using vc++6.0


If exe1 already has a mutex, you can simply check in the other exe if it is
running or not. call CreateMutex in your other exe and check the error code.
From MSDN:

"If the mutex is a named mutex and the object existed before this function
call, the return value is a handle to the existing object, GetLastError
returns ERROR_ALREADY_EXISTS, bInitialOwner is ignored, and the calling
thread is not granted owernship. "

This will tell you if the mutex already exists or not. Hence you know if the
exe1 is running or not. Remebmber to close the mutex handle afterwards.

A general way of checking if a process is running (using win32) would be to
use the Process Status API (PSAPI). Check this:
http://msdn.microsoft.com/library/de..._processes.asp
For more details.

If you were using .NET you would use the Process class for that.

--

Kind regards,
Bruno.
br**********************@hotmail.com
Remove only "_nos_pam"
Mar 23 '06 #2

P: n/a

"Bruno van Dooren" <br**********************@hotmail.com> wrote in message
news:83**********************************@microsof t.com...
Hi,

I have written a win32 console application(exname1.exe) which runs for
ten minutes.I am calling this exname1.exe from another exe named
exname.exe using shellexecuteex.Now from exname.exe coding i have to
check whether exname1.exe is already running or not.How to find whether
a win32 console application is already runing or not from another win32
console application.I need only one copy of exe has to run(for that i
have already used createmutex in exename1.exe.But now i want to know
from exname.exe whether exename1.exe is running or not).How to find all
the processes or particular exe running in the computer using vc++6.0
If exe1 already has a mutex, you can simply check in the other exe if it
is
running or not. call CreateMutex in your other exe and check the error
code.
From MSDN:


Except you should use OpenMutex instead, because you don't want to exclude
exe1 from starting.

http://msdn.microsoft.com/library/de.../openmutex.asp

Return Values
If the function succeeds, the return value is a handle to the mutex object.

If the function fails, the return value is NULL. To get extended error
information, call GetLastError.

If a named mutex does not exist, the function fails and GetLastError returns
ERROR_FILE_NOT_FOUND.


"If the mutex is a named mutex and the object existed before this function
call, the return value is a handle to the existing object, GetLastError
returns ERROR_ALREADY_EXISTS, bInitialOwner is ignored, and the calling
thread is not granted owernship. "

This will tell you if the mutex already exists or not. Hence you know if
the
exe1 is running or not. Remebmber to close the mutex handle afterwards.

A general way of checking if a process is running (using win32) would be
to
use the Process Status API (PSAPI). Check this:
http://msdn.microsoft.com/library/de..._processes.asp
For more details.

If you were using .NET you would use the Process class for that.

--

Kind regards,
Bruno.
br**********************@hotmail.com
Remove only "_nos_pam"

Mar 23 '06 #3

P: n/a
Ben Voigt wrote:
"Bruno van Dooren" <br**********************@hotmail.com> wrote in message
news:83**********************************@microsof t.com...
If exe1 already has a mutex, you can simply check in the other exe if it
is
running or not. call CreateMutex in your other exe and check the error
code.


Except you should use OpenMutex instead, because you don't want to exclude
exe1 from starting.


But if OpenMutex fails you should CreateMutex, right? But then there
might arise situation when both processes call OpenMutex, concludes that
there isn't one, then both call CreateMutex. To address this you must
finally check with the GetLastError after CreateMutex. That means that
OpenMutex is an extra call that achieves nothing.

CreateMutex doesn't automatically grants you ownership of the mutex.
Waiting functions do that (WaitForSingleObject et al.).
Mar 23 '06 #4

P: n/a
"Mihajlo Cvetanović" <ma*@RnEeMtOsVeEt.co.yu> wrote in message
news:Ob**************@TK2MSFTNGP14.phx.gbl...
Ben Voigt wrote:
"Bruno van Dooren" <br**********************@hotmail.com> wrote in
message news:83**********************************@microsof t.com...
If exe1 already has a mutex, you can simply check in the other exe if it
is
running or not. call CreateMutex in your other exe and check the error
code.


Except you should use OpenMutex instead, because you don't want to
exclude exe1 from starting.


But if OpenMutex fails you should CreateMutex, right? But then there might
arise situation when both processes call OpenMutex, concludes that there
isn't one, then both call CreateMutex. To address this you must finally
check with the GetLastError after CreateMutex. That means that OpenMutex
is an extra call that achieves nothing.

CreateMutex doesn't automatically grants you ownership of the mutex.
Waiting functions do that (WaitForSingleObject et al.).


The OP has already done that in his singleton application. Now he's asking
the question, is it possible to detect whether that application is running
from another application, and for that purpose he should use OpenMutex only.
Mar 23 '06 #5

P: n/a
> The OP has already done that in his singleton application. Now he's
asking the question, is it possible to detect whether that application is
running from another application, and for that purpose he should use
OpenMutex only.


Not true.
For the exe of which only 1 instance may be running (exe) it doesn't matter
if the mutext exists or not.
It just wants ownership. It tries to take it and bails out if it can't.

The managing app (exe1) only want to know if the mutex exists or not.
CreateMutex can achieve
the same thing as OpenMutex, as long as the InitialOwner parameter of
CreateMutex is set to 0, so
that it is not accidently owned.

--

Kind regards,
Bruno van Dooren
br**********************@hotmail.com
Remove only "_nos_pam"
Mar 23 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.