[DTM Testing] INF Testing Failed

James_Rassel · August 19, 2009, 2:45am

Hi,

We have developed a driver (non-pnp, unclassified) which is used to defrag the drives.
Now we are testing the DTM for WHQL/DRS submission.

But only the INF Testing is failed. As it is unclassified, it does not have any device.
We contacted with Winqual, is it possible to get the WHQL/DRS without the INF.
But they said, it is not possible.

I have attached the log file that it generates.

I also searched many forums
and someone suggested to install the updated filter. We are using the
WLK 1_4 RTM version and also installed the latest filter.

Does anybody have faced the similar problem ?

I also enclosed the log information here so that other people
can find by searching…

-

-

-

-

-

-

Looking forward
James

rtshiva · August 19, 2009, 3:31am

ErrCode=“0x6” ErrType=“WIN32” ErrorText=“The handle is invalid.”
UserText=“Could not find user specified INF files. Bailing out …”
CA=“570438” LA=“644237”>

did you give the INF path in one of the parameters ? try moving it to some
path that does not contain spaces

-rtshvia

On Wed, Aug 19, 2009 at 12:14 PM, James Rassel wrote:

> Hi,
>
> We have developed a driver (non-pnp, unclassified) which is used to defrag
> the drives.
> Now we are testing the DTM for WHQL/DRS submission.
>
> But only the INF Testing is failed. As it is unclassified, it does not have
> any device.
> We contacted with Winqual, is it possible to get the WHQL/DRS without the
> INF.
> But they said, it is not possible.
>
> I have attached the log file that it generates.
>
> I also searched many forums
> and someone suggested to install the updated filter. We are using the
> WLK 1_4 RTM version and also installed the latest filter.
>
> Does anybody have faced the similar problem ?
>
> I also enclosed the log information here so that other people
> can find by searching…
>
> -
> > ProcessName=“C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059\inftest.exe”
> ProcessID=“2944” ThreadID=“2956” BaseTime=“2009:8:12 10:31:33:665”
> Frequency=“2343876” />
>
> - > ServicePack=“” Version=“6.1” BuildLab=“winmain_win7rc”
> BuildDate=“090421-1700” Language=“English (US) (REDMOND)” Config=“n/a”
> CA=“568564” LA=“569936”>
>
>
>
> > Parent=“WTTLOG” />
> - > CA=“568669” LA=“570306”>
>
>
>
> - > ErrCode=“0x6” ErrType=“WIN32” ErrorText=“The handle is invalid.”
> UserText=“Could not find user specified INF files. Bailing out …”
> CA=“570438” LA=“644237”>
>
>
>
> -
>
>
>
> - > Result=“Fail”
> Repro="“C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059\i386\inftest.exe”
> -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059 -f
> /LG -l C:\Windows\inf" CA=“644327” LA=“644683”>
>
>
>
> - > Skipped=“0” CA=“644564” LA=“644878”>
>
>
>
>
>
>
>
> Looking forward
> James
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

OSR_Community_User · August 19, 2009, 8:24am

Check out the inf file with checkinf utility available under tools
directory. It will clearly give the warnings and errors. Posting the exact
error messages of checkinf instead of DTM errors to the list will help you
in isolating the problem.
Regards.

On Wed, Aug 19, 2009 at 1:01 PM, sivakumar thulasimani wrote:

> > ErrCode=“0x6” ErrType=“WIN32” ErrorText=“The handle is invalid.”
> UserText=“Could not find user specified INF files. Bailing out …”
> CA=“570438” LA=“644237”>
>
>
>
>
> did you give the INF path in one of the parameters ? try moving it to some
> path that does not contain spaces
>
> -rtshvia
>
> On Wed, Aug 19, 2009 at 12:14 PM, James Rassel wrote:
>
>> Hi,
>>
>> We have developed a driver (non-pnp, unclassified) which is used to defrag
>> the drives.
>> Now we are testing the DTM for WHQL/DRS submission.
>>
>> But only the INF Testing is failed. As it is unclassified, it does not
>> have any device.
>> We contacted with Winqual, is it possible to get the WHQL/DRS without the
>> INF.
>> But they said, it is not possible.
>>
>> I have attached the log file that it generates.
>>
>> I also searched many forums
>> and someone suggested to install the updated filter. We are using the
>> WLK 1_4 RTM version and also installed the latest filter.
>>
>> Does anybody have faced the similar problem ?
>>
>> I also enclosed the log information here so that other people
>> can find by searching…
>>
>> -
>> >> ProcessName=“C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059\inftest.exe”
>> ProcessID=“2944” ThreadID=“2956” BaseTime=“2009:8:12 10:31:33:665”
>> Frequency=“2343876” />
>>
>> - >> ServicePack=“” Version=“6.1” BuildLab=“winmain_win7rc”
>> BuildDate=“090421-1700” Language=“English (US) (REDMOND)” Config=“n/a”
>> CA=“568564” LA=“569936”>
>>
>>
>>
>> >> Parent=“WTTLOG” />
>> - >> CA=“568669” LA=“570306”>
>>
>>
>>
>> - >> ErrCode=“0x6” ErrType=“WIN32” ErrorText=“The handle is invalid.”
>> UserText=“Could not find user specified INF files. Bailing out …”
>> CA=“570438” LA=“644237”>
>>
>>
>>
>> -
>>
>>
>>
>> - >> Result=“Fail”
>> Repro="“C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059\i386\inftest.exe”
>> -wdk -p
>> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun9C49161F-179A-4C25-A45F-E3A3C98FF059 -f
>> /LG -l C:\Windows\inf" CA=“644327” LA=“644683”>
>>
>>
>>
>> - >> Skipped=“0” CA=“644564” LA=“644878”>
>>
>>
>>
>>
>>
>>
>>
>> Looking forward
>> James
>>
>>
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Tim_Roberts · August 19, 2009, 1:30pm

James Rassel wrote:

We have developed a driver (non-pnp, unclassified) which is used to defrag the drives.
Now we are testing the DTM for WHQL/DRS submission.

But only the INF Testing is failed. As it is unclassified, it does not have any device.
We contacted with Winqual, is it possible to get the WHQL/DRS without the INF.
But they said, it is not possible.

Right. It is not possible to get a WHQL signature on a legacy (non-PnP)
driver. Further, you don’t NEED a WHQL signature – it serves no
purpose. You don’t get the “unsigned driver” warning when starting a
legacy driver.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

James_Rassel · August 20, 2009, 9:05am

Hello

I have checked my INF file with the chkinf.bat file and I get the following error and warning

For those ERROR and WARNING, I do not know how to solve
followings. Have any idea ?

Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not defined.
Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
{8ECC055D-047F-11D1-A537-0000F8753ED2}) is unrecognized.

.\Defrag64.inf: FAILED
NTLOG REPORT--------------
Total Lines: 76 |
Total Errors: 2 |

Total Warnings: 8
Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not defined.
Line 0: WARNING: (W22.1.9998) NOTE: The ChkInf tool does not verify the
WDF sections and directives of the INF file.
Line 0: WARNING: (W22.1.2212) No Copyright information found.
Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
{8ECC055D-047F-11D1-A537-0000F8753ED2}) is unrecognized.
Line 4: WARNING: (W22.1.2203) Custom defined Classes should have a
[ClassInstall32] section.
Line 26: WARNING: (W22.1.2083) Section [DEFAULTINSTALL.NTAMD64] not
referenced
Line 30: WARNING: (W22.1.2083) Section [INITIALREGENTRY] not referenced
Line 55: WARNING: (W22.1.2083) Section [DEFRAGDLLINSTALLER] not referenced
Line 61: WARNING: (W22.1.2083) Section [DISKCOPYFILES] not referenced

