I have a small batch file that runs one-step-at-a-time on a Windows XP computer, but my Windows 7 computer blasts through all the commands in the file without waiting for the previous commands to finish, so my file transer/copy isn't done and it's already onto trying to rename the file and/or move it somewhere else. How do I get Windows 7 to run the .bat file the same way Windows XP did: one step at a time, waiting for each step to complete before moving to the next.
What you report is very strange since batch script statements are executed sequentially by definition. As far as I know, there are very very rare cases where this rule is disregarded, but for legacy plain DOS batch with special executables embedded. Post the script as more info is needed.
The behavior of batch scripts has not significantly changed since Vista. Without seeing the script or the environment, I'm just going to guess an anti-virus is getting in the way.
 |
|
| « creating a point of sale ... | Batch file help to backup... » |
TOM'S GUIDE AROUND THE WORLD | |
| United States | France |
| Germany | Italy |
| United Kingdom | Ireland |
