In theory there should NOT be a problem as long as he plugs the disk back into the same cable it came off of.

When a qualified technician can use the design and format documentaion to build tools to recover what with great certainity will soon be lost, the tool becomes much more comprehensive, and will in all cases have a higher success rate than a tool developed with little or no knowledge of the design.

As an example, Exchange recovery is at best hit and miss, and at its worst using stone knives and bear skins to solve a modern problem. The file format of the ‘priv’ file is not documented anywhere, and that “SECRET” has cost many an admin their job, and cost many companies millions of dollars. If the format were made open source, then wonderful tools could be developed that would recover a much higher percentage of Exchange crashes.

This is of course, only my opinion. However, an opinion steeped in 25 years of computer programming and data recovery expertise.

Hello Dick,
Well, it’s been about 10 days since we last spoke. Last weekend, I finally had enough of the financial files recovered so we could start posting our billings for the previous 4 weeks. This past Friday, we did our first insurance billing. I’m finally sleeping at night again.
I just wanted to thank you for all you did, and all you DIDN’T do. You didn’t bullshit me, you didn’t delay me, and you didn’t keep me from helping the process along. I’m not sure how many knowledgeable, professional, no-nonsense people there are in the world, but I do know there are precious few. You are one of them, and I appreciate your help. Winhex is a great program, and by the way, I’ve discovered it’s relatively easy and fast to use Access to eliminate duplicate records from a file. You can also use Access to compare two files and eliminate duplicates in both.
I’ll send your drive back as you requested. I’d like to hold onto it a few weeks just in case I find I’m missing a file I forgot to retrieve. Let me know if that’s not OK.
Again, thank you.