We have disk lower filter driver for which we are trying to run WHQL tests.
The problem is that it is not finding the inf file. Our setup program is not
copying the inf file ( like the device driver type packages).
What we use: (a) WLK 1.6. Windows 8 R2 as the controller machine. (b) We go
to controller and at the configure time it asks for inf file options(
provide or not provide). We pick up the - provide option. And we load this
from the local ( that is the controller machine’s file path, say -
c:\desktop\myfiltr.inf ).
Here is the output we get, when we select the option of providing the inf
file and run inf test.
( In the past, I knew that for some filter drivers, if we were
blocked for inf checking failure, we had the option of handing out the
inf(s) to whql team to process separately. Not sure if it is still valid or
not )
The logout put is -
Inftest is running …
Command line:
“C:\WLK\JobsWorkingDir\Tasks\WTTJobRun23813FAD-7933-465B-BFA7-8077979C6A93\i
386\inftest.exe” -wdk -p
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun23813FAD-7933-465B-BFA7-8077979C6A93 -f
/LG -l C:\windows\inf\
Current directory :
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun23813FAD-7933-465B-BFA7-8077979C6A93
Passing extra flags to Chkinf: /LG
FindPerl : ChkinfPath =
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun23813FAD-7933-465B-BFA7-8077979C6A93
FindPerl : perl.exe found on the system!
Setting chkinf directory as :
C:\WLK\JobsWorkingDir\Tasks\WTTJobRun23813FAD-7933-465B-BFA7-8077979C6A93\ch
kinf.bat
Processing command line …
Find First File operation failed! Bailing out …
<<< From the wtt log
d:\6229\sdktools\ddk\tools\inftest\wttlog.cpp
Line: 272
Error Type:
WIN32
Error Code:
0x6
Error Text:
The handle is invalid.
>>
Could not find user specified INF files. Bailing out …Could not expand
user supplied lists of infs into individual filenames.
Running InfTest : Could not expand user supplied list of infs.
Clearing list of infs …
Processing command line … DONE!
The inftest check failed to run. Please check the debug logs for more
information.
Questions are -
-
Is it the right way to specify inf file? Meaning just provide the
filefullpath(including the file name) from the local controller machine? -
AS far as I know, creation of oemNNN.inf file in c:\widows\inf is
simply copying inffile and rename ( in the setup process). Would manually
copy/rename work? If so, then which machine should have this ? Must be the
client test machine! -
Looks like the package creates some disk(folder) and mapps to d:
then gets those packages, but I don’t see they are there, wondering if I
need to turn the debugger or not (but would take longer ). -
If I cookup an app to just use the setupapi to copy ( including
renaming to oemNNN.inf) would that be an alternative? -
Finally, if we don’t provide the inf test, but we do the rest of the
tests, would that exercise our driver’s quality?
What it is trying to tell by giving this error??
-pro