I was recently testing command lines for Robocopy on Windows 7. I failed to have quotations around the path and file name of the log file, so it was rejected as an invalid parameter.
D:\K_DRIVE\Delphi XE projects\Backup Menu\SynchronizeFiles.log << this is the full path for the log file that I asked for - not part of the error message. I don't see how it generates any improper command line switches.
Now, every time the machine reboots, Robocopy appears to run with one of the bad command lines and tries to display the resulting error file. I have to tell it to use Notepad, then the error messages looks like this: (the first time this happened was May
6 and the error is always May 6, so perhaps it is just displaying the error every time the machine boots?) Notepad does not show a file name in File > SaveAs so it appears to be generated during each boot.
-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows :: Version XP010
-------------------------------------------------------------------------------
Started : Fri May 06 17:07:49 2016
Source - D:\My Documents\Diary\
Dest - X:\diary\
Files : XE
Options : /TS /L /TEE /S /E /COPY:DAT /PURGE /MIR /XA:ET /R:1 /W:1
------------------------------------------------------------------------------
ERROR : Invalid Parameter #13 : "projects\Backup"
Simple Usage :: ROBOCOPY source destination /MIR
source :: Source Directory (drive:\path or \\server\share\path).
destination :: Destination Dir (drive:\path or \\server\share\path).
/MIR :: Mirror a complete directory tree.
For more usage information run ROBOCOPY /? or read Robocopy.Doc.
NOTE: Read "True Replication" in Robocopy.Doc prior to first use of /MIR !
**** /MIR can DELETE files as well as copy them !
=============================================================
I have searched the registry, taskmanager, event viewer, msconfig, and StartupCop. I can find nowhere that Robocopy is being run. I have never deliberately used the scheduling commands for RoboCopy. I've also searched the hard drive for some of the text in this message. No luck.
Can anyone explain where this bogus message is coming from during bootup? And better yet, how to stop it?