XEmacs 21.4.19: Problem with customized folders on Windows XP

[Benson Margulies]

There are two access control mechanisms at work here: the old
'read-only' attribute and the ACL. Indeed, when you set a custom icon in
the explorer, it sets the read-only attribute, and it keeps on setting
it.

I've never seen any program other than xemacs pay any attention to the
read-only attribute on a Windows directory. I suspect that XEmacs is
manually checking the bit. Given the complexity of ACLS, XEmacs needs to
just go ahead and try to write to the directory and see what comes back,
or learn to use the API that asks 'do I have effective Write access'.
Looking at the flag is only causing confusion.