Re: DDKBuild ISSUE with WINDDK...
From: Mark Roddy (markr_at_hollistech.com)
Date: 10/10/04
- Previous message: Matthew Gillespie: "bulkusb.sys returns error 0xc0000005"
- In reply to: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Next in thread: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Reply: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 10 Oct 2004 16:22:11 -0400
In article <eZVLsSYrEHA.3988@tk2msftngp13.phx.gbl>, hpotter@azkabar.com says...
> ohh... I read the help file and it says
> -WNET indicates development system uses WNETBASE environment variable to
> locate the .Net ddk and builds .net binaries (optional)
> -WNETW2K indicates development system uses the WNETBASE environment variable
> to locate the .Net ddk and builds W2K binaries (optional.)
>
>
> I don't have .NET env in my computer..... could this be the reason??? As I
> mention I'm running VC++ 6.0 on Windows 2000... therefore mybe I should
> still be using NTDDK (Windows 2000 DDK) not the WINDDK (windows server
> 20003DDK)?
>
No that is not relevant. Windows 2003 Server was originally named Windows .Net
Server, and ddkbuild reflects that naming convention. You do not need the .net
versions of visual studio. VS6 works just fine. In fact you do not need VS at
all as ddkbuild works from the command line.
If you would include the complete output from ddkbuild with the -debug flag set
I might have a chance of diagnosing the problem. Giving me the 'last line' is
not much help.
> what do you think?
> Thanks
>
> "Harry Potter" <hpotter@azkabar.com> wrote in message
> news:Oxeez1WrEHA.324@TK2MSFTNGP11.phx.gbl...
> > huuummmm I did what you suggested and yet nothing..... here is what I have
> > Env variable is set to:
> > WNETBASE C:\WINDDK
> > Build command line: ddkbuild -debug -WNETW2K checked .
> > Rebuild all options: /a
> > Output file name: passthru.sys
> > Browse info file name: passthru.bsc
> >
> > I also tried
> > Build command line: ddkbuild -debug -h -WNETW2k checked .
> > which invoke the help file
> >
> > and here is the last line I'm getting
> > C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>goto
> > :EOF
> > C:\d\Code\C Projects\TDI-NDIS\PCADev\NdisIM\PassThruEx\Part1\driver>goto
> > :EOF
> >
> > Passthru.sys - 0 error(s), 0 warning(s)
> >
> > Any thoughts?
> > Would appreciate your help.
> >
> >
> > > Try ddkbuild -h
> > >
> > > this either will produce the help file for your version of ddkbuild, or
> > you
> > > have a very old version and you should download the latest version.
> > >
> > > For the w2k3 ddk you should use the -WNET* target options and you should
> > set
> > > WNETBASE in order to locate the ddk. For example, to build a checked w2k
> > driver
> > > using the w2k3 ddk and ddkbuild use "ddkbuild -WNETW2K checked .".
> > >
> > > If all else fails, try adding the "-debug" flag as the first argument to
> > > ddkbuild.
> > >
> > > If and when the DDK organization and build syntax stops changing I can
> > stop
> > > having "50 ways to build your driver" incorporated into ddkbuild :-)
> > > --
> > >
> > > =====================
> > > Mark Roddy DDK MVP
> > > Windows 2003/XP/2000 Consulting
> > > Hollis Technology Solutions 603-321-1032
> > > www.hollistech.com
> > > markr@hollistech.com
> >
> >
> > "Mark Roddy" <markr@hollistech.com> wrote in message
> > news:MPG.1bcfa80b791def459896b7@news.microsoft.com...
> > > In article <el#zniLrEHA.452@TK2MSFTNGP09.phx.gbl>, hpotter@azkabar.com
> > says...
> > > >
> > > > Hi Mark/All,
> > > >
> > > > My Dev Env is:
> > > > Windows2000 + VC++ 6.0 + Latest DDKBuild + WINDDK (windows server 2003
> > ddk)
> > > > Env variable is set to:
> > > > W2KBASE C:\WINDDK
> > > >
> > > > when I create the project as it's been suggested by MARK at his
> website
> > > > www.hollistech.com
> > > > I get a directory called "objchk_wnet_x86" under my source directory
> > which
> > > > contains all the .sys, .pdb and others.... (this is right after
> creating
> > the
> > > > project and build it for the first time)
> > > > then I make the change to let say one or multiple of .c files and do
> the
> > > > build again.... build goes through with no error.... then I look at my
> > .sys
> > > > file under the "objchk_wnet_x86" and I'll see that it hasn't been
> > updated...
> > > > the creation time is still the old one.!!!!!! why? then I delete the
> log
> > > > file and all the old file and do the build again and guess what... It
> > > > doesn't generate any of the outputs??!!! what is happening
> > > > here is what i have under the project setting
> > > > Build command line: ddkbuild -debug -W2k checked .
> > > > Rebuild all options: /a
> > > > Output file name: passthru.sys
> > > > Browse info file name: passthru.bsc
> > > >
> > > >
> > > > the system works (regenerates and updates the outputs) if I unistall
> the
> > > > WINDDK and install NTDDK (Windows 2000 DDK) with the following setup
> > > > My Dev Env is:
> > > > Windows2000 + VC++ 6.0 + Latest DDKBuild + NTDDK (windows 2000 ddk)
> > > > Env variable is set to:
> > > > W2KBASE C:\NTDDK
> > > > Build command line: ddkbuild -debug -W2k checked .
> > > > Rebuild all options: /a
> > > > Output file name: passthru.sys
> > > > Browse info file name: passthru.bsc
> > > >
> > > > Do I need to make any change in source/make file? do I have to set
> > certain
> > > > option under the IDE??
> > > >
> > > > Would appreciate your help.
> > > >
> > > >
> > > >
> > > >
> > > > In article <usHcez$pEHA.3668@TK2MSFTNGP15.phx.gbl>,
> hpotter@azkabar.com
> > > > says...
> > > > > indeed.... I learned my lesson:( and that's the difference between
> > newbie
> > > > > and others the expensive lessons
> > > > >
> > > > >
> > > > > Mark you seems to be the genius behind the DDK build tool... got a
> > > > question,
> > > > > does your ddk build work with windows server 2003 ddk installed over
> > > > windows
> > > > > 2000 pro??? I had NTDDK on windows 2000 and using VC++ 6.0 and the
> > build
> > > > was
> > > > > working fine... then I've been told to use Windows server 2003 DDK
> > since
> > > > it
> > > > > includes all the subset but then your DDK build tool wasn't
> working...
> > I
> > > > > changed the even value to be C:\WINDDK but yet wasn't working.....
> > > > > Any feedbacks???
> > > > >
> > > >
> > > > DDKBUILD works just fine with all of the released supported DDKs, plus
> > the
> > > > last
> > > > publicly released longhorn DDK, plus the w2k3 sp1 beta ddk. (WDF
> support
> > > > coming
> > > > soon.) What exactly do you mean by not working?
> > > >
> > > > Also try running "ddkbuild -h" as that will pop up the man page for
> the
> > > > script.
> > > > You do have to set an environment variable correctly along with the
> > correct
> > > > command line options to indicate which ddk you are using and where it
> is
> > > > located.
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>
-- ===================== Mark Roddy DDK MVP Windows 2003/XP/2000 Consulting Hollis Technology Solutions 603-321-1032 www.hollistech.com markr@hollistech.com
- Previous message: Matthew Gillespie: "bulkusb.sys returns error 0xc0000005"
- In reply to: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Next in thread: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Reply: Harry Potter: "Re: DDKBuild ISSUE with WINDDK..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|