durex Posted May 31, 2005 Posted May 31, 2005 Does anyone know if 'start /wait' command works in WPI?I havent tested it, but thought Id check to see if anyone else is using it without issue.. For example:start /wait "Title" C:\whatever.cmdWhich of course will keep anything else from executing until the 'whatever.cmd' completes.Thanks!
Lost Soul Posted June 1, 2005 Posted June 1, 2005 im not sure if it does but i would think it would since wpi just clones the runonceex method when it installs the progs
oioldman Posted June 6, 2005 Posted June 6, 2005 i've tried this and it doesn't workThe command i use is this%windir%\\system32\\cmd /c start /wait %CDROM%\\Apps\\activesync\\setup.exe /sYou need to call cmd as otherwise start doesn't isn't called, the /c, is so the the dos box terminates on endi've found the other apps in order after it are just run.
Noise Posted June 6, 2005 Posted June 6, 2005 (edited) Put the "Title In Quotes" before the /wait statement, not after it. Looks like you're quote refences a line from a registry file (judging from the double backslashes "\\"). Try loading up the registry file and looking at the results in regedit directly. Make sure it ends up the way you expect. I.e.:%windir%\system32\cmd /c start "ActiveSync Install" /wait "%CDROM%\Apps\activesync\setup.exe" /s Edited June 6, 2005 by Nois3
oioldman Posted June 7, 2005 Posted June 7, 2005 And what if your not using a title of the dos box?, which i'm not.Having looked at the start /? your correct in that it should be/start "tilte" /wait <command to run>
durex Posted June 8, 2005 Author Posted June 8, 2005 not sure if it was just a typo or not, but you want to make sure you take off the leading slash. also, from what Ive gathered, because its a shell command you need to call it though that...cmd /c start "" /wait "command to run"
Noise Posted June 8, 2005 Posted June 8, 2005 No. It's simply because the start command expects the first set of quotes to define the title. It doesn't change the title of the command prompt, in fact I don't know what it does.What I do know is that if you don't use it this way you'll run into problems. Especially if your first set of quotes is used to specify the program name and you need to use quotes in that programs command line.
durex Posted June 9, 2005 Author Posted June 9, 2005 (edited) Actually, a title isnt necessarily required. The only time its required is when you use quotes for your program/command, of which you only need to use if there are spaces in either the program name or path. So when you do use quotes, the start command expects the 1st set of quotes to be the title and the second set of quotes for the command to run. Lastly, you dont need to actually need to put in a title description, using 2 double quotes will also suffice.So.. the following all work.start /wait c:\blah.cmdstart /wait "this is my title" c:\blah.cmdstart /wait "title title" "c:\blah.cmd"start /wait "" c:\blah.cmdYou get the point....Oh 2 other things... the title does in fact set the title bar of the command prompt window the command is running in; its the only function it serves and it doesnt matter if you place it before or after the '/wait' parameter. Edited June 9, 2005 by durex
oioldman Posted June 12, 2005 Posted June 12, 2005 durex, your right was sa typo that put the / in front of start.Did you manage to get this working? as i've plugged away and so far no luck.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now