-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New registry key? #13
Comments
Its will be fixed in next build. Will be changed to create key before using, to store var, instead of on DLL-start phase, So its wiil not be empty, if user not watched video. |
try build 5053. |
Yep, now the key is only created when you start the video: |
Try another build with same number, uploaded now. There was little bug. The value was incorrect. |
Now: |
That strange. |
It should not be < 0 in any case. |
UPD: yes the bug with value still here. I will check it more in such case... |
5054 fixes issue with value. |
HKLM\SOFTWARE\Chrome-xpapi-adapter Everything seem all right? |
Yes, it should be 1, when video playing, and 0 when stopped. |
If you have sceensaver enabled on you system, you can test how this approach works. |
Yes, it is! Thank you! One more question. |
This service started not by DLL's, but by the browser. |
I can try to do this when I have time between other tasks, and found where to do it by patching the browser on the fly. I hope its not influents to sandbox )) |
BTW I have not seen any messages frm WMI on My XP system (on both systems). May be I disabled it early. I mean "Event Viewer" |
I found that |
Have checked it on both real XP's SP3; on XP SP2 Vm; on Win2k3 Vm -- the event logs are clean. |
I will close this issue as resolved. But you can continue to write here about your second question. |
Why in new version 5052 is the HKLM\Software\Chrome-XPAPI-Adapter key created in the registry?
It's an empty key without any parameters, and any registry cleaner (like CCleaner) removes it, but it's still a bit unnerving...
Supermium XP
The text was updated successfully, but these errors were encountered: