retrieve/rebuild file info corrupted by data recovery?

scissorman

Registered
Below is a copy of a thread I posted at Apple Discussions/Mac OS Technologies. Can anyone here help?

I sent a failed ext. FW drive (clicking sound, wouldn’t mount) to a fairly-well-known data recovery specialist that advertised PC and Mac formats. The drive contained numerous Mac-only files, including Sound Designer II audio files (.sd2), Final Cut Pro (.fcp), and Digital Performer files (native, no suffix), to name a few.
After said specialist started working on the drive, it became frighteningly apparent that they were not up to speed on Mac systems. To make a long story short, after a couple of weeks I received a hard drive formatted FAT32, and every Mac-only file showed up in Finder as a Unix Executable file.
My first thought was they were using Windows-based software and had corrupted all my Mac-only files beyond repair. Forging ahead and knowing nothing about scripts, I used a 3rd party program called Super Get Info and was able to change the Type and Author of the Digital Performer files, and got them to open. So far, so good. But changing the Type and Author of the .sd2 files didn’t yield the same results; Finder sees the type, size, etc. but no audio program (DP, Peak, Jam) will open them.
Thinking I was screwed, I opened another project in DP that contained audio files which were still recognized in Finder as Unix Executables, and they played! I have no idea why this works---no other program will open them independently---but it shows if I can get an app to recognize them, they are still valid files.
Is there a way to dig deeper, besides just changing the Type and Author, to essentially get back all the header(?) information that was originally there in the .sd2 files (before the “data recovery”) so an audio program can see that these are indeed valid files and it’s legit to operate on them? Something in Developer Tools, 3rd party, etc.?

Thanks!
 
The Finder and some applications still use the resource fork which FAT32 does not handle at all. So all those are lost when they copied your data to that volume. Some applications may not use it and then that's probably why some files work and others don't. I'd be going back to the company as they didn't do it correctly at all. They should format the drive as HFS+ and do it the right way. Or refund your money and get another company to do it.
 
Thanks for the reply---had it on my teleprompter as I called Gillware (oops, wasn't going to reveal their identity!) and demanded they reformat the drive HFS+ and transfer the data again.
They said they would "try" and they've "never had a problem like this before."
A programmer friend of mine could only comment that this experience was "wrong on so many levels."

Guess I'm still wondering if there are other resources for manually editing a file's resource fork, Unix number, etc. or if that's off-limits.
 
Hopefully they'll do it right this time. You can manually edit the resource fork with a program called ResFork in OS X or ResEdit in OS 9 which allow you to do all kinds of things to the resource forks. But I wouldn't suggest this for most things because it'd just be a huge pain to do it all by hand. And you have to know the 4 letter resource codes for each file type.
 
Back
Top