in reply to detecting activities of scripts

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

Replies are listed 'Best First'.
Re: Re: detecting activities of scripts
by flyingmoose (Priest) on May 13, 2004 at 19:29 UTC
    Yep, InstallShield apps almost always can be fed a setup.iss file to make them install silently. Running GUI ("is this on my screen") checks is definitely hackish, wouldn't go there. If setup.iss doesn't work for one or more of your programs, I'd suggest you see if you can get them fixed, as this isn't your problem, but a problem with those installers.
[reply]

In Section Seekers of Perl Wisdom