An all encompassing Sandbox?

[Simple_One]

Can you make a sandbox that will encompass all as yet unknown drives/drive letters without overrding other sandboxes?

The intent of this is to have a sandbox that will automatically capture auto-runs and the like, from devices that people may attach to the PC. I realise I could probably do this by adding all of the currently unused drive letters to a single sandbox using forced folders, but I'm curious if there is a more dynamic way of doing it...

To explain:

It's easy to set up Sandboxie using forced folders to account for all currently used drive letters, but what about one or more USB devices that may be attached to system in future (for which there is currently no known drive letter), can I make a sandbox that will capture executions from these drives without overriding my exisiting sandboxes?
If I just add an asterisk to the forced folder resources, this would work for the above purpose, but since the forced folders takes precdence it will basically make my other sandboxes for specific forced programs null and void. Could you for instance change or specify the sequence in which the sandboxes (and their associated forcing rules) are applied when something initiates sandboxie?

[bs1]

It's easy to set up Sandboxie using forced folders to account for all currently used drive letters, but what about one or more USB devices that may be attached to system in future (for which there is currently no known drive letter), can I make a sandbox that will capture executions from these drives without overriding my exisiting sandboxes?
If I just add an asterisk to the forced folder resources, this would work for the above purpose, but since the forced folders takes precdence it will basically make my other sandboxes for specific forced programs null and void. Could you for instance change or specify the sequence in which the sandboxes (and their associated forcing rules) are applied when something initiates sandboxie?

Not sure I completely understand your questions, but will comment based on what I think you're asking. If I want my cd rom or dvd drives (folders D and E) to be forced to open in a particular sandbox, then I will create that special sandbox and use the Add Folder button to add D:\ and E:\ as forced folders. And if I want any other devices that I attach to my computer to be forced to auto-run in a sandbox that's different than the one I established for my cd rom or dvd drives, then I will create yet another, separate sandbox and once again use the Add Folder button to manually add F:\, G:\, H:\, I:\, J:\, K:\, L:\, etc.

[Simple_One]

Okay, thanks for the response. what you have provided is what I already had in mind as a way I could do this (create a sandbox and use forced folders on all drive letters that are currently unused) but this isn't as idiot proof as what I had hoped for.

My question was if there was a more dynamic way of doing the above by giving the sandboxes different priorities; so, could I somehow prioritise or sequence the sandboxes in a way that would determine which sandbox it executes in but still have a fail safe in the form of a 'catch all' sandbox.
If it matches rules for more than one sandbox then it executes in the first one that is tested, if it doesn't match the rules of a specific box, it moves to the next lowest priority one etc, but the last sandbox catches everything that hasn't been specifically addressed with other sandboxes, because it would have a rule that is always true (or as close as possible, such as forced folders on absolutely everything)

For Example
A program of some type auto runs.
Sandboxie catches it and then starts to determine which sandbox to run the application in.
First, Sandboxie checks the rules I have in sandbox A (my highest priority sandbox) - if it matches these rules then it runs in Sandbox A, otherwise;
It moves on and checks the rules in Sandbox B, if it matches it these then it runs in Sandbox B, and so on...
If at the end of this process it hasn't matched the rules in any of the prior sandboxes, I make my last (lowest priority) sandbox have some sort of all encompassing rule (something like forced folders = *).

The idea here being that I can keep certain programs and folders executing in separate controlled sandboxes through use of specific rules (using rules for specific forced folders or programs and setting the sequence in which they are tested), but ultimately if something runs that I haven't created a specific rule for, then it gets caught in the last sandbox no matter what. This way nothing can 'sneak past' Sandboxie due to human error in having missing rules, typos or rules that you forgot to update etc

My understanding though is that forced folders takes precedence (so an all encompassing rule based of this will always capture everything) as there is currently no way to 'prioritise' the sequence in which sandbox rules are tested...is that correct?
(What I'm suggesting might not be possible with the way a sandbox must be implemented at low levels, I don't know, just want to make sure I can't do it the easy way before I use the harder way )

[tzuk]

There is a way to prioritize the settings by editing the configuration file manually and moving selected sandbox sections higher in the file. Sandboxie looks at "forced program" type settings in the order they appear in the configuration file.

[Simple_One]

There is a way to prioritize the settings by editing the configuration file manually and moving selected sandbox sections higher in the file. Sandboxie looks at "forced program" type settings in the order they appear in the configuration file.

Ah, thats golden, that's exactly what I was after. Thanks Tzuk!