— On Wed, 8/19/09, Tim Roberts wrote:

> From: Tim Roberts
> Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> To: “Windows System Software Devs Interest List”
> Date: Wednesday, August 19, 2009, 11:00 PM
> James Rassel wrote:
> > We have developed a driver (non-pnp, unclassified)
> which is used to defrag the drives.
> > Now we are testing the DTM for WHQL/DRS submission.
> >
> > But only the INF Testing is failed. As it is
> unclassified, it does not have any device.
> > We contacted with Winqual, is it possible to get the
> WHQL/DRS without the INF.
> > But they said, it is not possible.
> >???
>
> Right.? It is not possible to get a WHQL signature on
> a legacy (non-PnP)
> driver.? Further, you don’t NEED a WHQL signature –
> it serves no
> purpose.? You don’t get the “unsigned driver” warning
> when starting a
> legacy driver.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>

Tim_Roberts · August 20, 2009, 1:12pm

James Rassel wrote:

I have checked my INF file with the chkinf.bat file and I get the following error and warning

For those ERROR and WARNING, I do not know how to solve
followings. Have any idea ?

Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not defined.

This is pointing out a likely spelling error. You have a line that
referring to a section called [SourceNext] but that section was not
found. Since you didn’t post the INF, we can’t tell you how this came
to be.

Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
{8ECC055D-047F-11D1-A537-0000F8753ED2}) is unrecognized.

Well, you made that class up, right? It’s not surprising that it would
be unrecognized. Assuming you did intend to make up your own class,
that’s not an error. ChkInf is just telling you “by the way, because
this is a custom class, I can’t check any class-specific stuff.”

By the way, I see there is already a class LegacyDriver with a GUID that
is 1 below that one. That is NOT a good way to create new GUIDs. In
particular, that is a “type 1” GUID, where the last 6 bytes are the MAC
address of the primary NIC on the machine that created it. Since there
probably IS a network device with the MAC address you chose, you are
interfering with the guarantee of uniqueness. Always use guidgen or
uuidgen to create a new GUID.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

OSR_Community_User · August 21, 2009, 4:45am

Dear James,

That might be an absolute pointer. Please kindly post your inf file.
If checkinf utility reports no errors, then DTM inf test will be
definitely successful.

Regards.

On Thu, Aug 20, 2009 at 10:35 PM, Tim Roberts wrote:
> James Rassel wrote:
>> I have checked my INF file with the chkinf.bat file and I get the following error and warning
>>
>> For those ERROR and WARNING, I do not know how to solve
>> followings. Have any idea ?
>>
>> Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not defined.
>>
>
> This is pointing out a likely spelling error. ?You have a line that
> referring to a section called [SourceNext] but that section was not
> found. ?Since you didn’t post the INF, we can’t tell you how this came
> to be.
>
>> Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
>> {8ECC055D-047F-11D1-A537-0000F8753ED2}) is unrecognized.
>>
>
> Well, you made that class up, right? ?It’s not surprising that it would
> be unrecognized. ?Assuming you did intend to make up your own class,
> that’s not an error. ?ChkInf is just telling you “by the way, because
> this is a custom class, I can’t check any class-specific stuff.”
>
> By the way, I see there is already a class LegacyDriver with a GUID that
> is 1 below that one. ?That is NOT a good way to create new GUIDs. ?In
> particular, that is a “type 1” GUID, where the last 6 bytes are the MAC
> address of the primary NIC on the machine that created it. ?Since there
> probably IS a network device with the MAC address you chose, you are
> interfering with the guarantee of uniqueness. ?Always use guidgen or
> uuidgen to create a new GUID.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

James_Rassel · August 21, 2009, 5:06am

Thank you for giving advice.

We have FIXED our INF file and remove all the ERROR
and do the DTM test again. But getting the same problem.

One strange thing is, following path even does not exits that is written in the error log file:

<error file=“d:\5289\sdktools\ddk\tools\inftest\wttlog.cpp” line=“272” …>
did you give the INF path in one of the parameters ? try moving it to some path that does not contain spaces

>>Our INF file is in C:\Windows\inf directory, and as we know this is the default directory to look the inf file. Could you please tell which path you are indicating. But C:\Windows\inf is not in the PATH environment variable.

=====================================================================
Additionally I am posing other log information that may help
=====================================================================
log.xml
---------------------------------------------------------------------
-
-
-
-
-
The Library job that was called by this RunJob task has failed. Hence this RunJob task will also be marked failed.

The task found to be failed. Look at the inner errors to find out why the task is failed.

=====================================================================
log2.xml
---------------------------------------------------------------------

-
-
-
-
-
Job was found to have failed. Look at the inner errors to find out why.

Job was found to have failed. Look at the inner errors to find out why.

-
-
-
-
-
The task exited with an ExitCode other than the ExpectedTaskExitCode. This may cause the Task to Fail if it is set to Fail On Exit Code

The task was marked failed after parsing the log file.

The task was marked failed after parsing the log file.

The task found to be failed. Look at the inner errors to find out why the task is failed.

— On Thu, 8/20/09, Tim Roberts wrote:

> From: Tim Roberts
> Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> To: “Windows System Software Devs Interest List”
> Date: Thursday, August 20, 2009, 10:35 PM
> James Rassel wrote:
> > I have checked my INF file with the chkinf.bat file
> and I get the following error and warning
> >
> > For those ERROR and WARNING, I do not know how to
> solve
> > followings. Have any idea ?
> >
> > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not
> defined.
> >???
>
> This is pointing out a likely spelling error.? You
> have a line that
> referring to a section called [SourceNext] but that section
> was not
> found.? Since you didn’t post the INF, we can’t tell
> you how this came
> to be.
>
> > Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
> > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> unrecognized.
> >???
>
> Well, you made that class up, right?? It’s not
> surprising that it would
> be unrecognized.? Assuming you did intend to make up
> your own class,
> that’s not an error.? ChkInf is just telling you “by
> the way, because
> this is a custom class, I can’t check any class-specific
> stuff.”
>
> By the way, I see there is already a class LegacyDriver
> with a GUID that
> is 1 below that one.? That is NOT a good way to create
> new GUIDs.? In
> particular, that is a “type 1” GUID, where the last 6 bytes
> are the MAC
> address of the primary NIC on the machine that created
> it.? Since there
> probably IS a network device with the MAC address you
> chose, you are
> interfering with the guarantee of uniqueness.? Always
> use guidgen or
> uuidgen to create a new GUID.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>

rtshiva · August 21, 2009, 5:14am

James,
From what you are telling it seems you did not provide any inf path in
the test parameters. Copy the inf file to say c: and when you schedule the
inf test i think you have to specify the path to the file like
“c:\yourinf.inf” in one of the parameters. Think the parameter name is
“PATH” check with the wdk documentation on the exact details of these. Now
if you run the test with the path in parameter, wdk will be able to find
your inf file.

-rtshiva

On Fri, Aug 21, 2009 at 2:36 PM, James Rassel wrote:

