acforensics wrote:Jono,
I just bought one. I'm used to Data Extractor. How does it compare? I know you can't disable heads.
A
I think you'll figure it out soon after you start to use it.
I use DE when I have to disable heads, and DI when I don't. With DI there is a great deal more flexibility than DE.
A few other DI features:
1. Skip sectors based upon specific errors;
2. Clone and wipe drives;
3. Show the stream of binary data along with the sectors map, which is helpful in determining where you are on the drive without switching to a separate map;
4. The various parameters are extremely variable, so you can fine tune the recovery;
5. It's easier to go back over specific read errors to try alternate methods
6. Redundancy -- vs. with DI you have to tie up the PC3000 PC
7. An image map function is available, where you can see what's going on with the entire drive and exactly where various problems are located.
8. DI doesn't really use the CPU BIOS, so it's faster
9. You can do multiple passes and get the "easy" data first, which is important when you have limited time to work because of a failing drive
OTOH, DE seems to work better with some kinds of recoveries, but it may be that I may not have mastered fine tuning of DI. Also, DE is good when you have to keep the drive energized right after a firmware fix, and you don't want to interrupt the recovery process.
With DI, you have to fix the firmware problems first (just like DE) for optimum results. You could still image a drive with a bad translator if you wanted to, but you have to deal with the translator issue eventually.
This is not an exhaustive list, but it should give you a good idea.
Jon