Global delete function
Global delete function
Using Multiple sandboxes, I now had the option to either terminate processes in individual sandboxes, or terminate processes globally in all the sandboxes.
I would like the same ability with the empty sandbox functionality.
Pete
I would like the same ability with the empty sandbox functionality.
Pete
I don't think it's commonly useful to delete all your sandboxes at once, so I won't be adding such a feature. However you can create a batch file to accomplish that. Let's say you have three sandboxes, box1, box2, box3, so you can put the following in a batch file:
Fairly simple, yes?
Code: Select all
"c:\program files\sandboxie\start.exe" /box:box1 /terminate
"c:\program files\sandboxie\start.exe" /box:box2 /terminate
"c:\program files\sandboxie\start.exe" /box:box3 /terminate
"c:\program files\sandboxie\start.exe" /box:box1 delete_sandbox
"c:\program files\sandboxie\start.exe" /box:box2 delete_sandbox
"c:\program files\sandboxie\start.exe" /box:box3 delete_sandbox
tzuk
-
- Posts: 2690
- Joined: Tue Dec 26, 2006 5:44 pm
- Location: West Florida
I was hoping for something moreso user friendly.
Sure one could use the auto-delete, but that can be troublesome when you want to close an app in the sandbox but not have it auto-deleted. Sure it's simple the use batch files, but it's a hassle and unconvenient when you want to save specific boxes taking into account your choice of boxes for deletion will vary each time.
Maybe one could wait until work is finished then use the batch file to delete all the boxes but there's the possibilty that specific boxes need to be save for another time, keep in mind choices of boxes varies all the time still making the batch file an unpleasant method.
My boxes are increasing in numbers so as you can imagine it can get extremely time consuming.
Is it not possible to have some sort of check box menu where you could define boxes you want deleted. It could save your last checked settings, and of coarse a select all option. And possibly merge into one menu or have a seperate menu for terminating the sandboxes.
It's a very convenient feature to add. I simply can't imagine anyone against having this this feature implemented. I don't understand why you would say this feature isn't useful. I'm sure the hardcore Sandboxie users would find it exceptionally useful.
I understand you may feel this is not a major issue but please do consider it as ideas like this help improve Sandboxie and of coarse give us extra excuses for updates
Sure one could use the auto-delete, but that can be troublesome when you want to close an app in the sandbox but not have it auto-deleted. Sure it's simple the use batch files, but it's a hassle and unconvenient when you want to save specific boxes taking into account your choice of boxes for deletion will vary each time.
Maybe one could wait until work is finished then use the batch file to delete all the boxes but there's the possibilty that specific boxes need to be save for another time, keep in mind choices of boxes varies all the time still making the batch file an unpleasant method.
My boxes are increasing in numbers so as you can imagine it can get extremely time consuming.
Is it not possible to have some sort of check box menu where you could define boxes you want deleted. It could save your last checked settings, and of coarse a select all option. And possibly merge into one menu or have a seperate menu for terminating the sandboxes.
It's a very convenient feature to add. I simply can't imagine anyone against having this this feature implemented. I don't understand why you would say this feature isn't useful. I'm sure the hardcore Sandboxie users would find it exceptionally useful.
I understand you may feel this is not a major issue but please do consider it as ideas like this help improve Sandboxie and of coarse give us extra excuses for updates
Before ProcessGroup was invented, there was a very real need for multiple sandboxes. But since that invention, I think things need to be reevaluated. Let's say that I have 10 programs that I want to run sandboxed and only want to grant internet access to 4 of them - that's all one sandbox. I can also grant 'run access' to only those 10 total programs. Even openfilepaths can be set program specific.
Now, of course folks want the freedom to run multiple sandboxes, and every usage is different and I am not advocating a single box system. But the thing is that having the ability to auto/delete is one of the primary reasons for even running mutiple sandboxes in the first place. So I guess I am not seeing how auto/delete is not sufficient because you are running multiple sandboxes.
In that example, if I wanted to discard only the items left by 4 of the ten programs I would need another box and force those 4 programs into it and set it to delete on closing. So that is now two sandboxes.
After that, every program that I want to test out gets its own 'temporary' box usually set to not delete till I am finished evaluating it.
For example, I see ini files all the time where the user has Internet Explorer, Firefox, and Opera all set up in different sandboxes. Why? Even if you run all three at the same time, what is the reasoning for keeping them seperate? Throw Microsoft Word in there and grant it 'run' but not 'internet' access if that is what you want. Set an openfilepath to your Firefox sqlite files and mark it firefox only. But if some things you usually want to keep, and have other items usually discarded, then you create a new box.
Now, of course folks want the freedom to run multiple sandboxes, and every usage is different and I am not advocating a single box system. But the thing is that having the ability to auto/delete is one of the primary reasons for even running mutiple sandboxes in the first place. So I guess I am not seeing how auto/delete is not sufficient because you are running multiple sandboxes.
In that example, if I wanted to discard only the items left by 4 of the ten programs I would need another box and force those 4 programs into it and set it to delete on closing. So that is now two sandboxes.
After that, every program that I want to test out gets its own 'temporary' box usually set to not delete till I am finished evaluating it.
For example, I see ini files all the time where the user has Internet Explorer, Firefox, and Opera all set up in different sandboxes. Why? Even if you run all three at the same time, what is the reasoning for keeping them seperate? Throw Microsoft Word in there and grant it 'run' but not 'internet' access if that is what you want. Set an openfilepath to your Firefox sqlite files and mark it firefox only. But if some things you usually want to keep, and have other items usually discarded, then you create a new box.
wraithdu,wraithdu wrote:I was really bored.
Any idea why I'm getting this
--
[sbdelete]
ini=C:\Winnt\Sandboxie.ini
start=C:\Program Files\Sandboxie\Start.exe
[sandboxes]
--
same message with or without quotes around the path to start.exe, in line 3
Paul
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Cyberfox, Thunderbird
Sandboxie user since March 2007
Win 10 Home 64-bit (w/admin rights) - Zone Alarm Pro Firewall, MalwareBytes Premium A/V, Cyberfox, Thunderbird
Sandboxie user since March 2007
Fixed version is uploaded (1.0.0.1).
It's Sandboxie's optional use of a BOM (byte-order-mark) to indicate that the INI is a Unicode file. So I forced Unicode reading to fix the problem.
@Mitch
Not exactly, but somehow deleting that first blank line gets the BOM inserted by your text editor (notepad probably).
It's Sandboxie's optional use of a BOM (byte-order-mark) to indicate that the INI is a Unicode file. So I forced Unicode reading to fix the problem.
@Mitch
Not exactly, but somehow deleting that first blank line gets the BOM inserted by your text editor (notepad probably).
Who is online
Users browsing this forum: No registered users and 1 guest