NDIS is not documented, but in the past if you were willing to go the
NDIS/WDM route you could develop an NDIS miniport with almost no NDIS in
it. I suspect the same is true today with NDIS/KMDF. Of course this
only works for miniports not for all the other aspects of NDIS.
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
-----Original Message-----
From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
Posted At: Saturday, July 10, 2010 8:00 PM
Posted To: ntdev
Conversation: Re: need advice learning driver development
Subject: RE: Re: need advice learning driver development>…NDIS is not in the outline. The guy can’t sit and do nothing for
1.5
months.IIRC, NDIS is one of the most undocumented parts of Windows kernel. I
would
say the only possible way to learn it on your own is to go through ALL
samples
regardless of a project type (because you have a slim chance to
understand
what miniport does and why it does things this way if you don’t
understand how
protocol drivers work), read ndis.h ( this is particularly helpful if
you are
dealing with NDIS_version<6), read whatever documentation is available
and
disasm, disasm, disasm. In other words, the whole thing involves quite
a lot
of work and requires a certain degree of determination.However, someone who already how NDIS works and knows what makes it
tick can
explain it to you, effectively saving you A LOT of efforts…Anton Bassov
__________ Information from ESET Smart Security, version of virus
signature
database 5268 (20100710) __________The message was checked by ESET Smart Security.