Bloody Hell! Now what?? The saga continues....

[chamelion]

Like a drowning man clutching at a straw, I have been living in hope that Disk Warrior would gallantly slay the dragon, fix my DP5 launch problems, and gallop off into the sunset. Not today, sunshine! I ran the DW routine, and it found all kinds of mayhem on Macintosh HD. It created a new directory, which I installed. I then fired up DP5 with hope in my heart, and.... not a bloody sausage! After dropping $$$ for DW, I'm still denied access because I still have insufficient privileges. What the hey do I do now? I'd love to know exactly what privileges I don't have, and whom I have to arm-wrestle to the ground to get the bloody things.

Surely this should be simple to sort out. I've repaired permissions, booted up from my original installer disk and run the disk repair routine from its disk utility. I've checked that Ownership & Permissions on DP5's Get Info window are set to both read and write. I confirmed that I'm logged in as administrator. I've re-installed DP5. I've tried removing all 3rd party plug-ins from the Components and MAS folders. I've thrown salt over my shoulder and run around the computer three times (a remedy of last resort, whose efficacy I have lately begun to doubt). What else is there...?

Do any tech-head Mac gurus out there have any other possible avenues to try? All suggestions gratefully accepted.

Thanx,

Geoff

[Frodo]

Now, now, not yet...

I'm anything but a guru, but I heard the sound of a wounded soul from the furthest reaches of the Outback...

You ran the Directory Repair AND the File Repair? And had DW repair permissions?

Okay. I'll take that as a yes.

Did you save the report of what wasn't fixed? If so, post that unfixed info here and we'll see where we are.

Now, it's mid-evening in Australia, but it's half past 3 AM here. I may need a nap first but I'll do what I can to help.

By the way, did you run directory repair and file repair for all of your drives?

[chamelion]

Hi Frodo, me old mate from the ever-lovin' Yew Ess & Aye.

Being a total twonk, Disk-Warrior-wise, I'm not absolutely certain about what did and didn't happen.

You ran the Directory Repair AND the File Repair? And had DW repair permissions?

I clicked the button I was directed to click, and waited until it did its thing. I have no idea exactly what it did. It may have done down to the pub for a coldie, for all I know.

Did you save the report of what wasn't fixed? If so, post that unfixed info here and we'll see where we are.

Dang! I wonder where I'd find that?

Now, it's mid-evening in Australia, but it's half past 3 AM here. I may need a nap first Laughing but I'll do what I can to help.

Thanks mate. I'll see what info I can unearth.


Geoff

[Frodo]

Jus fyi--

At the top of the DW window, there are four icons. One is the DW icon. The second one is the Directory repair, the third one is the File repair, and the last one is the Hardware check.

I'm guess the Directory Repair is the default starter, but it doesn't sound like your ran the File repair. That may do the trick for you.

Just click the File icon, then let it do its thing.

[Frodo]

Hi Frodo, me old mate from the ever-lovin' Yew Ess & Aye.

Love that accent!!

Being a total twonk,

"twonk"?

That's a new one! That goes right next to "mozzies" (I'm keeping a notebook...)

[chamelion]

Jus fyi--

At the top of the DW window, there are four icons. One is the DW icon. The second one is the Directory repair, the third one is the File repair, and the last one is the Hardware check.

I'm guess the Directory Repair is the default starter, but it doesn't sound like your ran the File repair. That may do the trick for you.

Just click the File icon, then let it do its thing.

Riiight... Doh! I'll run the other routines and maybe..? Dare I hope?

Thanx,

G

[96khz]

Hi Chamelion.

Did you trashed MOTU's DP5 folder and installed it again? By your description, it really seems that some DP file isn't configured correctly.
What exactly happens when you launch Digital Performer? Could you post the text here?
If it really is a wrong permission setting, you should try running DP as the root user. In Mac OS X, the Root user has access to everything, so DP would have to open.
The root user isn't configured by default, but it's very easy to do it:
http://docs.info.apple.com/article.html?artnum=106290
For security reasons, you shouldn't be running as root all the time, it's just for troubleshooting purposes.
If you still can't open DP in this account, it definitely shouldn't be a owner/permission misconfiguration.
If you don't have any problem opening DP in this account, log out and try to correct the wrong permission settings:

You already did a Get Info in the Digital Performer app, but I guess you didn't check inside the package. Right-click (or control-click) in DP's app and choose "Show Package Contents". Do a get Info in these files and folders (I recommend Command+Option+I, this way you don't need to open several Get Info windows), check and configure the owner/privileges of these folders. The owner and permissions should be something like:
You can "Read & Write"
Owner "You"
Access "Read & Write"
Group "You"
Access "Read Only"
Others "Read Only"

Select "Apply to enclosing items" for the entire contents of the folders to be configured this way.

Hope it helps! Give us some feedback.

[chamelion]

Wow! That stuff is well and truly over my head, but I have it on good authority that my ancestors were cavemen - afraid of nothing. I'll rip into it as soon as I can, and post the results here.

Thanks so much for your input.

Cheers,

Geoff

[emulatorloo]

Wow! That stuff is well and truly over my head

Geoff, check out this site:

http://www.macattorney.com/ts.html

Also this one is really really good:

http://www.thexlab.com/faqs/faqs.html


-------------------------------------------------------------

[cuttime]

Did you ever trash your authorization files?

http://www.motu.com/techsupport/technot ... horization

http://www.motu.com/techsupport/technot ... 0207641721

MainMenu will allow you to see invisible files:

http://www.santasw.com/

[chamelion]

Did you ever trash your authorization files?

http://www.motu.com/techsupport/technot ... horization

http://www.motu.com/techsupport/technot ... 0207641721

MainMenu will allow you to see invisible files:

http://www.santasw.com/

No, but sounds like a dang good idea. Thanx for the tip.

G

[cuttime]

Bumping this back up because I was concerned, and since Mr. Geoff appears to be back in business, I just wanted to know what the cure was. I think there was a similar thread in the general Mac forum.

[HeadMaster]

Like a drowning man clutching at a straw, I have been living in hope that Disk Warrior would gallantly slay the dragon, fix my DP5 launch problems, and gallop off into the sunset. Not today, sunshine! I ran the DW routine, and it found all kinds of mayhem on Macintosh HD. It created a new directory, which I installed. I then fired up DP5 with hope in my heart, and.... not a bloody sausage! After dropping $$$ for DW, I'm still denied access because I still have insufficient privileges. What the hey do I do now? I'd love to know exactly what privileges I don't have, and whom I have to arm-wrestle to the ground to get the bloody things.

Surely this should be simple to sort out. I've repaired permissions, booted up from my original installer disk and run the disk repair routine from its disk utility. I've checked that Ownership & Permissions on DP5's Get Info window are set to both read and write. I confirmed that I'm logged in as administrator. I've re-installed DP5. I've tried removing all 3rd party plug-ins from the Components and MAS folders. I've thrown salt over my shoulder and run around the computer three times (a remedy of last resort, whose efficacy I have lately begun to doubt). What else is there...?

Do any tech-head Mac gurus out there have any other possible avenues to try? All suggestions gratefully accepted.

Thanx,

Geoff

Exactly what happens, and where/when? Screendumps and a description in detail of what you do would help lots here.

There are very few things that can't be solved by some hacking with terminal, bring it on!

. . .
HM