DirDate is not free but you might find other touch tools that are. It makes use of DirDate.exe, which you can download from. Use a "touch" utility to apply the folder dates to the target folder.Use robocopy to copy a folder, complete with subfolders. " It appears that robocopy will not preserve the date stamp of a folder. To retain directory timestamp when copying between drives you can use as starting point: That said I found this thread on experts exchange how When the OP eventually upgrades to a newer version of Windows, such as Windows 10, he will have a recent version of Robocopy where this old bug has been patched and this logging glitch will no longer occur.I agree with you: moving files doesn't preserve folder timestamps onlyĬopy will prevent it for changing (I tested it by using Robocopy.exe command on His immediate options are to either use XCOPY or some other file-copy utility. The OP will not be able to upgrade his version of Robocopy as Windows 7 cannot use anything newer than the 2009 version. The OP could put 20 GB of data in there and Robocopy would still report an instantaneous transfer! Had these file copies really taken place, then "100%" and "New File" would have been shown beside each successfully copied file. Just to clarify what's shown in the first green box: I added the " No 100% New File" lines to show where the log was correct to show blank space. Subsequent copies across two different volumes will take approximately the same time. This can be easily demonstrated by performing a copy job that includes a relatively large file and observing how long it takes, then deleting the large file from the destination drive and re-running the same job. USB bandwidth and flash drive write speed). Whatever bottlenecks limited the speed of the initial file copy would affect subsequent copies in exactly the same way (i.e. If copying a file from one volume to another takes 42 seconds the first time around, the same process can't take 0 seconds the second time! The instantaneous copies we're seeing here are impossible. Robocopy actually does exactly what it's supposed to here, it just incorrectly reports it. There's no question that the problem is with the logs rather than with the copy process itself. I was unable to recreate this issue on my Windsystem, which has the latest version of Robocopy. Robocopy is just a utility that will call into underlying file system components. Unfortunately, Windows 7 lacks certain prerequisites required by the current Robocopy executable, so the latest executable cannot simply be copied across from a Windows 10 system:Įven copying from Windows 8 is not going to work as underlying components have to support it. BAT, it errors out stating that it’s not a valid Win32 application I tried copying Robocopy from Windows 10 (64) PC on to my Windows 7 (64) but when command is put in. I am certain this is not possible with 312MB data on USB 2.0 pendrive. It finishes in 0 seconds but still logs 2 files and stats show 2 files copied. It takes 42 seconds to copy then to USB 2 pendrive destination. I placed 2 large files in source together 312 MB. I believe it's not copying but still logging. I checked using Free File Sync, both directories are in Sync when it comes to file size, timestamp and actual contents. FFT or absence thereof does not change the log data. Would greatly appreciate further clarity on this.Ĭase 3 - No change, still it list all 4 files in log file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |