more on building NT4 drivers with Win2K DDK

NTDEV
1

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.

2

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:xxxxx@grouplogic.com]
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: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

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”
To: “NT Developers Interest List”
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: xxxxx@flashcom.net
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
>