I've written a script that will install a set of applications for a baseload I use at the office when i build computers.

here are the first two lines

START /WAIT "\\servername\smspkg\MICROSOFT OFFICE 2003 SP1\Source\SETUPPRO.EXE"
START /WAIT "\\servername\smspkg\CITRIX ICA CLIENT 7.10\WXP\setup.EXE"

Now, if that is run, just like it is, it will immediatly pop open another CMD prompt and take me to C:\WINDOWS and NOT launch the application that is in quotes. I think the quotes are screwing it up.

If I remove the quotes it will say that the path is invalid because of the spaces.

If anyone has any ideas about what I'm doing wrong, or if I could use a VBS script to launch the files, that would be fine also. I'm just looking for a way to install the "typical" 50 programs that our office needs.

try using 8.3 filenames probably something like:

START /WAIT "\\servername\smspkg\MICROS~1\Source\SETUPPRO.EXE"
START /WAIT "\\servername\smspkg\CITRIX~1\WXP\setup.EXE"

with or without the quotes.

nope. same deal

The 1st set of quotes are expected to be a description. Use this:

START "Office Setup" /WAIT "\\servername\smspkg\MICROS~1\Source\SETUPPRO.EXE"
START "Citrix Install" /WAIT "\\servername\smspkg\CITRIX~1\WXP\setup.EXE"

The 1st set of quotes are expected to be a description. Use this:

START "Office Setup" /WAIT "\\servername\smspkg\MICROS~1\Source\SETUPPRO.EXE"
START "Citrix Install" /WAIT "\\servername\smspkg\CITRIX~1\WXP\setup.EXE"

Yup! Thanks!

Could that be used in this case

D:\<offdir>\setup.exe transforms= setup.mst?

Or you could of course just forget 'start' altogether. The command line interface waits for an application to terminate by default. Unless you require the additional functionality of start, theres really no point to using it.

The 1st set of quotes are expected to be a description. Use this:

Didn't know about that....

I was going to say: use double backslashes in the path, that has worked for me in the past.