it's not clear to me what this option is designed to accomplish. this is not a
criticism. it's just that it's not clear to me how to use and what it does.

i thought it would allow me to "punch a hole" and make a change to the profile of a sandboxed ffox session, ie add or modify one of the addons, and have that change reflected in the un-sandboxed ffox. is this possible
with this option?? if so, i must be doing something wrong.

i tried the above but can't recover the profile folders when given the choice to do so. i selected the top profile folder for recovery but the recovery fails.

thanks for the help

Thats not quite what immediate recovery is for, ill try to explain how it works, if you set a recovery folder in your ini (ill use My Pictures as an example) than when you goto delete your sandbox, sandboxie will first check any folders specified in the ini file (in this case My Pictures) and see if there are any files in the folder(s), if there are it will ask you if you want to recover them (using quick recovery), well the way immediate recovery works, is by "monitoring" any folders you have specified in your ini as a recover file (again, in this case My Pictures) to see when a file(s) is saved to that folder, if a file is saved to that (sandboxed) folder, than it is immediately recovered "on the fly" to your unsandboxed folder while you continue your sandboxing session, i hope that made sense

Now the option you would need if you want changes to your FF profile to happen in "real time" to the unsandboxed FF profile would be the OpenFilePath option, you can read up on it here http://www.sandboxie.com/index.php?OpenFilePath

thanks for the clear explanation of the difference between quick and immediate recovery of files, and how to apply the "OpenFilePath" option for realtime changes to my ffox profile.
does this look correct?

OpenFilePath=C:\Documents and Settings\user name\Local Settings\Application Data\Mozilla\Firefox\Profiles\profile name

On "The Automatic Cleanup" option there is a choice for the
quick or immediate recovery of files in a firefox profile. i guess what is confusing is how is this option different from using the OpenFilePath statement??

thanks again for the quick response

Actually if im not mistaken, the correct line should be:
OpenFilePath=C:\Documents and Settings\username\Application Data\Mozilla\Firefox\Profiles\*

hi SnDPhoenix,

the ini statement that worked for me is:

OpenFilePath=firefox.exe,%AppData%\Mozilla\Firefox\Profiles\*

i was then able to install a new extension (addon) in a sandboxed ffox
session as well as make changes to options of existing extensions and
after terminating the sandboxed session the additions and changes made
were installed in the un-sandboxed ffox.

however, as tzuk has pointed out to me in a previous post, this change does increase the risk of bad things happening by 'punching holes" in
SBIE.

thanks again for your help..you and tzuk have been great.

hi SnDphoenix...following on with my last post about using the OpenFilePath statement, which i now know provides less security but more convenience because the FFox profile can be modified "on-the-fly" , i thought there might be a way to get both security and convenience as follows;

create a "secure browser" sandboxie.ini file without the OpenFilePath statement that can change the FFox profile. use this as the default config file for regular browsing, insuring that the "fence' is always up and keeping the bad stuff out.

create a second sandboxie.ini config file, ie "update browser" with the
corresponding OpenFilePath statement included to allow for "on-the-fly" updates to a FFox profile.

when updates are necessary replace the default config file with the "update browser" config file, and perform the updates.

once the updates are finished , replace the "update browser" config file with the default "secure browser" config file, which gets you once more back in the most secure browsing environment.

i know it's not pretty, but at least this way you're sandboxed all the time and when you're in browse mode there are no holes in the sandbox.

is this workable or am i missing something?? thanks for your help, rube