Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Cyberlink: Testing Kernel Mode CL Helper and Windows Platform Readiness
nullack [Avatar]
Member Joined: Dec 29, 2010 04:09 Messages: 139 Offline
[Post New]
Hello Cyberlink

I previously posted about how you can test deinterlacing (which was been horridly broken in PowerDVD for ages, atleast back all the way to PowerDVD10) in both TFF and BFF formats quickly and easily in this thread:

http://forum.cyberlink.com/forum/posts/list/46520.page

In this post I'm providing assistance on how to test your broken kernel mode processes.

FACT: The cl helper sys object which you install as part of PowerDVD fails Microsofts verification tests. You can easily test this yourself by running a Windows OS in the device driver verifier mode, enable the cl helper sys object, and use Cyberlink PowerDVD with a bluray disc in the drive, you'll see it fail the tests.

https://support.microsoft.com/en-us/kb/244617

FACT: Your softtware fails to pass because of coding errors in the cl helper process which only you Cyberlink can fix

FACT: This means you are inelligible for membership into the Windows Platform Readiness and Certified for WIndows Microsoft Programs

FACT: It also means that your claims about certain operating systems from Microsoft being supported in your products are dubious at best, and the claims you make about it, are really just your organisations opinion and not something based on any common standard or properly auditable or recognised programs like the Certified for WIndows programme.

FACT: It is a dangerous and undesirable situation to have coding errors in kernel mode processes. Microsoft pays particular attention to these, as they know all too well the undesirable consequencs that coding errors in kernel mode processes provide. A quote from Microsoft about this:

"The Driver Verifier tool that is included in every version of Windows since Windows 2000 is used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior."

If you wish to push a beta that has proposed fixes, I would be willing to assist testing of it.
Powered by JForum 2.1.8 © JForum Team