Device path excersizer problems.

Hi all,

Another problem. When installing HCT 11.2 and running, there is no
'DEVICE PATH EXCERSIZER' field shown. After running the USB
interoperability test, this field appears and takes over 10hours to
test all drivers, rather than just my device!

Also Initially DRIVER VERIFIER runs and completes very fast with one
reboot. After interoperability test, DRIVER VERIFIER runs S1 and S3
stress tests, and a whole load others.

Is there anyway to remove HCT and re-install it so that it these test
fields behave as they did initially. The only option I have now is to
restore from a system image.

Mark

Please do make sure that you do not have any unsigned drivers installed in
your system, except your device driver. Driver Verifier and Device Path
Exerciser will test all the unsigned driver in the system. Thus, if you have
other unsigned driver in the test system, those two tests would run longer
and may caused failure that is not related to your driver.


"Mark Vanstone" <mvanstone@semtech.com> wrote in message
news:6600f53.0307121115.37a3f318@posting.google.com...
> Hi all,
>
> Another problem. When installing HCT 11.2 and running, there is no
> 'DEVICE PATH EXCERSIZER' field shown. After running the USB
> interoperability test, this field appears and takes over 10hours to
> test all drivers, rather than just my device!
>
> Also Initially DRIVER VERIFIER runs and completes very fast with one
> reboot. After interoperability test, DRIVER VERIFIER runs S1 and S3
> stress tests, and a whole load others.
>
> Is there anyway to remove HCT and re-install it so that it these test
> fields behave as they did initially. The only option I have now is to
> restore from a system image.
>
> Mark

"Andy Wen [MSFT]" wrote:
> Please do make sure that you do not have any unsigned drivers installed in
> your system, except your device driver. Driver Verifier and Device Path
> Exerciser will test all the unsigned driver in the system. Thus, if you have
> other unsigned driver in the test system, those two tests would run longer
> and may caused failure that is not related to your driver.

What *possible* relevance do other unsigned drivers have to whether the
driver being logo'ed should pass? A major reason why companies bypass
driver certification is that it's so hard to do the testing on their
development machines, which inevitably have after-market stuff installed
and, consequently, some number of unsigned drivers.

I think we appreciate being told how the test works, but Microsoft needs
to understand how difficult it is for us out here in the real world to
run the test when it works the way it does. In this situation, it would
be simplicity itself to change the test to only verify the driver or
drivers that are going to be part of the submission.

--
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com

Thanks all. Andy is correct, one of my devices is using an unsigned driver.

Mark

"Rick Brooks" <rick_brooks@vibren.com> wrote in message news:<uKr1G37SDHA.2128@TK2MSFTNGP12.phx.gbl>...
> IMHO I would argue that testing during development is a separate issue from
> certification testing. I think it makes sense for WHQL to require that your
> driver has been tested in an environment that meets certain minimum
> criteria. Testing on a system which has devices/drivers installed that have
> already met the established requirements is the best way to insure
> reproducible and consistent results.
>
> It would be nice to get better test documentation and instruction for
> running tests privately or outside of the test shell during development.
> Some level of testing can be run on the individual driver/device on a
> platform with known limitations as long as the tester understands those
> limitations and how to interpret the exceptions. However, I would argue
> that, for a certification test run, I see a definite need to be sure the
> test platform meets certain minimum requirements.
>
> With regards to device path exerciser, the HCT 11.2 help file does include
> command-line instructions to run the test privately on the driver under test
> which would exclude the other unsigned drivers in a development system. The
> test scenario where all unsigned drivers are tested which Andy refers to in
> his reply is a result of running the test from the HCT shell.
>
> Just my two cents.
> --
> Rick Brooks
> Industry Certification Engineering
> Vibren Technologies, Inc.
> rick_brooks@vibren.com
>
>
> "Walter Oney" <waltoney@oneysoft.com> wrote in message
> news:3F152C47.7750D1A9@oneysoft.com...
> > "Andy Wen [MSFT]" wrote:
> > > Please do make sure that you do not have any unsigned drivers installed
> in
> > > your system, except your device driver. Driver Verifier and Device Path
> > > Exerciser will test all the unsigned driver in the system. Thus, if you
> have
> > > other unsigned driver in the test system, those two tests would run
> longer
> > > and may caused failure that is not related to your driver.
> >
> > What *possible* relevance do other unsigned drivers have to whether the
> > driver being logo'ed should pass? A major reason why companies bypass
> > driver certification is that it's so hard to do the testing on their
> > development machines, which inevitably have after-market stuff installed
> > and, consequently, some number of unsigned drivers.
> >
> > I think we appreciate being told how the test works, but Microsoft needs
> > to understand how difficult it is for us out here in the real world to
> > run the test when it works the way it does. In this situation, it would
> > be simplicity itself to change the test to only verify the driver or
> > drivers that are going to be part of the submission.
> >
> > --
> > Walter Oney, Consulting and Training
> > Basic and Advanced Driver Programming Seminars
> > Check out our schedule at http://www.oneysoft.com