Victor
Tue Mar 13 06:46:50 CDT 2007
Of course, I tried chkinf and fixed all errors. It seems like problem in
the DTM itself.
"Paul Kamboj" <Paul Kamboj@discussions.microsoft.com> wrote in message
news:FB5A3903-F93C-4F03-BF1A-412A648CCFE3@microsoft.com...
> Have you tried running chkinf.bat against your INF and fix any warnings.
>
> "Victor Punegov" wrote:
>
>> Thanks a lot, Adrian!
>>
>> I will post my problem to this newsgroup.
>>
>>
>> "Adrian Accinelli" <hclnospamalias2@newsgroup.nospam> wrote in message
>> news:evpD50NZHHA.1216@TK2MSFTNGP03.phx.gbl...
>> >
>> > "Don Burn" <burn@stopspam.windrvr.com> wrote in message
>> > news:OBMd7JNZHHA.4692@TK2MSFTNGP04.phx.gbl...
>> >> Victor,
>> >>
>> >> Officially, the only way to contact the DTM team is through a
>> >> support incident. There is a blog on DTM
>> >>
http://blogs.msdn.com/craigrow/
>> >> so you might contact that blogger who is on the team. Rumor has it
>> >> there
>> >> will be a newsgroup in a month or so.
>> >>
>> >>
>> >> --
>> >> Don Burn (MVP, Windows DDK)
>> >> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> >> Website:
http://www.windrvr.com
>> >> Blog:
http://msmvps.com/blogs/WinDrvr
>> >> Remove StopSpam to reply
>> >>
>> >> "Victor Punegov" <wint64@gmail.com> wrote in message
>> >> news:eCvl1FNZHHA.2448@TK2MSFTNGP02.phx.gbl...
>> >>>
>> >>> Hi All,
>> >>>
>> >>> I'm trying to complete "Driver Reliability" tests on the driver using
>> >>> DTM on Vista x86. And every time I got INFTest failure with the log
>> >>> like following:
>> >>>
>> >>> ===
>> >>> Inftest is running ...
>> >>> Command line:
>> >>> "C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91\i386\inftest.exe"
>> >>> -wdk -p
>> >>> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91
>> >>> -f /LG -l C:\Windows\inf\
>> >>> Current directory :
>> >>> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91
>> >>> Passing extra flags to Chkinf: /LG
>> >>> FindPerl : ChkinfPath =
>> >>> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91
>> >>> FindPerl : perl.exe found on the system!
>> >>> Setting chkinf directory as :
>> >>> C:\WTT\JobsWorkingDir\Tasks\WTTJobRun46B67F2B-7841-4AA6-829D-685B8C0D7C91\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.
>> >>> ===
>> >>>
>> >>> Also, I cannot find any ways to contact DTM support team directly.
>> >>>
>> >>> Any help very appreciated!
>> >>>
>> >>>
>> >
>> > Victor,
>> >
>> > I think you are having the exact same problem as I am. In my case the
>> > Check INF job fails because the WDKDevice_InfPath parameter is empty.
>> > This results in a broken command line to inftest.exe (it gets -l
>> > %windir%\inf\ instead of -l %windir%\inf\OEMxxx.INF).
>> >
>> > I am using WDK\ConfigureUnclassified MCU policy and test is running on
>> > Vista x86 DTM client.
>> >
>> > I opened a case for this issue on Friday and sent in my CPK file. I
>> > think
>> > the only solution is a patch from DTM group since if you edit the job
>> > to
>> > correct the parameter yourself you can no longer submit the package.
>> >
>> > FYI - there's a brand new newsgroup for DTM created today.
>> > microsoft.public.development.device.drivers.dtm.
>> >
>> > Sincerely,
>> > Adrian Accinelli
>> >
>> >
>> >
>>
>>
>>
>