[-X-]

no switch at all would be the same as 2
I think you mean no start.

[Martin H]

@g-force

Exactly, mate! (as X stated, if you by "no switch" means no START command in no.3, which i'm sure you do...)

This post has been edited by Martin H: 11 March 2010 - 10:58 AM

[maxXPsoft]

agree with g-force
Think this is a situation where some apps will continue and some will not, I've tried removing the /wait and turns into a nightmatre doing 20-30 apps. even on Seven 64 bit

[submix8c]

Quote

So... the original assertion is somewhat correct (as it all depends on the process and/or program in question), but not entirely since in other cases it will be required.

Additionally, it may depend on the app in question as to how it "exits" and/or whether it calls other subroutines (e.g. dual-extract/execute... one-inside-the-other)???

Perhaps this is the reason the original recommendation was "start /wait" (cover all the bases, regardless).

Ennyhoo, a good learning experience with relevant information as to "how/why".

Aaannnd... Edit!!!
I re-read above; only says "removed wait"(See Next Post/Prev Posts)...

This post has been edited by submix8c: 12 March 2010 - 05:35 PM

[Martin H]

maxXPsoft, on 12 March 2010 - 08:19 AM, said:

agree with g-force
Think this is a situation where some apps will continue and some will not, I've tried removing the /wait and turns into a nightmatre doing 20-30 apps. even on Seven 64 bit

You havent read what I have stated throughout the whole thread then...

"start /wait" makes ZERO difference in BAT/CMD files...

YES, some apps dosent wait, but thats besides the point, as "start /wait" dosent fix it...

Lastly, you should not remove "/wait", but "start /wait"...

@submix8c

"start /wait" dosent cover the bases and are always 100% redundant in cmd/bat files...

This post has been edited by Martin H: 12 March 2010 - 04:29 PM

[g-force]

maxXPsoft, on 12 March 2010 - 08:19 AM, said:

agree with g-force
Think this is a situation where some apps will continue and some will not, I've tried removing the /wait and turns into a nightmatre doing 20-30 apps. even on Seven 64 bit

Agree - I use "setup.cmd" in some of my Silent-WinRAR-SFX (I usually install with this method).
Some Setups won`t install (or stuck) without that "start /wait" because of false or "too fast" execution.
I´m sure it makes a difference in a .cmd.

[Martin H]

Well, then lets agree to disagree then...

Btw, please give me an example of ANYTHING where "start /wait" makes a difference in cmd, and i will test it out...

Also, so you guys are not believing msft when they say in their technet article>

Quote

When you run a 32-bit graphical user interface (GUI) application, cmd does not wait for the application to quit before returning to the command prompt. This new behavior does not occur if you run the application from a command script.

Console apps never waits obviously, but gui apps are gui apps no matter if they are silently executed or not...

Quote

Notice that the operation of the START command differs from the default command shell sequence:

First, the START command never waits for the command to complete.

And hence, the /wait switch when using it... Said in another way, the /wait switch modifies the start commands normal behaviour, but NOT the command shells behaviour in any way...

If that was the case, then there would instead be a switch for cmd.exe itself to change that behaviour obviously...

Anyway, im done with this now if not getting an example, as i have proven it previously in this thread both with tests and technet quotes, so unless im givin an example to prove wrong, i dont want to continue repeaing myself here...

This post has been edited by Martin H: 13 March 2010 - 08:41 AM

[gunsmokingman]

Then explain why this cmd waits until notepad is closed before the message appears.
Perhaps I have been reading this wrong, but this Cmd script from what I read should
not wait for notepad to close before the message appears. That is not the case it
waits until notepad closes before the message appears.

@Echo Off
CLS
Mode 55,9

Echo.
Start /wait notepad
CLS
Echo.
Echo This does not show until Notepad is closed
pause

[jaclaz]

gunsmokingman, on 13 March 2010 - 11:03 AM, said:

Then explain why this cmd waits until notepad is closed before the message appears.
Perhaps I have been reading this wrong, but this Cmd script from what I read should
not wait for notepad to close before the message appears. That is not the case it
waits until notepad closes before the message appears.

What happens if you run this?:

@Echo Off
CLS
Mode 55,9

Echo.
notepad.exe
CLS
Echo.
Echo This does not show until Notepad is closed
pause

Anything different happening form the one you posted?

jaclaz

[Martin H]

THANK YOU jaclaz, my friend!

Finnaly someone who understands what i've been saying for two pages now... (sorry, Yzöwl as ussual also does...)

Please everyone, READ before posting!!!

Edit: I didn't even have to, but anyway i've just tested this and obviously you know what the result was...

This post has been edited by Martin H: 13 March 2010 - 04:41 PM

[briant]

Here's an example GUI application that won't wait, no matter if it's on the command line or in a script:

at the command prompt:
> start "" /wait "c:/Program Files/Mozilla Firefox/firefox.exe"
=> DOESN'T WAIT

in a .cmd file:
start "" "c:/Program Files/Mozilla Firefox/firefox.exe"
or
start "" /wait "c:/Program Files/Mozilla Firefox/firefox.exe"
=> DOESN'T WAIT

i think it's a function of how the application is programmed to exit.

[Outbreaker]

You could try this:

Quote

START "" /WAIT "C:/Program Files/Mozilla Firefox/firefox.exe"
:CHECK
ping -n 10 localhost 1> NUL
TASKLIST /v /fi "IMAGENAME eq firefox.exe" 2>&1 > NUL
IF ERRORLEVEL 1 GOTO CHECK

This post has been edited by Outbreaker: 26 May 2010 - 07:28 PM

[submix8c]

briant, on 26 May 2010 - 05:15 PM, said:

i think it's a function of how the application is programmed to exit.

I think that's what I was trying to say.