I was recently asked to breathe new life into a dying script. One thing I would like to do with the script is reorganize it so that things the user depends on (ex. mapped drives) are taken care of immediately, and anything the user does not rely on or interact with can be performed in the background with another script. I was planning on using the "RUN" command to do this, but I have a few questions about how this would work:

If I issue several "RUN" statements in a row, each one will spawn a new Windows process, correct? So, theoretically (and I'm not relying on this assumption by any means), if a workstation has more than one processor, two of the "subscripts" could be executing simultaneously? Which would make it a bad idea for me to attempt to write to a single file with both "subscripts?"