Test to see if Batch File is running

[BatchFileCommand]

In my program, I want to be able to test if the same batch file is running. If so, I want it to shut down the current session. How would you do this?

[macdad-]

you'd probably use Tasklist and Taskill.

[BatchFileCommand]

I can't see how to do this. Could I have a little more help.

[macdad-]

actually, i tested this and no you could do this since even if you title your batch program, it would still show up as CMD.EXE in tasklist.

[BatchFileCommand]

So, I'm still trying to figure something out. How would you test to see if it is running in Task list.

[macdad-]

here: http://technet.microsoft.com/en-us/library/bb491010.aspx

[BatchFileCommand]

So, how would you combine the status into the tasklist statement.

[macdad-]

pipe it

[BatchFileCommand]

Meaning?

[devcom]

i would do this like this :

Code: [Select]

@echo off
set title=Title 1234

title Test 1234

tasklist /V >nul | findstr "%username%:  %title%" && echo Cmd with title: %title% is running || echo Cmd with title: %title% is not running
pause

[BatchFileCommand]

Hm.. Didn't work.

[Dias de verano]

Hm.. Didn't work.

How about this?

Code: [Select]

@echo off
set title=Title 1234
title %title%
tasklist /v | find "%title%">nul
if %errorlevel% EQU 0 (
set state=running
) else (
set state=not running
)
echo Task with title %title% is %state%
pause

[BC_Programmer]

Or, you could write a program that uses the EnumWindows() routine to enumerate all windows, and for each window call
GetWindowThreadProcessId, and then use the resulting ProcessID in a call to GetModuleBasename, and after determining that the window belongs to CMD, proceed to use OpenProcess() and ReadProcessMemory() to determine the opened file handles of the CMD.EXE instance, and if you find your batch file, kill the current instance and otherwise continue.

Really quite straightforward really. Although I suppose Openprocess() will fail anyway, and ReadProcessMemory() is a fairly big gamble  on pretty much any NT system. Oh well.

[BatchFileCommand]

How about this?

Code: [Select]

@echo off
set title=Title 1234
title %title%
tasklist /v | find "%title%">nul
if %errorlevel% EQU 0 (
set state=running
) else (
set state=not running
)
echo Task with title %title% is %state%
pause


It always returns and says it's running, I echoed the errorlevel, and it always returned 0, now It's also possible that because it's looking to see if it's running itself it will always be found. However, the batch file is listed as cmd.exe.

[Dias de verano]

It always returns and says it's running

Of course it does! (How could it do otherwise?) It's a demo to show you how to look for a running batch by its window title.

[BatchFileCommand]

Oh, I was thinking to see if there are to sessions of cmd.exe running.

[oldun]

Maybe the batch file could create a file when it starts, and delete it when it completes.

The batch file could then check for the existence of that file when it starts, and if it finds the file, it would exit, or else it would carry on.

[BatchFileCommand]

That would be a lot of work. Because the only way that you could really quit would to click the exit button in the corner of the screen. Or doing quit. But the person will probably press the X button.

[Dias de verano]

the only way that you could really quit would to click the exit button in the corner of the screen. Or doing quit.

A batch file will quit when it encounters the EXIT command. 

[oldun]

I may have misunderstood your requirements, but what I was thinking of was something like this:


@Echo Off
:: Check if temporary file exists
If Exist %temp%\AlreadyRunning.tmp (
   Echo This batch file is already running & Goto :EOF)
:: Else create it
Echo . > %temp%\AlreadyRunning.tmp
:: Carry on with remainder of batch file
Echo.
Echo Do whatever here, then
Echo.
:: Delete temporary file
Del %temp%\AlreadyRunning.tmp

[BatchFileCommand]

My program. Doesn't really have a beginning and an end. It has a old GUI with options.

[BC_Programmer]

My program. Doesn't really have a beginning and an end. It has a old GUI with options.

all programs have a beginning and an end.  instead of exiting the batch file using EXIT, you can redirect to a label that performs the necessary cleanup.

[BatchFileCommand]

Even if it does have a beginning and an end. What if someone doesn't know about the file and clicks the X button in the corner of the screen. Then they would never be able to use it again.

[BC_Programmer]

This is why I stopped using this method in my batch files/programs early on.