Building NT4 code under new Win2k DDK

We have a kernel mode driver that we build using the old NT4 sp6 DDK. Is
there a way we can build the driver using the Win2k DDK and have the driver
still work on NT4 SP6? We are not calling any new functions just building
the same sources we use in NT4 environment. Is there a switch in the Win2k
DDK we can use or are we doomed to using the NT4 DDK.

I am not sure I can sell development on building multiple versions of the
driver.

Yes you can build an NT4 driver using the 2000 DDK. However, you open
yourself to a dozen subtle bugs that you probably do not want to deal with
and all of them related to a driver compiled for the 2000 DDK and running
under NT4. Simply put … I wouldn’t waste the time debugging a myriad of
problems discussed here many times when your best option is to port the
driver to WDM.


Gary G. Little
Seagate Technologies, LLC

“Joe Stivaletta” wrote in message news:xxxxx@ntdev…
> We have a kernel mode driver that we build using the old NT4 sp6 DDK. Is
> there a way we can build the driver using the Win2k DDK and have the
driver
> still work on NT4 SP6? We are not calling any new functions just building
> the same sources we use in NT4 environment. Is there a switch in the
Win2k
> DDK we can use or are we doomed to using the NT4 DDK.
>
> I am not sure I can sell development on building multiple versions of the
> driver.
>
>
>

Well, WDM is not really an option if you only intend the driver to run on
NT4.


Gary G. Little
Seagate Technologies, LLC

“Gary G. Little” wrote in message
news:xxxxx@ntdev…
> Yes you can build an NT4 driver using the 2000 DDK. However, you open
> yourself to a dozen subtle bugs that you probably do not want to deal with
> and all of them related to a driver compiled for the 2000 DDK and running
> under NT4. Simply put … I wouldn’t waste the time debugging a myriad of
> problems discussed here many times when your best option is to port the
> driver to WDM.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
> “Joe Stivaletta” wrote in message
news:xxxxx@ntdev…
> > We have a kernel mode driver that we build using the old NT4 sp6 DDK.
Is
> > there a way we can build the driver using the Win2k DDK and have the
> driver
> > still work on NT4 SP6? We are not calling any new functions just
building
> > the same sources we use in NT4 environment. Is there a switch in the
> Win2k
> > DDK we can use or are we doomed to using the NT4 DDK.
> >
> > I am not sure I can sell development on building multiple versions of
the
> > driver.
> >
> >
> >
>
>
>

The driver we build is used on all versions of NT4sp6, Win 2000, WinXP and
Win Server 2003 currently. I guess we are stuck with the NT4 sp DDK. We
can still use driver verifier but I guess CUV is out as well as any other
tool dependent on the newer DDKs. Maybe I will suggest using conditionals
in sources and wherever else we need to allow us to build the same sources
in the latest DDK for development and test versions and the old NT4 DDK for
customer release.

“Gary G. Little” wrote in message
news:xxxxx@ntdev…
> Well, WDM is not really an option if you only intend the driver to run on
> NT4.
>
> –
> Gary G. Little
> Seagate Technologies, LLC
>
> “Gary G. Little” wrote in message
> news:xxxxx@ntdev…
> > Yes you can build an NT4 driver using the 2000 DDK. However, you open
> > yourself to a dozen subtle bugs that you probably do not want to deal
with
> > and all of them related to a driver compiled for the 2000 DDK and
running
> > under NT4. Simply put … I wouldn’t waste the time debugging a myriad
of
> > problems discussed here many times when your best option is to port the
> > driver to WDM.
> >
> > –
> > Gary G. Little
> > Seagate Technologies, LLC
> >
> > “Joe Stivaletta” wrote in message
> news:xxxxx@ntdev…
> > > We have a kernel mode driver that we build using the old NT4 sp6 DDK.
> Is
> > > there a way we can build the driver using the Win2k DDK and have the
> > driver
> > > still work on NT4 SP6? We are not calling any new functions just
> building
> > > the same sources we use in NT4 environment. Is there a switch in the
> > Win2k
> > > DDK we can use or are we doomed to using the NT4 DDK.
> > >
> > > I am not sure I can sell development on building multiple versions of
> the
> > > driver.
> > >
> > >
> > >
> >
> >
> >
>
>
>

Why “doomed”?

I still build the very major and important piece of code using NT4 DDK
only. I have some definitions copied from the w2k DDK headers though.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Joe Stivaletta”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Tuesday, June 22, 2004 10:21 PM
Subject: [ntdev] Building NT4 code under new Win2k DDK

> We have a kernel mode driver that we build using the old NT4 sp6 DDK. Is
> there a way we can build the driver using the Win2k DDK and have the driver
> still work on NT4 SP6? We are not calling any new functions just building
> the same sources we use in NT4 environment. Is there a switch in the Win2k
> DDK we can use or are we doomed to using the NT4 DDK.
>
> I am not sure I can sell development on building multiple versions of the
> driver.
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

“Doomed” in the sense that I cannot easily use the CUV with the code that
currently uses the NT4 DDK. Maybe that is not such a loss.

“Maxim S. Shatskih” wrote in message
news:xxxxx@ntdev…
> Why “doomed”?
>
> I still build the very major and important piece of code using NT4 DDK
> only. I have some definitions copied from the w2k DDK headers though.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> ----- Original Message -----
> From: “Joe Stivaletta”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Tuesday, June 22, 2004 10:21 PM
> Subject: [ntdev] Building NT4 code under new Win2k DDK
>
>
> > We have a kernel mode driver that we build using the old NT4 sp6 DDK.
Is
> > there a way we can build the driver using the Win2k DDK and have the
driver
> > still work on NT4 SP6? We are not calling any new functions just
building
> > the same sources we use in NT4 environment. Is there a switch in the
Win2k
> > DDK we can use or are we doomed to using the NT4 DDK.
> >
> > I am not sure I can sell development on building multiple versions of
the
> > driver.
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

If you do not link to unexistant routines, then everything must be OK.
Except SEH. Check this article http://htfv.vba.com.by/articles/nt4ddk.asp

–htfv

“Joe Stivaletta” wrote in message news:xxxxx@ntdev…
> We have a kernel mode driver that we build using the old NT4 sp6 DDK. Is
> there a way we can build the driver using the Win2k DDK and have the
driver
> still work on NT4 SP6? We are not calling any new functions just building
> the same sources we use in NT4 environment. Is there a switch in the
Win2k
> DDK we can use or are we doomed to using the NT4 DDK.
>
> I am not sure I can sell development on building multiple versions of the
> driver.
>
>
>

I am not able to access that article.

“Alexey Logachyov” wrote in message news:xxxxx@ntdev…
> If you do not link to unexistant routines, then everything must be OK.
> Except SEH. Check this article http://htfv.vba.com.by/articles/nt4ddk.asp
>
> --htfv
>
>
>
> “Joe Stivaletta” wrote in message
news:xxxxx@ntdev…
> > We have a kernel mode driver that we build using the old NT4 sp6 DDK.
Is
> > there a way we can build the driver using the Win2k DDK and have the
> driver
> > still work on NT4 SP6? We are not calling any new functions just
building
> > the same sources we use in NT4 environment. Is there a switch in the
> Win2k
> > DDK we can use or are we doomed to using the NT4 DDK.
> >
> > I am not sure I can sell development on building multiple versions of
the
> > driver.
> >
> >
> >
>
>
>