DigitalVolcano Software Support

Hello,

I am trying Duplicate Cleaner Pro 3.2.2 in trial mode.

I get the above mentioned error message when I start the scan process. (I get the precise message "Error in Scan Process: Illegales Zeichen im Pfad" as I am on a German Windows system and .NET replies likewise.) The Log file states exactly the same.

• Please tell me which character in which file or path is illegal
• Please tell me whether this is because of length of path, file name or directory name
• Just skip this path (at least optionally). Do not stop the scanning process for asking this.
  (To make clear: if I scan 6TB of data over night, I do not want the whole process to stop at e.g. 5% because of only 1 single "broken" or "illegal" file name.)

I would really love to buy this application, but not with such a huge drawback.

At the moment, I am thinking about doing "illegal characters" recognition by writing a small program in Visual Studio Express.

Sorry you are having trouble. Is the drive you are scanning a share from Linux, or a NAS drive? It might have a character illegal in Windows (but allowed in Linux) such as < > or ?.

That said, it shouldn't quit the scan when it hits this. I've raised a bug report to get this fixed. Thanks!

Hello and a big "Thank you" for answering!

Yes, this is because of Linux writing files to these disks (either because of multi-boot OS, or Backup and Recovery via Linux, e.g. PartedMagic Boot CD).

I didn't look manually for those directories where I suspect the invalid characters in file name. But I will look for them manually, as a workaround, and for the moment. It will be a acceptable count, as far as I can tell.

About the error message stopping the scan:
I get the simple notification box with the text "Error in Scan Process: Illegales Zeichen im Pfad", click OK, then I am returned to the main window. Then, the result lists "Duplicate Files" and "Duplicate Directories" remain empty, or, if a previous scan brought up results, those old results are being displayed.

I'm looking forward to see this bug resolved!

Thanks again!
gg.

DigitalVolcano wrote:Sorry you are having trouble. Is the drive you are scanning a share from Linux, or a NAS drive? It might have a character illegal in Windows (but allowed in Linux) such as < > or ?.

That said, it shouldn't quit the scan when it hits this. I've raised a bug report to get this fixed. Thanks!

Has this problem been solved? I wanted to buy today, but I cannot figure out through the Changelog (http://www.digitalvolcano.co.uk/dcchangelog.html) whether this special bug was fixed?

Thanks!
gg.

This bug has recently been confirmed in testing, as is slated for a fix in v3.2.5!

Hello,

I made the decision to buy the Pro version not long ago. I enjoyed many of the unique and great features like the Hard linking of files.

But I was disappointed when I figured out that this bug wasn't fixed since my first mentioning in November 2013. That is more than half a year for - from my view - fixing a bug that makes it impossible to use the program in certain situations. There have been 2 releases since then (3.2.2 to 3.2.4) and the next release promises to fix it. That's a very long time.

I understand (from a professional point of view) that maintaining software products is a very tedious task, which requires more than punching in a line of code here and there. I have to respect your work and your ways.

Nethertheless it is terrible that (from a user's view) a bug - not a feature request - hasn't been handled in all this time.

Of course I am looking forward to the mentioned release v.3.2.5 and I wish you success to fix that bug!

Greetings!

Btw, those characters can be created for testing from within Windows using Cygwin. I will look into if I can make a workaround that way.

The actual problem code wasn't isolated and fixed until after v3.2.4 (Pro) came out. The fix did make it into v3.2.4 of the free version though, but isn't listed. The next update will be out very soon!

I'm getting this error using the newest v4.0.1 of the client. Didn't see it with pervious 3.x versions, but now on every scan of a network drive the scan will find files and then while trying to identify duplicates throw this error and stop the duplicate checking.

This occurred with v4.0, and still remains with v4.0.1 release.

Will take a look at this. Which mode / criteria were you using for the scan? Any chance of pasting the end of the log file with the starting details of the scan that crashed?

thanks!