Software Deployment

hi ,

When you run any install or command in wise script using " execute a program " .
please check if you have checked the checkbox "Wait for Program to Exit" .

Hey MahendraKumar,

That is there and the script keeps on jumping to the next command before finishing the first one. Once again "Pause" function does help, but I am looking for alternatives, just like the title says.

Thanks
Best Regards

i bet the setup launched is calling some other executable file and quits. i saw that behavior often enough.

Well, first of all it doesn't quit. Setup is not launching any other executable file either.

Okay, let me see if I can revisit the question here a little more clearly, I might be confusing people here.

I have a wise wrapper which is running multiple command line to execute different functions. Such as, clean up the previous version clean up the previous entries from any directories it exists. Then go ahead and install the actuall .msi and then trying to do two more thing. Problem is that I have to put some "pause" time to it in order for it to actually make sure it does all that, otherwise it doesn't wait to finish for (let's say the the 3rd command) to clean the c:\Program files\ABC or run the batch file to clean that and jumps to the forth command. This is where I have to put the "Pause" in there for it to actually make sure it runs the command or run the batch file to clean that and then move to next one instead of just going to next one. Now again the question is, does wise offer any other alternative to "Pause" function?

Sorry if my question caused any confusion.

Thanks.

see post #2 and make sure the option to wait is checked

See post #3......[:)]

I have never bothered with WiseScript, but I know that it can access Windows APIs so why not use that capability to find the set-up process's handle and then wait for that process to end? And no, I can't help with the code for that but I'm pretty sure I saw a fragment on Symantec Connect.

Sometimes in WiseScript I've noticed the 'pause' feature causes some sort of weirdness in which all processes halt that are launched in the background instead of just the script pausing while waiting for the set amount of time to pass. To get around that, I've called up sleep.exe available from various sources. When I call up an external pause feature it seems to function properly in those cases.

VBscript might help for this problem :)

Ok, so VBscript is the best answer thus far.

Case Closed.

Thank you all

AK