B
Bill Unruh
]I haven't heard that the company where I work, would "sign an exclusive
]contract with MS that won't allow them to provide either drivers or
]documentation for other systems" for getting "all of the information needed
]to write those drivers".
Since we have no idea of what company you work for, we have no idea
whether or not they do supply the documentation needed for other to
write drivers for their hardware (or even if they have anything anyone
would want to write drivers for. For all we know, you work for a screw
manufacturing company).
So, since you work there-- do they supply the detailed documentation
enabeling someone to write a driver?
]The DDK documentation used to be a bit terse in some important design
]guides, but Windows XP DDK and Windows 2003 DDK docs have become very good.
]One also may want to read Walter Oney's excellent book on writing WDM
]drivers.
?? Again, this is completely irrelevant. The question is not whether
Microsoft supplied documetnation about how to a device driver for
Windows, but whether the manufacturer supplied docmentation as to how
to interface a device driver with their specific hardware.
]]>
]> ]On Sun, 31 Aug 2003 21:42:04 -0700, "Alexander Grigoriev"
]>
]> ]>]> ]>>
]> ]>> The question has always been how much of this is because Micro$oft
]> ]>> won't release all of the information needed to write those drivers if
]> ]>> the hardware vendor doesn't sign an exclusive contract that won't
]> ]>> allow them to provide either drivers or documentation for other
]> ]>> systems. Of do they get other benefits for colluding with this
]> ]>> convicted criminal organization?
]> ]>>
]> ]>> Bob McConnell
]> ]>> N2SPP
]> ]>>
]> ]>
]> ]>One can have Windows DDK for about $15. It contains everything for
]writing
]> ]>kernel drivers (except for filesystem drivers). There is no strings
]> ]>attached, like NDA.
]>
]> That may be, but that helps very little. It is the detailed commands
]> which have to be sent to the hardware that is needed. Thus, if the
]> manufacturer refuses to release that info, writing adriver is
]> impossible.
]>
]>
]contract with MS that won't allow them to provide either drivers or
]documentation for other systems" for getting "all of the information needed
]to write those drivers".
Since we have no idea of what company you work for, we have no idea
whether or not they do supply the documentation needed for other to
write drivers for their hardware (or even if they have anything anyone
would want to write drivers for. For all we know, you work for a screw
manufacturing company).
So, since you work there-- do they supply the detailed documentation
enabeling someone to write a driver?
]The DDK documentation used to be a bit terse in some important design
]guides, but Windows XP DDK and Windows 2003 DDK docs have become very good.
]One also may want to read Walter Oney's excellent book on writing WDM
]drivers.
?? Again, this is completely irrelevant. The question is not whether
Microsoft supplied documetnation about how to a device driver for
Windows, but whether the manufacturer supplied docmentation as to how
to interface a device driver with their specific hardware.
]]>
]> ]On Sun, 31 Aug 2003 21:42:04 -0700, "Alexander Grigoriev"
]>
]> ]>]> ]>>
]> ]>> The question has always been how much of this is because Micro$oft
]> ]>> won't release all of the information needed to write those drivers if
]> ]>> the hardware vendor doesn't sign an exclusive contract that won't
]> ]>> allow them to provide either drivers or documentation for other
]> ]>> systems. Of do they get other benefits for colluding with this
]> ]>> convicted criminal organization?
]> ]>>
]> ]>> Bob McConnell
]> ]>> N2SPP
]> ]>>
]> ]>
]> ]>One can have Windows DDK for about $15. It contains everything for
]writing
]> ]>kernel drivers (except for filesystem drivers). There is no strings
]> ]>attached, like NDA.
]>
]> That may be, but that helps very little. It is the detailed commands
]> which have to be sent to the hardware that is needed. Thus, if the
]> manufacturer refuses to release that info, writing adriver is
]> impossible.
]>
]>
