I searched around a bit but couldnt find as to whether or not anyone was successfully using the 'start /wait' command in their RunOnceEx.

im not sure if its possible through the runonceex method,, but i think you can use a sleep.exe prog to delay programs with in the runonceex if thats whats needed,,

just my thoughts

Start is a command in the cmd shell, so you would have to call it through that. The nice one liner would be

CMD /C START /WAIT ooglyboogly.exe /moo

So has/is anyone actually used/using this without issue?

Ive just run into a couple items in my RunOnceEx which start prior to the previous job finishing, which I dont want to happen. So to keep this from happening and to also clean up my RunOnceEx, Ive decided to create a batch file for all of my program installs which will contain the install command.

Yes I know... I should just test it for myself, but Ive been way busy lately and need to reformat my pc pronto.

Thanks as always guys.

I've been away that long, I forgot how to use the search function...

http://www.msfn.org/board/index.php?showtopic=47319

instead of

• start /wait "mydrive:\mypath\my app.ext"
  

try

• start "" /w "mydrive:\mypath\my app.ext"
  

Im well aware of how to use the start /wait function... my question is whether or not they work in RunOnceEx.

If you implement start "" /w(ait), for your applications all within a single batch file run from runonce, then it should work perfectly, as it did previous to RunonceEx when we all used a start.cmd file. You may also prefer to use cmdow, or similar to hide the window whilst running.

Also my initial response wasn't to belittle you, but you said start /wait, when it is a fact that using a title, whether blank or not, is proven more successful. I just thought that you may fing that using that particular syntax would make your existing RunOnceEx work correctly without having to resort to this method as an alternative.