DigitalVolcano Software Support

Long standing and happy user of Duplicate Cleaner Pro 3.27 - command line options working fine with that until the upgrade.
Upgraded to Version 4 and the command line options don't seem to work.
Even the examples in the help file, pasted into the command line have no effect - I didn't create the folders in the examples, but I don't even get error messages saying the folders don't exist.

For the sake of clarity this is the command I'm using and my system specs; Windows 10 64 bit, fully up to date, clean of viruses and malware;

I CD to the folder first, but this would be the full command - I add quotes if there are any spaces in folder names.

C:\Program Files (x86)\Duplicate Cleaner Pro\DuplicateCleaner.exe /i f:/Media

I've tested and they are working correctly. The only difference is that it is giving no error message if the folder does not exist - just ignoring it. I'll get an update to that so it fails if the folders aren't there.

You example below is probably failing because you've used the forward slash rather than backslash on f:/media ?

Hi, thanks for the reply.
My mistake with the command line above, yes, I used the wrong slash - I usually use a custom button in FreeCommander which passes left pane/right pane direct to DuplicateCleaner.

Anyway, reverted to v3.27, ran

C:\Program Files (x86)\Duplicate Cleaner Pro\DuplicateCleaner.exe /i f:\Media

The software opens with f:\Media added to the "Folders to search" list.

Install version 4, hit cursor up and run the same command again, no f:\media in "Folders to search" list.

In a Windows 7 32 bit VM which has never had Duplicate Cleaner installed, downloading the v4 pro installer, installing but not registering, running the following command from the C:\Program Files\Duplicate Cleaner Pro folder

DuplicateCleaner.exe /i C:\Users

Still brings up nothing in the Folders to Search pane.
Running the command prompt as Admin and issuing the same commands makes no difference either.

Installing v327 Pro over the top, not registered, same command, C:\Users appears in the "Search Paths" pane.
Both files downloaded direct from DigitalVolcano's site.

The MD5 checksum for the v4 installation file i have is as follows if that helps, downloaded direct from DigitalVolcano after I received the discounted v3.27 upgrade email;

4FCACF4E20BAA18BB5BC0F87EB546526 *DuplicateCleanerPro4_setup.exe

You say you CD first, but to where?
To Duplicate Cleaner's program folder, or to the directory you're wanting to add/search?
(I suppose its got to be the former?)

(
Unable to check command-line operation, at present.
Anyhow...

4FCACF4E20BAA18BB5BC0F87EB546526 *DuplicateCleanerPro4_setup.exe

RFE: Post Version Number & (MD5 or whatever) Hash On (all) Downloads Page(s)
)

I open a command prompt and CD to the folder where the DuplicateCleaner.exe file is.
C:\Program Files (x86)\Duplicate Cleaner Pro on a 64 bit system
C:\Program Files\Duplicate Cleaner Pro on 32 bit system

Confirmed.
Does not look to be working?
Duplicate Cleaner opens
Folders to search says, "Add folders to search here".


(I'm on 4.0beta4.)


The same command in 3.2.7 populates the Search Paths with: c:\out\.


Changing database.ini to point "locally" made no difference.

4FCACF4E20BAA18BB5BC0F87EB546526 *DuplicateCleanerPro4_setup.exe

I got a different (MD5) hash: 529dd870119795ea16b12a5b6f9d641b

DuplicateCleanerPro4_setup.exe, 8,451,752, 05/16/2016, 09:35:29 AM


(Let me test that in a moment...)


Did an install.
Initial run of Duplicate Cleaner:
Prompts for language, then...

Error adding path(s): Object reference not set to an instance of an object.

(In my case, I'm unable to activate 4.0 with the license that I have.)

Thanks for your input - I downloaded the file again, 1kb larger than the one I had, and yes now the MD5 matches what you posted, and yes, I get the same error when I include a path.

Not sure if that's progress!

OK, bug noted ("Object ref...") - I've fixed it and it'll be in the next update.

You can still add paths from the commandline via an already saved profile (.dc), if that fits your workflow.

OK, thanks, will look forward to the update.