R
RDI
I've got an executable that I'm running from my login script. The
executable requires a mapped drive (can't use a UNC path). We don't want to
leave this drive permanently mapped. So I tried to use the "Start" command
to run the executable and wait 'til it finished. The executable finishes,
the loginscript needs to Unmap the drive.
rem When the Net Use command tries to unmap the drive
rem I get a message that files from the o: drive are still being used.
rem Why is the script regaining control BEFORE the executable
rem finishes?
start o:\SCAN\HSLAUNCH.EXE O:\SCAN /wait
net use /delete o:
The following comes from the help:
<<When executing an application that is a 32-bit GUI application, CMD.EXE
does not wait for the application to terminate before returning to
the command prompt. This new behavior does NOT occur if executing
within a command script.
When it says "script" wouldn't that be a batch file?
executable requires a mapped drive (can't use a UNC path). We don't want to
leave this drive permanently mapped. So I tried to use the "Start" command
to run the executable and wait 'til it finished. The executable finishes,
the loginscript needs to Unmap the drive.
rem When the Net Use command tries to unmap the drive
rem I get a message that files from the o: drive are still being used.
rem Why is the script regaining control BEFORE the executable
rem finishes?
start o:\SCAN\HSLAUNCH.EXE O:\SCAN /wait
net use /delete o:
The following comes from the help:
<<When executing an application that is a 32-bit GUI application, CMD.EXE
does not wait for the application to terminate before returning to
the command prompt. This new behavior does NOT occur if executing
within a command script.
When it says "script" wouldn't that be a batch file?