|Thanks for your help. I think I am about to give up. I added a pause command to the bottom of your suggested batch, to monitor what the batch file actually did when I ran it before it closed. With the ping command added to the end of the last line, as you had it, the batch file seemed to ignore the entire set of commands and skip to the pause at the end. No error messages, just nothing. No files copied. I then tried to add the ping command to the top of the batch file instead (I even extended the interval to some ungodly long value) to see if the batch file would hesitate before proceeding with the copy file routine. Here the batch file seems to just ignore the ping command and proceed to function as it had before. Lastly I asumed that perhaps the Nul at the end of the ping command should be spelled as Null. Making that change, the batch file still does not hesitate at all however it does create a little text file in the batch file root directory named Null that contains the following lines: |
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This doesn't seem like something that cannot be done which has left me feeling utterly frustrated. Looks like a picked a bad week to quit drinking.