Need help with cmd start wait command

I had a perplexed regarding this. At present I have in conclusion originate out what the deal is regarding this. The CMD prompt determine to by defaulting not wait for a win32 gui app to terminate previous to returning to the cmd prompt the entire in excess of again UNLESS it's run commencing a NT command script. So, this means by means of the intention of the parameter is consideration to be utilized merely when running commencing the cmd prompt and not commencing a NT command script! Anyway, I immediately required to add with the intention of you be able to the entire at present eliminate your 'start "" /wait' commands commencing your NT command scripts I need some information in sequence to the related topic.

If Command Extensions are facilitated, exterior command invocation from side to side the command line or the START command revolutionize as go subsequent to non-executable files might be invoked from side to side their file association immediately by typing the name of the file as a command. (For illustration WORD.DOC would commence the appliance associated by means of the .DOC file extension). Observe the ASSOC and FTYPE commands for how to generate these associations commencing within a command script. When accomplish an submission by means of the intention of is a 32-bit GUI submission, CMD.EXE does not hang approximately for the application to conclude previous to returning to the command prompt. This innovative behavior does not happen if executing within a command script.

I am not certain if it does additional than I would imagine it would in view of the fact by means of the intention of wpi immediately clones the runonceex technique when it installs the progs position the "Title In Quotes" previous to the /wait statement, not subsequent to it. Give the impression of being similar to you is quote refences a line commencing a registry file (judging commencing the double backslashes "\\"). Endeavor loading up the registry file and giving the impression of being at the results in regedit unswervingly. Create certain it ends up the method you expect. For illustration %windir%\system32\cmd /c start "ActiveSync Install" /wait "%CDROM%\Apps\activesync\setup.exe" /s And what if you are not utilizing a title of the dos box which I am not. Having give the impression of being at the start. You are accurate in with the intention of it be supposed to be /start "tilte" /wait <command to run> It’s basically for the reason by means of the intention of the start command expects the first set of quotes to define the title. It does not revolutionize the title of the command prompt, in actuality I do not be familiar by means of what it does. Particularly if your first set of quotes is used to identify the program name and you necessitate utilizing quotes in by means of the intention of programs command line.

Essentially, a title is not necessarily necessary. The merely time its necessary is when you utilize quotes for your program/command, of which you merely necessitate to utilize if there are spaces in moreover the program name or path. So when you do utilize quotes, the start command is expecting the 1st set of quotes to be the title and the subsequent set of quotes for the command to run. Finally, you do not necessitate to essentially necessitating putting in a title description, using 2 double quotes will also suffice. Oh 2 other things... the title does in actuality set the title bar of the command prompt window the command is working with in; it’s the merely function it serves and it does not matter if you place it previous to or subsequent to the '/wait' parameter.

Imagine this is a situation where a number of apps determine to continue and some determine to not, I have comprised and endeavor eliminating the /wait and turns into a terrifying doing 20-30 apps. Even on Seven 64 bit in addition, it might depend on the app in query as to how it "exits" and/or whether it calls additional subroutines (e.g. dual-extract/perform. one-inside-the-other). Perhaps this is the motivation the innovative recommendation was "start /wait" (cover the entire the bases, regardless). A superior learning experience by means of relevant information in sequence as to "how/why". You have not read what I encompass stated throughout the whole.

If I do not utilize Start /wait I am my CMD, the entire lines are perform without waiting. So it create a dissimilarity for me. There is no waiting facilitated by defaulting in a CMD. Immediately tested, and exclusive of /WAIT in my .cmd file, the programs the entire launched concurrently. Added /WAIT, and the programs merely ran one at a time. Every time you utilize START, you are essentially opening a innovative CMD window, if this is considered as a innovative Command Prompt session then according to it determine to not wait by defaulting for the app to close. Endeavor therefore to run some tests utlizing combinations of STARTs /I and /B switches devoid of the /WAIT switch and observe if it makes a dissimilarity to you in your circumstances.