Be sure you're using SHELL and not RUN to launch the setup commands.
Even when you use SHELL, many installers launch a second install process to do the actual work. When you run it interactively, you can't tell, but it screws up automation since the command that the script calls exits in a few seconds after initializing the "real" install process. If this is the case, you'll need to do nothing less than monitor the install process. Basically, launch the pre-installer, loop waiting for the actual install process to start, and then loop waiting for it to end. There are several UDFs to return a list of processes, including WMIProcessList.
Glenn
_________________________
Actually I
am a Rocket Scientist!
