chiners_68 Posted March 17, 2006 Share Posted March 17, 2006 (edited) I have one aplication i want to activate through runonceexe.cmd but then want the cmd file to continue to the next command.at present it waits till the current install has completed before moving on.is there a way to get it to move to the next line without waiting..? only want to do this for 1 or two lines not all..in using the runonceex as explained here.. http://unattended.msfn.org/unattended.xp/v...d0bbda27204c49/ Edited March 17, 2006 by chiners_68 Link to comment Share on other sites More sharing options...
Lazy8 Posted March 19, 2006 Share Posted March 19, 2006 Most people avoid running multiple installations simultaneously, for obvious reasons. I guess that explains the poor response to your initial post.Instead of calling your program directly from the RunOnceEx line, why not use a .cmd file execute it? It should close as soon as it opens the program, leaving RunOnceEx to proceed to the next line. I have yet to try this, so I don't know how well it will work (or guarantee its stability). It's simple enough to try right away, though. Link to comment Share on other sites More sharing options...
chiners_68 Posted March 20, 2006 Author Share Posted March 20, 2006 ill give it ago.i ciurrently call my office install as the path is long pointing to an mst file. the only problem is, is the cmd box stays open till office has completed. This may not be the case for all aplications so ill give it a go.. Link to comment Share on other sites More sharing options...
Lazy8 Posted March 20, 2006 Share Posted March 20, 2006 Command box, eh...are you using the CMDOW utility in your instructions? Link to comment Share on other sites More sharing options...
lasswellt Posted March 21, 2006 Share Posted March 21, 2006 ill give it ago.i ciurrently call my office install as the path is long pointing to an mst file. the only problem is, is the cmd box stays open till office has completed. This may not be the case for all aplications so ill give it a go..i believe as long as you don't use "start /wait" and put a quit at the end of your cmd statement, it should close your command box up.hope that helps Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now