SandboxIE 2.86 on Windows 2000 SP4

[tzuk]

Re: SBIE2208

There is no solution yet. When any activity starts in a particular sandbox, then Sandboxie recreates the registry for that sandbox. When all activity stops in that sandbox, then Sandboxie wants to unload that registry.

The SBIE2208 indicates that Sandboxie cannot unload the sandboxed registry because something, most likely from outside the sandbox, is using that registry.

If you can identify the other software that is causing this problem, then perhaps I could do something about it.

* * *

Another issue.

got the May updates (KBs 931768, 922770 and 917283)

Ah! Maybe I could experience the problem first hand if I update my Windows 2000 box with all the latest updates. I'll give it a try.

I've recently updated my Windows 2000 box with all updates, and I still didn't get the hang martinr described with OE and IE.

Martinr, if you read this, I still want to send you a version of SbieDll that will help to show exactly who is accessing that 'ntsvcs' pipe. I'll be ready with this when I release the next beta. (I think I said this before.)

[martinr]

Hi Ronen,

No problem at all - I realise your're a very busy person.


Regards

Martin

[tzuk]

Martin, please try the new beta version. If you still have a problem with ntsvcs, then add the following to the Sandboxie.ini, GlobalSettings section:

BreakOnNtsvcs=Y

Then run the sandboxed Outlook in a debugger, and it will break into the debugger when Outlook tries to access this ntsvcs pipe. Then you can type 'k 99' and see exactly what happens.

[martinr]

Good news, Ronen: I completely uninstalled version 2.86 and installed version 2.92.06.

Outlook Express and Internet Explorer now open as quickly when sandboxed as they do unsandboxed. I've run for an hour or so now without any problems at all. So it seems your new version has solved this particular problem.

Many thanks.

Martin

[tzuk]

Nice! I'm glad to see it worked out.