Hey no problem man, thank you for the email!
Just as a little history, I was finishing install of Zone Alarm, it presented me w/ the option to scan my existing programs, then reboot; it got stuck during the reboot (maybe trying to sniff out boot sector viruses or something?). Then kept getting UNMOUNTABLE_BOOT_VOLUME blue screen (reason 0xC0000006). Rebooted from CD/Recover Console, tried to run CHKDSK /R couple of times as suggested for this problem; it would get at max 50% of the way through before reporting "1 or more unrecoverabe problems". Ever since then, when booting, I get the "something's wrong with your hard drive" msg, then I get the UNMOUNTABLE_BOOT_VOLUME. I never tried the "FixBoot" command from Win Recovery Console.
Tried "GetBackData"s product (sorry, didn't see yours out there @ 1st!), but it only counted 63 of my 150M+ sectors/failed on the rest. I did notice that in GetBackData's "DiskExplorer" had the word "Invalid" across all but 1st of the sectors in the partition table, so it appeared I may have a corrupted partition table. I then enlisted your product. Tried the DOS boot disk ver of PTD, but couldn't find "Bowse root", which brings me to the current point (trying BartPE).
After including CAB files for both products, could get DRW to run, but not PTD via BartPE. I figured the partition table repair feature of DRW was bascally what PTD was doing (a "superset" of PTD functionality), so I kicked one off. I cancelled it abou 40 mins through, as it looked like to was going to take several hours to c omplete. I did this thinking "ya know, I haven't even tried 'FixBoot' yet; what if it works and I can boot w/out having to go through the partition scan/repair?"; I'd been hesitant because I didn't know what kind of damage it would do/how much it would limit my opportnity to try the other utilities if "FixBoot" didn't work if it wrote stuff to my disk.
So, I figred if "FixBoot" didn't work, I could at least use DRW and go back to the long partition scan/repair. So then I loaded the DOS boot CD back - and from rereading your documentation, saw that the drive had a red "X" next to it anyway - so I did a "FixBoot". It ran for a while, then hung onck on "PTD trying 14 sectors per cluster" and "please wait... 32%" (it started w; "8 sectors per cluster"). Since that didn't seem to work, I restarted the computer, and loaded up DRW again, started Partition Recovery again and it went into quick partition scan again (that looked like it would take such a long time before); to my surprise, from how fast it progressed in the beginning, it looked as though it would complete a lot faster than it did before the failed/hung "FixBoot" attempt - which it did.
It found the partition, said data quality was "High", but "Files/Folders" was "0", and no FAT or NTFS options were listed. I hit "Next", it presented a treeview "NTFS>RAW" and listed some generic files, but not even close to the # of files on the drive or named anthing like the old file names. What if these "RAW" types didn't cover the kinds of files you were looking for on the drive? Some i portant files I was looking for had nothing to do with the default file types listed. I don't even know why "RAW" files came up; does that mean it couldn't find the normal files? Sheesh. Anyway, I backed out of this screen since it wasn'r even close to the files I was looking for/files on the drive - then my "C:" drive no longer was showing up - either in "Complete Recovery" or "Partition Recovery"! I rebooted BartPE and the C: drive showed up again.
I then booted back up with the WinP ecovery Console and tried its "FixBoot"; that seemed to screw everything up! From there I tried to reboot with your bootable DOS CD, but got "BIOS cannot process interrupt 13 extensions" msg - and now, the BIOS won't even run!!! I can't get anything to boot. Times like this makes you hate Windows! Wha the hell did Windows RC "FixBoot" do?
Lost and confused. I guess my only hope now is to ship the drive off for hardware recovery (if that will even work!).