Hi,
What I'm to recommend is not for "only temporary sandbox(es)" users since SBIE deletes the SBx itself ("everything") if it's chosen among its options...
For others like me, we like to test the programs with SBIE for a while before we inject them to our system, we don't want trials to install additional software and we like to keep a leash on certain programs all thanks to SandBoxIE. Yet SBx'ing applications like G' Chrome is inefficient since they keep many temporary files and so. Unlike Firefox, Chrome doesn't provide "Exit Cleaning" causing SBx to bloat more and more. Also many other programs doesn't clean their garbage either...
Adding mentioned behavior to the SBx'ing process, virtualizing everything, copies everything (small) "touched" into the SBx. I most of the times find folders/files that I've never run under that particular SBx yet executed sideways anyways creating more garbage. Of course you can "manually" run third party ccleaners afterward within these SBx'es yet I believe it's somewhat SandBoxIE's responsibility to provide an automated mechanism to do so. Like an "EXIT" function which will run your favorite cleaner for that SBx after you're done...
Similar function already exists in "Program Stop"/"Lingering..." for leftover resident programs cleaning memory from them yet not the disk. All I ask is an option under "Program Stop" section to "Run" your cleaner program after your "Leader Program" Exits...
For the "Start" part, well this is not so important for me yet, some users may need the vice versa function when starting a Sbx like the "Startup" folder of Windows. They might like to start helper applications with the program that started Sbx automatically...
I'm also aware that there are many workarounds, some I'm currently using, to achieve these features yet wouldn't it be nice and easier if SandBoxIE does this?
Thanks...
Start/Exit Functions for Non-Temporary SBoxes
Who is online
Users browsing this forum: No registered users and 1 guest