Re: "Recovered Files" Always in Trash

What the script did was to set the permissions correctly on your invisible
Temporary Items folder. And would have done the same for any files within
it, but there weren't any (which is fine).

So that proves that the people wondering if the "problem" (personally I
can't see any problem) was faulty permissions guessed wrong. That's all.

THERE'S NO PROBLEM. I see the same thing in my own Trash. Big deal. That's
where they should be, it seems. Word puts them there when quitting. They're
useless files you don't need, so the trash is the right place for them. Just
Empty the trash, like Philip said.

And STOP removing and reinstalling Office That's not going to do anything.

I wouldn't be totally surprised if the difference between seeing these files
and not seeing them had something to do with the difference between choosing
Yes (either explicitly or by the preference that does it for you
automatically) to "Do you want to save Normal?" and choosing No. Or not.

Just forget about it.

--
Paul Berkowitz
MVP MacOffice
Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html>
AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/>

Please "Reply To Newsgroup" to reply to this message. Emails will be
ignored.

PLEASE always state which version of Microsoft Office you are using -
**2004**, X or 2001. It's often impossible to answer your questions
otherwise.


From: Mark Pedretti <markpedretti@xxxxxxxxxxx>
Organization: SBC http://yahoo.sbc.com
Newsgroups: microsoft.public.mac.office.word
Date: Sun, 19 Nov 2006 06:18:59 GMT
Conversation: "Recovered Files" Always in Trash
Subject: Re: "Recovered Files" Always in Trash

Paul:

Thanks for the advice and the script. Unfortunately, it doesn't seem to be
doing the trick. I did as you said, and ran the script from the Script
Editor; I didn't get the error you were speaking of, and I followed the
script's progress in the event log, where it seemed to be making some
changes. Here is a transcript of the log:

tell current application
path to temporary items as Unicode text
"Macintosh HD:private:var:tmp:folders.501:TemporaryItems:"
end tell
tell application "Finder"
get folder "Macintosh HD:private:var:tmp:folders.501:TemporaryItems:"
folder "TemporaryItems" of folder "folders.501" of folder "tmp" of
folder "var" of item "private" of startup disk
set owner privileges of folder "TemporaryItems" of folder "folders.501"
of folder "tmp" of folder "var" of item "private" of startup disk to read
write
read write
set group privileges of folder "TemporaryItems" of folder "folders.501"
of folder "tmp" of folder "var" of item "private" of startup disk to read
only
read only
set everyones privileges of folder "TemporaryItems" of folder
"folders.501" of folder "tmp" of folder "var" of item "private" of startup
disk to read only
read only
get entire contents of folder "TemporaryItems" of folder "folders.501"
of folder "tmp" of folder "var" of item "private" of startup disk
{}
end tell

Maybe you are a little better at reading these things than I am, but it
didn't throw any errors at me so I assume everything went as you intended it
to. I guess my question at this point is whether I ran it at the right time
or in the right way, etc. After reading your post, I shut down my newsgroup
reader, launched Script Editor, compiled the script, and ran it, with no
other applications running and without having used Word during this session.
Then, I launched Word, wrote some stuff, quit, and restarted to see what was
going on. Lo and behold, the "Recovered Files" folder with a "Word Work
File x_x" was back in the trash. Sigh.

I don't know if I was supposed to run the script AFTER using Word, or if you
intended this to be something that I would have to do before or after each
time I used Word. My assumption was that this was a one-time shot, and that
running it once was supposed to fix the problem for good.

By the way, I'm the only user of my Mac and I have (obviously) administrator
privileges. Thanks for the effort, and if you see something I'm missing
please let me know.

Best, Mark


On 11/18/06 10:46 AM, in article C18494F4.1919F%berkowit@xxxxxxxxxxxxxx,
"Paul Berkowitz" <berkowit@xxxxxxxxxxxxxx> wrote:

On 11/16/06 7:30 PM, in article C1826C7D.326A%markpedretti@xxxxxxxxxxx,
"Mark Pedretti" <markpedretti@xxxxxxxxxxx> wrote:

So this leaves me/us with a couple of options:

-(1) figure out how to repair the permissions on an invisible folder
(Temporary Items). I made some initial forays into investigating this by
using an app that showed all invisible items, but I couldn't change the
permissions in the Get Info window for anything that looked like it might be
the responsible folder.

Run this script in Script Editor:


set tempFolderPath to path to temporary items as Unicode text
tell application "Finder"
set tempFolder to folder tempFolderPath
tell tempFolder to set {owner privileges, group privileges, everyones
privileges} to {read write, read only, read only}
set allTempFiles to entire contents of tempFolder
repeat with i from 1 to (count allTempFiles)
set tempFile to item i of my allTempFiles
tell tempFile
set {owner privileges, group privileges, everyones privileges}
to {read write, read only, read only}
end tell
end repeat
end tell

(If you get an error saying this is not allowed, it would mean that you are
not the owner of your own temp folder, which is pretty well impossible. But
if you do, report back.)

-(2) screwing around at the root user level. This might include seeing if I
can change the permissions at this level, or even performing an install of
Office from here. I must admit that this idea strikes fear into my heart,
if only because I'm new to this file system and worry that I might make
things even worse. But then again, most of my major breakthroughs on the
Mac have come from taking such risks.


Don't!


.

Relevant Pages

  • Problem Creating HomeDirectories and Permissions using VBScript
    ... and assigning permissions to it in a VBScript script. ... it creates the setting for the folder inside the ...
    (microsoft.public.win2000.active_directory)
  • Re: Logon Script Elevated Privileges
    ... script within the GPO if you want, such as selecting from between user ... I'm using XCacls.vbs to create the permissions structure. ... the root folder to create the folder, ...
    (microsoft.public.windows.group_policy)
  • Re: Logon Script Elevated Privileges
    ... script within the GPO if you want, such as selecting from between user ... I'm using XCacls.vbs to create the permissions structure. ... > the root folder to create the folder, ... >> of a GPO using elevated privileges. ...
    (microsoft.public.windows.group_policy)
  • Re: Deny _WRITE_ access to a file
    ... > trying to talk about was a STARTUP script (if I'm not mistaken, ... > script runs as BUILTIN\SYSTEM). ... If it is possible to script a permissions change such that the ... folder remains read/write for everyone except for the restricted group who ...
    (microsoft.public.security)
  • Re: Deny _WRITE_ access to a file
    ... > trying to talk about was a STARTUP script (if I'm not mistaken, ... > script runs as BUILTIN\SYSTEM). ... If it is possible to script a permissions change such that the ... folder remains read/write for everyone except for the restricted group who ...
    (microsoft.public.win2000.security)