Hello,
Is there any body that can recommand on a networking device driver book ?
I’m planning to write a virual miniport NDIS device driver.
OS.
> Hello,
Is there any body that can recommand on a networking device driver book =
?I’m planning to write a virual miniport NDIS device driver.
OS.
There are no networking device driver books, the market is too small.
That
being said, since you are talking a virtual miniport which implies
NDIS/WDM
the good news that you only need a few calls (My team just completed one
with
only 21 unique Ndis routines being referenced). Now if we could just get
Microsoft to recognize that with one kernel in the future, they ougth to
eliminate 90% of NDIS, there is the possibility someone would add a
chapter
or two to an existing book to cover the rest.
Don Burn
Egenera, Inc
> Now if we could just get
Microsoft to recognize that with one kernel in the future, they ougth to
eliminate 90% of NDIS, there is the possibility someone would add a
chapter or two to an existing book to cover the rest.
Preach on brother!!
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
wrote in message news:xxxxx@ntdev…
>
> > Hello,
> >
> > Is there any body that can recommand on a networking device driver book
=
> > ?
> >
> > I’m planning to write a virual miniport NDIS device driver.
> >
> > OS.
>
> There are no networking device driver books, the market is too small.
> That
> being said, since you are talking a virtual miniport which implies
> NDIS/WDM
> the good news that you only need a few calls (My team just completed one
> with
> only 21 unique Ndis routines being referenced). Now if we could just get
> Microsoft to recognize that with one kernel in the future, they ougth to
> eliminate 90% of NDIS, there is the possibility someone would add a
> chapter
> or two to an existing book to cover the rest.
>
> Don Burn
> Egenera, Inc
>
>
The current DDK contains NDIS documentation that is quite good. It has never
been so complete before. Miniports are very well documented. Even NDIS/WDM
miniports are discussed.
–
Udo Eberhardt
Thesycon GmbH, Germany
xxxxx@thesycon.de
www.thesycon.de
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of osmlist
Sent: Thursday, February 13, 2003 5:44 PM
To: NT Developers Interest List
Subject: [ntdev] Looking for a good networking device driver book
Hello,
Is there any body that can recommand on a networking device driver book ?
I’m planning to write a virual miniport NDIS device driver.
OS.
You are currently subscribed to ntdev as: xxxxx@thesycon.de
To unsubscribe send a blank email to xxxxx@lists.osr.com
xxxxx@acm.org wrote:
There are no networking device driver books, the market is too small.
That
being said, since you are talking a virtual miniport which implies
NDIS/WDM
the good news that you only need a few calls (My team just completed one
with
only 21 unique Ndis routines being referenced). Now if we could just get
Microsoft to recognize that with one kernel in the future, they ougth to
eliminate 90% of NDIS, there is the possibility someone would add a
chapter
or two to an existing book to cover the rest.
Amen. With WDM support in the 98/Me kernels, who needs all the kernel
wrappers that NDIS misimplements for 9x?
–
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Now teaming with John Hyde for USB Device Engineering Seminars
Check out our schedule at http://www.oneysoft.com
Oh but Walter, you aren’t thinking about all of the other platforms that
NDIS might run on someday 
I agree, totally. The myth of NDIS being platform independent, and that
buying the developer anything, is heavily running counter to the reality of
it only running on Windows systems and even there just getting in the way.
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
“Walter Oney” wrote in message news:xxxxx@ntdev…
>
> xxxxx@acm.org wrote:
> > There are no networking device driver books, the market is too small.
> > That
> > being said, since you are talking a virtual miniport which implies
> > NDIS/WDM
> > the good news that you only need a few calls (My team just completed one
> > with
> > only 21 unique Ndis routines being referenced). Now if we could just
get
> > Microsoft to recognize that with one kernel in the future, they ougth to
> > eliminate 90% of NDIS, there is the possibility someone would add a
> > chapter
> > or two to an existing book to cover the rest.
>
> Amen. With WDM support in the 98/Me kernels, who needs all the kernel
> wrappers that NDIS misimplements for 9x?
>
> –
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Now teaming with John Hyde for USB Device Engineering Seminars
> Check out our schedule at http://www.oneysoft.com
>
>
How about a couple of you NDIS gurus just writing such a book ? I’ll buy a
copy.
Alberto.
-----Original Message-----
From: Bill McKenzie [mailto:xxxxx@compuware.com]
Sent: Friday, February 14, 2003 9:44 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Looking for a good networking device driver book
Oh but Walter, you aren’t thinking about all of the other platforms that
NDIS might run on someday
I agree, totally. The myth of NDIS being platform independent, and that
buying the developer anything, is heavily running counter to the reality of
it only running on Windows systems and even there just getting in the way.
–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
“Walter Oney” wrote in message news:xxxxx@ntdev…
>
> xxxxx@acm.org wrote:
> > There are no networking device driver books, the market is too small.
> > That
> > being said, since you are talking a virtual miniport which implies
> > NDIS/WDM
> > the good news that you only need a few calls (My team just completed one
> > with
> > only 21 unique Ndis routines being referenced). Now if we could just
get
> > Microsoft to recognize that with one kernel in the future, they ougth to
> > eliminate 90% of NDIS, there is the possibility someone would add a
> > chapter
> > or two to an existing book to cover the rest.
>
> Amen. With WDM support in the 98/Me kernels, who needs all the kernel
> wrappers that NDIS misimplements for 9x?
>
> –
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Now teaming with John Hyde for USB Device Engineering Seminars
> Check out our schedule at http://www.oneysoft.com
>
>
—
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
> How about a couple of you NDIS gurus just writing such a book ? I’ll buy a
copy.
Alberto.
-----Original Message-----
From: Bill McKenzie [mailto:xxxxx@compuware.com]
Sent: Friday, February 14, 2003 9:44 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Looking for a good networking device driver bookOh but Walter, you aren’t thinking about all of the other platforms that
NDIS might run on somedayI agree, totally. The myth of NDIS being platform independent, and that
buying the developer anything, is heavily running counter to the reality of
it only running on Windows systems and even there just getting in the way.–
Bill McKenzie
Compuware Corporation
http://www.compuware.com/products/driverstudio/
Let’s see on a normal driver book like Walter’s you probably get 20,000
sales
at $2/book royalty thats $40,000 for over a years work, pretty poor wages.
Now something like NDIS will be more likely 5000 sales or $10,000, I
don’t see the profit in that.
As I pointer out in my post, the real problem here is that there is no
need for NDIS miniports as they presently are defined. This ought to be a
small helper library for a WDM driver, with almost none of the current
crap such as their own implementation of spinlocks present. This would do
a lot of good things:
-
Reduce the learning curve, if you know WDM a miniport would be a
straight forward extension. -
Force to Networking team at microsoft to concentrate on
performance and
reliability, not creating their own OS. -
Allow people like Walter to add a chapter to his book so NDIS is
covered. -
Make it easier to use the available Microsoft tools and
capabilities
with NDIS, and encourage people to create additional tools.
Note rumor is that NDIS 6.0 is incompatible with NDIS 5 and will of course
not be this thin wrapper, but instead its own bloated, over-engineered
mess.
Don Burn
Egenera, Inc
Good idea. But who should rewrite all the existing NDIS miniports?
–
Udo Eberhardt
Thesycon GmbH, Germany
xxxxx@thesycon.de
www.thesycon.de
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@acm.org
Sent: Friday, February 14, 2003 5:37 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Looking for a good networking device driver bookLet’s see on a normal driver book like Walter’s you probably get 20,000
sales
at $2/book royalty thats $40,000 for over a years work, pretty poor wages.
Now something like NDIS will be more likely 5000 sales or $10,000, I
don’t see the profit in that.As I pointer out in my post, the real problem here is that there is no
need for NDIS miniports as they presently are defined. This ought to be a
small helper library for a WDM driver, with almost none of the current
crap such as their own implementation of spinlocks present. This would do
a lot of good things:
Reduce the learning curve, if you know WDM a miniport would be a
straight forward extension.Force to Networking team at microsoft to concentrate on
performance and
reliability, not creating their own OS.Allow people like Walter to add a chapter to his book so NDIS is
covered.Make it easier to use the available Microsoft tools and
capabilities
with NDIS, and encourage people to create additional tools.Note rumor is that NDIS 6.0 is incompatible with NDIS 5 and will of course
not be this thin wrapper, but instead its own bloated, over-engineered
mess.Don Burn
Egenera, Inc
You are currently subscribed to ntdev as: xxxxx@thesycon.de
To unsubscribe send a blank email to xxxxx@lists.osr.com
If you look down in my post, you will see that the rumor out of Redmond is
that NDIS 6.0 is completely incompatible with current NDIS, so the
Microsoft newworking group is already planning to force the rewrite, so
wouldn’t be nice if they did something good this time.
Actually, I would take the approach of leaving NDIS alone, and adding this
as the new way to go, with a plan to phase out NDIS miniports, but then
that would be logical.
Don Burn
Egenera, Inc
Good idea. But who should rewrite all the existing NDIS miniports?
–
Udo Eberhardt
Thesycon GmbH, Germany
xxxxx@thesycon.de
www.thesycon.de> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@acm.org
> Sent: Friday, February 14, 2003 5:37 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Looking for a good networking device driver book
>=20
>=20
> Let’s see on a normal driver book like Walter’s you probably get =
20,000
> sales
> at $2/book royalty thats $40,000 for over a years work, pretty poor =
wages.
> Now something like NDIS will be more likely 5000 sales or $10,000, I
> don’t see the profit in that.
>=20
> As I pointer out in my post, the real problem here is that there is no
> need for NDIS miniports as they presently are defined. This ought to =
be a
> small helper library for a WDM driver, with almost none of the current
> crap such as their own implementation of spinlocks present. This =
would do
> a lot of good things:
>=20
> 1. Reduce the learning curve, if you know WDM a miniport would be =
a
> straight forward extension.
>=20
> 2. Force to Networking team at microsoft to concentrate on
> performance and
> reliability, not creating their own OS.
>=20
> 3. Allow people like Walter to add a chapter to his book so NDIS =
is=20
> covered.
>=20
> 4. Make it easier to use the available Microsoft tools and
> capabilities
> with NDIS, and encourage people to create additional tools.
>=20
> Note rumor is that NDIS 6.0 is incompatible with NDIS 5 and will of =
course
> not be this thin wrapper, but instead its own bloated, over-engineered
> mess.
>=20
> Don Burn
> Egenera, Inc
>=20
> —
> You are currently subscribed to ntdev as: xxxxx@thesycon.de
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>=20
>=20
OK, there are rumors…
But, wouldn’t be a new NDIS able to run older drivers, and only newly
developed drivers would be forced to be NDIS6-compliant (e.g. by WHQL)?
I don’t assume that MS will break existing drivers, especially for such
common devices like network cards. This would make acceptance of a new
Windows system problematic, or at least defer its success.
–
Udo Eberhardt
Thesycon GmbH, Germany
xxxxx@thesycon.de
www.thesycon.de
xxxxx@acm.org wrote:
If you look down in my post, you will see that the rumor out of Redmond is
that NDIS 6.0 is completely incompatible with current NDIS, so the
Microsoft newworking group is already planning to force the rewrite, so
wouldn’t be nice if they did something good this time.Actually, I would take the approach of leaving NDIS alone, and adding this
as the new way to go, with a plan to phase out NDIS miniports, but then
that would be logical.Don Burn
Egenera, Inc>Good idea. But who should rewrite all the existing NDIS miniports?
>
>–
>Udo Eberhardt
>Thesycon GmbH, Germany
>xxxxx@thesycon.de
>www.thesycon.de
>
>
>
>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com]On Behalf Of xxxxx@acm.org
>>Sent: Friday, February 14, 2003 5:37 PM
>>To: NT Developers Interest List
>>Subject: [ntdev] Re: Looking for a good networking device driver book
>>=20
>>=20
>>Let’s see on a normal driver book like Walter’s you probably get =
>
>20,000
>
>>sales
>>at $2/book royalty thats $40,000 for over a years work, pretty poor =
>
>wages.
>
>> Now something like NDIS will be more likely 5000 sales or $10,000, I
>>don’t see the profit in that.
>>=20
>>As I pointer out in my post, the real problem here is that there is no
>>need for NDIS miniports as they presently are defined. This ought to =
>
>be a
>
>>small helper library for a WDM driver, with almost none of the current
>>crap such as their own implementation of spinlocks present. This =
>
>would do
>
>>a lot of good things:
>>=20
>> 1. Reduce the learning curve, if you know WDM a miniport would be =
>
>a
>
>> straight forward extension.
>>=20
>> 2. Force to Networking team at microsoft to concentrate on
>>performance and
>> reliability, not creating their own OS.
>>=20
>> 3. Allow people like Walter to add a chapter to his book so NDIS =
>
>is=20
>
>> covered.
>>=20
>> 4. Make it easier to use the available Microsoft tools and
>>capabilities
>> with NDIS, and encourage people to create additional tools.
>>=20
>>Note rumor is that NDIS 6.0 is incompatible with NDIS 5 and will of =
>
>course
>
>>not be this thin wrapper, but instead its own bloated, over-engineered
>>mess.
>>=20
>>Don Burn
>>Egenera, Inc
>>=20
>>—
>>You are currently subscribed to ntdev as: xxxxx@thesycon.de
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>=20
>>=20
>
You are currently subscribed to ntdev as: xxxxx@thesycon.de
To unsubscribe send a blank email to xxxxx@lists.osr.com