Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


ndis support for deserialized miniport in nt4.0

OSR_Community_UserOSR_Community_User Member Posts: 110,217
Hi all,
Does anyone know where I can current (sp5/sp6) versions of ndis.h and
ndis.lib that support the deserialized miniport model?

It really annoys me to read statements like this from knowledge base article
Q214455 and then have them not follow up with support for it in the ddk.

"Microsoft has determined that the performance penalties incurred in
an Ndis Intermediate driver are unacceptable, and has abandoned the
Intermediate model. All development in this area should follow the
Ndis Deserialized model."

Thanks in advance,
Toby

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Toby,

    I believe you can use SP3 version for SP5/6. Necessary ndis.h can be found
    in ImSamp example; it is somewhere on ms web. I don't know where is ndis.lib
    but you can create it for yourself. If I remember it correctly (sorry, it is
    almost three years), I created a dummy C file containing all exported
    ndis.sys functions (empty) with correct number of DWORD paremeters + .def
    file with all these function names. It must contain NAME NDIS.SYS header.
    Compiling it like an exe or dll correct lib should be created.

    Alternatively you could use ndis.lib from w2k DKK. I haven't tried it but it
    should be safe if only NT4 (NDIS4) functions are used.

    BTW, they are right, original IM driver model was really bad idea. The sad
    thing is that they recognized it long time after NT4 and DDK release when
    tried to use it for the first time (ImSamp).

    Michal

    Best regards,

    Michal Vodicka
    RKK Informationssysteme s.r.o.
    :We support your Future
    [WWW: http://www.rkk.cz , http://www.skytale.com]

    > ----------
    > From: Toby Ball[SMTP:[email protected]]
    > Reply To: NT Developers Interest List
    > Sent: Thursday, March 30, 2000 3:53 PM
    > To: NT Developers Interest List
    > Subject: [ntdev] ndis support for deserialized miniport in nt4.0
    >
    > Hi all,
    > Does anyone know where I can current (sp5/sp6) versions of ndis.h and
    > ndis.lib that support the deserialized miniport model?
    >
    > It really annoys me to read statements like this from knowledge base
    > article
    > Q214455 and then have them not follow up with support for it in the ddk.
    >
    > "Microsoft has determined that the performance penalties incurred in
    > an Ndis Intermediate driver are unacceptable, and has abandoned the
    > Intermediate model. All development in this area should follow the
    > Ndis Deserialized model."
    >
    > Thanks in advance,
    > Toby
    >
    >
    > ---
    > You are currently subscribed to ntdev as: [email protected]
    > To unsubscribe send a blank email to $subst('Email.Unsub')
    >
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online
Writing WDF Drivers 12 September 2022 Live, Online