I ran both and all is hopefully now all well. I recycled yoru message in to my 
folder where I keep these things in case I or anyone else needs them.


Take care. and I managed to safe the file. Now I can get back to my single when 
I  have the time.¬ HOpe that goes well. I cannot keep you allposted on that but 
I'll keep you all posted if I run in to any more problems.

Take care.
On Feb 26, 2012, at 4:24 PM, Esther wrote:

> Hi Sarah, 
> 
> The first Terminal command to clear ACLs typically did give error messages.  
> In all cases it was OK to ignore them.  It attempts to recursively remove 
> previous access control lists.
> 
> The second Terminal command with the:
> chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents ~/Downloads 
> ~/Library ~/Movies ~/Music ~/Pictures ~/Public
> 
> (everything in one line) is supposed to do the heavy lifting correction.  
> This basically sets up an access control list that  denies delete access to 
> everyone but you for files in your user account.
> 
> Did you manage to run the second command in your Terminal session?  There 
> were a few posters who thought that just running the second command by itself 
> would work to fix things.
> 
> HTH.  Cheers,
> 
> Esther
> 
> On Feb 26, 2012, at 1:47 PM, Sarah Alawami wrote:
> 
>> Ok. goign back to this thread and sorry for bouncing I'm getting these 
>> messages. what's up. I don't like the sound of them. Here is an export.
>> 
>> Failed to clear ACL on file 7-Zip File Manager — win7.app: Operation not 
>> permitted
>> chmod: Failed to clear ACL on file _26C5A5C16DC67BAA01E199 — win7.app: 
>> Operation not permitted
>> chmod: Failed to clear ACL on file _2D1F402522862B82F63CF9 — win7.app: 
>> Operation not permitted
>> chmod: Failed to clear ACL on file Accessibility On-Screen Keyboard — 
>> win7.app: Operation not permitted
>> 
>> 
>> Looks like the problem is bigger then I anticipated.
>> 
>> Take care all.
>> 
>> On Feb 25, 2012, at 12:05 PM, Esther wrote:
>> 
>>> Hi Sarah and Jim,
>>> 
>>> I found a discussion in the Apple Support forums that talks about this 
>>> permissions problem under Lion, and steps that people have taken to solve 
>>> it.  The described symptoms sound familiar -- for example, preferences not 
>>> being saved.  The solution involves  using Terminal to type in a command 
>>> that sets permissions for your home folder so that you have read and write 
>>> access, but so that everyone else has only read access.  Since I'm newly 
>>> using Lion, and not having this permissions problem, I'm not able to try 
>>> this out.
>>> 
>>> Here are the instructions.  (I'm pasting in the version "for less 
>>> experienced users"):
>>> <begin quote>
>>> For less experienced terminal users, these are more explicit instructions 
>>> to follow cgDesign's method from page 1:
>>> 
>>> Step 0:
>>>   Be sure to complete ALL steps
>>> 
>>> Step 1:
>>>   Open the application Terminal.app (Utilities folder inside of your 
>>> applications folder)
>>> 
>>> Step 2:
>>>   when the prompt comes up, on the line that ends in "$", paste in (exactly)
>>> 
>>>             chmod -R -N ~
>>> 
>>>    and hit the enter key on your keyboard, and wait a couple of minutes for 
>>> this to complete. You may see several messages regarding invalid arguments 
>>> - these are OK.
>>> 
>>> Step 3:
>>>   When the prompt ending in "$" returns, paste in (exactly)
>>> 
>>>             chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents 
>>> ~/Downloads ~/Library ~/Movies ~/Music ~/Pictures ~/Public
>>> 
>>> When the prompt ending in "$" returns, you have completed all steps. You 
>>> can quit Terminal.app.
>>> <end quote>
>>> 
>>> There is some debate about whether using the first command is necessary.  
>>> The second command with the "everyone deny delete" argument is what fixes 
>>> the permissions issue.  Both use the "chmod" command -- spelled "c h m o d" 
>>> -- which changes the file mode access bits (permissions), and/or modifies 
>>> access control lists associated with these files.  Unix is case sensitive, 
>>> and inserting spaces between keys to commands -- like the hyphen and 
>>> capital letter R, or the hyphen and capital letter N  in the first command 
>>> -- alters the meaning of the command.  Instead of applying the command 
>>> recursively to subfolders, which is what the "-R" key indicates, typing the 
>>> "R" with a space before it would turn it into an argument -- a 
>>> (non-existent) folder with the name "R" in the present directory. The tilde 
>>> symbol is preceded by a space, because this is the argument to the command, 
>>> and is the shorthand way of indicating the current user's home directory.
>>> 
>>> All Terminal commands are entered by pressing the "return" key after you've 
>>> typed the line.
>>> 
>>> So, Sarah, open a Terminal session in Finder:
>>> 1. Command-Shift-U to go to "Utilities", press "t" to go to Terminal, and 
>>> Command-Down arrow to launch Terminal
>>> 2. In the Terminal window, type or paste in:
>>> chmod -R -N ~
>>> then press return. (That's the chmod command, followed by a space, followed 
>>> by hyphen capital R, followed by a space, followed by hyphen capital N, 
>>> followed by a space, followed by the tilde symbol.)
>>> 3. Wait a few minutes for this to complete, and ignore error messages. 
>>> 4. Type or paste in:
>>> chmod +a "everyone deny delete" ~/ ~/Desktop ~/Documents ~/Downloads 
>>> ~/Library ~/Movies ~/Music ~/Pictures ~/Public
>>> 
>>> then press return. (That's the chmod command, followed by a space, filed by 
>>> a plus sign and small letter a, followed by the three words in quotes, 
>>> "everyone deny delete", followed by a space, followed by a list of folders 
>>> in your home directory, all separated by spaces.  These arguments all begin 
>>> with a tilde symbol followed by a slash, which indicates your top level 
>>> home directory. So in addition to tilde slash by itself as the first 
>>> argument, you'll be typing tilde slash before all the default folders that 
>>> should appear in your home directory: Desktop, Documents, Downloads, 
>>> Library, Movies, Music, Pictures, and Public.  The names of all these 
>>> folders begin with a capital letter.  The command is a single line.
>>> 
>>> 5.Wait a while for the last command to be executed, then quite your 
>>> Terminal app with Command-q.
>>> 
>>> Sarah,  this should fix your not being able to write to the Documents 
>>> folder on your home directory.  For some reason, your permissions access 
>>> was being superseded, so that either the system or some other application 
>>> could change the permissions to those folders, locking you out.  Either the 
>>> system access control lists or default permissions were not set correctly, 
>>> so repairing permissions didn't fix this.  This would also explain why 
>>> preferences weren't being saved, since you wouldn't be able to write to the 
>>> files in your account's Library folder.
>>> 
>>> Probably one person should try this out to see whether this works.  I'll 
>>> give the URL of the Apple Support Forum thread that discusses this.  It's 
>>> titled "Lion Permissions Problem":
>>> https://discussions.apple.com/thread/3202084?start=0&tstart=0
>>> 
>>> HTH.  Cheers,
>>> 
>>> Esther
>>> 
>>> On Feb 25, 2012, at 8:50 AM, Sarah Alawami wrote:
>>> 
>>>> Actually I want to know the same thing. I was afraid to ask so thanks for 
>>>> doing this. I have this every time I move or copy a folder.
>>>> 
>>>> thanks all for any ideas.
>>>> On Feb 25, 2012, at 10:39 AM, Jim Noseworthy wrote:
>>>> 
>>>>> Hi Folks:
>>>>> 
>>>>> I must have done something somewhere because every time I copy a file, I 
>>>>> need to authenticate myself.
>>>>> 
>>>>> How do I overcome this issue gang?
>>>>> 
>>>>> Thanks.
>>>>> 
>>>>> 
>>>>> The triune God created human kind to participate, through the Holy 
>>>>> Spirit, in the incarnate Son's communion with the Father.
>>>>> 
>>> 
> 
> <--- Mac Access At Mac Access Dot Net --->
> 
> To reply to this post, please address your message to 
> [email protected]
> 
> You can find an archive of all messages posted    to the Mac-Access forum at 
> either the list's own dedicated web archive:
> <http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
> or at the public Mail Archive:
> <http://www.mail-archive.com/[email protected]/>.
> Subscribe to the list's RSS feed from:
> <http://www.mail-archive.com/[email protected]/maillist.xml>
> 
> The Mac-Access mailing list is guaranteed malware, spyware, Trojan, virus and 
> worm-free!
> 
> Please remember to update your membership options periodically by visiting 
> the list website at:
> <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>

<--- Mac Access At Mac Access Dot Net --->

To reply to this post, please address your message to [email protected]

You can find an archive of all messages posted    to the Mac-Access forum at 
either the list's own dedicated web archive:
<http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
or at the public Mail Archive:
<http://www.mail-archive.com/[email protected]/>.
Subscribe to the list's RSS feed from:
<http://www.mail-archive.com/[email protected]/maillist.xml>

The Mac-Access mailing list is guaranteed malware, spyware, Trojan, virus and 
worm-free!

Please remember to update your membership options periodically by visiting the 
list website at:
<http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>

Reply via email to