Re: Problem when executing application from batch file
- From: "Someone" <nobody@xxxxxxx>
- Date: Tue, 4 Oct 2005 22:38:06 -0400
To force the batch file to not wait for your app and return immediately, use
"start" without the /wait option. For example, I made a test.bat with the
following:
project1
project1
project1
This executed 1 copy at a time, each taking 10 seconds to run because the
loop I had in Main. When I changed the batch file to the following:
start Project1
start Project1
start Project1
The 3 copies were executed almost simultaneously, and 3 Project1.exe
appeared in Task Manager each using about %33 of CPU time. The prompt
returned immediately before they finished executing.
Using "start" this way insures consistent behavior if your OS happens to
behave differently.
"Jack" <replyto@newsgroup> wrote in message
news:eBfB3EVyFHA.3312@xxxxxxxxxxxxxxxxxxxxxxx
>I am confused about your suggestion.
> My app primary task is not accepting commands from the batch file.
> It is a big, universal app, and one of the added (on request) features is
> to accept commands from a batch file.
> When commands are incoming my app is not smart enough to know whether it
> is a single command from command prompt or it is part of batch file
> execution. As a consequence of that I cannot just ignore checking for
> previous instance. I have to do that to avoid multiple instances.
> Hope it clears up a little.
> Jack
> "Someone" <nobody@xxxxxxx> wrote in message
> news:iaG0f.292$MN6.75@xxxxxxxxxxxxx
>> It appears that outside a batch file, i.e., in Command Prompt, the app is
>> started and you are returned to the "C:\" prompt immediately. In a batch
>> file it waits for the App to finish before going to the next line, so
>> checking for previous instance is not necessary. If you are at Command
>> Prompt and wanted to type the EXE name and wait till the program
>> finishes, use:
>>
>> start /wait yourapp /para1 /para2...
>>
>>
>>
>>
>> "DanS" <t.h.i.s.n.t.h.a.t@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:Xns96E5DB32A2E19idispcom@xxxxxxxxxxxxxxxxx
>>> "Jack" <replyto@newsgroup> wrote in
>>> news:evhDSZUyFHA.464@xxxxxxxxxxxxxxxxxxxx:
>>>
>>>> I do not understand and maybe someone please can explain to why, after
>>>> executing the first line of the batch file the batch execution stops
>>>> until I close my application.
>>>> What kind of mechanism is that?
>>>> sample of batch file:
>>>> [].exe /5553331234
>>>> [].exe /5556770808
>>>> [].exe /5553451234
>>>>
>>>> That happens only if there is not previous instance running.
>>>> I can see batch execution in CMD window. I can see the first batch
>>>> line being executed and then nothing. I close my app and then second
>>>> line of batch file appears and my app is alive again. I close my app
>>>> and then the third line of batch file will appear.
>>>> If I understand the mechanism of that behaviour maybe I can patch over
>>>> that problem
>>>> Jack
>>>>
>>>
>>> Is that 3 seperate lines in the batch file ?
>>>
>>> In the OP, I thought by accept multiple command line params I thought
>>> you
>>> meant like: program.exe /param1 /param2 /param3
>>>
>>> The batch file acts exactly as it was intended. It runs the first line,
>>> waits until that program ends, then runs the next line.
>>>
>>> I would have written the command$ handler to parse the string and look
>>> for
>>> multiple params, which is what I thought you did, and you wouldn't have
>>> had
>>> this issue.
>>>
>>> Regards,
>>>
>>> DanS
>>>
>>
>>
>
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: Problem when executing application from batch file
- Next by Date: Re: Problem when executing application from batch file
- Previous by thread: Re: Problem when executing application from batch file
- Next by thread: Re: Problem when executing application from batch file
- Index(es):
Relevant Pages
|
