Char Jackson wrote:
> On Wed, 27 Jul 2011 22:46:17 -0400, Paul <> wrote:
>
>> As an example, you can't store a file under C: directly.
>> There are also limits on dumping you own files into Program Files.
>
> Side question...I have no problem storing files in the root of C: or
> in the Program Files folder. Is that because I have UAC disabled?
>
http://en.wikipedia.org/wiki/User_Account_Control
"UAC attempts to alleviate this using File and Registry Virtualization"
http://support.microsoft.com/kb/927387
"When you use an application for which virtualization is enabled, you
create data files in virtualizable locations of the file system. When
you use another application or Windows Explorer to access these newly
created files, you cannot find them. For example, if you save a file in
a photo editing application in the %programfiles%, %systemroot%,
%systemdrive%, or %programdata% folders, you cannot locate this file."
It looks like that is a function of UAC, but who knows when these
features are really turned off.
*******
If Microsoft wants to do stuff like this, they should have designed
an Explorer for the file system, that would explain these things.
Like if you attempt to delete a file, it could give you a lecture
in a giant balloon dialog, about where the file is actually
stored, what permissions are involved, what program has the
file open, and so on. Rather than making the OS into a giant
"Whack a mole" game :-(
http://en.wikipedia.org/wiki/Whac-A-Mole
That's why I'd prefer to see posters mention a path, so it's
easier to explain what is going on. Just suggesting a bigger
nuclear weapon to delete files, isn't the best approach, as
sooner or later the wrong thing is going to get deleted.
Paul