OSRLogoOSRLogoOSRLogo x OSR Custom Development Services

Everything Windows Driver Development

GoToHomePage xLoginx

    Thu, 14 Mar 2019     118020 members


  Online Dump Analyzer
OSR Dev Blog
The NT Insider
The Basics
File Systems
ListServer / Forum
  Express Links
  · The NT Insider Digital Edition - May-June 2016 Now Available!
  · Windows 8.1 Update: VS Express Now Supported
  · HCK Client install on Windows N versions
  · There's a WDFSTRING?
  · When CAN You Call WdfIoQueueP...ously

Are You Writing a Port Driver?

Are you writing a port driver that sits underneath the disk, tape, or CD-ROM class driver? If so, want to drop me a line and tell me why you didn't write your driver as a SCSI or IDE miniport driver? I'm collecting a list of reasons for some friends in Redmond.

Also, if you have taken on this task, be sure you read the code in the disk class driver that shows how one large request (exceeding the maximum buffer size for the underlying disk device) is broken-up into a series of smaller requests. Note how the MDL is reused for each subsequent request.

We've seen a bunch of folks burned by this logic. Which on one hand is understandable, because it's unexpected, but on the other hand it's also inexcusable, because the complete source code for the disk class driver appears in the DDK, Caveat, driver writers.

And please do drop me a line if you're writing a port driver, OK? I'd appreciate it.

Related Articles
Writing a Virtual Storport Miniport Driver

User Comments
Rate this article and give us feedback. Do you find anything missing? Share your opinion with the community!
Post Your Comment

Post Your Comments.
Print this article.
Email this article.
bottom nav links