One practical approach might be to start your software install programs with their silent flag and look for the exit code (assuming you are using system to fire them up). Another approach is to start the installers with Win32::Process You can then SetPriorityClass, Wait, GetExitCode and Kill them if they have not successfully exited after a sufficiently long period determined by you in the Wait.
cheers
tachyon
In reply to Re: detecting activities of scripts
by tachyon
in thread detecting activities of scripts
by blackadder
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |