From: Sushma on
The client machine is clean before the driver package is installed.

Do i need to install any kind of QFEs on DTM controller or DTM client
for the test to pass. As i said earlier, i had installed the latest
errata filters as well, but the test had still failed.

Any comments or suggestion would be helpful.

Regards,
Sushma
From: Ray Trent on
*How* clean?

DTM is really bad at "pointing the finger" at the wrong driver for these
kinds of violations. We're constantly getting bug reports from OEMs
where our driver is blamed for the installation of a beta 1.9 WDF by
some other driver package. If any driver on the system had just exactly
the wrong BETA 1.9 coinstaller in its package, it's possible that your
1.9 coinstaller is not getting installed.

diff the one in \windows\... against the one in your driver package. Are
they the same?

Sushma wrote:
> The client machine is clean before the driver package is installed.
>
> Do i need to install any kind of QFEs on DTM controller or DTM client
> for the test to pass. As i said earlier, i had installed the latest
> errata filters as well, but the test had still failed.
>
> Any comments or suggestion would be helpful.
>
> Regards,
> Sushma


--
Ray
From: Sushma on
I was able to see the test being passed now. I was really confused as
the test is shown as failed with red mark in job monitor. When i
captured the submission package, the failing test was shown as pass.

Regards,
Sushma
From: Hannes on
I recall having the same issue, and there is a fault in the DTM test suite.
There is a filter (or QFE?) that fixes this.

/ Hannes.

"Sushma" wrote:

> Hi All,
>
> We are developed a USB driver for Win XP/Vista and Win 7. We are
> currently running WLK tests. We get a WLK test failure for Windows
> Vista while the same test pass on Win 7.
>
> The test is "Verify WDF Coinstaller Version for KMDF". I'm using co-
> installer wdfcoinstaller01009.dll with WDK 7600.16385 and WLK 1.4 for
> DTM testing. Here is the DTM log ouput.
>
> Context Index: 4076053519
> Current: WDF LOGO TEST -CHECK COINSTALLER VERSION
> Parent: WTTLOG
> Start Test 10/15/2009 2:25:27.530 AM WDF LOGO TEST -CHECK COINSTALLER
> VERSION
> Message 10/15/2009 2:25:27.530 AM Enumerate Devices have been called
> for device : usb\vid_1aed&pid_413a
> Message 10/15/2009 2:25:27.530 AM DumpDeviceDriverFiles have been
> called
> Message 10/15/2009 2:25:27.530 AM DumpDeviceDriversCallback has been
> called
> Message 10/15/2009 2:25:27.530 AM DumpDeviceDriversCallback has been
> called
> Message 10/15/2009 2:25:27.530 AM DumpDeviceDriversCallback has been
> called
> Message 10/15/2009 2:25:27.530 AM WdfCoinstaller
> \wdfcoinstaller01009.dll has been found
> Message 10/15/2009 2:25:27.530 AM DumpDeviceDriversCallback has been
> called
> Message 10/15/2009 2:25:27.530 AM Find the timestamp and version for
> file :
>
> C:\Windows\system32\wdfcoinstaller01009.dll
> Message 10/15/2009 2:25:27.530 AM TimeStamp is 1247528983 Size is
> 1482752
> Error 10/15/2009 2:25:27.530 AM CoInstaller version doesn't match any
> of the RTM fre versions
> File: d:\5289\drivers\wdf\kmdf\tests\tools\wdftester\exe
> \cwdflogger.cpp Line: 59
> Error Type: BOOL
> Error Code: 0x0
> Error Text: Error 0x00000000
> Error 10/15/2009 2:25:27.530 AM CoInstaller version doesn't meet the
> requirements
> File: d:\5289\drivers\wdf\kmdf\tests\tools\wdftester\exe
> \cwdflogger.cpp Line: 59
> Error Type: BOOL
> Error Code: 0x0
> Error Text: Error 0x00000000
> End Test 10/15/2009 2:25:27.530 AM WDF LOGO TEST -CHECK COINSTALLER
> VERSION
> Result: Fail
> Repro: Wdftester.exe -kmdf -checkcoinstallerversion "usb
> \vid_1aed&pid_413a" "Windows Vista" KMDF
>
>
> Which WdfCoInstaller need to be used for Windows Vista.
>
> Are there any filters that need to be installed for the failure.
> Please advice which co-installer need to be used for Windows XP/Vista
> and Windows 7 for logo testing.
>
> Any help is much appreciated.
>
> Thanks and Regards,
> Sushma
> .
>