Talk:Windows Driver Model

message: Can be found here. - Ta bu shi da yu 11:08, 28 January 2006 (UTC)
replies: text: Broken link --ThG 12:33, 28 May 2007 (UTC)
replies: text: Can be found here, now. Muad 18:36, 1 June 2007 (UTC)
thread_title:  Excellent overview 

message: It is interesting that the Wikipedia description of what is called a "model" for the arcane world of driver programming contains this comment:  "There were also a number of concerns about the quality of documentation and samples that Microsoft provided."  A model is something that is invented to abstract away complexity in a problem domain or, failing that, to present a way of organizing an approach that shall be used or is recommended to complete a task.  Obviously, the Windows Driver Model was a failure in this regard.   "Quality of documentation and samples" is an issue of concern well outside this one corner of the product gamut.  If you design and manufacture peripheral devices for Wintel machines, getting drivers delivered is a serious, time-constrained and financial burden.  The documentation and samples issue therefore gains visibility.  On the other hand, programmers of business applications grin and bear it or phone up Microsoft for paid assistance.  Few academic computer scientists spend time on the issue of documentation.  Of late, documentation has a reputation for being unnecessary, perpetually out of date, and expensive to produce.  Oh, and by the way, nobody reads it.  The problem, I think, is manifold, but when I think of the documentation I want, it isn't at the microscopic level that I assume most people conceive it to be.  Rather, I'd settle for overviews and tours of the terrain.  For example, each of the major classes should be documented as to the behaviors they exhibit, the data members they expose, and the other classes they interact with.  The typical boilerplate documentation contains, perhaps, a one sentence restating of the name of the class.  The DataGridView class, for example, might have the following remarks:  "The DataGridView class implements a view of a grid of data."  Full stop.  Upper management asks the vendor "Do you have documentation?"  The answer, of course, is "Yes."  End of discussion.  Pity.   70.108.175.203 03:01, 10 August 2006 (UTC)
thread_title:  Documentation 

message: In the article:
 "No support for writing pure user-mode drivers."
I think this is no longer true. In Windows XP i'm developing a pure usermode printer driver, using WDM. Also, Microsoft discourages the use of Kernel mode drivers since Windows XP.
Can someone clear the point about this? --ThG 12:32, 28 May 2007 (UTC)
thread_title:  Disagree with criticism 

message: Why is there an HTML-style comment hidden into the page's source (in the opening paragraph of the Overview section)?  It says, "for those who care, this makes Windows backward compatible, but the driver itself is being forward compatible." 128.244.208.71 (talk) 18:04, 30 April 2008 (UTC)
thread_title:  HTML comment in source 

message: Unless detractors are explicitly calling it for being limited and novice-oriented (which driver models are *not*), I don't see how having a shallow learning curve is a criticism, if anything it is something to be desired. A steep learning curve is usually what is listed as a criticism, if this is what the writer intended, then it should be changed to reflect this. Anthiety (talk) 02:38, 16 August 2010 (UTC)
thread_title:  Criticism: Shallow Learning Curve 

message: "almost impossible" that's the reality when Microsoft say "Cancellation logic is difficult to get right."https://msdn.microsoft.com/en-us/library/windows/hardware/dn613954(v=vs.85).aspx87.102.44.18 (talk) 14:18, 5 August 2016 (UTC)
thread_title:  Dubious