I just meant myself on a few computers. I wouldn't want a black screen everytime. It always gives me the feeling of an evil script. Anyway, I have a folder of the latest installation files for all my programs, which I store for backup. If you release a new version, I delete the old installation and put the new one instead. It's more comfortable having just one file for each installation.

Although I did and hopefully will again help people install and set up their own Sandboxie. But if they ask how to save/restore sandboxes, there's no way they'll understand how to use a batch file.

But that's all off-topic. The point is "Pre Exec" would be as helpful as "Delete Command". Since "Delete Command" already exists, it means there's potential support for "Pre Exec".

You can't just assume that because there is a Delete Command, it must be a trivial task to also have the PreExec you suggest. But I'm afraid that is just not the case. It would be true if all programs went through Start.exe, which begins un-sandboxed and might run a PreExec command, before switching to sandboxed mode. But forced programs completely bypass Start.exe.

On the other hand, Delete Command always works the same, regardless of the way the program started. And AutoExec also works the same way, regardless of the way the program started.

Point taken. So "Delete Command" aside, do you plan to eventually enable a standalone facility to do something before the sandbox begins (even if they begin without Start.exe)?

If not, how about a checkbox next to "Delete Command" called "prepare for deletion"? Signaling no would just run the delete command on the regular folder (thus supporting something like Toucan).

I don't think such a feature deserves a GUI element. At this point I believe you'd probably be the only one using it. But I can revise Start.exe so if the Delete Command starts with a special indication, then it would skip the "preparation" process.

But you should take into consideration that if a new sandboxed program is started, while you mirror the contents, and the sandbox folder has not been renamed, then it might mess up your mirroring results.

So maybe keep the renaming, but prevent anything else. The question is what is anything else. Is there a list or is it just renaming plus unhiding the LOG file?

Although note that those who save/restore sandboxes (there were a lot of these questions lately) already take the risk. This is because the current method copies over the backup folder, which assumes the destination doesn't exist. This is exactly why "Pre Exec" is more fitting (it wouldn't start the sandbox until it's "ready"). Do you think it'll ever be possible to have such a thing?

I thought we were past the PreExec thing.

Have you considered having scripts that are unrelated to Sandboxie and Delete Command, which you invoke when you wish to save or restore the sandbox?

Maybe a couple of shortcuts on your desktop that take care of this.

I've considered it but I prefer it to be internal. When I get people to install their own Sandboxie, I don't want to also give them my own script. It'll just be confusing. Sandboxie should be standalone.

It's not a bad feature request but look, I haven't even added an easy way to set up AutoExec commands. I will probably work on these type of automation utilities at some point but it's not a high priority at this time.

I join this request with this posting http://www.sandboxie.com/phpbb/viewtopic.php?t=11284