Post by Andrew Morton Post by Walter Clayton Post by Andrew Morton Post by Walter Clayton
What is displayed is an optional status change request for *files*
within the directory heirarchy.
So, what would cause that option to be enabled?
From what standpoint? Reflecting the current state of the RO
attribute of the target directory? If so, then MS would have to put
the code back into the GUI and doubt they will. RO on a directory is
I thought you meant that the grey RO attribute on a folder indicated that
there was a status change request set.
Nope. Means there is no intended *future* change. The inital state is "I
have no desire to make a change". As you toggle you are saying "I want to
clear the RO bit on *files* at some point in the future", then it switches
to "I want to set the RO bit on *files* at some point in the future" and
then back to "I have no desire to make a change".
It is a future state change and that is all it means. It is *totally*
divorced from current state.
Post by Andrew Morton
Post by Walter Clayton
Sure about that? I just deleted a directory into the recycle bin with
RO both set and not set. No fuss, no muss or bother. There is no such
thing a current 'grayed-out' state.
Oh yes there is! It looks like this:-
I suppose the grey-out of the box makes it look like it is an inherited
BINGO! The problem is it is *not* inherited. I has *nothing* do to with
current state. It is strictly and always future state change.
Post by Andrew Morton
Also, when clearing it and clicking apply, a dialog comes up titled "Confirm
Attribute Changes" asking if I want to unset read-only for this folder only
or to this folder, subfolders and files.
Allowing it to do the change makes no difference - the next time the
property sheet is displayed it has reverted to greyed-out.
Yep. It is *future* state. It *never* represents current sate.
Post by Andrew Morton Post by Walter Clayton
The RO indicator on the directory property sheet has absolutely *no*
bearing or relationship to the current state of *anything* on the
machine. It is a possible future state only, and only for *files*.
This is on NTFS on Windows Server 2003.
It has happened to every folder on every partition of every hard disk for
every user. They are basic, not dynamic, disks.
Chkdsk doesn't find any errors.
If I access the computer from another one (W2000) the read-only box is
Yep. That's beause in Win2K the GUI display the *current* state and did
allow the RO bit on a directory to be manipulated. And it would not matter
if the disks are dynamic or nor, FATxx or NTFS. On a directory the RO bit is
Now for the fun. Copy the following into a bat file. Name it what you will,
run it and follow the instructions. During this test, pay careful attention
to the current state of the RO attribute bit vs. what is display in the
explorer GUI. You may modify the bat file as you see fit as long as the
overall intent is followed, which is to display current state information on
a directory and a file as the RO bit is *actually* changed.
------------------ start copy below this line------------------
attrib -s -h boot.ini
copy boot.ini c:\test
attrib +s +h boot.ini
attrib -r testnest
@echo At this time use explorer to check the properties of c:\test\testnest.
@echo Be aware that the RO attribute of the directory testnest is *OFF* as
you can confirm by the following attrib output.
@echo While in explorer check the attributes of c:\test\boot.ini.
@echo At this time the RO attribute of c:\test\boot.ini is *OFF* as you can
confirm by the following attrib output.
@echo Hit any key to proceed to the next step
attrib +r testnest
attrib +r boot.ini
@echo At this time use explorer to check the properties of c:\test\testnest
@echo Be aware that the RO attribute on c:\test\testnest is now *ON*
@echo While in explorer check the properteis of c:\test\boot.ini
@echo At this time the RO attribute of c:\test\boot.ini is *ON*
@echo Hit any key to delete the test directory and data.
rmdir /s /q c:\test
@echo Test is now complete
----------------stop copy above this line-------------------------
Any technology distinguishable from magic is insufficiently advanced.