4 replies to this topic

[kgiloo]

[IS PRO 12, SP1]

I have a Master Setup which calls some other IS Setup.exe.
Typically let's say it's a kind of a wrapper with an AskOptions Dialog.

I use "LaunchAppAndWait" with LAAW_OPTION_WAIT so that once the first setup is finished it starts the second one and so on...

When I start the Master Setup from the hard disc, things behave OK.

But when I burn the package on a CD-ROM, the function "LaunchAppAndWait" does NOT wait till the first setup.exe is done, it starts the second one right away after the first has finished to decompress the data.

What's wrong with LaunchAppAndWait? With IS 6 I had no problem...

Thank you for your help.

[kgiloo]

I compare the 2 processes:

From the HD: the started setup has a thread "setup.exe"
From the CD-ROM: the started setup has a thread "_isAF7.exe" <-- What's that?

[kgiloo]

_is###.exe is the clone.

/clone_wait solves the trouble.

/clone_wait : Wait for the cloned setup process to complete before exiting (InstallScript projects only)

[mmppeegg]

Excuse me,
Is the command "/clone_wait" is just for IS 12 or above?
My IS 10.5 project doesnt work...

[mmppeegg]

Hi all, it's me again
Final I use the parameter "/deleter" to solve this problem...
But this will cause anything wrong??

Edited by mmppeegg, 07 May 2007 - 08:43.