David
Wed Jul 02 19:31:33 CDT 2003
I think you haven't been reading the HTM files correctly. Go back and
reread them. They say use the Windows Server 2003 check build environment
and don't even mention the Windows 2000 environment. Many of the samples do
not work with 2000. Your earlier question did mention the prefast
directory, so I didn't make a mistake. As a general rule, I don't build the
entire DDK, as I find it too slow and not very useful. I do load the entire
DDK and those drivers or samples I want to examine I will copy to a work
directory and compile them.
"Just E" <just.e@eudoramail.com> wrote in message
news:457e01c340f1$c2900420$a601280a@phx.gbl...
> David,
>
> Thanks for that information. I'm installing from the
> May'03 MSDN DDK DVD and it contains no top-level README nor
> are there any README files within the DDK subdirectories
> (win2003 or XP). At the risk of taking more of your time,
> on what media and where do you find this README? I've read
> all the installation documentation that seems appropriate
> within the DDK directories yet it seems you have more
> pertinent information. I'm not sure what you mean
> regarding "modifying the app" and the IFS package (which I
> have no intention of installing at this time).
>
> On my media there does exist a "prefast_install.htm"
> document that mentions something similar (but different) to
> what you are mentioning:
>
> "To see what PREfast does and how it works, see the
> examples in the %PREFAST_ROOT%\examples\ directory. Go to
> that directory in a DDK build environment and type prefast
> build -cZ. Press ENTER, and then type prefast view. This
> reports 33 defects. (The errors from the compiler are
> intended.)"
>
> Since I am not in %PREFAST_ROOT% to build the examples,
> this does not seem appropriate.
>
> I'll attempt your suggestion regardless later tonight and
> update this thread when I have feedback to provide.
>
> Thanks again.
>
> >-----Original Message-----
> >The README says "prefast build -cZ". Rather simple. The
> latest DDK doesn't
> >mention modifying the app, but the XP SP1 IFSKit does.
> >
> >"Just E" <just.e@eudoramail.com> wrote in message
> >news:01af01c340cf$119c4dd0$a501280a@phx.gbl...
> >> Could you please be more specific? I've read both the
> >> relnote.htm and install.htm; both files indicate
> >> post-installation verification can be done by opening the
> >> appropriate command build environment command window and
> >> executing "build -cZ". I've not found any other command
> >> that is to be run prior to "build -cZ" listed as part of
> >> the install and verification procedure.
> >>
> >> From relnote.htm:
> >> "The result is that the correct set of drivers is always
> >> built when a command window is started for a given build
> >> environment, and the build -cZ command is issued from the
> >> DDK's base directory."
> >>
> >> From install.htm, Verifying DDK Installation, Item 2:
> >> "In the command window, type the command build -cZ. This
> >> command compiles and links the complete set of installed
> >> sources. This can take more than 30 minutes to complete,
> >> depending on which DDK components are installed and the
> >> system on which the build is being performed."
> >>
> >> So, could you please clarify what you believe I should be
> >> doing?
> >>
> >> E
> >>
> >>
> >> >-----Original Message-----
> >> >Read the readme. Wrong command.
> >> >
> >> >"Just E" <just.e@eudoramail.com> wrote in message
> >> >news:0b2001c340ac$3aadb100$a501280a@phx.gbl...
> >> >> Hello Eliyas,
> >> >>
> >> >> As per your suggestion I did a full uninstall, purged the
> >> >> install directory and re-installed the 2003 DDK
> preserving
> >> >> all default component selections for install (plus I
> added
> >> >> the "Illustrative Driver Examples"). The same errors
> >> >> occur. There are no product incompatibilities listed for
> >> >> the DDK, but I really have to wonder at this point.
> >> >> Following is some of the output from the build process--
> >> >> any further suggestions are greatly appreciated.
> >> >>
> >> >> Output:
> >> >> C:\WINDDK\3790>build -cZ
> >> >> ...
> >> >> BUILD: Examining c:\winddk\3790 directory tree for files
> >> >> to compile.
> >> >> BUILD:
> c:\winddk\3790\bin\x86\prefast\examples\sources(8):
> >> >> Unsupported TARGETTYPE value - LIB
> >> >> ...
> >> >> BUILD: Compiling c:\winddk\3790\src\set\pnpports
> directory
> >> >> ...
> >> >> BUILD: Linking c:\winddk\3790\src\setup\pnpports
> directory
> >> >> BUILD: Done
> >> >>
> >> >> <In buildchk_wnet_x86.log>
> >> >> ...
> >> >> Linking c:\winddk\3790\src\setup\pnpports directory
> >> >> ************
> >> >> 'nmake.exe /c BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1
> >> >> NTTEST= UMTEST= MAKEDLL=1 386=1'
> >> >> Bad command or file name
> >> >>
> >> >> Thanks in advance for any further assistance.
> >> >>
> >> >> >-----Original Message-----
> >> >> >I have a feeling that you didn't install the build
> >> >> environment properly.
> >> >> >There is a good chance that you might have unchecked
> >> >> something in the custom
> >> >> >install dialog. I would reinstall the kit and see if the
> >> >> problem persists.
> >> >> >
> >> >> >--
> >> >> >-Eliyas
> >> >> >This posting is provided "AS IS" with no warranties, and
> >> >> confers no rights.
> >> >> >
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >