Quite recently I began having a -5000 Result Code And a message saying: Insufficient access privileges for operation When creating overviews on imported audio files even with files existing inother closed projects. It never happened before and I'm quite puzzled as the overview is done correctly and everything works as it should but I've to wait for that message every time. Any idea? Thanks in advance. Carlos "ZINGARO" Alves ZNGR - Nature Morte R. Prest. Arriaga, 59-4º/5º 1200-771 Lisboa - Portugal ph.fx: 351.21.3970052 zngr@... http://www.shef.ac.uk/misc/rec/ps/efi/mzingaro.html http://www.granular.fm

On May 2, 2005, at 3:53 AM, Carlos Zingaro wrote: > Quite recently I began having a -5000 Result Code > And a message saying: > Insufficient access privileges for operation > When creating overviews on imported audio files even with files > existing in other closed projects.Any idea? > Thanks in advance. > open you apps folder, then utilities folder, and then the disc utility application. Select your main system hard drive in the box to the left, and then select repair permissions. That should fix it. George ________________________________________________________ www.utopiaparkwaymusic.com Mac AND PC: The only way to fly 8-}

> open you apps folder, then utilities folder, and then the > disc utility application. > > Select your main system hard drive in the box to the left, > and then select repair permissions. > > That should fix it. George, maybe you can answer a question that I've had for some time. Why is repair permissions ever needed? I know I don't personally change permissions of anything myself, so how do permissions get corrupt in the first place. It just seems like an OS bug to me. A pretty severe one at that. Do you know what is going on to make permissions become corrupt? Kamm

> George, maybe you can answer a question that I've had for some time. Why is > repair permissions ever needed? I know I don't personally change > permissions of anything myself, so how do permissions get corrupt in the > first place. It just seems like an OS bug to me. A pretty severe one at > that. Do you know what is going on to make permissions become corrupt? I hope George doesn't mind if I answer it for him, since he didn't yet..:o) First of all, the OS itself doesn't change a single permission without being asked to, so it's never an OS bug. Also keep in mind there is no such thing as "the" correct permissions (or corrupt permissions, for that matter). If there was, they wouldn't be configurable and you wouldn't need to fix them. For system files however, there is a certain common way of setting permissions but in the hundreds of folders and thousands of files, there are bound to be different views on how this should be done (and all of them are right). This is why a software install script (or even a running application writing config files) might choose one way, and Apple's repair-permission tool might decide otherwise. The original question in this case (and most other questions on the list about permissions) was about user document files, and the repair tool doesn't even touch those AFIK (it has no idea what permissions you want on your documents), which is why it was pretty likely that the repair tool wouldn't help. Wrong permissions on user documents are there either because the user sets them himself, or an application does (which might even be a bug or a misunderstood feature), or because the user copied it from another source preserving the permissions (coming from a cdrom it might become readonly, or when copied via HFS from another Mac it might keep the original owner). Keep in mind that the repair permissions tool is not a sort of disk cleaner (like a sector checker or something), it's just a convenient script that follows a rule-of-thumb for when your system acts weird and you want to make sure that it is not caused by some inaccessible system file. Even if you do see it changing something, that doesn't mean it's necessary. I hope this helps clear things up.. welcome to the Unix world - safe and powerful, but slightly more complicated. :o) Maurits.