Reply to thread

Message

<blockquote data-quote="n8chavez" data-source="post: 966689" data-attributes="member: 90863">Here's something interesting.&nbsp; I have my sandboxie RAM drive assigned to s:\, and as you can see from the screenshot the block rule for s:\ is disabled.&nbsp; I would think that would mean that the block rule is invalid.&nbsp; There are also block rules set up for every other harddisk drive letter.&nbsp; But I am still getting prompted for sandboxed processes even though there is no block rule in effect for s:\.&nbsp; As soon as I enable the other rules I start to get prompts from verified and safe sandboxed processes.&nbsp; If I enable the rule for s:\ and enable whitelisting, after doing so I still get prompts for verified safe processes, such as Mozilla Firefox.That tell me that either there is a bug in VoodooShield, or, it does not play nicely with Sandboxie and there is some soft of conflict between the two.&nbsp; Or, third option, I'm an idiot and am doing something wrong.</blockquote>

[QUOTE="n8chavez, post: 966689, member: 90863"] Here's something interesting. I have my sandboxie RAM drive assigned to s:\, and as you can see from the screenshot the block rule for s:\ is disabled. I would think that would mean that the block rule is invalid. There are also block rules set up for every other harddisk drive letter. But I am still getting prompted for sandboxed processes even though there is no block rule in effect for s:\. As soon as I enable the other rules I start to get prompts from verified and safe sandboxed processes. If I enable the rule for s:\ and enable whitelisting, after doing so I still get prompts for verified safe processes, such as Mozilla Firefox. That tell me that either there is a bug in VoodooShield, or, it does not play nicely with Sandboxie and there is some soft of conflict between the two. Or, third option, I'm an idiot and am doing something wrong. [/QUOTE]

Verification