A member of my team is using SilkTest to run an InstallShield install. Seems the install kicks off and then invokes a second instance of Javaw.exe to complete the install process. This second Javaw.exe then opens a successive slew of install screens as the user works their way through the install.

What is happening (it appears) is that the original Java.exe is keeping the initial install screen open in the background. When the script attempts to set the Password screen active SilkTest is getting confused and setting this initial screen active.

Has anyone else encountered this and do you have a solution?