DDK e100bex sample

I was just wondering about porting miniport drivers from NDIS 5.X to
NDIS 6.0.

I noticed that the e100bex source code in the DDK version 6000 has a 5x
and a 60 directory. Is this because NDIS 6.0 has made so many changes
to the driver IF that it is too messy to single-source the code?

I also noticed that the ndisprot and mux sample drivers are organized in
the same way, thus giving more weight to the idea that single-sourcing
NDIS 5.x and 6.0 drivers is not good for your health.

I've read through the porting doc in the DDK and agree that this would
be a difficult task, but I was wondering if anybody had ever tried it.

Any thoughts?

((&->

Of course you can write the same code for NDIS 5 and NDIS 6 if you are just
desperate to prove that it can be done. However, in practical terms, it seems
to be just unreasonable approach, and your chance of staying frieds with
people who have to reuse (maintain) your code is critically close to zero -
imagine the number of '#ifdef' blocks in your code...

Anton Bassov




"QuasiCodo" wrote:

> I was just wondering about porting miniport drivers from NDIS 5.X to
> NDIS 6.0.
>
> I noticed that the e100bex source code in the DDK version 6000 has a 5x
> and a 60 directory. Is this because NDIS 6.0 has made so many changes
> to the driver IF that it is too messy to single-source the code?
>
> I also noticed that the ndisprot and mux sample drivers are organized in
> the same way, thus giving more weight to the idea that single-sourcing
> NDIS 5.x and 6.0 drivers is not good for your health.
>
> I've read through the porting doc in the DDK and agree that this would
> be a difficult task, but I was wondering if anybody had ever tried it.
>
> Any thoughts?
>
> ((&->
>