Just spent a couple days using iRecover. I didn't have much luck getting my data back, but none of the other programs I tried would work either, so it must just be too badly damaged.
I do have a few suggestions to improve iRecover though...
- During validation, iRecover needs to be able to validate more file types... especially important data types (.QDB = Quicken, .CDR = Corel, etc.)
- At the end of the process, when you are choosing files to restore, there needs to be more views than just the tree view. A "details" view similar to that in Windows Explorer, with the addition of a "folder" or "path" column and a "Valid/Invalid/Unknown" would be nice.
- The ability to "show only valid files" and "select all valid files" when choosing files to recover.
- When choosing which drives to include, show the drive serial number (or provide "Properties" for the drives.) Controllers aren't always numbered on the mainboard/controller in the same order as Windows sees them.
- When creating an image file, allow the file to be broken into smaller pieces, either set by the user or if the disk ends up full.
- Provide the user the ability to set more of the search paramters. For example, I know what order my drives should be, so let me specify that specifically.
- If a user has backups of some of the files, let the user provide those files to help determine the layout of the files/partitions/arrays.
- When in the Analysis stage, provide a "Step x of y" in the Current Operation area. Counting up to 100% a bunch of times doesn't help the user know how far into the process the analysis is.
- Let the user specify what RAID controller was used. This should help identify what parameters may have been used to create the array and how parity is stored, etc.
...anyhow, this is a great program. I appreciate the ability to try before I buy. Hopefully I won't need to try it again.