Bottom line is the box is used to set/unset the RO bit of the files on
the folder, not the folder itself. Think of it as a GUI command that
runs DOS command "attrib +r %files%" or "attrib -r %files%" where files
is a list of file names.
If you truly want to set a folder as RO, which I think only means you
can't remove the folder when empty, you'd have to shell to CMD & then
use "attrib +r foldername".
On 10/25/2010 7:56 AM, DSinc wrote:
Josh,
I've noodled your reply since receipt. Still confused.
Lemme split below and respond...............
On 10/16/2010 02:33, Joshua MacCraw wrote:
"Greyed out" typically means an option is disabled for input, not the
meaning in this case. The filled box indicates a 3rd state of neither,
a placeholder, because the box does not indicate status. If you check
or uncheck & apply it sets the folder's files' bits then reverts back
to a filled box next time you open folder properties.
OK, never aware of the state of 'neither.' Odd. What I see is that any
new folder I create pops out with "read-only" checked, but greyed-out,
as default creation. I will accept this as normal XP behavior, as has
been suggested.
The tough part is that if/when I actively click and clear the default
grayed-out/default/selected "read-only" props of the new folder, the
next time I come back to this same folder, the original default
attribute has been re-applied. I can repeat this exercise ad nauseum.
So, I accept this is a high level XP behavior. Worse, it may be some
"policy!" I do not play with XP policies, yet............ :)
I think for files it reacts differently reflecting the files' actual
bit state. Under W7 there's even a note next to the box saying "Only
applies to files in folder". As a test I did "attrib +r" on a folder &
then checked the properties, no change in the box same for "attrib -r".
YES! The attributes of the any added files to the folder DO create
additional noise. I have learned many new tricks for dealing with saved
PDF files. PDF files are chronic Copy/Move games after download!
As to files flagged as "in use" you'd have to get a program like
Unlocker involved to track down what has the file open.
http://ccollomb.free.fr/unlocker/
I will go check this one out for sure. Thank you!
Best,
Duncan
On 10/15/2010 2:01 PM, DSinc wrote:
Thane,
Thanks for the reply. And the confirm! I suspected a 'default' XP
behavior.
Because of this, I now suspect the 'red-X' behavior is either comm
between my clients, and/or my NAS. Yes, my NAS can be really
picky........... :)
I will dig more now that I have energy behind 'default behavior.'
Acceptable for now.......Until I figure out how to change it.
Thanks,
Duncan
On 10/15/2010 14:46, Thane Sherrington wrote:
At 04:38 PM 13/10/2010, DSinc wrote:
Lately I have noticed something odd.
Whenever I create a new blank folder it appears with attributes
pre-set to "read-only" (grayed out)
This "read-only" attribute is grayed-out, but can be manually
disabled.
Is this a default XP behavior?
Default XP behaviour.
I ask this because I now notice that anything I place into one of
these 'new' folders can not be copied/moved across my LAN to other
locations because XP posts the red "access denied-file is in use"
pop-up.
Now that is strange.
T
