Also info on VT shadow and virtual methods, as there are programs that can accomplish this. Some may have features or options, as I am not aware of many programs or methods that can create any virtual system on a drive or in RAM.
The point is that some might remove and or delete the info on a closed session, this is the worst case thought I have had as in creating a circuit in spice and then saving resulted in the session saving the schematic asc. in the virtualized document folder in the hidden VT or shadow share methods the file would be gone, resulting in having to do save as, assign name then retrieve from hidden shares VT Documents and copy to another non Virt location before closing that session (closing Spice) This is not very likley, just a mentioning about programs that may exist with this feature and a test would be "if" such a method would be used to function spice for those that may utilize this concept. As for others they have to have the VT deleted manually via Temp file cleaning or have "Reset Sandbox" for those methods. The files saved in VT would then be gone. So if important files are saved vial this method, retrieval from the VT "backing up" the files to any other primary, such as documents folder or a new directory off the VT entirely would be advised. Virtuals are a copy to hidden drive share virtual sector on read from the main operating system files. Open a folder if running in virtual the folder and files accessed and run in Virt or Sand Boxed will be formed And modified in the VT copy. Manual retrieval is needed to save them elsewhere, or not clear the VT as it will hold them depending on the type of software more than less. Also the VT version of file when in operating in virtual will continue to be the file changed when said changes are made and saved via system or save file option. The original file from the main location initially open in virtual should be left alone by the vt system and be the "original" un altered from that point on unless changed out of virtual on normal OS. Not sure what will happen if an updated virtual version is altered then modified with same name copied back to the read from directory. A potential copy and replace may apply and still function, testing. hm well here it appears in LTVII to actually change the main non virtual directory when the VT run version is altered then saved. Just for the info spec only, Comodo virtual sand box is what I am using. Just to mention any results I have in potential comparison with any others on this form of method to get LTVII to run without the potential of a crash. Method shared as it is one I have used and will continue to use for some time.