>Our distributed VFP6 system provides for downloading and installing new exe files in a self-extracting exe file. Upon a successful FTP download, a batch file is created and run that contains commands for running a shut down exe that shuts down all copies of the system, running the self-extracting exe, deleting the self-extracting exe, and running a startup exe that starts up the master copy of the system.
>
>The process works flawlessly under Windows NT, 2000, and XP. However, it does not behave properly under Windows 98 as the batch processing does not wait for each step to finish before starting the next step. As a result the self-extracting exe fails because at least one file being replaced is still in use when it is started.
>
>The exe that shuts down running copies of the system has code in it to keep it running until the window handles for the running copies have been released which is intended to keep the next step from starting prematurely.
>
>I have made sure that the Windows 98 machine has a copy of foxrun.pif and that the backgound processing is not always suspended. Also because the batch file does not close at the end with the exit command, I have confirmed this background processing status at the time it runs.
>
>Any ideas out there?

Is the Windows Script Host an option?