x
anonymous 7 February 2004

I recentley started taking projects home from the studio to
mix on a G4 powerbook running 9.2 and Pro-Tools with an M-Box.I bring the project home on CD and then load it on
to a mercury elite fire wire drive.This worked fine for a while,then one day on a new project when I hit play there
it was DAE error-9060.The only way around it so far is to
tranfer the same files to the boot drive.Then it seems to
work fine.
As a test I then opened an earlier project,dated before the
problem from the same fire wire drive,and it worked fine.
I do'nt know wat changed in beteween working and not,
but if there are any ideas out there I Shure would appreciate
them.
PS. Is there any way to look these codes up and find out what they mean.
Thanks,
Calvin

Tags

Comments

anonymous Sat, 02/07/2004 - 17:47

From the Digidesign [[url=http://[/URL]="http://answerbase.d…"]Answerbase:[/]="http://answerbase.d…"]Answerbase:[/]

DAE error -9060 - a general list of potential causes on Mac OS and Windows.

1. Pro Tools does NOT support RAID arrays.
This error can occur if drives are connected to a RAID SCSI controller, or if drives have been striped or formatted with a RAID formatting utility such as "Soft Raid".

2. Corrupt audio files can cause -9060 errors.
In this scenario, the -9060 error message will come up in exactly the same spot in the session. A simple workaround is to set the track containing the corrupt audio to "inactive".

3. In one case, a bad Volume Bitmap on the audio drive was the cause (Disk Doctor reported "the contents of the bitmap do not agree with the locations of all files in the catalog").
Run a disk utility on the drive to check it. If an error is found, backup your data, initialize the drive, then restore your data.

4. In one case this was resolved by removing a Jaz drive from the SCSI bus.

5. In at least one instance disabling Norton AntiVirus or Norton SystemWorks caused DAE -9060 errors to stop occurring when recording to SCSI or internal drives that were formatted with Apple Disk Utility. To do this run the Norton uninstaller or remove the Norton files from Library>Startup Items.

Looks like you may need to do some directory maintenence on your drive. I would steer clear of Norton though. I recommend DiskWarrior, or TechTool for OS9. :c:

x

User login