Video Screencast Help
Endpoint Virtualization Community Blog

Which types of processes can get captured in layers?

Created: 03 Jul 2006 • Updated: 29 Jul 2010 • 2 comments
Admin's picture
0 0 Votes
Login to vote

Vaughn wrote: "On any flavor of Windows, it's nearly impossible to run without TSRs in the background. Which types can get captured in layers?"

Well, strictly speaking, "TSR" is a DOS concept. But perhaps it will help to explain, Vaughn, that SVS captures file system and registry writes into layers based on where the process tree was launched from. If the process tree was started by a program running from Layer X, then the writes go into Layer X. If the process tree was started by a program running from the base, then the writes go into the base. In this regard, it's irrelevant to SVS what kind of process it is (driver, service, system vs. user process, application -- whatever).

Comments 2 CommentsJump to latest comment

Josh Bernson's picture

One good example of this, and a good way to test (and get more familiar with) the process is a combination of Firefox and Java each in their own layers. Processes that run strictly in the browser will leave behind files and reg entries in the Writable section of the Firefox layer. Java applets, on the other hand, will leave trails in the Java layer.

Login to vote
Col Peters's picture

Does this mean that if a base process starts a child that is a SVS'd app that it's changes will be captured into the base ?

I made a terrible mess of my SVS app structure by launching SVSd apps and SVS itself (and capturing new layers) under the ObjectDock (SVSd) 'Dock' application. Things were going very strangely wrong for over a week before I got an inkling of what was happening :|

I'm going to install ObjectDock into the base but am still worried what might happen....

Login to vote