Why does the /W parameter of the start command work when starting other programs but not when calling internal commands? I have checked many previous posts and none mentioned the delay of START when calling commands, only when calling other programs.
How to make START wait for 200 seconds to complete after executing shutdown -s -t 200 in the above code, then continue to execute shutdown -a and wait for completion, then continue to execute START /W XCOPY /S/C/H/R/Y rpl\*.* d:\, and after the copy is completed, execute shutdown -s -t 100.
Explanation: Although each internal command can be written into a BAT file to achieve, but it is very troublesome when there are many commands. How to solve this problem? Is it really impossible for START to handle internal commands?
[ Last edited by HUNRYBECKY on 2006-12-30 at 11:55 PM ]
@echo off
rem To solve the problem that the download is damaged when the computer automatically shuts down after using EMULE to download, this script is written. The idea is as follows:
START /W shutdown -s -t 200
START /W shutdown -a
START XCOPY /S/C/H/R/Y rpl\*.* d:\
shutdown -s -t 100
@echo on
How to make START wait for 200 seconds to complete after executing shutdown -s -t 200 in the above code, then continue to execute shutdown -a and wait for completion, then continue to execute START /W XCOPY /S/C/H/R/Y rpl\*.* d:\, and after the copy is completed, execute shutdown -s -t 100.
Explanation: Although each internal command can be written into a BAT file to achieve, but it is very troublesome when there are many commands. How to solve this problem? Is it really impossible for START to handle internal commands?
[ Last edited by HUNRYBECKY on 2006-12-30 at 11:55 PM ]
