At 12:41 PM 2/2/2007, Phil Daley wrote:
>At 2/2/2007 10:56 AM, Aaron Sherber wrote:
>
> >At 08:59 AM 2/2/2007, Phil Daley wrote:
> > >In Vista, you are not allowed access to files in some directories. You
> > >cannot even see them in explorer. And it has nothing to do
with them being
> > >hidden, it has to do with them being system.
> >
> >Just curious, can you give an example? Have you tried enabling 'Show
> >hidden files and folders' and disabling 'Hide protected operating
> >system files' through Explorer?
>
>Right, but no one is allowed access to Documents and Settings/ some of the
>sub directories there.
Okay, I've just played around with this, because my interest was
piqued. I've got Vista installed under Virtual PC, so I haven't done
much with it yet. In Vista, Documents and Settings is now a shortcut
to c:\Users, and in fact the shortcut does have Everyone set to Deny
for list contents, making things unaccessible through that route.
However, as Administrator I could remove that Deny and get into the
folder. I could also just go to c:\Users with no trouble at all.
At any rate, I am reasonably certain that as Administrator you would
somehow be able to access every single file on the computer. That's
sort of the sine qua non of Administrator, after all.
> >In any event, I would agree with David. If an application has decided
> >to store its settings file in a way that makes Vista think it should
> >be hidden, that's the fault of the application, not the OS.
>
>But, since this was not a problem in XP, whose fault is it???
Have you ever read Raymond Chen's blog,
<http://blogs.msdn.com/oldnewthing/>? He talks a lot about how MS
tends to bend over backwards to ensure compatibility with old
applications, even those which do things like rely on behavior which
MS has explicitly said might not always work that way. They do this
because when users upgrade to a new Windows and suddenly one of their
apps stops working, the users naturally assume that it's the fault of
Windows. They don't imagine that it's because the app was doing
something which MS had said "Don't do this; we know you can do it in
XP, but we can't guarantee that it will work in future versions of Windows."
Now, I don't really know what files you're having problems reaching,
or where they are, or why they're there. But it's entirely possible
that an app had been storing settings in a way which was not
recommended by MS, and now they're getting bitten by it.
It's a little like saying, "Gee, I could always drive 80 mph on this
road under the old police commissioner; the new one must have changed
the law." When in fact all the new one did was actually post a patrol
car on the road to enforce the existing speed limit.
See also
<http://windowsconnected.com/blogs/jerry/archive/2005/12/19/86.aspx>,
which talks about some related issues.
Aaron.
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
