• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

winternal's DISKCOMMANDER vs. ontrack's EASYRECOVERY

abc

Diamond Member

seems like both of these products are the 'one-two'? punch? in the file recovery of disks that are not physically damaged, just corrupted?

can anyone be kind enough to share some opinions of either or both, if you have used both, or vouch for something other than these two?


one of my pcs got a corrupted OS and cannot boot, cannot reinstall the OS -tried both win2k,XP Prof. off cdrom because it halts midway in the cdrom to hd data copy process... the error message I is something about the cd not having a certain file (false) well I think is not important now.


but it all started with a system crash and failure to reboot becuase a kernel file is missin/corrupt, last known config was useless.

so i tried rerunning the cd, but it would fail. then i found out it was because of disk corruption, so I ran scandisk a few times to clear things up.

but after it starts scanning clean, i reran the OS cdrom, but it would stall, giving a error message (which I said is not important anymore)

thanks!
 
boy, I tried ontrack's product on a drive that is pretty messed up (but no physical damage) and it took 6 hrs to scan and produced almost no results... loser app.

I used a old freeware thing called DriveRescue... and it shows ALOT of results.... however I'm only restoring 1 file at a time as the freeware version does not allow restoration of an entire folder at a time...

It has since be sold by the author to some company, who has revamped it and sells it commercially.

Anyhow, anybody has used diskcommander from winternal?
 
so i tried rerunning the cd, but it would fail. then i found out it was because of disk corruption, so I ran scandisk a few times to clear things up.
but whats causing the corruption in the first place ? have you tryed the drive manufacters utility ? also could be a bad stick of ram.
just some thoughts
good luck
 
what caused the corruption was boot failure, a win2k file got corrupted 'missing, corrupted' etc. message.

tried to reinstall the os and everything went downhill from there.


i can scan the drive with a freeware European thing called File Recovery, and it shows ALOT of files, shows the whole DIR structure, good job there.

however I dont think any recovery prog. can correctly recover files that are larger than say 2-6 MB in size.

it will 'recover' large files but when you use them you'll encounter errors in the file.

 
Back
Top