Re: using ddkbuild.bat

I couldn't less this one pass. If you look at the directory tree in the
Server 2003 SP1 kit, the directories for that OS are still given as NET.
Why shouldn't you use the same? It actually makes sense. With the new WDK
you might have to use whatever MS is using as the define that controls OS
version to help us see the relationship. Should it be Longhorn or Vista or
whatever the Longhorn Server is renamed to be? Glad it is your headache.

I find that your website prints much better if you get the complete URL and
enter it instead of going thru the Resources link. I like to keep the
tutorial in a notebook for reference and the command line options too since
I taught how to use ddkbuild.bat last year to others in our company.

"Mark Roddy" <markr@xxxxxxxxxxxxxx> wrote in message
news:d0pli213butnnamkbbvpmttt3h70btm61s@xxxxxxxxxx
On Sun, 8 Oct 2006 17:50:02 -0700, mirage2k2
<mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Thanks Mark. I did read through the help but I didn't realise that
WNETBASE
and WNET had anything to do with w2k3. Now I'm using -WNETW2K and it
fine.



So what happens is that I adjust ddkbuild to work with early beta
releases of the DDK tied to early beta releases of the OS. Those
releases all use code names line Windows.Net or Longhorn or whatever.
Ddkbuild gets released with the code name built into the runtime
switches. Then as the OS and its related DDK move to public beta and
release status the real product name gets assigned (Windows 20003
Server, Windows Vista etc.) and suddenly the runtime switches make no
sense unless you were along for the ride. I can't actually change the
switch names as that breaks other people's build systems (and mine
too.) Oh well....

Mirage2k2

"Mark Roddy" wrote:

On Thu, 5 Oct 2006 20:19:01 -0700, mirage2k2
<mirage2k2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I'm using VS and ddkbuild.bat to build my driver. I call ddkbuild as
follows... ddkbuild -W2K checked. My driver gets built in
objchk_wnet_x86\i386. If I build the driver from the w2k checked build
environment it builds my driver in objchk_w2k_x86\i386. It looks like
ddkbuild is invoking a different ddk build environment. Is this a
problem
and what is wnet?


For the w2k3 ddk the correct syntax would be "ddkbuild -WNETW2K
checked ."

Try ddkbuild -h for more information about how to run it correctly.


=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP/2000 Consulting
Device and Filesystem Drivers
Hollis Technology Solutions 603-321-1032
www.hollistech.com



=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP/2000 Consulting
Device and Filesystem Drivers
Hollis Technology Solutions 603-321-1032
www.hollistech.com


.

Relevant Pages

  • Re: Passthru Driver Problem
    ... > i have built a Passthru driver available with Windows DDK 3790 on windows ... > i am making a Free Build release version for windows 2003 Server. ... The PassThru sample from the Windows Server 2003 DDK is better than the ...
    (microsoft.public.development.device.drivers)
  • Re: using ddkbuild.bat
    ... So what happens is that I adjust ddkbuild to work with early beta ... releases of the DDK tied to early beta releases of the OS. ... Windows Vista etc.) and suddenly the runtime switches make no ... If I build the driver from the w2k checked build ...
    (microsoft.public.development.device.drivers)
  • Re: using ddkbuild.bat
    ... If I build the driver from the w2k checked build ... ddkbuild is invoking a different ddk build environment. ... For the w2k3 ddk the correct syntax would be "ddkbuild -WNETW2K ...
    (microsoft.public.development.device.drivers)
  • Re: Driver Development Environment (Olney Says, "VC 6.0")
    ... I'm not familiar with KDMF, but for quite some time now, the DDK has come ... If you want to use an IDE, grab a copy of Mark Roddy's DDKBUILD batch file ... That way, the driver is built ...
    (microsoft.public.development.device.drivers)
  • Re: Platform compatibility
    ... Maxim Shatskih, Windows DDK MVP ... > I have a driver for Server 2003 that now needs to be compatibile with 2K. ... > The driver uses some features that are not included in the 2K DDK such as the ...
    (microsoft.public.development.device.drivers)
Loading