@tim thanks for your support
>Loaded the testucsi.sys driver on both UCSI_1 and UCSI_2 capable system
and followed section of the “Running the test” in this link(
https://msdn.microsoft.com/en-us/library/windows/hardware/mt770579(v=vs.85).
aspx) We have >>manually entered the name of the machine in partner system
when we run test cases.When we run the HLK test in server machine where i
can see the script running on UCSI_1 capable system but i can’t see any
script which is >>not running in UCSI_2 capable system.
Suppose when i run the some test for UCSI on HLK server where it will ask
the partner system name and i cant see any script were running on UCSI_2
capable system but i can see the script were running on UCSI_1 capable
system (SUT device) where HLK client and TAEF & their service were
installed and running on both system.
Question:
1)When the HLK server running the test case for UCSI where I can’t see the
script running in UCSI_2 capable system(Partner system I have entered the
machine name in HLK server when it encounters the pop message for asking
the partner machine name ) which is connected to J2 of MUTT device whereas
I can see the script running on UCSI_1 (SUT )capable system ?
- whether the UCSI script should run on both UCSI_1 and UCSI_2 capable
system or not ? if not it’s a correct behavior ?
Could you please provide your inputs for the above query.
Regards,
Prabhakar V
On Tue, Mar 28, 2017 at 11:25 AM, Tim Roberts wrote:
> On Mar 27, 2017, at 9:23 PM, Prabhakar V wrote:
>
>
> 1)Whether its mandatory or any command which we can bypass to pass all
> commands which has been listed in the HLK test and get certification ?
>
> You have to pass all of the tests for your device class. In a very few
> cases, Microsoft has sometimes found bugs in their tests. In that case,
> they issue “errata” that allow you to submit logs with very specific
> failures, as long as you include the errata that supports your failure.
> You get the list of errata from the HLK dashboard.
>
> 2) Using the Compatibility playlist for HLK version 1607 whether we can
> remove the some of the test cases for UCSI , pass the HLK test and create a
> submission package
>
> Not unless there is an errata, or unless you get specific permission from
> the Microsoft HLK for a test that you cannot pass for some reason. That
> doesn’t happen very often.
>
> 3) Whether any vendor has passed the HLK certification for UCSI on windows
> 10 version 1607 ( we are not able to check in dashboard).
>
> Any vendor who is shipping desktop or laptop computers with USB 3 and
> Windows 10 will have passed it.
>
> Loaded the testucsi.sys driver on both UCSI_1 and UCSI_2 capable system
> and followed section of the “Running the test” in this link(
> https://msdn.microsoft.com/en-us/library/windows/
> hardware/mt770579(v=vs.85).aspx)
>
> We have manually entered the name of the machine in partner system when we
> run test cases.
>
> When we run the HLK test in server machine where i can see the script
> running on UCSI_1 capable system but i can’t see any script which is not
> running in UCSI_2 capable system.
>
> I don’t know what that means.
> —
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>