Testing drivers

1> Is there a way to reduce the perceived RAM available to the OS?
2> Is there a tool that uses a bunch of CPU cycles available for testing?
3> What are the best tools for Driver Verification in everyones opinion?
4> and finally… What are the most usefull test performed by the Driver
Verifier?

Thanks in advance.


Add photos to your messages with MSN Premium. Get 2 months FREE*
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines

(1) /maxmem= n to your boot.ini file. n = megabytes.
(2) cpugrap.exe a Microsoft utility from the Direct Media SDK. You may find
it elsewhere.
(3) Always run with Driver Verifier on. Run the HCT test for your device.
Run them on an multiple processor machine and run multiple copies of the
tests if you can. In other words get as much going thru your driver as
possible from as many processes as possible. This is one boundary condition
I suggest
(4) All but Low Memory Resources.

“greg jacklin” wrote in message news:xxxxx@ntdev…
> 1> Is there a way to reduce the perceived RAM available to the OS?
> 2> Is there a tool that uses a bunch of CPU cycles available for testing?
> 3> What are the best tools for Driver Verification in everyones opinion?
> 4> and finally… What are the most usefull test performed by the Driver
> Verifier?
>
> Thanks in advance.
>
> _________________________________________________________________
> Add photos to your messages with MSN Premium. Get 2 months FREE*
>
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=htt
p://hotmail.com/enca&HL=Market_MSNIS_Taglines
>
>

And besides Driver Verifier:

  1. Test the driver under the checked build, it should run clean
  2. Test the driver under both uni-processor and multi-processor
    systems.
  3. If you have the latest DDK:
    a. Use PREFAST on your build and fix all the warnings
    b. Test the driver with Call Usage Verifier
  4. Consider using /W4 on your compile (yes you have to pragma out
    some things!) and fix all the warnings.
  5. Run the INF file for the driver through ChkInf and fix all the
    errors and warnings
  6. Go to the tools directory of the DDK and:
    a. If you have power management support use the acpi tests
    b. Always run dc2
    c. For any PNP driver run pnpdtest
  7. Consider getting a Code Coverage tool see
    http://www.compuware.com or http://www.bullseye.com/ and run your driver
    with this, add tests to so all the major code paths are exercised. Note:
    Microsoft just started a program to sign “unique devices” you have to have
    75% code coverage.
  8. Get the HCT tests:
    a. Run the general tests for any device
    b. Run the device specific tests if your device is a
    supported class


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

“Michael Jones” wrote in message
news:xxxxx@ntdev…
> (1) /maxmem= n to your boot.ini file. n = megabytes.
> (2) cpugrap.exe a Microsoft utility from the Direct Media SDK. You may
find
> it elsewhere.
> (3) Always run with Driver Verifier on. Run the HCT test for your device.
> Run them on an multiple processor machine and run multiple copies of the
> tests if you can. In other words get as much going thru your driver as
> possible from as many processes as possible. This is one boundary
condition
> I suggest
> (4) All but Low Memory Resources.
>
> “greg jacklin” wrote in message news:xxxxx@ntdev…
> > 1> Is there a way to reduce the perceived RAM available to the OS?
> > 2> Is there a tool that uses a bunch of CPU cycles available for
testing?
> > 3> What are the best tools for Driver Verification in everyones opinion?
> > 4> and finally… What are the most usefull test performed by the
Driver
> > Verifier?
> >
> > Thanks in advance.
> >
> > _________________________________________________________________
> > Add photos to your messages with MSN Premium. Get 2 months FREE*
> >
>
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=htt
> p://hotmail.com/enca&HL=Market_MSNIS_Taglines
> >
> >
>
>
>

Thanks for the many good ideas and suggestions.

From: “Don Burn”
>Reply-To: “Windows System Software Devs Interest List”
>
>To: “Windows System Software Devs Interest List”
>Subject: Re:[ntdev] Testing drivers
>Date: Wed, 28 Apr 2004 14:39:19 -0400
>
>And besides Driver Verifier:
>
> 1. Test the driver under the checked build, it should run clean
> 2. Test the driver under both uni-processor and multi-processor
>systems.
> 3. If you have the latest DDK:
> a. Use PREFAST on your build and fix all the warnings
> b. Test the driver with Call Usage Verifier
> 4. Consider using /W4 on your compile (yes you have to pragma out
>some things!) and fix all the warnings.
> 5. Run the INF file for the driver through ChkInf and fix all the
>errors and warnings
> 6. Go to the tools directory of the DDK and:
> a. If you have power management support use the acpi tests
> b. Always run dc2
> c. For any PNP driver run pnpdtest
> 7. Consider getting a Code Coverage tool see
>http://www.compuware.com or http://www.bullseye.com/ and run your driver
>with this, add tests to so all the major code paths are exercised. Note:
>Microsoft just started a program to sign “unique devices” you have to have
>75% code coverage.
> 8. Get the HCT tests:
> a. Run the general tests for any device
> b. Run the device specific tests if your device is a
>supported class
>
>
>–
>Don Burn (MVP, Windows DDK)
>Windows 2k/XP/2k3 Filesystem and Driver Consulting
>
>“Michael Jones” wrote in message
>news:xxxxx@ntdev…
> > (1) /maxmem= n to your boot.ini file. n = megabytes.
> > (2) cpugrap.exe a Microsoft utility from the Direct Media SDK. You may
>find
> > it elsewhere.
> > (3) Always run with Driver Verifier on. Run the HCT test for your
>device.
> > Run them on an multiple processor machine and run multiple copies of the
> > tests if you can. In other words get as much going thru your driver as
> > possible from as many processes as possible. This is one boundary
>condition
> > I suggest
> > (4) All but Low Memory Resources.
> >
> > “greg jacklin” wrote in message
>news:xxxxx@ntdev…
> > > 1> Is there a way to reduce the perceived RAM available to the OS?
> > > 2> Is there a tool that uses a bunch of CPU cycles available for
>testing?
> > > 3> What are the best tools for Driver Verification in everyones
>opinion?
> > > 4> and finally… What are the most usefull test performed by the
>Driver
> > > Verifier?
> > >
> > > Thanks in advance.
> > >
> > >
> > > Add photos to your messages with MSN Premium. Get 2 months FREE*
> > >
> >
>http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=htt
> > p://hotmail.com/enca&HL=Market_MSNIS_Taglines
> > >
> > >
> >
> >
> >
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at
>http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@hotmail.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com

-------------------
Greg Jacklin
Email: xxxxx@hotmail.com
CELL: 503.504.7220
-------------------


Add photos to your messages with MSN Premium. Get 2 months FREE*
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines