Is it possible that the log is cut off because I exceeded the limit for the maximum # of characters permitted per post?

Yes, it is possible the log was too long for a single forum post. You can paste the log data first into Notepad, and then you can paste it here into multiple posts. Or you can email the log to me, although the forum is best, I think.

These lines are basically repeated dozens of times, and it's not necessary to see them all.
You can just cut out most of them, and leave a few - above
and below the <snip> point:

Ipc O \BaseNamedObjects\Mutex, mAH, Process 00000930, Api 0x7629d77a
Ipc O \BaseNamedObjects\Mutex, mAH, Process 00000930, Api 0x762a07bb
Ipc O \BaseNamedObjects\Mutex, mAH, Process 00000930, Api 0x762a2bb1
<snip>
Ipc O \BaseNamedObjects\Mutex, mAH, Process 000016fc, Api 0x77ec7869

Ipc O \Sessions\1\BaseNamedObjects\Global\Mutex, mAH, Process 0000014c, Api 0x762a2bb1
Ipc O \Sessions\1\BaseNamedObjects\Global\Mutex, mAH, Process 0000014c, Api 0x762a3344
Ipc O \Sessions\1\BaseNamedObjects\Global\Mutex, mAH, Process 0000014c, Api 0x762a509b
<snip>
Ipc O \Sessions\1\BaseNamedObjects\Global\Mutex, mAH, Process 00000b98, Api 0x77d74e00

That will reduce the space needed for posting in a forum message.

As I am not qualified to know what is or is not important/redundant in the Resource Access Monitor log file, I don't know what is OK to delete from the log. I tried posting in two pieces, but the log file still got cut off.

tzuk, I have emailed the log file to you instead. This is a new capture, with Sandboxie 3.53.06 / Firefox 3.6.15. During the capture period, Firefox stopped responding, the window grayed out, and I had to force the shutdown of Firefox.

I got the email but I'm afraid I still don't see anything that might suggest any problem. The only thing I see is a minor thing related to WinPatrol. Let's see if this makes a difference: Please go to Sandbox Settings, Resource Access, Window Access, click Add, and paste: WinPatrol
Then OK all the way back and restart the programs in the sandbox.

tzuk,

I added WinPatrol to Window Access, but it didn't make any difference

Well honestly I can't say I'm surprised, I did not expect this small setting to make a difference.

At this point I can only suggest that you remove other software one by one and note when Sandboxie starts working, i.e. which program had to be removed for Sandboxie to work.

tzuk,

I have good news to report. Around the time Sandboxie stopped working, Win 7 Service Pack 1 was available on Windows Update. However, I have been having problems getting SP 1 installed. The install would proceed ("Configuring Service Pack") up to 8%, then lock up. I went through several 'system restore/retry SP 1 install' cycles. I've been working with a Microsoft level 2 technician for over a month(!) to get this resolved. Well, SP 1 finally installed correctly today. And guess what? Sandboxie 3.53.06 works with Firefox now! Some things that I did differently after the SP 1 install (at the suggestion of the MS technician): instead of Avast! anti-virus and PC Tools Firewall, I went with Microsoft Security Essentials for anti-virus, and and using the built-in MS Firewall. I don't know how/why the service pack install problem has anything to do with Sandboxie, but perhaps posting the details of what happened might help someone else experiencing similar problems with Sandboxie. If nothing else, at least it provides a place to start looking (i.e., MS updates/service packs might be causing the problem).

tzuk, thank you very much for your help. One other question: is it OK to stay with the 3.53.06 beta version of Sandboxie, or do you recommend I go back to the stable 3.52 version?

Very good news, thanks for the update.

When I have some time, I will try to install both Avast! anti-virus and PC Tools Firewall to see if I can reproduce this problem.

As for staying with version 3.53.06, basically it should be ok, but I am aware of a couple of tweaks, so check back in a few days to get version 3.53.07.

Right, I forgot to include the possibility that the problem was caused by either (or both) Avast anti-virus or PC Tools Firewall Plus. When you test Avast and PC Tools, please post and let us know what you found. (It would be nice to have the option of having alternatives to the MS anti-virus and MS Firewall).

Again, tzuk, thanks a lot for your patience and your efforts in resolving this problem.

I just installed avast 6 and disabled autosandbox to avoid possible confilcts. Avast has a dll file snxhk.dll, if i block it from OA then programs fail to run in sandbox, when i allow it programs run, but run slowly, is there some conflict with sandbox? (i use sandbox 3.53.07 on XP with avast compatibility checked)

Also previously i had avast on a different drive, a drive where i choose for my sandboxes not to have access. I failed to update avast on that drive, had to uninstall. I updated sandbox to 3.53.07 but again I failed to make a clean installation of avast on that drive and a message SBIE2334 opened while i was not trying to use sandbox(?) - that looks like a bug

I am not sure, shall i try to downgrade avast/change antivirus/continue to use avast 6 since that is no(?) conflict/wait for a sandboxie update?

Thanks & Regards

The problem with avast's snxhk.dll was also reported here:

http://www.sandboxie.com/phpbb/viewtopic.php?t=10104

Thanks for informing me. i will repost my message there, best regards!