"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. 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".
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/
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
