ResEdit & lost resource forks? Oldschool Macheads?

[rhythm_kitchen]

Sorry. I discovered soon after this post Vision or Performer files can't be repaired. These are early MIDI only sessions Mac OS 7 off a Quadra.

Vision or performer files that are not archived .MID cannot be recovered.

Here are the terminal instructions to put the file and removed resource fork .xxx back together again in OS-X : (but only 1 data file and 1 .xxx resource-fork in folder). Mind your Sudo Ps and Qs.
http://macstuff.beachdogs.org/blog/?p=11

SD2 can be repaired with SoundHack a free download.
http://www.macupdate.com/app/mac/5891/soundhack

JPEGs and other standardized graphic files (Alsoft TS suggests to ignore the lost resource fork, add known suffix if going to windows from a Mac and/or open on a Windows or MacIntel machine.)

Bulk standard graphic file resource-fork repair utility:
http://mac.softpedia.com/get/Graphics/C ... pair.shtml

---------A TIGER formatted Firewire drive ate my resource forks---------
What I said above. However now perhaps an even worse problem may be upon us.

---------A Leopard formatted PPC ate my GUID partition------------------

GUID partitions mounted via Firewire, auto rebuild back to a broken semi-GUID partition immediately upon mounting on PPC 10.5.8 desktop. 10.5.8 all updates applied Feb 1, 2010. That rebuilt GUID partition is semi-broken. It will no longer boot a MacIntel.

However it didn't damage the existing HFS+ partitions. Now many files cannot be copied over to that broken GUID partition.

This is not the infamous 'too long of a file name' as in the Fat 32 error. There is no message to shorten the file name and try again. Just an error message: file cannot be copied (not MP-3 or MP-4 either). Then the same file copies fine to HFS+.

Files previously copied to the SL 10.6.8 formatted GUID Firewire partition now no longer copy over to the semi-broken GUID partition. But copy to HFS+

Note: Not tested with Tiger. I believe this is a Leopard PPC disk mounting utility issue or SL's Disk Utility format.

I wanted a bootable clone in case the internal hard drive went .... can't say it.

Now Alsoft is saying Apple has advised them now it is required that both GUID and HFS+ partitions must coexist on all new Mac OS internal drives.

OWC TS is advising Firewire or eSATA users to not mix GUID and HFS+ on external drives (Pro Tools approved Oxford chipsets).

I have not tested this with eSATA (Sonnet Tempo's Silicon Graphics driver)

So proceed with caution while testing continues to pinpoint the exact problem (one cannot in Leopard (PPC) stop this auto-reformatting as it is immediate and instantaneous auto-reformat when drive mounts

Hopefully Apple will release a patch.

Many are still running Leopard on G-5s. Naturally I didn't heed the advise of OWC's A/V tech support as MacIntel's SL Disk Utility (10.6. allows mixed partitioning of all external drives.

1) Don't mix partitions of GUID and HFS+ if running Leopard on a PPC.
2) If formatting mixed on 10.6.8 never plug drive into a PPC running Leopard 10.5.8 (since this is likely to happen down the road and harder to prevent I'm going with OWC's sage advise)

Yeah. So I ordered Drive Genius 3 by ProSoft and discovered I have to install it and go online to authenticate. Unlike a bootable CD/DVD as in DiskWarrior. So I bailed concerned with software RAID etc. and how the installation would affect Pro Tools or DP. Idea was to repair the GUID partition without losing 200 gigs of HFS+ archived Session DATA.

I read the thread on Drive Genius here. Perhaps it will repair the GUID partition itself but I imagine the clone would no longer boot a MacIntel.

If it does and anyone has used it successfully this way. We' like to hear.

[mikehalloran]

The original culprit is likely to be the FW housing and not the drive itself - older FW housing power supplies appear to be the culprit. I have trashed a few lately (including a NewerTech v3 today) only to put the drive into one of those inexpensive usb docks and have it work perfectly.

One of the symptoms is that the error messages tell you that the partitions can't be mounted. In my case, putting the drives in a usb dock reveals this to be false.

Stop worrying about trying to boot anything off of that drive. Get another drive and try to rescue your data. If a docking station doesn't let you recover, salvage what you can - if you can.

The problem with usb housings is that you can't boot a PPC from one. Oh well...

Since FW housings have become so flakey lately, I no longer buy them and avoid FW externals except for a portable FW DVD-DL that I keep for trouble shooting about 30 PPCs that I still maintain. Fortunately, I have eSATA and some of those docks are eSATA / usb.

This may help:
http://hints.macworld.com/article.php?s ... 2511133285

[dosuna11]

+1 Just had the same thing happen. I had a aftermarket SATA enclosure and loaded the drive. It mounted and runs great. Here is what I used.

http://www.google.com/imgres?um=1&hl=en ... 9,r:23,s:5

[rhythm_kitchen]

The original Oxford 9-1-1 Macally you all remember used the Mac serial cable for power. The 4 pins started losing contact and it glitched (only 2 are hot).

OWC reselling non-fitting 1394a cables with enclosures? They wiggle in my MBP when an Apple Firewire cable fits snugly. This is the age of Web 3d?

I'm using eSATA now as they clip in place. Nuegg is reselling an extra long with additional sheild 'round' eSATA 6' cable. OWC doesn't carry it although I suggested to TS the manufacturer (sorry it was a link off the DUC) and I called. They won't sell retail.