Playing with Sandboxie, v338 has a Templates.ini file in the program directory. Examining this the other day, it is a nice feature. You have preprogrammed templates, and this tells how to make Local templates in your Sandboxie.ini file. It can provide some nice shorcut features. I decided to play with this to see if I could force all executables on all drives but c: into a sandbox. The NOT character is !. I knew that but it was not working. Here is what I was trying to do: logically say to forcefolder every drive EXCEPT c:\, with this structure ForceFolder=!c:\. This does not work, as the ! is currently limited to processes. However, it did lead to learning a little about the templates. To make one, create an .ini secion in your Sandboxie.ini file. The suggested guideline is to use [Template_Local_Name]. It appears that Template_ is removed, so you reference the template as Local_Name. Some monikers to use for example would be Tmpl.Title Tmpl.Class There are many procedures to use as well. Just examine the templates.ini file in the program files directory of Sandboxie. Anyway, I add this to my Sandboxie.ini file Code: [Template_Local_LockDrives] Tmpl.Title=LockDrives Tmpl.Class=Misc ForceFolder=e:\ ForceFolder=f:\ ForceFolder=g:\ Then, in my chosen sandbox section, I add this Code: Template=Local_LockDrives Now, when an executable in e, f or g is created, it is forced into the associated sandbox. You could prepopulate one template with your local hdds for one sandbox, and another template for all remaining drive letters for a different sandbox, thereby seperating hdds and removable media to different sandboxes. I have not tried this with autorun stuff yet though. But I can see templates becoming very handy, as well as good to share what you come up with because it is so easy to apply. Cheers. Sul.