> Thank you for giving advice.
>
> We have FIXED our INF file and remove all the ERROR
> and do the DTM test again. But getting the same problem.
>
> One strange thing is, following path even does not exits that is written in
> the error log file:
>
> - > …
>
> did you give the INF path in one of the parameters ? try moving it to some
> path that does not contain spaces
>
> >>Our INF file is in C:\Windows\inf directory, and as we know this is the
> default directory to look the inf file. Could you please tell which path you
> are indicating. But C:\Windows\inf is not in the PATH environment variable.
>
>
> =====================================================================
> Additionally I am posing other log information that may help
> =====================================================================
> log.xml
> ---------------------------------------------------------------------
> -
> -
> - > MessageTime=“2009-08-21T05:55:00.387”>
> -
> - > of CHKINF and INFTest Library Job" As Failed as the LibraryJob “CHKINF and
> INFTest Library Job” has Failed" Hresult=“0x8201b0ab”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\runjobtask\src\runjobtask.cpp”
> Line=“246” Function=“CRunJobTask::Cleanup” Machine=“WINDIWS7-PC”>
> The Library job that was called by this RunJob task has
> failed. Hence this RunJob task will also be marked failed.
>
>
> The task found to be failed. Look at the inner errors to find
> out why the task is failed.
>
>
>
>
>
> =====================================================================
> log2.xml
> ---------------------------------------------------------------------
>
> -
> -
> - > MessageTime=“2009-08-21T05:55:00.293”>
> -
> - > Cause=“Job Failed because Task “Run INF Test” Failed with Failure Action
> FailAndContinue” Hresult=“0x8201acad”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\job\src\job.cpp”
> Line=“2179” Function=“CJob::HandleFailureAction” Machine=“WINDIWS7-PC”>
> Job was found to have failed. Look at the inner errors to find
> out why.
>
>
> Job was found to have failed. Look at the inner errors to find
> out why.
>
> - > MessageTime=“2009-08-21T05:55:00.167”>
> -
> - > LogFile" Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1601” Function=“CExecutionTask::Cleanup” Machine=“WINDIWS7-PC”>
> - > File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\common\taskresults\src\taskresults.cpp”
> Line=“324” Function=“CTaskResults::ParseTaskGuidXML” Machine=“WINDIWS7-PC”>
> - > -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun1D2535AC-6659-4BE4-8D69-A18EAE78D789 -f
> /LG -l %windir%\inf\ Failed with ExitCode 1" Hresult=“0x8201adb2”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1436” Function=“CExecutionTask::Cleanup” Machine=“WINDIWS7-PC”>
> The task exited with an ExitCode other than the
> ExpectedTaskExitCode. This may cause the Task to Fail if it is set to Fail
> On Exit Code
>
> The task was marked failed after parsing the log
> file.
>
> The task was marked failed after parsing the log
> file.
>
>
> The task found to be failed. Look at the inner errors to find
> out why the task is failed.
>
>
>
>
>
> — On Thu, 8/20/09, Tim Roberts wrote:
>
> > From: Tim Roberts
> > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> > To: “Windows System Software Devs Interest List”
> > Date: Thursday, August 20, 2009, 10:35 PM
> > James Rassel wrote:
> > > I have checked my INF file with the chkinf.bat file
> > and I get the following error and warning
> > >
> > > For those ERROR and WARNING, I do not know how to
> > solve
> > > followings. Have any idea ?
> > >
> > > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT] not
> > defined.
> > >
> >
> > This is pointing out a likely spelling error. You
> > have a line that
> > referring to a section called [SourceNext] but that section
> > was not
> > found. Since you didn’t post the INF, we can’t tell
> > you how this came
> > to be.
> >
> > > Line 4: WARNING: (W22.1.2215) Class ddrv (ClassGUID
> > > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> > unrecognized.
> > >
> >
> > Well, you made that class up, right? It’s not
> > surprising that it would
> > be unrecognized. Assuming you did intend to make up
> > your own class,
> > that’s not an error. ChkInf is just telling you “by
> > the way, because
> > this is a custom class, I can’t check any class-specific
> > stuff.”
> >
> > By the way, I see there is already a class LegacyDriver
> > with a GUID that
> > is 1 below that one. That is NOT a good way to create
> > new GUIDs. In
> > particular, that is a “type 1” GUID, where the last 6 bytes
> > are the MAC
> > address of the primary NIC on the machine that created
> > it. Since there
> > probably IS a network device with the MAC address you
> > chose, you are
> > interfering with the guarantee of uniqueness. Always
> > use guidgen or
> > uuidgen to create a new GUID.
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars
> > visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online
> > at http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

James_Rassel · August 21, 2009, 9:51am

Hello Siva,

Thanks for your information.

I did a deeper check for several hours. And I think I have some clue.

Every time I run the DTM Job, it creates a dynamic location, something like

cmd /c set path=%path%;C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C && “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe” -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l %windir%\inf\

It tries to set the PATH environment variable in the DTM-Client PC.
But observed that, this dynamic created location is not exists in my DTM-Client PC.
So this task basically failed as it can not execute the inftest.exe file.

In the xml log file it says to look at the inftestdbg.log file. So I checked in that file. It was written as below:

Inftest is running …
Command line: “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe”? -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l C:\Windows\inf\
Current directory : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
Passing extra flags to Chkinf: /LG
FindPerl : ChkinfPath = C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
FindPerl : perl.exe found on the system!
Setting chkinf directory as : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\chkinf.bat
Processing command line …
Find First File operation failed! Bailing out …
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.

As it says
Find First File operation failed! Bailing out …

So this message comes for not finding the desired file.
Ultimately this test is FAILED!

So Can I guess this is my DTM Studio/Controller configuration problem ?
Any Idea ?

James

— On Fri, 8/21/09, sivakumar thulasimani wrote:

> From: sivakumar thulasimani
> Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> To: “Windows System Software Devs Interest List”
> Date: Friday, August 21, 2009, 2:43 PM
> James,
> ???From what you are?telling it seems you
> did not provide any inf?path?in the test parameters.?Copy
> the inf file to say c: and when you schedule the inf test i
> think you have to specify the path to the file like
> “c:\yourinf.inf”? in one of the parameters.
> Think the parameter name is “PATH” check with the
> wdk documentation on the exact details of these. Now if you
> run the test with the path in parameter, wdk will be able to
> find your inf file.
>
>
> ?
> -rtshiva
>
>
> On Fri, Aug 21, 2009 at 2:36 PM,
> James Rassel
> wrote:
>
> Thank
> you for giving advice.
>
> We have FIXED our INF file and remove all the ERROR
> and do the DTM test again. But getting the same problem.
>
>
>
> One strange thing is, following path even does not exits
> that is written in the error log file:
>
> - > File=“d:\5289\sdktools\ddk\tools\inftest\wttlog.cpp”
> Line=“272” …
>
>
> did you give the INF path in one of the parameters ? try
> moving it to some path that does not contain spaces
>
> >>Our INF file is in C:\Windows\inf
> directory, and as we know this is the default directory to
> look the inf file. Could you please tell which path you are
> indicating. But C:\Windows\inf is not in the PATH
> environment variable.
>
>
>
>
> =====================================================================
> Additionally I am posing other log information that may
> help
> =====================================================================
> log.xml
>
>
> ---------------------------------------------------------------------
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.387”>
>
>
> -
> - > INFTest Library Job" As Failed as the LibraryJob
> “CHKINF and INFTest Library Job” has Failed"
> Hresult=“0x8201b0ab”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\runjobtask\src\runjobtask.cpp”
> Line=“246”
> Function=“CRunJobTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The Library job that was called by this
> RunJob task has failed. Hence this RunJob task will also be
> marked failed.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
> =====================================================================
>
>
> log2.xml
> ---------------------------------------------------------------------
>
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.293”>
>
>
> -
> - > INFTest Library Job"" Cause=“Job Failed
> because Task “Run INF Test” Failed with Failure
> Action FailAndContinue” Hresult=“0x8201acad”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\job\src\job.cpp”
> Line=“2179”
> Function=“CJob::HandleFailureAction”
> Machine=“WINDIWS7-PC”>
>
>
> ?Job was found to have failed. Look at
> the inner errors to find out why.
> ?
> ?
> ?Job was found to have failed. Look at
> the inner errors to find out why.
>
>
> ?
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.167”>
> -
> - > INF Test" is Marked Failed From the LogFile"
> Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1601”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> - > Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\common\taskresults\src\taskresults.cpp”
> Line=“324”
> Function=“CTaskResults::ParseTaskGuidXML”
> Machine=“WINDIWS7-PC”>
>
>
> - > -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun1D2535AC-6659-4BE4-8D69-A18EAE78D789
> -f /LG -l %windir%\inf\ Failed with ExitCode 1"
> Hresult=“0x8201adb2”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1436”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The task exited with an ExitCode other
> than the ExpectedTaskExitCode. This may cause the Task to
> Fail if it is set to Fail On Exit Code
> ?
> ?The task was marked failed after
> parsing the log file.
>
>
> ?
> ?The task was marked failed after
> parsing the log file.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
>
> — On Thu, 8/20/09, Tim Roberts
> wrote:
>
> > From: Tim Roberts
> > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
>
>
> > To: “Windows System Software Devs Interest
> List”
> > Date: Thursday, August 20, 2009, 10:35 PM
>
>
>
> > James Rassel wrote:
> > > I have checked my INF file with the chkinf.bat
> file
> > and I get the following error and warning
> > >
> > > For those ERROR and WARNING, I do not know how
> to
>
>
> > solve
> > > followings. Have any idea ?
> > >
> > > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT]
> not
> > defined.
> > >???
> >
> > This is pointing out a likely spelling error.? You
>
>
> > have a line that
> > referring to a section called [SourceNext] but that
> section
> > was not
> > found.? Since you didn’t post the INF, we
> can’t tell
> > you how this came
> > to be.
> >
>
>
> > > Line 4: WARNING: (W22.1.2215) Class ddrv
> (ClassGUID
> > > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> > unrecognized.
> > >???
> >
> > Well, you made that class up, right?? It’s not
>
>
> > surprising that it would
> > be unrecognized.? Assuming you did intend to make up
> > your own class,
> > that’s not an error.? ChkInf is just telling you
> “by
> > the way, because
> > this is a custom class, I can’t check any
> class-specific
>
>
> > stuff.”
> >
> > By the way, I see there is already a class
> LegacyDriver
> > with a GUID that
> > is 1 below that one.? That is NOT a good way to
> create
> > new GUIDs.? In
> > particular, that is a “type 1” GUID, where
> the last 6 bytes
>
>
> > are the MAC
> > address of the primary NIC on the machine that
> created
> > it.? Since there
> > probably IS a network device with the MAC address you
> > chose, you are
> > interfering with the guarantee of uniqueness.?
> Always
>
>
> > use guidgen or
> > uuidgen to create a new GUID.
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> > —
>
>
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other
> seminars
> > visit:
> > http://www.osr.com/seminars
> >
>
>
> > To unsubscribe, visit the List Server section of OSR
> Online
> > at http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at
> http://www.osronline.com/page.cfm?name=ListServer

James_Rassel · August 21, 2009, 2:44pm

Hi,
?
Just for updates:
?
Then I run inftest.exe manually in my DTM-Clint PC
and get the following error always, Even after checking the PATH environment variable.
All the things are OK but still giving following error
?

?

?

-

?

?
?

?

-

?

?
?

-

?

?
?

-

?

?
?

-

?

?
?
?

— On Fri, 8/21/09, James Rassel wrote:

From: James Rassel
Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
To: “Windows System Software Devs Interest List”
Date: Friday, August 21, 2009, 7:20 PM

Hello Siva,

Thanks for your information.

I did a deeper check for several hours. And I think I have some clue.

Every time I run the DTM Job, it creates a dynamic location, something like

cmd /c set path=%path%;C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C && “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe” -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l %windir%\inf\

It tries to set the PATH environment variable in the DTM-Client PC.
But observed that, this dynamic created location is not exists in my DTM-Client PC.
So this task basically failed as it can not execute the inftest.exe file.

In the xml log file it says to look at the inftestdbg.log file. So I checked in that file. It was written as below:

Inftest is running …
Command line: “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe”? -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l C:\Windows\inf Current directory : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
Passing extra flags to Chkinf: /LG
FindPerl : ChkinfPath = C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
FindPerl : perl.exe found on the system!
Setting chkinf directory as : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\chkinf.bat
Processing command line …
Find First File operation failed! Bailing out …
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.

As it says
Find First File operation failed! Bailing out …

So this message comes for not finding the desired file.
Ultimately this test is FAILED!

So Can I guess this is my DTM Studio/Controller configuration problem ?
Any Idea ?

James

— On Fri, 8/21/09, sivakumar thulasimani wrote:

> From: sivakumar thulasimani
> Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> To: “Windows System Software Devs Interest List”
> Date: Friday, August 21, 2009, 2:43 PM
> James,
> ???From what you are?telling it seems you
> did not provide any inf?path?in the test parameters.?Copy
> the inf file to say c: and when you schedule the inf test i
> think you have to specify the path to the file like
> “c:\yourinf.inf”? in one of the parameters.
> Think the parameter name is “PATH” check with the
> wdk documentation on the exact details of these. Now if you
> run the test with the path in parameter, wdk will be able to
> find your inf file.
>
>
> ?
> -rtshiva
>
>
> On Fri, Aug 21, 2009 at 2:36 PM,
> James Rassel
> wrote:
>
> Thank
> you for giving advice.
>
> We have FIXED our INF file and remove all the ERROR
> and do the DTM test again. But getting the same problem.
>
>
>
> One strange thing is, following path even does not exits
> that is written in the error log file:
>
> - > File=“d:\5289\sdktools\ddk\tools\inftest\wttlog.cpp”
> Line=“272” …
>
>
> did you give the INF path in one of the parameters ? try
> moving it to some path that does not contain spaces
>
> >>Our INF file is in C:\Windows\inf
> directory, and as we know this is the default directory to
> look the inf file. Could you please tell which path you are
> indicating. But C:\Windows\inf is not in the PATH
> environment variable.
>
>
>
>
> =====================================================================
> Additionally I am posing other log information that may
> help
> =====================================================================
> log.xml
>
>
> ---------------------------------------------------------------------
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.387”>
>
>
> -
> - > INFTest Library Job" As Failed as the LibraryJob
> “CHKINF and INFTest Library Job” has Failed"
> Hresult=“0x8201b0ab”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\runjobtask\src\runjobtask.cpp”
> Line=“246”
> Function=“CRunJobTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The Library job that was called by this
> RunJob task has failed. Hence this RunJob task will also be
> marked failed.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
> =====================================================================
>
>
> log2.xml
> ---------------------------------------------------------------------
>
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.293”>
>
>
> -
> - > INFTest Library Job"" Cause=“Job Failed
> because Task “Run INF Test” Failed with Failure
> Action FailAndContinue” Hresult=“0x8201acad”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\job\src\job.cpp”
> Line=“2179”
> Function=“CJob::HandleFailureAction”
> Machine=“WINDIWS7-PC”>
>
>
> ?Job was found to have failed. Look at
> the inner errors to find out why.
> ?
> ?
> ?Job was found to have failed. Look at
> the inner errors to find out why.
>
>
> ?
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.167”>
> -
> - > INF Test" is Marked Failed From the LogFile"
> Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1601”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> - > Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\common\taskresults\src\taskresults.cpp”
> Line=“324”
> Function=“CTaskResults::ParseTaskGuidXML”
> Machine=“WINDIWS7-PC”>
>
>
> - > -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun1D2535AC-6659-4BE4-8D69-A18EAE78D789
> -f /LG -l %windir%\inf\ Failed with ExitCode 1"
> Hresult=“0x8201adb2”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1436”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The task exited with an ExitCode other
> than the ExpectedTaskExitCode. This may cause the Task to
> Fail if it is set to Fail On Exit Code
> ?
> ?The task was marked failed after
> parsing the log file.
>
>
> ?
> ?The task was marked failed after
> parsing the log file.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
>
> — On Thu, 8/20/09, Tim Roberts
> wrote:
>
> > From: Tim Roberts
> > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
>
>
> > To: “Windows System Software Devs Interest
> List”
> > Date: Thursday, August 20, 2009, 10:35 PM
>
>
>
> > James Rassel wrote:
> > > I have checked my INF file with the chkinf.bat
> file
> > and I get the following error and warning
> > >
> > > For those ERROR and WARNING, I do not know how
> to
>
>
> > solve
> > > followings. Have any idea ?
> > >
> > > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT]
> not
> > defined…
> > >???
> >
> > This is pointing out a likely spelling error.? You
>
>
> > have a line that
> > referring to a section called [SourceNext] but that
> section
> > was not
> > found.? Since you didn’t post the INF, we
> can’t tell
> > you how this came
> > to be.
> >
>
>
> > > Line 4: WARNING: (W22.1.2215) Class ddrv
> (ClassGUID
> > > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> > unrecognized.
> > >???
> >
> > Well, you made that class up, right?? It’s not
>
>
> > surprising that it would
> > be unrecognized.? Assuming you did intend to make up
> > your own class,
> > that’s not an error.? ChkInf is just telling you
> “by
> > the way, because
> > this is a custom class, I can’t check any
> class-specific
>
>
> > stuff.”
> >
> > By the way, I see there is already a class
> LegacyDriver
> > with a GUID that
> > is 1 below that one.? That is NOT a good way to
> create
> > new GUIDs.? In
> > particular, that is a “type 1” GUID, where
> the last 6 bytes
>
>
> > are the MAC
> > address of the primary NIC on the machine that
> created
> > it.? Since there
> > probably IS a network device with the MAC address you
> > chose, you are
> > interfering with the guarantee of uniqueness.?
> Always
>
>
> > use guidgen or
> > uuidgen to create a new GUID.
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> > —
>
>
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other
> seminars
> > visit:
> > http://www.osr.com/seminars
> >
>
>
> > To unsubscribe, visit the List Server section of OSR
> Online
> > at http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at
> http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

James_Rassel · August 22, 2009, 10:24am

Hello,
?
I got the REASON of the failure.
?
Everything is running inftest.exe or chkinf.bat correctly.
The problem is setting the INF path that , it is looking for.
?
I have manually tested my inf file uisng inftest and this is passed.
while manually testing I can set the path[my inf filename.inf]
?
But If I only give the path the manual testing is failed as well.
It says, “No valid INFs found in the list. Exiting.”
?
So I need to set my INF file name specifically as someone suggested.
?
BUT the problem is, in WLK 1.4, there is no way to set the inf file name
like C:\Windows\inf\myinffile.inf.
?
Any Idea ?
?
?
?
?

— On Fri, 8/21/09, James Rassel wrote:

From: James Rassel
Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
To: “Windows System Software Devs Interest List”
Date: Friday, August 21, 2009, 7:20 PM

Hello Siva,

Thanks for your information.

I did a deeper check for several hours. And I think I have some clue.

Every time I run the DTM Job, it creates a dynamic location, something like

cmd /c set path=%path%;C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C && “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe” -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l %windir%\inf\

It tries to set the PATH environment variable in the DTM-Client PC.
But observed that, this dynamic created location is not exists in my DTM-Client PC.
So this task basically failed as it can not execute the inftest.exe file.

In the xml log file it says to look at the inftestdbg.log file. So I checked in that file. It was written as below:

Inftest is running …
Command line: “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe”? -wdk -p C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f /LG -l C:\Windows\inf Current directory : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
Passing extra flags to Chkinf: /LG
FindPerl : ChkinfPath = C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
FindPerl : perl.exe found on the system!
Setting chkinf directory as : C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\chkinf.bat
Processing command line …
Find First File operation failed! Bailing out …
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.

As it says
Find First File operation failed! Bailing out …

So this message comes for not finding the desired file.
Ultimately this test is FAILED!

So Can I guess this is my DTM Studio/Controller configuration problem ?
Any Idea ?

James

— On Fri, 8/21/09, sivakumar thulasimani wrote:

> From: sivakumar thulasimani
> Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> To: “Windows System Software Devs Interest List”
> Date: Friday, August 21, 2009, 2:43 PM
> James,
> ???From what you are?telling it seems you
> did not provide any inf?path?in the test parameters.?Copy
> the inf file to say c: and when you schedule the inf test i
> think you have to specify the path to the file like
> “c:\yourinf.inf”? in one of the parameters.
> Think the parameter name is “PATH” check with the
> wdk documentation on the exact details of these. Now if you
> run the test with the path in parameter, wdk will be able to
> find your inf file.
>
>
> ?
> -rtshiva
>
>
> On Fri, Aug 21, 2009 at 2:36 PM,
> James Rassel
> wrote:
>
> Thank
> you for giving advice.
>
> We have FIXED our INF file and remove all the ERROR
> and do the DTM test again. But getting the same problem.
>
>
>
> One strange thing is, following path even does not exits
> that is written in the error log file:
>
> - > File=“d:\5289\sdktools\ddk\tools\inftest\wttlog.cpp”
> Line=“272” …
>
>
> did you give the INF path in one of the parameters ? try
> moving it to some path that does not contain spaces
>
> >>Our INF file is in C:\Windows\inf
> directory, and as we know this is the default directory to
> look the inf file. Could you please tell which path you are
> indicating. But C:\Windows\inf is not in the PATH
> environment variable.
>
>
>
>
> =====================================================================
> Additionally I am posing other log information that may
> help
> =====================================================================
> log.xml
>
>
> ---------------------------------------------------------------------
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.387”>
>
>
> -
> - > INFTest Library Job" As Failed as the LibraryJob
> “CHKINF and INFTest Library Job” has Failed"
> Hresult=“0x8201b0ab”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\runjobtask\src\runjobtask.cpp”
> Line=“246”
> Function=“CRunJobTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The Library job that was called by this
> RunJob task has failed. Hence this RunJob task will also be
> marked failed.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
> =====================================================================
>
>
> log2.xml
> ---------------------------------------------------------------------
>
> -
> -
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.293”>
>
>
> -
> - > INFTest Library Job"" Cause=“Job Failed
> because Task “Run INF Test” Failed with Failure
> Action FailAndContinue” Hresult=“0x8201acad”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\job\src\job.cpp”
> Line=“2179”
> Function=“CJob::HandleFailureAction”
> Machine=“WINDIWS7-PC”>
>
>
> ?Job was found to have failed. Look at
> the inner errors to find out why.
> ?
> ?
> ?Job was found to have failed. Look at
> the inner errors to find out why.
>
>
> ?
> - > ResourceName=“WINDIWS7-PC”
> MessageTime=“2009-08-21T05:55:00.167”>
> -
> - > INF Test" is Marked Failed From the LogFile"
> Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1601”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> - > Hresult=“0x8201aeac”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\common\taskresults\src\taskresults.cpp”
> Line=“324”
> Function=“CTaskResults::ParseTaskGuidXML”
> Machine=“WINDIWS7-PC”>
>
>
> - > -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun1D2535AC-6659-4BE4-8D69-A18EAE78D789
> -f /LG -l %windir%\inf\ Failed with ExitCode 1"
> Hresult=“0x8201adb2”
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> Line=“1436”
> Function=“CExecutionTask::Cleanup”
> Machine=“WINDIWS7-PC”>
>
>
> ?The task exited with an ExitCode other
> than the ExpectedTaskExitCode. This may cause the Task to
> Fail if it is set to Fail On Exit Code
> ?
> ?The task was marked failed after
> parsing the log file.
>
>
> ?
> ?The task was marked failed after
> parsing the log file.
> ?
> ?
> ?The task found to be failed. Look at
> the inner errors to find out why the task is
> failed.
>
>
> ?
> ?
> ?> XSLTDirectory=“\XSLTs\ErrorView”
> Title=“Result Error” />
> ?
>
>
> — On Thu, 8/20/09, Tim Roberts
> wrote:
>
> > From: Tim Roberts
> > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
>
>
> > To: “Windows System Software Devs Interest
> List”
> > Date: Thursday, August 20, 2009, 10:35 PM
>
>
>
> > James Rassel wrote:
> > > I have checked my INF file with the chkinf.bat
> file
> > and I get the following error and warning
> > >
> > > For those ERROR and WARNING, I do not know how
> to
>
>
> > solve
> > > followings. Have any idea ?
> > >
> > > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT]
> not
> > defined…
> > >???
> >
> > This is pointing out a likely spelling error.? You
>
>
> > have a line that
> > referring to a section called [SourceNext] but that
> section
> > was not
> > found.? Since you didn’t post the INF, we
> can’t tell
> > you how this came
> > to be.
> >
>
>
> > > Line 4: WARNING: (W22.1.2215) Class ddrv
> (ClassGUID
> > > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> > unrecognized.
> > >???
> >
> > Well, you made that class up, right?? It’s not
>
>
> > surprising that it would
> > be unrecognized.? Assuming you did intend to make up
> > your own class,
> > that’s not an error.? ChkInf is just telling you
> “by
> > the way, because
> > this is a custom class, I can’t check any
> class-specific
>
>
> > stuff.”
> >
> > By the way, I see there is already a class
> LegacyDriver
> > with a GUID that
> > is 1 below that one.? That is NOT a good way to
> create
> > new GUIDs.? In
> > particular, that is a “type 1” GUID, where
> the last 6 bytes
>
>
> > are the MAC
> > address of the primary NIC on the machine that
> created
> > it.? Since there
> > probably IS a network device with the MAC address you
> > chose, you are
> > interfering with the guarantee of uniqueness.?
> Always
>
>
> > use guidgen or
> > uuidgen to create a new GUID.
> >
> > –
> > Tim Roberts, xxxxx@probo.com
> > Providenza & Boekelheide, Inc.
> >
> >
> > —
>
>
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other
> seminars
> > visit:
> > http://www.osr.com/seminars
> >
>
>
> > To unsubscribe, visit the List Server section of OSR
> Online
> > at http://www.osronline.com/page.cfm?name=ListServer
> >
>
>
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at
> http://www.osronline.com/page.cfm?name=ListServer
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

rtshiva · August 22, 2009, 1:30pm

James,
Its been months since i last did DTM tests hence i dont remember exact
config settings to do this. What you found is the test tools that DTM copies
to the test machine for the job you scheduled. The DTM will then execute
these tools with the parameters you see in the XML files. i still think it
is not able to find your inf file and thats the reason it is failing.

1> copy the inf like is said before to say “c:\youinf.inf” in the test pc
2> when you schedule the run inf test, right click on it and select
parameters ( this is based on my fuzzy memory ). it will show a two column
table.
3> type PATH in first column and the actual path to the inf file in the test
system in second column
Now run the test.

it this still fails i’ll refer this to my friend and get a reply from him

-rtshiva
On Fri, Aug 21, 2009 at 7:20 PM, James Rassel wrote:

> Hello Siva,
>
> Thanks for your information.
>
> I did a deeper check for several hours. And I think I have some clue.
>
> Every time I run the DTM Job, it creates a dynamic location, something like
>
>
> cmd /c set
> path=%path%;C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
> && “C:\WTT\JobsWorkingDir\Tasks > WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe” -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f
> /LG -l %windir%\inf >
> It tries to set the PATH environment variable in the DTM-Client PC.
> But observed that, this dynamic created location is not exists in my
> DTM-Client PC.
> So this task basically failed as it can not execute the inftest.exe file.
>
> In the xml log file it says to look at the inftestdbg.log file. So I
> checked in that file. It was written as below:
>
> Inftest is running …
> Command line:
> “C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\i386\inftest.exe”
> -wdk -p
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C -f
> /LG -l C:\Windows\inf > Current directory :
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
> Passing extra flags to Chkinf: /LG
> FindPerl : ChkinfPath =
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C
> FindPerl : perl.exe found on the system!
> Setting chkinf directory as :
> C:\WTT\JobsWorkingDir\Tasks\WTTJobRunF229E800-4AE0-4F1A-8512-512A5812679C\chkinf.bat
> Processing command line …
> Find First File operation failed! Bailing out …
> 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.
>
>
> As it says
> Find First File operation failed! Bailing out …
>
> So this message comes for not finding the desired file.
> Ultimately this test is FAILED!
>
> So Can I guess this is my DTM Studio/Controller configuration problem ?
> Any Idea ?
>
> James
>
>
>
> — On Fri, 8/21/09, sivakumar thulasimani wrote:
>
> > From: sivakumar thulasimani
> > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> > To: “Windows System Software Devs Interest List”
> > Date: Friday, August 21, 2009, 2:43 PM
>
> > James,
> > From what you are telling it seems you
> > did not provide any inf path in the test parameters. Copy
> > the inf file to say c: and when you schedule the inf test i
> > think you have to specify the path to the file like
> > “c:\yourinf.inf” in one of the parameters.
> > Think the parameter name is “PATH” check with the
> > wdk documentation on the exact details of these. Now if you
> > run the test with the path in parameter, wdk will be able to
> > find your inf file.
> >
> >
> >
> > -rtshiva
> >
> >
> > On Fri, Aug 21, 2009 at 2:36 PM,
> > James Rassel
> > wrote:
> >
> > Thank
> > you for giving advice.
> >
> > We have FIXED our INF file and remove all the ERROR
> > and do the DTM test again. But getting the same problem.
> >
> >
> >
> > One strange thing is, following path even does not exits
> > that is written in the error log file:
> >
> > - > > File=“d:\5289\sdktools\ddk\tools\inftest\wttlog.cpp”
> > Line=“272” …
> >
> >
> > did you give the INF path in one of the parameters ? try
> > moving it to some path that does not contain spaces
> >
> > >>Our INF file is in C:\Windows\inf
> > directory, and as we know this is the default directory to
> > look the inf file. Could you please tell which path you are
> > indicating. But C:\Windows\inf is not in the PATH
> > environment variable.
> >
> >
> >
> >
> > =====================================================================
> > Additionally I am posing other log information that may
> > help
> > =====================================================================
> > log.xml
> >
> >
> > ---------------------------------------------------------------------
> > -
> > -
> > - > > ResourceName=“WINDIWS7-PC”
> > MessageTime=“2009-08-21T05:55:00.387”>
> >
> >
> > -
> > - > > INFTest Library Job" As Failed as the LibraryJob
> > “CHKINF and INFTest Library Job” has Failed"
> > Hresult=“0x8201b0ab”
> >
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\runjobtask\src\runjobtask.cpp”
> > Line=“246”
> > Function=“CRunJobTask::Cleanup”
> > Machine=“WINDIWS7-PC”>
> >
> >
> > The Library job that was called by this
> > RunJob task has failed. Hence this RunJob task will also be
> > marked failed.
> >
> >
> > The task found to be failed. Look at
> > the inner errors to find out why the task is
> > failed.
> >
> >
> >
> >
> > > > XSLTDirectory=“\XSLTs\ErrorView”
> > Title=“Result Error” />
> >
> >
> > =====================================================================
> >
> >
> > log2.xml
> > ---------------------------------------------------------------------
> >
> > -
> > -
> > - > > ResourceName=“WINDIWS7-PC”
> > MessageTime=“2009-08-21T05:55:00.293”>
> >
> >
> > -
> > - > > INFTest Library Job"" Cause=“Job Failed
> > because Task “Run INF Test” Failed with Failure
> > Action FailAndContinue” Hresult=“0x8201acad”
> >
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\job\src\job.cpp”
> > Line=“2179”
> > Function=“CJob::HandleFailureAction”
> > Machine=“WINDIWS7-PC”>
> >
> >
> > Job was found to have failed. Look at
> > the inner errors to find out why.
> >
> >
> > Job was found to have failed. Look at
> > the inner errors to find out why.
> >
> >
> >
> > - > > ResourceName=“WINDIWS7-PC”
> > MessageTime=“2009-08-21T05:55:00.167”>
> > -
> > - > > INF Test" is Marked Failed From the LogFile"
> > Hresult=“0x8201aeac”
> >
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> > Line=“1601”
> > Function=“CExecutionTask::Cleanup”
> > Machine=“WINDIWS7-PC”>
> >
> >
> > - > > Hresult=“0x8201aeac”
> >
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\common\taskresults\src\taskresults.cpp”
> > Line=“324”
> > Function=“CTaskResults::ParseTaskGuidXML”
> > Machine=“WINDIWS7-PC”>
> >
> >
> > - > > -wdk -p
> > C:\WTT\JobsWorkingDir\Tasks\WTTJobRun1D2535AC-6659-4BE4-8D69-A18EAE78D789
> > -f /LG -l %windir%\inf\ Failed with ExitCode 1"
> > Hresult=“0x8201adb2”
> >
> File=“e:\6120\sdktools\wtt\jobs\runtime\wttexecutionagent\coreea\executiontask\src\executiontask.cpp”
> > Line=“1436”
> > Function=“CExecutionTask::Cleanup”
> > Machine=“WINDIWS7-PC”>
> >
> >
> > The task exited with an ExitCode other
> > than the ExpectedTaskExitCode. This may cause the Task to
> > Fail if it is set to Fail On Exit Code
> >
> > The task was marked failed after
> > parsing the log file.
> >
> >
> >
> > The task was marked failed after
> > parsing the log file.
> >
> >
> > The task found to be failed. Look at
> > the inner errors to find out why the task is
> > failed.
> >
> >
> >
> >
> > > > XSLTDirectory=“\XSLTs\ErrorView”
> > Title=“Result Error” />
> >
> >
> >
> > — On Thu, 8/20/09, Tim Roberts
> > wrote:
> >
> > > From: Tim Roberts
> > > Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
> >
> >
> > > To: “Windows System Software Devs Interest
> > List”
> > > Date: Thursday, August 20, 2009, 10:35 PM
> >
> >
> >
> > > James Rassel wrote:
> > > > I have checked my INF file with the chkinf.bat
> > file
> > > and I get the following error and warning
> > > >
> > > > For those ERROR and WARNING, I do not know how
> > to
> >
> >
> > > solve
> > > > followings. Have any idea ?
> > > >
> > > > Line 19: ERROR: (E22.1.1003) Section [SOURCENEXT]
> > not
> > > defined…
> > > >
> > >
> > > This is pointing out a likely spelling error. You
> >
> >
> > > have a line that
> > > referring to a section called [SourceNext] but that
> > section
> > > was not
> > > found. Since you didn’t post the INF, we
> > can’t tell
> > > you how this came
> > > to be.
> > >
> >
> >
> > > > Line 4: WARNING: (W22.1.2215) Class ddrv
> > (ClassGUID
> > > > {8ECC055D-047F-11D1-A537-0000F8753ED2}) is
> > > unrecognized.
> > > >
> > >
> > > Well, you made that class up, right? It’s not
> >
> >
> > > surprising that it would
> > > be unrecognized. Assuming you did intend to make up
> > > your own class,
> > > that’s not an error. ChkInf is just telling you
> > “by
> > > the way, because
> > > this is a custom class, I can’t check any
> > class-specific
> >
> >
> > > stuff.”
> > >
> > > By the way, I see there is already a class
> > LegacyDriver
> > > with a GUID that
> > > is 1 below that one. That is NOT a good way to
> > create
> > > new GUIDs. In
> > > particular, that is a “type 1” GUID, where
> > the last 6 bytes
> >
> >
> > > are the MAC
> > > address of the primary NIC on the machine that
> > created
> > > it. Since there
> > > probably IS a network device with the MAC address you
> > > chose, you are
> > > interfering with the guarantee of uniqueness.
> > Always
> >
> >
> > > use guidgen or
> > > uuidgen to create a new GUID.
> > >
> > > –
> > > Tim Roberts, xxxxx@probo.com
> > > Providenza & Boekelheide, Inc.
> > >
> > >
> > > —
> >
> >
> > > NTDEV is sponsored by OSR
> > >
> > > For our schedule of WDF, WDM, debugging and other
> > seminars
> > > visit:
> > > http://www.osr.com/seminars
> > >
> >
> >
> > > To unsubscribe, visit the List Server section of OSR
> > Online
> > > at http://www.osronline.com/page.cfm?name=ListServer
> > >
> >
> >
> >
> >
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars
> > visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online
> > at http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars
> > visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online
> > at
> > http://www.osronline.com/page.cfm?name=ListServer
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Tim_Roberts · August 23, 2009, 1:19am

You wrote:

Everything is running inftest.exe or chkinf.bat correctly.
The problem is setting the INF path that , it is looking for.

I have manually tested my inf file uisng inftest and this is passed.
while manually testing I can set the path[my inf filename.inf]

But If I only give the path the manual testing is failed as well.
It says, “No valid INFs found in the list. Exiting.”

So I need to set my INF file name specifically as someone suggested.

BUT the problem is, in WLK 1.4, there is no way to set the inf file name
like C:\Windows\inf\myinffile.inf.

Well, no, of course there isn’t. First of all, you should NEVER copy your own INF file directly into the \Windows\INF directory. You need to let Device Manager or the SetupDi APIs do that, and they will copy your INF with one of the oem##.inf file names.

DTM tests a driver PACKAGE. You need to have your INF in the same directory as your driver files, just as you will when you distribute the signed driver package.

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

James_Rassel · August 23, 2009, 10:41am

Hello,

Thank you for your information.
This is the most helpful information for me.

Basically I never copy the INF file to C:\Windows\inf directory while testing the DTM.
For manual testing I just copy that file for testing purpose whether inftest.exe is really worked. Now I understand this is my lack of knowledge.

You need to let? Device Manager or the SetupDi APIs do that, and they will copy your INF with one of the oem##.inf file names.

> Now I understand why our INF Test is actually failing. Basically, we do not have any device with this driver. We just load this driver at run time and use it. We programmatically
copy this file in C:\Windows\drivers folder and use it from our application…
So there is no INF installer for this driver.

?If we do not have Device for this driver, how we will make the INF that install that driver and copy the file in oem##.inf naming format ?

But now as I can understand, even if we make the INF installer, then this will be PASSED.
Is my understanding correct ?

Thank you
James

rtshiva · August 23, 2009, 1:10pm

James,
Tim talked about driver package, i.e the inf file along with the
various sys and other files needed for your driver. And i never told you to
rename any inf inside the inf folder in windows,please read all the messages
again. The “Run INF” test simply runs chkinf.bat in your inf file and as far
as i know it does not identify the file automatically. i.e it does not look
for your driver inside the inf folder. You have to tell the test where the
inf is available in the system. then the DTM will run the test and return
the report. This informing the system is what i explained you in previous
mails.

On Sun, Aug 23, 2009 at 8:10 PM, James Rassel wrote:

> Hello,
>
> Thank you for your information.
> This is the most helpful information for me.
>
> Basically I never copy the INF file to C:\Windows\inf directory while
> testing the DTM.
> For manual testing I just copy that file for testing purpose whether
> inftest.exe is really worked. Now I understand this is my lack of knowledge.
>
>
> You need to let Device Manager or the SetupDi APIs do that, and they will
> copy your INF with one of the oem##.inf file names.
>
> >> Now I understand why our INF Test is actually failing. Basically, we do
> not have any device with this driver. We just load this driver at run time
> and use it. We programmatically
> copy this file in C:\Windows\drivers folder and use it from our
> application.
> So there is no INF installer for this driver.
>
> If we do not have Device for this driver, how we will make the INF that
> install that driver and copy the file in oem##.inf naming format ?
>
> But now as I can understand, even if we make the INF installer, then this
> will be PASSED.
> Is my understanding correct ?
>
> Thank you
> James
>
>
>
>
>
> — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

James_Rassel · August 24, 2009, 12:02am

Hi,

Here is my latest report.

Basically I have put all the SYS and DLL files in one folder related with the drivers

For Instance
MyInf\sample.inf
MyInf\sample.sys
MyInf\sample.dll
MyInf\sample.cat

I have used the DPInst.exe application for installing the driver and I put this file in MyInf
folder. According to the DTM steps, I first install the driver using the DPInst.exe and the driver successfully install and I checked that oem1.inf file has made in %windir%\inf directory.
Then I run the DTM INF Test as usual. But got the same result.
So now I am really confused how to solve this issue.

Now we are planning to submit the package with a Readme.doc to Winqual about this issue.
Is this is the perfect idea ?

James

— On Sun, 8/23/09, sivakumar thulasimani wrote:

From: sivakumar thulasimani
Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
To: “Windows System Software Devs Interest List”
Date: Sunday, August 23, 2009, 10:39 PM

James,
???Tim talked about driver package, i.e the inf file along with the various sys and other files needed for your driver. And i never told you to rename any inf inside the inf folder in windows,please read all the messages again. The “Run INF” test simply runs chkinf.bat in your inf file and as far as i know it does not identify the file automatically. i.e it does not look for your driver inside the inf folder. You have to tell the test where the inf is available in the system. then the DTM will run the test and return the report. This informing the system is what i explained you in previous mails.

On Sun, Aug 23, 2009 at 8:10 PM, James Rassel wrote:

Hello,

Thank you for your information.
This is the most helpful information for me.

Basically I never copy the INF file to C:\Windows\inf directory while testing the DTM.
For manual testing I just copy that file for testing purpose whether inftest.exe is really worked. Now I understand this is my lack of knowledge.

You need to let? Device Manager or the SetupDi APIs do that, and they will copy your INF with one of the oem##.inf file names.

>> Now I understand why our INF Test is actually failing. Basically, we do not have any device with this driver. We just load this driver at run time and use it. We programmatically

copy this file in C:\Windows\drivers folder and use it from our application.
So there is no INF installer for this driver.

?If we do not have Device for this driver, how we will make the INF that install that driver and copy the file in oem##.inf naming format ?

But now as I can understand, even if we make the INF installer, then this will be PASSED.
Is my understanding correct ?

Thank you
James

— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Tim_Roberts · August 24, 2009, 12:10am

You wrote:

Now I understand why our INF Test is actually failing. Basically, we do
not have any device with this driver. We just load this driver at run
time and use it. We programmatically copy this file in
C:\Windows\drivers folder and use it from our application…
So there is no INF installer for this driver.

So, this is a non-PnP driver? You do not have an AddDevice routine, and you install it using the DefaultInstall section?

If so, you cannot get a WHQL signature for this driver (nor is one necessary), so your DTM failures are irrelevant.

If we do not have Device for this driver, how we will make the INF
that install that driver and copy the file in oem##.inf naming format?

If it really is a legacy driver, then you don’t use an INF. You install it just as you are doing, by copying the .sys file to system32\drivers. End of story.

But now as I can understand, even if we make the INF installer, then
this will be PASSED.
Is my understanding correct ?

No. If you are not a PnP device, the test will never pass, but that’s OK because you couldn’t submit it anyway.

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Tim_Roberts · August 24, 2009, 12:27am

You wrote:

Here is my latest report.

Basically I have put all the SYS and DLL files in one folder related with the drivers

For Instance
MyInf\sample.inf
MyInf\sample.sys
MyInf\sample.dll
MyInf\sample.cat

I have used the DPInst.exe application for installing the driver and
I put this file in MyInf folder.

Would you be willing to post your INF file, so we can figure out whether this is a PnP driver or not? That makes a huge difference in whether a WHQL submission is even possible or not.

Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

James_Rassel · August 24, 2009, 12:30am

Hello Tim Roberts,

But this is marked as PASSED after installing the latest filter from the winqual just few minutes ago.

So If it is non-pnp, then normal Digital Signature is enough to avoid the WARNING message during installing the driver in x64 bit OS ?

James

— On Mon, 8/24/09, Tim Roberts wrote:

From: Tim Roberts
Subject: Re: [ntdev] [DTM Testing] INF Testing Failed
To: “Windows System Software Devs Interest List”
Cc: “Windows System Software Devs Interest List”
Date: Monday, August 24, 2009, 9:39 AM

You wrote:
>
> Now I understand why our INF Test is actually failing. Basically, we do
> not have any device with this driver. We just load this driver at run
> time and use it. We programmatically copy this file in
> C:\Windows\drivers folder and use it from our application…
> So there is no INF installer for this driver.

So, this is a non-PnP driver?? You do not have an AddDevice routine, and you install it using the DefaultInstall section?

If so, you cannot get a WHQL signature for this driver (nor is one necessary), so your DTM failures are irrelevant.

>?If we do not have Device for this driver, how we will make the INF
> that install that driver and copy the file in oem##.inf naming format?

If it really is a legacy driver, then you don’t use an INF.? You install it just as you are doing, by copying the .sys file to system32\drivers.? End of story.

>But now as I can understand, even if we make the INF installer, then
>this will be PASSED.
>Is my understanding correct ?

No.? If you are not a PnP device, the test will never pass, but that’s OK because you couldn’t submit it anyway.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer