Which types of processes can get captured in layers?
Created: 03 Jul 2006 | Updated: 29 Jul 2010 | 2 comments
Q:
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?"
A:
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).
Blog Entry Filed Under:
The Endpoint Virtualization Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Virtualization community. Any authenticated Connect member can contribute to this blog.
Comments 2 Comments • Jump to latest comment
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.
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....
Would you like to reply?
Login or Register to post your comment.