I just tried using DEDUPE for the first time. Since I was not familiar with it, I used the command dialog (/=) to generate the command, so I was quite surprised when it generated an error message. The command started with
Yes, but it's NOT the /Nd ALONE which fails. It's the /Nj /Nd combo. /Nd without /Nj is working - also /Nj without /Nd is working ... so the error msg is confusing.
Exactly. I don't see what was wrong with the command, and it was created by the command dialog. I would like to think that the dialog would not allow the generation of an erroneous command line. I also don't see any incompatibility with skipping junctions and hidden directories.
Now I just tried the command again and am puzzled again. I seem not to understand how it is supposed to work. The command, run from a backup folder, looked like this:
Code:
DEDUPE /D /SHA256 *.pdf source_folder
There are many PDF files in the backup area that are also in the the source area, but the dedupe reported, "Total files: 80 Unique: 80 Duplicates: 0". I even checked the CRC values, and they definitely are duplicates.
Then I created a new file named junk.txt in my c:\temp folder, copied it to the c:\temp\conf folder, and set up the new command using the dialog:
Really? The help shows that one can name one or more target directories in which to search for the files. Unless that's just a way to run the equivalent of multiple DEDUPE commands in different directories. Do people really end up with duplicate files in the same directory (obviously with different names)?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
