Virtualization

I believe your referring to the folder and files - folders are yellow & files are shown as gray/grey. Does that help?

Looking at the VFS structure one more time I realized that the Virtual File System Root folder and all CSIDL_xxx folders are also grey/gray (I couldn't find out what CSIDL stood for, but it represents important OS environment variable locations created by the Sequencer & translated by the client's SystemGuard). If a folder is created by the application that isn't a common OS environment variable (i.e. c:\Orant), it will show up as yellow.

I tried to import a small .jpg (29k), but it kept timing out & then I get a 'File too large!' error. Maybe I don't have permissions?

CSDIL is used to ensure proper mapping to well know directories on windows machines
List of CSIDL values
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/enums/csidl.asp

If you R-Click on a grey folder you will notice that "Virtualized" is *not* checked
If you R-Click on a yellow folder you will notice that "Virtualized" is checked

Virtualized means that the Virtual App sees that folder as the only instance of that path. So if there is a virtualized folder named c:\orant with file a.exe in it and there is a local folder c:\orant with a file b.exe, the virtual app only sees a.exe.
If you remove the "virtualized" check, then the application will merge the two directories contents and the virtual app will see
c:\orant
a.exe
b.exe

By default, any new directories created while monitoring in the sequencer are Virtualized while existing directories are not. The packager can overide if necessary.

By the way, the virtual registry tab has the same concept but the coloring is reversed and the term different. Yellow Reg keys merge with the local registry and yellow reg keys with grey shadow behind them are "virtualized" (Right click the registry key, choose *key*..you will see "Override Local Key")