- This topic has 8 replies, 1 voice, and was last updated 3 days, 10 hours ago by
.
-
Posts
-
Have something to say about DoYourData Recovery Pro? Say it here!
Have suggestions, comments, or need help? Post it here! If you know of better software than DoYourData Recovery Pro, post it here! If you know of issues with DoYourData Recovery Pro, post it here! Share your knowledge with all of us. :-)
[ @Ashraf] on their webpage you link to it says:
“Support Windows 11/10/8/7/Vista/Server”
I just tried my older version 7.8 of this on my Vista server and after update check it promptly popped up a software counterfeiting warning window that on dismissing it the program closed … I know that was obtained from a legitimate giveaway on giveawayoftheday and was in no way counterfeit. Hopefully (though net desperately hopeful) this new version will be compatible with Vista like it says on their website … though I’ve never had a reason to use it in anger due to no data loss that I’d need a file recovery program for… Sadly doyourdata product page stating Vista compatibility is a lie and oddly Ashraf got it right this time! I was able to reinstall 7.8 from my archives but the original giveaway license failed to activate BUT THIS giveaway license did activate version 7.8 so is not version locked to this giveaways version.
[@TK] NOTE the release version of this on their website is 8.2 NOT 8.3 that means we are being used as an unannounced public beta test of version 8.3 there is NO published version history for this product so who knows what bugs it’s got or had… feel free to download their previous stable release version 8.2 and use the giveaway license here. Personally I find this not particularly unique amongst file recovery programs version 8 of this changes the UI compared to 7.x it gets rid of the pointless Desktop drive entry that just mimicked the C: drive action. Version 8 adds a disk management section that is a bit of a scam as it just repackages windows built in functions into their GUI… repair just runs CHKDSK with a auto approve script that responds “Y” to run a chkdsk at restart on the C: drive and forces unmount on other drives that are in use which may lead to unpredictable results with files left half open and incomplete… we should always be the one that makes the decision to force unmount a drive… The format option is always available in the context menu of any drive letter in windows explorer and rename just changes the volume label on a drive you can just right click on the drive letter and select properties and rename the volume label there…
Another bug the installer defaults to installing into the 32bit C:\Program Files (x86)\ hierarchy instead of the proper C:\Program Files\ hierarchy. The installer includes bith 32bit and 64bit editions but the iss script logic fails to select the correct pf string. They are using quite an old version of inno installer compiler, maybe it’s time to upgrade and re-write the install_script.iss file. You can edit the default install path and put the program in the proper place if you feel so inclined.
oops another design FLAW is it writes THREE log files to the install folder each launch which A: is bad and unnecessary for SSD drives and B: could be overwriting deleted data you need to recover but cannot because the program just overwrote it with pointless logging that is of no use to man nor beast! I deal with unwanted logging by creating a new folder in the same location as the log file I want to stop writes to by renaming the folder to the name of the log file after deleting the previous log file, invariably the program will try to open the folder name as a file for writing and fail and ignore the error and give up. It also autoswitches from quick scan to deep scanning which can take hours on modern drives without asking and without an option to stop the deep scan! Oh hang on, there IS an option to stop the deep scan it’s just obscured by a light grey square button that LOOKS LIKE IT’S a DISABLED BUTTON! DUHHH stupid GUI designer! Oh great the UI has crashed because I X’d out of one of the interstitial windows before it completed and it left the GUI with a disabled main “X” button so I cannot use the GUI to close the program to fix some OTHER file writes it’s doing CalcPartition.log and videoRepair.txt both surplus to requirements on a release build with no telemetry reporting… and an always blank file recoveryFree.ini A file update.ini is created when one does an update check… reporting inside it 8.2 is the current version being offered I did the same folder rename trick on that too and that makes the update check fail but we are not supposed to be entitled to free updates to a giveaway license anyway…
Unwanted file writes prevented are:DYDLog.log
Eaolog.log
DefaultLog.txt
DYDUI.log
CalcPartition.log
recoveryFree.ini
Upgrade.iniOddly the file videoRepair.txt MUST be allowed to be written to or the program crashes when you try to scan a drive
This is a very poorly designed data recovery program writing megabytes of data to the installation drive by always saving scan results to the installation drive taking up tens of megabytes per scan done, you can delete the saved scans but you cannot prevent them from initially being created unless one does a similar trick and copies a 0 byte text file to the install folder and rename it to SaveScan after deleting the original SaveScan folder so the program silently fails but continues when it tries to open the now non-existent SaveScan folder as well as performing many unnecessary file writes described above as well as some others in the config sub folder.
In it’s default installation it is a fundamentally destructive program, overwriting previously deleted data on every execution and even more so after each scan and update check. If I were in the habit of losing files through bad data resilience practices or hardware failure I would choose a far less destructive file recovery solution.
Don’t work on USB drives as it can’t find them
Hi
Do Your Data Recovery Professional
