Third run of Recuva duplicated the results of the second run, described above, with the same error message. Attached is the debug log of the run.
Once again, the scan reached 100% and then began spewing out error messages "Invalid Clusters Range" and was unable to recover any files at all.
As I mentioned, the all-or-nothing approach used by Recuva is self-defeating and means I cannot use it to recover my files, because it doesn't save the information as it goes. If it were to log every file found and place it into a file of my choosing on another drive, and then be able to use the file to go and recover the files it found, that would be an improvement. A bigger improvement would be for it to list the files in the main window as it goes, and not close the window when it encounters an error. Still better would be to make it ask for a drive/directory where the recovered files could be saved and to save those files so that one could examine them and restore the wanted ones after the scan is done (errors or not.)
I will now have to look for other methods to recover the files I know are present. The Disk Utilites package I have, which includes Partition Commander 10 Pro, doesn't appear to have any recovery program that works on a reformatted partition to recover the data that is still on it.
In addition, many of my files on that drive that I want to recover were generated by WordPerfect 11, 8 or 6 - all have the same basic format though 6 is slightly different. A program that specifically can recover .wpd and .wp files is needed. Among image files there are several types I want to recover including .pcx, .wpg, .tif, .wmf, as well as the supported .png, .bmp and .jpg types. Other document types I want to recover are .doc, .xls, .ppt, .ppd, .pps. .xlt, .dot (Microsoft); .ws (WordStar 4); .wpd, .wpt, .wpg, .qpw (Corel); .sch, .dat, .prb, .cir, (Microsim), .vb, .vbs, (Visual Basic), .fcd, .fcw, (Fastcad), and many more - mostly related to technical applications or older DOS and Windows applications. Some of these are simply text files stored with a different extension, so should be recoverable.
If you have a fix for these problems, let me know. Meanwhile, I'll appreciate any alternative solutions you can recommend.
Recuva_log_1_30_435__11_9_2009_19_40_.txt
Recuva_log_1_30_435__11_9_2009_19_40_.txt