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/


more on building NT4 drivers with Win2K DDK

OSR_Community_UserOSR_Community_User Member Posts: 110,217
I have isolated the problem I was having, but I'm somewhat afraid it
highlights either a bug in the DDK or a major misunderstanding on my part.

The problem is that when my driver links, it links with NTOSKRNL.LIB in
the Windows 2000 DDK (which I installed yesterday), and it pulls in
"_except_handler3" from this library. Unfortunately, this routine isn't
exported by NTOSKRNL.EXE on NT4.

To get the driver to build, I replaced the NTOSKRNL.LIB file in the
DDK\LIB directory with the one from the NT4 DDK. Now it works.

Did I really muck something up somewhere? It is possible that my build
environment is messed up. The wonderful Platform SDK and DDK installers
claim to detect if you have VC5 or VC6, but I think they don't do the
right thing if you actually have _BOTH_. I have to keep VC5 around for
something else, but I don't want it used.

Anyway, what's up with the "_except_handler3" being linked from
NTOSKRNL.EXE?

Thanks tons!

Rob

---------------------------------------------------------------------
Rob Newberry
Director of Fajita Technology
Group Logic, Inc.

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I'm really curious why you think it is at all legitimate to build an NT4
    driver using the W2K ddk? Wouldn't the NT4 ddk be a better choice? Am I
    missing something?

    > -----Original Message-----
    > From: Rob Newberry [mailto:[email protected]]
    > Sent: Thursday, February 24, 2000 10:48 AM
    > To: NT Developers Interest List
    > Subject: [ntdev] more on building NT4 drivers with Win2K DDK
    >
    >
    >
    > I have isolated the problem I was having, but I'm somewhat afraid it
    > highlights either a bug in the DDK or a major
    > misunderstanding on my part.
    >
    > The problem is that when my driver links, it links with
    > NTOSKRNL.LIB in
    > the Windows 2000 DDK (which I installed yesterday), and it pulls in
    > "_except_handler3" from this library. Unfortunately, this
    > routine isn't
    > exported by NTOSKRNL.EXE on NT4.
    >
    > To get the driver to build, I replaced the NTOSKRNL.LIB file in the
    > DDK\LIB directory with the one from the NT4 DDK. Now it works.
    >
    > Did I really muck something up somewhere? It is possible
    > that my build
    > environment is messed up. The wonderful Platform SDK and DDK
    > installers
    > claim to detect if you have VC5 or VC6, but I think they don't do the
    > right thing if you actually have _BOTH_. I have to keep VC5
    > around for
    > something else, but I don't want it used.
    >
    > Anyway, what's up with the "_except_handler3" being linked from
    > NTOSKRNL.EXE?
    >
    > Thanks tons!
    >
    > Rob
    >
    > ---------------------------------------------------------------------
    > Rob Newberry
    > Director of Fajita Technology
    > Group Logic, Inc.
    >
    >
    >
    > ---
    > You are currently subscribed to ntdev as: [email protected]
    > To unsubscribe send a blank email to $subst('Email.Unsub')
    >
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    The readme.html file in the root directory of the Windows 2000 DDK for
    Release Candidate 2 CD from MSDN clearly indicates that the windows 2000 DDK
    is only for drivers that will be loaded in Windows 2000. You still must use
    the Windows NT 4.0 DDK to build drivers which are targeted for Windows NT
    4.0 and miniport drivers for Windows 95/98.

    I cannot believe that much has changed from the Win 2000 release candidate
    DDK to the windows 2000 release DDK.

    Dominick

    ----- Original Message -----
    From: "Rob Newberry" <[email protected]>
    To: "NT Developers Interest List" <[email protected]>
    Sent: Thursday, February 24, 2000 10:48 AM
    Subject: [ntdev] more on building NT4 drivers with Win2K DDK


    >
    > I have isolated the problem I was having, but I'm somewhat afraid it
    > highlights either a bug in the DDK or a major misunderstanding on my part.
    >
    > The problem is that when my driver links, it links with NTOSKRNL.LIB in
    > the Windows 2000 DDK (which I installed yesterday), and it pulls in
    > "_except_handler3" from this library. Unfortunately, this routine isn't
    > exported by NTOSKRNL.EXE on NT4.
    >
    > To get the driver to build, I replaced the NTOSKRNL.LIB file in the
    > DDK\LIB directory with the one from the NT4 DDK. Now it works.
    >
    > Did I really muck something up somewhere? It is possible that my build
    > environment is messed up. The wonderful Platform SDK and DDK installers
    > claim to detect if you have VC5 or VC6, but I think they don't do the
    > right thing if you actually have _BOTH_. I have to keep VC5 around for
    > something else, but I don't want it used.
    >
    > Anyway, what's up with the "_except_handler3" being linked from
    > NTOSKRNL.EXE?
    >
    > Thanks tons!
    >
    > Rob
    >
    > ---------------------------------------------------------------------
    > Rob Newberry
    > Director of Fajita Technology
    > Group Logic, Inc.
    >
    >
    >
    > ---
    > 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. If you want to get involved, click one of these buttons!

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!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE