I cannot run a program called "My Lockbox" with S

[ProfessorNelson54]

Hi there Mr. Tzur and everyone,

I cannot run a program called "My Lockbox" with Sandboxie (version 3.74, 64-bit). I'm including the "Resource Acess Monitor" data below. FYI, my OS is Windows 7 64-bit, and Sandboxie's "Experimental Protection 64-bit" option is enabled. Thank so much for your help!

PS. The "My Lockbox" program can be found here: http://fspro.net/my-lockbox/

snipped. --tzuk

[tzuk]

Haven't looked at the program in question yet, but I saw something in your log.

I have to point out that I assume that c:\program files (x86)\shield\idle64.dll is part of your lockbox software.

Please open Sandboxie Control > Sandbox menu > Sandbox Settings,
expand Resource Access > IPC Access > Direct Access,
click add and paste:

*\BaseNamedObjects*\shdidlesdata*

Click OK all the way back and restart the program under Sandboxie.

[ProfessorNelson54]

Hi Tzuk,

The c:\program files (x86)\shield\idle64.dll is NOT part of the lockbox software, but is a component of a program called RollBack Rx -- which is a system restore utility:

Code: Select all

http://www.horizondatasys.com/169614.ihtml

Having clarified the idle64.dll file, I still went ahead and followed your copy/paste instructions: The My Lockbox software will not launch, sorry.

[tzuk]

I see. But I don't see any other resources in your log that might be relevant. Are you trying to run the Lockbox program in the sandbox? Because the log doesn't show that.

Or alternatively perhaps you expect some functionality from Lockbox to be available for programs in the sandbox?

[ProfessorNelson54]

Thanks again for your help, Tzuk.

I was attempting to both install AND launch the Lockbox program in the sandbox. Perhaps this is the wrong approach? I've successfully ran other applications in the same manner (install then run via Sandboxie) without issue so I thought that it would be Ok to run the Lockbox software the same way.

Actually, I've only had one other problem with a different application that wouldn't run immediately after I had installed it with Sandboxie, but that was a unique problem altogether because it required a 'system reboot' in order for the install changes to apply: The app in question would not launch at all unless the reboot was done first. However, the Lockbox program doesn't need an 'immediate' system restart to function after it is installed. I know this because I did a *test install* without Sandboxie's protection and things worked fine.

Anyway, in case I encounter similar problems in the future I would like to know how to resolve them myself instead of bothering you with this mess. LOL!!!

This is why this particular incident is so important to me, Tzuk.

[tzuk]

The Resource Access Monitor log, and any follow up experiments with the Sandbox Settings > Resource Access settings, are specifically about making it possible for programs in the sandbox to talk to their components outside the sandbox.

When you install the program in the sandbox, then everything about the program is in the sandbox, and the Resource Access stuff is not applicable.

From a brief look at this program, it seems it might want to install a filesystem component into Windows so that it can manage folders as they are accessed by programs. That can't of integration into Windows is not something that Sandboxie can allow. That is probably why your program doesn't run under Sandboxie, and you might have to use virtual machine software to test a program like this in isolation.

[ProfessorNelson54]

Thank you so much for that explanation, Tzurk, I now understand!!! So from what I'm learned so far, every piece of software on the market cannot be ran under the protection of Sandboxie for testing purposes (which I somehow erroneously thought so), and this can only be discovered through 'trial-and-error'. And this rule still applies even if I configure the Resource Access Monitor to allow *every* single filesystem component [of a sandboxed program] to have access during the install process...

Anyway, you have a very nice product my friend -- keep up the good work. Thanks again for your time and assistance!

[tzuk]

every piece of software on the market cannot be ran under the protection of Sandboxie for testing purposes

That's not really accurate. Most programs run fine under Sandboxie. Perhaps you mean to say that not every piece of software can run under Sandboxie.

In any case, Sandboxie is a solution at the application level. System level software, like filesystem enhancement drivers, try to tie into the operating system, this occurs below the application level, and is blocked by Sandboxie.

[ProfessorNelson54]

Thanks for the correction/s, you are spot on!