Virutal Path, or formally called "File System Visualization" is mainly for
compatibility reasons. Although Windows Vista is the coolest windows system
ever, and Microsoft is expecting it’s adopted very fast, the application
softwares are not going to be that quick. So there much be some kind of
method to ensure the existing application can work on Vista without any
changes.
So main reasons:
1) Make Vista compatible with existing application, providing a entry path
for old guys
2) Make sure new application must be working with UAC, keep [Windows]
[Program Files] folder clean; close the door for new guys
3) Ultimate goal, ensure system reliability and security
And by the way, File system visualization is not really for “Standard
Users�, it’s for the application that doesn’t work with UAC, aka: provide UAC
manifest to allow Vista determine it’s running level; once you specify UAC
manifest for your APP, Visualization will be disabled.
Anyway, confusing by “Standard Users� is reasonable because once your
elevated your permission, you will have full permission to any kind of
resources, eg.c:\Program Files; then there is nothing can stop you writing
file to such location.
Last Note: Visualization is also applicable to registry entries.


"æ‚©ã‚�ã‚‹å*�羊" wrote:

> Hi ALL,
>
> I'd like to ask you to teach me "Virtual Path",which is new to Windows
> Vista, if you know a lot about its feature.
>
> [FYI]
> My recognition of it is as follows:
>
> 1. Its feature is only for "Standard Usrs" on Vista.
> 2. If a standard user downloads/installs a program into C:ProgramFiles or
> C:Windows,it will be redirected to C:users..."VirtualStore"...
>
> However, I can't make out a real reason why such a complicated feature is
> implemented on Vista..What on the hell is good for a user?
>
> Maybe,my recognition is wrong...so please find a fault in my recognitons 1-2
> and point out this feature's merit??
>
> Thanks you for in advance.