I've inherited a script (batch file) that installs a series of
application objects via calls to \sys\public\nal.exe using the following
switches: /A= /F /H /U. Each call to nal.exe is preceded by "start
/wait". I'm finding that in many cases nal.exe is exiting before an app
object finishes the distribution/launch process and returns control back
to the script, in which case the next app object is executed. The end
result is that multiple applications are installing at the same time,
which is not desired.

I'm toying with consolidating the individual app objects into a single
object as dependencies hoping that this will enforce a "wait" between

For discussion sake, is there way to configure the script-based approach
so that NAL won't exit prematurely?