Forced programs always run in default box

[Unknown_User_684]

Forced programs started via a program shortcut always run in the default box when using multiple sandboxes. As far as I am aware this behaviour was also true of previous versions.

Programs started explicitly using the shell extension "Run Sandboxed" command with the "/box:current" parameter do run in the current box, so no problem there.

Does anyone know of a workaround that will cause a "Forced Program" to run in the current box when started via a program shortcut?

Thanks.

Peter

P.S. I do like the new option to allow the box name to be displayed in the window title - it's now much easier to see at a glance which box a program is running in.

[wraithdu]

Where in your INI are you placing the ForceProcess= entry? It should be under a specific sandbox, and I'd imagine it would start under whatever sandbox you place the entry.

[Guest]

Hi wraithdu,

Many thanks for your post. Yes, you are correct. I should have realised that ForceProcess is designed to force a program to start in a specific sandbox, as it is a Sandbox Setting not a Global Setting.

It would be nice if there were the option to specify ForceProcess as either a Sandbox Setting - to force the use of a specific sandbox - or as a Global Setting to enable a program to be started in the sandbox designated as current in the "Switch to Sandbox" menu in Sandboxie Control.

It does look therefore as though there is no way to force a program started from outside the sandbox environment to run in the current sandbox.

It's no big deal anyway, as right clicking on the program shortcut and explicitly selecting "Run Sandboxed" from the context menu bypasses ForceProcess and starts the program in the current sandbox.

Thanks again for clarifying this for me.

Regards
Peter

[Unknown_User_684]

Sorry, I forgot to login before replying, just now.