[SOLVED] DP 8.0 Mac OS error: File permissions error (-54)

[jmc]

I just upgraded to a new SSD for my OS, I installed DP8 yesterday, was able to open files just fine, but this morning I have encountered an inability to open anything. Even creating a new file crashes the program. I'm going to try updating to 8.04 and hopefully that will fix it.

I tried repairing permissions. I even tried 7.24 and that gives me the same. I restarted. Not sure what to do, except go back to my old drive where things actually worked.

If anyone has any thoughts, they are eagerly welcomed.

[MIDI Life Crisis]

Get Info on the drive and check the permissions. They may not need repairing, but changing!

[MIDI Life Crisis]

If there's nothing on the drive yet, try reformatting it from your machine as well.

[jmc]

Thanks! I did already triple check every drive has the proper permissions (and all enclosed contents as well).

Restarted again. Repaired permissions again. Still no love after the 8.04 update.

[jmc]

No love. This what I get as soon as I open the program. I guess it's back the old hard drive and 7.24 on OS10.6.8.

[jmc]

Okay... I think I figured it out, though the solution puzzles me. I hit Cmd+I to get info on the drive and even though all the users, staff, admin can read and write, I checked the "Ignore ownership for this volume" and everything works.

So...shrug and keep going? Okay fine.

[MIDI Life Crisis]

That's kind of what I meant by changing permissions.

[jmc]

...

[MIDI Life Crisis]

Got it. Not a jerk at all.

[dix]

Okay... I think I figured it out, though the solution puzzles me. I hit Cmd+I to get info on the drive and even though all the users, staff, admin can read and write, I checked the "Ignore ownership for this volume" and everything works.

So...shrug and keep going? Okay fine.

Whoa. I've spent several hours getting this error on launching DP today. Checking this box on my project drive seems to have fixed the issue for me too. I was assuming it was a permissions issue with my boot drive, but I guess not.

It appears "Ignore ownership on this volume" is the correct setting. ....if so, how did these get turned off I wonder.