Sorry to disapoint you tzuk but after a while of browsing in youtube and when i tried to pressed the backward button in youtub the tab froze/got stuck again in 3.67.02 version, I will stick with 3.64 it still works fine.

No sound with 3.67.02. If there is anything I can do to help you diagnose this let me know.

i install SB 37.02 and my problem with 18.1025.42 and weird message " message SBIE2205 (19/C0000022)" no longer exist

i encore no sound issue what so ever in youtube or any other site streaming video ...

i keep on testing , to see if any other issue remain like i was reported in my first thread .

using win 7 x64 sp1

good work tzuk so far

BTW

ppl who comment about problem plz add your os version so tzuk know where to look and check

Hi Tzuk,

In relation to error "SBIE2205 Service not implemented: ConnectPort (19/C0000022)", for me is only displayed when i try to execute a function in chrome with the mouse button. If i open the browser i see no such error, until i click something like bookmarks/new tab/app. Right click of the mouse also triggers this error. I have an extension in chrome V18 called smooth gestures. Right click and hold of the mouse and drawing a gesture will execute a command like create new tab, next page.etc. It is supposed to also, trace in Red the path you have drawn. It does not.

When you reported a problem earlier you mentioned the Iron browser first, presumably your primary borwser. Was this the browser you were using when you encounter this problem now? Do you know which version of Chrome it uses?



You said it was working in version 3.67.01c. The part I had to fix was related to registry access and I didn't change that in version 3.67.02. Can you install 3.67.01c again to make sure if the sound is still working in that version?



Thanks, I'll check it out.

Yes I use Iron as my primary browser the version of the iron is 17.0.1000.1, I think it's the latest version of chrome 17 which contains all features and updates known from Chromim 17, I dont know excatly which version but Im sure its the latest version of chrome 17.

same problem here , with iron 17.0.1000.1(2) , using sb 3.67.02 on win 7 x64 sp1

My mistake, .01c is not working either.

D1G1T@L -- I actually prefer "consistently not working" than "confusingly not working" Can you remind me which version of Chrome that is, and which version of Windows?

* * *

I'm still a bit curious about that SBIE2205 message, so in version 3.67.03, I've included some diagnosis prints. Those of you who experienced SBIE2205 at some point, I would like to ask you to install 3.67.03 and then have a DebugView window open while you run Chrome under Sandboxie. You should see these type of messages from Sandboxie appear in DebugView:



Would appreciate if you could collect these messages and post them here for my analysis. Thanks!

Couple of notes about DebugView: It should run as Administrator, and the Capture Global Win32 should be selected (checked) in the Capture menu.

I'll be more careful from now on Using chrome ver. 18.0.1025.142 m with Vista x86 SP2.

ok , now there are final results
i open debugger than start my google chrom under sb


[6292] SBIE process 003856 port <plugplay>
[6292] SBIE process 000000 restrict step 1 00000000
[6292] SBIE process 000000 restrict step 3
[6292] SBIE process 000000 restrict step 4 00000000
[6292] SBIE process 000000 restrict step 5 00000000
[6292] SBIE process 000000 restrict step 6 00000000
[6292] SBIE process 000000 restrict step 7 00000000
[6292] SBIE process 000000 restrict step 8 00000000
[6292] SBIE process 000000 restrict final 1
[6292] SBIE process 003856 restrict ok
[6292] SBIE process 003856 connect 00000000
[6292] SBIE process 003856 final 00000000
[6292] SBIE process 005868 port <plugplay>
[6292] SBIE process 000000 restrict step 1 00000000
[6292] SBIE process 000000 restrict step 3
[6292] SBIE process 000000 restrict step 4 00000000
[6292] SBIE process 000000 restrict step 5 00000000
[6292] SBIE process 000000 restrict step 6 00000000
[6292] SBIE process 000000 restrict step 7 00000000
[6292] SBIE process 000000 restrict step 8 00000000
[6292] SBIE process 000000 restrict final 1
[6292] SBIE process 005868 restrict ok
[6292] SBIE process 005868 connect 00000000
[6292] SBIE process 005868 final 00000000
[6292] SBIE process 005868 port <plugplay>
[6292] SBIE process 000000 restrict step 1 00000000
[6292] SBIE process 000000 restrict step 3
[6292] SBIE process 000000 restrict step 4 00000000
[6292] SBIE process 000000 restrict step 5 00000000
[6292] SBIE process 000000 restrict step 6 00000000
[6292] SBIE process 000000 restrict step 7 00000000
[6292] SBIE process 000000 restrict step 8 00000000
[6292] SBIE process 000000 restrict final 1
[6292] SBIE process 005868 restrict ok
[6292] SBIE process 005868 connect 00000000
[6292] SBIE process 005868 final 00000000





results from chrome 18.0.1025.142 running on win 7 x64 sp1

Couple of notes about DebugView: It should run as Administrator, and the Capture Global Win32 should be selected (checked) in the Capture menu.

* * *

D1G1T@L, I don't have a Vista x86 installation but I tried on Vista x64 and I do get audio.
How about if you add the following setting in Resource Access > Registry Access > Read-Only Access:
*\MMDevices\Audio\*
Does it get the sound back?

Yes after doing that it works!

Good. The audio problem was reported a couple of days ago (in this topic) and the problem had something to do with access to a registry key which matches this resource setting pattern. But the way the access was made, it was specific to 32-bit programs on 64-bit Windows, so the fix was also specific to 32-on-64. And the problem does not occur on 32-bit Windows 7 in my tests. So this is Vista specific it seems. In any event, now that we know the cause, I'll see what I can do to fix this without resource settings. I'll probably ask you to check this again when I release version 3.67.04.

demoneye your results don't show any error which is strange. We'll see what other people have to post.