Hi,

I'm a driver newbie and I'd really appreciate it if someone could clarify
this simple question for me:

I am porting a custom driver from a w2k/xp to w2k3 server. The driver was
originally built with the 2000 ddk. From what I understand, I should be
using the w2k3 server sp1 ddk to develop/port/rebuild this driver for the
w2k3 server platform. However, what *build* environment should i be using?
Should I use the new ddk, but still target the w2k platform? Should I build a
new driver for each platform, using the new ddk? I have taken over this
project and the last developer claims that this driver is WDM compliant. Does
that mean that it is source code compatible across platforms, or are the
binaries compatible too?

Again, some clarification on these 'basics' would really really be
appreciated....
I'm confused!

Thanks!

PJS

Use the latest DDK, and target Windows 2000. Yes your code should be source
and binary compatible across platforms. There are things that have been
added to XP and 2003, but I presume you would wish to have one binary for
all systems. Definitely, run PreFast and clean up the driver. You should
have your driver run clean with Driver Verifier and the checked build on a
multi-processor (or hyperthreaded) system.

Take a look at
http://www.microsoft.com/whdc/driver...Dev_Intro.mspx for a more
detailed explanation of this stuff.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply



"pjs" <pjs@discussions.microsoft.com> wrote in message
news:7048B76C-AC50-4AB6-8C84-1A0DB127BFC4@microsoft.com...

This is a good idea, it gives you the single binary for all Windows from w2k
up. The drawback is that you cannot use the APIs which are newer then w2k.

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