DSynchronize won't synchronize since last update to that software.
I can't tell much about the causes but when I start synchronization it will just stop somewhere during phase one. Not during an action like deletion or creating new folders.
Anyone else have these problems ?
Is there any additional info that I can possibly provide to help solve the problem ?
Can you test this against the base app? (Download DSynchronize from http://dimio.altervista.org/eng/ and test the app that way.) Does it still do it?
I downloaded the base app from the authors site and checked the MD5-sum and it is exactly the same as the Exe in the PortableApps.com installation. Replacing the PA Exe with the downloaded Exe didn't solve anything (as expected).
He didn't say to replace it. He said to download the standard portable version from the publisher and test that.
Sometimes, the impossible can become possible, if you're awesome!
I have now tested the standard portable version from the publisher. I found that it will successfully add a few files and then gets stuck during the first replacing of a file. This file is a Microsoft Word file (Office 2000) with a .DOC extension. It's only two pages of text and has no graphics.
So it's either an issue with DSynchronize itself or your PC, not DSynchronize Portable. In that case, it sounds like it could be a drive error. Please check your source and destination drives for errors.
Sometimes, the impossible can become possible, if you're awesome!
Done a chkdsk/r on my pendrive and it didn't find anything wrong. The source Pc is a office-Pc therefor I do not have the authority to do any chkdsk there. I have just installed the new update to DSynchronize Portable, so next week I'll be able to report back on new attempts.
Today I tried the updated version and it will not do any synchronizations. It will start indexing and then stop working. The interface will just freeze and become unresponsive. Then when I restart the program my settings and all path's are gone as well.
As we don't publish this app, we merely portablize it, I'd suggest reporting the bug to the publisher. Our updated version was just to fix a portablization issue.
Sometimes, the impossible can become possible, if you're awesome!