Hollistech DDKBUILD problem

OSR_Community_User · April 4, 2008, 6:29am

Hi,

I have configured Hollistech DDKBUILD for use with visual studio V6 and the
build option of
“c:\ddkbuild\ddkbuild -WNETXP checked .” works fine. However, when I try to
rebuild which uses the option “c:\ddkbuild\ddkbuild -WNETXP checked . -cZ” I
get errors reported as follows.

Deleting intermediate files and output files for project ‘PCPS0000 - Win32
Debug’.
--------------------Configuration: PCPS0000 - Win32
Debug--------------------
DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
Comments? Suggestions? xxxxx@hollistech.com
DDKBUILD using NET DDK in directory .
for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
commandline: " build -e -MI c:\ddkbuild\ddkbuild -WNETXP checked . -cZ "
XmlLog::File::CopyXslFile(): Unable to copy the XML Style Sheet.
C:\WinDDK\6001.18000\bin\x86\build.xsl => .\build.xsl. Error: 0x00000002
SetFileAttributeW(.\build.xsl) failed. Error: 0x00000002
BUILD: Compile and Link for x86
.
.

All the files compile OK and the driver file is generated as expected. The
problem appears to be regarding the file
“C:\WinDDK\6001.18000\bin\x86\build.xsl” which is not actually present.

I have noticed that if I use “c:\ddkbuild\ddkbuild -WNET checked . -cZ”
instead I do not get the error. Should I being -WNETXP given that I want a
Windows XP driver?

Regards FarmerJo

OSR_Community_User · April 4, 2008, 6:45am

FarmerJo wrote:

Mr. Jo,

I don’t know what is causing this error; I use the WDK build tools
personally. In your last
thread you posted a few minutes ago, you asked a question that goes to
the heart of this issue.

You asked, “What is the advantage of using DDKBUILD over BUILD?”.

My first thought was, “none really, kinda depends on what works for
you”. With that said,
obviously this method DOES NOT work for you (at least not right now).
Editing your code
in VS is fine, but spending all your time trying to bypass the default
build method only to return
to it programically is a waste of time.

Kinda reminds me of that Elvis song titled, “A Little Less
Conversation and a Little More Action”

Best Wishes,

Matt

Hi,

I have configured Hollistech DDKBUILD for use with visual studio V6 and the
build option of
“c:\ddkbuild\ddkbuild -WNETXP checked .” works fine. However, when I try to
rebuild which uses the option “c:\ddkbuild\ddkbuild -WNETXP checked . -cZ” I
get errors reported as follows.

Deleting intermediate files and output files for project ‘PCPS0000 - Win32
Debug’.
--------------------Configuration: PCPS0000 - Win32
Debug--------------------
DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
Comments? Suggestions? xxxxx@hollistech.com
DDKBUILD using NET DDK in directory .
for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
commandline: " build -e -MI c:\ddkbuild\ddkbuild -WNETXP checked . -cZ "
XmlLog::File::CopyXslFile(): Unable to copy the XML Style Sheet.
C:\WinDDK\6001.18000\bin\x86\build.xsl => .\build.xsl. Error: 0x00000002
SetFileAttributeW(.\build.xsl) failed. Error: 0x00000002
BUILD: Compile and Link for x86
.
.

All the files compile OK and the driver file is generated as expected. The
problem appears to be regarding the file
“C:\WinDDK\6001.18000\bin\x86\build.xsl” which is not actually present.

I have noticed that if I use “c:\ddkbuild\ddkbuild -WNET checked . -cZ”
instead I do not get the error. Should I being -WNETXP given that I want a
Windows XP driver?

Regards FarmerJo

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · April 4, 2008, 7:22am

Does anyone use the standard build.bat file with visual studio? If so could
you tell me how to configure a visual studio project? I am usnig V6 of VS
and run windows XP.

FarmerJo

David_R_Cattley · April 4, 2008, 8:13am

Build is not a ‘batch’ file. It is BUILD.EXE. It requires a number of
environment variables be setup by the SETENV.BAT batch file which is
specific to each WDK (DDK).

DDKBUILD.BAT is the best way to make this work. You can always write your
own but why? You will essentially be duplicating DDKBUILD.

-dave

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of FarmerJo
Sent: Friday, April 04, 2008 7:25 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Hollistech DDKBUILD problem

Does anyone use the standard build.bat file with visual studio? If so could
you tell me how to configure a visual studio project? I am usnig V6 of VS
and run windows XP.

FarmerJo

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · April 4, 2008, 9:40am

Create/set an environment variable like

WHLBASE=C:\WinDDK\6001.18000

Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat
Create a new “Makefile” project in VC6.
In “Project Settings” -> Genral -> “Build command line” replace the
content by

ddkbuild -WLHXP checked .

for “Win32 Debug” build and by

ddkbuild -WLHXP free .

for “Win32 Release” build. Do not miss a . (dot) at the end of both lines!
It points to the current directory!

You may also replace “Output file name” by yourDrvr.sys.

[Later You will probably want to add in-IDE browsing capabilities.]

Copy all relevant source and header files into this newly created
directory (simplest case assumed here), the one where you should have a DSP
file by now. Make sure that the “sources” file is in it also.
Build the project in debug mode.

You get \objchk_wxp_x86\i386\echo.sys.

In the IDE’s output window You get something like (echo is the driver’s
name):

--------------------Configuration: echo - Win32 Debug--------------------
DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
Comments? Suggestions? xxxxx@hollistech.com
DDKBUILD using WLH DDK in directory .
for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
commandline: " build -e -MI "
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\6001.18000\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Start time: Fri Apr 04 09:29:28 2008
BUILD: Examining c:\projects\echo directory for files to compile.
c:\projects\echo
BUILD: Saving c:\winddk\6001.18000\build.dat…
BUILD: Compiling c:\projects\echo directory
_NT_TARGET_VERSION SET TO WINXP
BUILD: Linking for c:!projectsone_now_c\echo directory
_NT_TARGET_VERSION SET TO WINXP
BUILD: Finish time: Fri Apr 04 09:29:30 2008
BUILD: Done
=============== build warnings ======================

build complete status 0

echo.sys - 0 error(s), 0 warning(s)

That’s it.

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-319920-
> xxxxx@lists.osr.com] On Behalf Of FarmerJo
> Sent: Friday, April 04, 2008 7:25 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Hollistech DDKBUILD problem
>
> Does anyone use the standard build.bat file with visual studio? If so
> could
> you tell me how to configure a visual studio project? I am usnig V6 of
> VS
> and run windows XP.
>
> FarmerJo
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Mark_Roddy · April 4, 2008, 10:11am

Unless I have a typo in ddkbuild.bat (and that would not be the frist
tmie) that step one action ought to be “WLHBASE=” rather than “WHLBASE=”,
other than that this is the correct answer.

The OP’s problem was that he was pointing ddkbuild at the WDK for Vista
Sp1 and telling ddkbuild that it was the W2K3 DDK.: ":\ddkbuild\ddkbuild
-WNETXP checked " The various released ddks have their singularities
oddities and peculiarities that ddkbuild tries to smooth over but needs an
initial clue to get right.

On Fri, Apr 4, 2008 at 9:39 AM, Alex Shvedov wrote:

> 1. Create/set an environment variable like
>
> WHLBASE=C:\WinDDK\6001.18000
>
> 2. Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat
>
> 3. Create a new “Makefile” project in VC6.
>
> 4. In “Project Settings” -> Genral -> “Build command line” replace the
> content by
>
> ddkbuild -WLHXP checked .
>
> for “Win32 Debug” build and by
>
> ddkbuild -WLHXP free .
>
> for “Win32 Release” build. Do not miss a . (dot) at the end of both lines!
> It points to the current directory!
>
> You may also replace “Output file name” by yourDrvr.sys.
>
> [Later You will probably want to add in-IDE browsing capabilities.]
>
> 5. Copy all relevant source and header files into this newly created
> directory (simplest case assumed here), the one where you should have a
> DSP
> file by now. Make sure that the “sources” file is in it also.
>
> 6. Build the project in debug mode.
>
> You get \objchk_wxp_x86\i386\echo.sys.
>
> In the IDE’s output window You get something like (echo is the driver’s
> name):
>
>
> --------------------Configuration: echo - Win32 Debug--------------------
> DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
> Comments? Suggestions? xxxxx@hollistech.com
> DDKBUILD using WLH DDK in directory .
> for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
> commandline: " build -e -MI "
> BUILD: Compile and Link for x86
> BUILD: Loading c:\winddk\6001.18000\build.dat…
> BUILD: Computing Include file dependencies:
> BUILD: Start time: Fri Apr 04 09:29:28 2008
> BUILD: Examining c:\projects\echo directory for files to compile.
> c:\projects\echo
> BUILD: Saving c:\winddk\6001.18000\build.dat…
> BUILD: Compiling c:\projects\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Linking for c:!projectsone_now_c\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Finish time: Fri Apr 04 09:29:30 2008
> BUILD: Done
> =============== build warnings ======================
>
>
> build complete status 0
>
> echo.sys - 0 error(s), 0 warning(s)
>
>
> That’s it.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-319920-
> > xxxxx@lists.osr.com] On Behalf Of FarmerJo
> > Sent: Friday, April 04, 2008 7:25 AM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] Hollistech DDKBUILD problem
> >
> > Does anyone use the standard build.bat file with visual studio? If so
> > could
> > you tell me how to configure a visual studio project? I am usnig V6 of
> > VS
> > and run windows XP.
> >
> > FarmerJo
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Mark Roddy

Mark_Roddy · April 4, 2008, 10:12am

Unless I have a typo in ddkbuild.bat (and that would not be the frist
tmie) that step one action ought to be “WLHBASE=” rather than “WHLBASE=”,
other than that this is the correct answer.

The OP’s problem was that he was pointing ddkbuild at the WDK for Vista
Sp1 and telling ddkbuild that it was the W2K3 DDK.: ":\ddkbuild\ddkbuild
-WNETXP checked " The various released ddks have their singularities
oddities and peculiarities that ddkbuild tries to smooth over but needs an
initial clue to get right.

On Fri, Apr 4, 2008 at 9:39 AM, Alex Shvedov wrote:

> 1. Create/set an environment variable like
>
> WHLBASE=C:\WinDDK\6001.18000
>
> 2. Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat
>
> 3. Create a new “Makefile” project in VC6.
>
> 4. In “Project Settings” -> Genral -> “Build command line” replace the
> content by
>
> ddkbuild -WLHXP checked .
>
> for “Win32 Debug” build and by
>
> ddkbuild -WLHXP free .
>
> for “Win32 Release” build. Do not miss a . (dot) at the end of both lines!
> It points to the current directory!
>
> You may also replace “Output file name” by yourDrvr.sys.
>
> [Later You will probably want to add in-IDE browsing capabilities.]
>
> 5. Copy all relevant source and header files into this newly created
> directory (simplest case assumed here), the one where you should have a
> DSP
> file by now. Make sure that the “sources” file is in it also.
>
> 6. Build the project in debug mode.
>
> You get \objchk_wxp_x86\i386\echo.sys.
>
> In the IDE’s output window You get something like (echo is the driver’s
> name):
>
>
> --------------------Configuration: echo - Win32 Debug--------------------
> DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
> Comments? Suggestions? xxxxx@hollistech.com
> DDKBUILD using WLH DDK in directory .
> for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
> commandline: " build -e -MI "
> BUILD: Compile and Link for x86
> BUILD: Loading c:\winddk\6001.18000\build.dat…
> BUILD: Computing Include file dependencies:
> BUILD: Start time: Fri Apr 04 09:29:28 2008
> BUILD: Examining c:\projects\echo directory for files to compile.
> c:\projects\echo
> BUILD: Saving c:\winddk\6001.18000\build.dat…
> BUILD: Compiling c:\projects\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Linking for c:!projectsone_now_c\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Finish time: Fri Apr 04 09:29:30 2008
> BUILD: Done
> =============== build warnings ======================
>
>
> build complete status 0
>
> echo.sys - 0 error(s), 0 warning(s)
>
>
> That’s it.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-319920-
> > xxxxx@lists.osr.com] On Behalf Of FarmerJo
> > Sent: Friday, April 04, 2008 7:25 AM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] Hollistech DDKBUILD problem
> >
> > Does anyone use the standard build.bat file with visual studio? If so
> > could
> > you tell me how to configure a visual studio project? I am usnig V6 of
> > VS
> > and run windows XP.
> >
> > FarmerJo
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Mark Roddy

Mark_Rodriquez · April 4, 2008, 10:12am

Did you mean WLHBASE?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Shvedov
Sent: Friday, April 04, 2008 9:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Hollistech DDKBUILD problem

Create/set an environment variable like

WHLBASE=C:\WinDDK\6001.18000

Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat
Create a new “Makefile” project in VC6.
In “Project Settings” -> Genral -> “Build command line” replace the
content by

ddkbuild -WLHXP checked .

for “Win32 Debug” build and by

ddkbuild -WLHXP free .

for “Win32 Release” build. Do not miss a . (dot) at the end of both lines!
It points to the current directory!

You may also replace “Output file name” by yourDrvr.sys.

[Later You will probably want to add in-IDE browsing capabilities.]

Copy all relevant source and header files into this newly created
directory (simplest case assumed here), the one where you should have a DSP
file by now. Make sure that the “sources” file is in it also.
Build the project in debug mode.

You get \objchk_wxp_x86\i386\echo.sys.

In the IDE’s output window You get something like (echo is the driver’s
name):

--------------------Configuration: echo - Win32 Debug--------------------
DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
Comments? Suggestions? xxxxx@hollistech.com
DDKBUILD using WLH DDK in directory .
for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
commandline: " build -e -MI "
BUILD: Compile and Link for x86
BUILD: Loading c:\winddk\6001.18000\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Start time: Fri Apr 04 09:29:28 2008
BUILD: Examining c:\projects\echo directory for files to compile.
c:\projects\echo
BUILD: Saving c:\winddk\6001.18000\build.dat…
BUILD: Compiling c:\projects\echo directory
_NT_TARGET_VERSION SET TO WINXP
BUILD: Linking for c:!projectsone_now_c\echo directory
_NT_TARGET_VERSION SET TO WINXP
BUILD: Finish time: Fri Apr 04 09:29:30 2008
BUILD: Done
=============== build warnings ======================

build complete status 0

echo.sys - 0 error(s), 0 warning(s)

That’s it.

> -----Original Message-----
> From: xxxxx@lists.osr.com [mailto:bounce-319920-
> xxxxx@lists.osr.com] On Behalf Of FarmerJo
> Sent: Friday, April 04, 2008 7:25 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Hollistech DDKBUILD problem
>
> Does anyone use the standard build.bat file with visual studio? If so
> could
> you tell me how to configure a visual studio project? I am usnig V6 of
> VS
> and run windows XP.
>
> FarmerJo
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · April 4, 2008, 3:45pm

> Did you mean WLHBASE?

Unless I have a typo in ddkbuild.bat
If it’s a typo, then it is permeating the web help also,
check out

http://www.hollistech.com/Resources/ddkbuild/ddkbuildhelp3_14.htm

that ddkbuild honestly presents once you screw up its cmd line.

Quote from the web page: “WLHXP indicates development system
uses the WHLBASE environment variable to locate WDK versions
6000 or 6001 and build X86 XP binaries (optional.)”

That’s what I call a pro script writer: scripts work after any
permutation of variable names… Next step - surviving any
permutation of a script text as a whole…

Seriously, I doubt that WHLBASE is a typo, I still have
WDF_DDK=C:\WinDDK\6000
WDF_ROOT=C:\WinDDK\6000
so there is no way for a script to guess where 6001 lives
(and it does, see the log below).

The purpose of my exercise actually was - well, to help the
guy out in the first place - to check whether it still is
as simple as that.

I did not look into the bat file itself, I grabbed the
first folder with “sources” and followed the instructions,
I did not bother to check what the code I used as a
sample does…

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-319934-
xxxxx@lists.osr.com] On Behalf Of Mark Rodriquez
Sent: Friday, April 04, 2008 10:12 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Hollistech DDKBUILD problem

Did you mean WLHBASE?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alex Shvedov
Sent: Friday, April 04, 2008 9:39 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Hollistech DDKBUILD problem

Create/set an environment variable like

WHLBASE=C:\WinDDK\6001.18000

Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat

Create a new “Makefile” project in VC6.

In “Project Settings” -> Genral -> “Build command line” replace the
content by

ddkbuild -WLHXP checked .

for “Win32 Debug” build and by

ddkbuild -WLHXP free .

for “Win32 Release” build. Do not miss a . (dot) at the end of both
lines!
It points to the current directory!

You may also replace “Output file name” by yourDrvr.sys.

[Later You will probably want to add in-IDE browsing capabilities.]

Copy all relevant source and header files into this newly created
directory (simplest case assumed here), the one where you should have a
DSP
file by now. Make sure that the “sources” file is in it also.

Build the project in debug mode.

You get \objchk_wxp_x86\i386\echo.sys.
>
> In the IDE’s output window You get something like (echo is the driver’s
> name):
>
>
> --------------------Configuration: echo - Win32 Debug------------------
> –
> DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
> Comments? Suggestions? xxxxx@hollistech.com
> DDKBUILD using WLH DDK in directory .
> for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
> commandline: " build -e -MI "
> BUILD: Compile and Link for x86
> BUILD: Loading c:\winddk\6001.18000\build.dat…
> BUILD: Computing Include file dependencies:
> BUILD: Start time: Fri Apr 04 09:29:28 2008
> BUILD: Examining c:\projects\echo directory for files to compile.
> c:\projects\echo
> BUILD: Saving c:\winddk\6001.18000\build.dat…
> BUILD: Compiling c:\projects\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Linking for c:!projectsone_now_c\echo directory
> _NT_TARGET_VERSION SET TO WINXP
> BUILD: Finish time: Fri Apr 04 09:29:30 2008
> BUILD: Done
> =============== build warnings ======================
>
>
> build complete status 0
>
> echo.sys - 0 error(s), 0 warning(s)
>
>
> That’s it.
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-319920-
> > xxxxx@lists.osr.com] On Behalf Of FarmerJo
> > Sent: Friday, April 04, 2008 7:25 AM
> > To: Windows System Software Devs Interest List
> > Subject: Re:[ntdev] Hollistech DDKBUILD problem
> >
> > Does anyone use the standard build.bat file with visual studio? If so
> > could
> > you tell me how to configure a visual studio project? I am usnig V6
> of
> > VS
> > and run windows XP.
> >
> > FarmerJo
> >
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Mark_Roddy · April 4, 2008, 4:11pm

I’ll check the docs and the bat file.

On Fri, Apr 4, 2008 at 3:44 PM, Alex Shvedov wrote:

> > Did you mean WLHBASE?
> > Unless I have a typo in ddkbuild.bat
> If it’s a typo, then it is permeating the web help also,
> check out
>
> http://www.hollistech.com/Resources/ddkbuild/ddkbuildhelp3_14.htm
>
> that ddkbuild honestly presents once you screw up its cmd line.
>
> Quote from the web page: “WLHXP indicates development system
> uses the WHLBASE environment variable to locate WDK versions
> 6000 or 6001 and build X86 XP binaries (optional.)”
>
> That’s what I call a pro script writer: scripts work after any
> permutation of variable names… Next step - surviving any
> permutation of a script text as a whole…
>
> Seriously, I doubt that WHLBASE is a typo, I still have
> WDF_DDK=C:\WinDDK\6000
> WDF_ROOT=C:\WinDDK\6000
> so there is no way for a script to guess where 6001 lives
> (and it does, see the log below).
>
> The purpose of my exercise actually was - well, to help the
> guy out in the first place - to check whether it still is
> as simple as that.
>
> I did not look into the bat file itself, I grabbed the
> first folder with “sources” and followed the instructions,
> I did not bother to check what the code I used as a
> sample does…
>
>
>
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com [mailto:bounce-319934-
> > xxxxx@lists.osr.com] On Behalf Of Mark Rodriquez
> > Sent: Friday, April 04, 2008 10:12 AM
> > To: Windows System Software Devs Interest List
> > Subject: RE: [ntdev] Hollistech DDKBUILD problem
> >
> > Did you mean WLHBASE?
> >
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com] On Behalf Of Alex Shvedov
> > Sent: Friday, April 04, 2008 9:39 AM
> > To: Windows System Software Devs Interest List
> > Subject: RE: [ntdev] Hollistech DDKBUILD problem
> >
> > 1. Create/set an environment variable like
> >
> > WHLBASE=C:\WinDDK\6001.18000
> >
> > 2. Copy ddkbuild.bat into C:\Windows\System32\ddkbuild.bat
> >
> > 3. Create a new “Makefile” project in VC6.
> >
> > 4. In “Project Settings” -> Genral -> “Build command line” replace the
> > content by
> >
> > ddkbuild -WLHXP checked .
> >
> > for “Win32 Debug” build and by
> >
> > ddkbuild -WLHXP free .
> >
> > for “Win32 Release” build. Do not miss a . (dot) at the end of both
> > lines!
> > It points to the current directory!
> >
> > You may also replace “Output file name” by yourDrvr.sys.
> >
> > [Later You will probably want to add in-IDE browsing capabilities.]
> >
> > 5. Copy all relevant source and header files into this newly created
> > directory (simplest case assumed here), the one where you should have a
> > DSP
> > file by now. Make sure that the “sources” file is in it also.
> >
> > 6. Build the project in debug mode.
> >
> > You get \objchk_wxp_x86\i386\echo.sys.
> >
> > In the IDE’s output window You get something like (echo is the driver’s
> > name):
> >
> >
> > --------------------Configuration: echo - Win32 Debug------------------
> > –
> > DDKBUILD VERSION 3.14.37 FREEWARE FROM HOLLIS TECHNOLOGY SOLUTIONS
> > Comments? Suggestions? xxxxx@hollistech.com
> > DDKBUILD using WLH DDK in directory .
> > for chk version basedir C:\WinDDK\6001.18000 extension chk_wxp_x86
> > commandline: " build -e -MI "
> > BUILD: Compile and Link for x86
> > BUILD: Loading c:\winddk\6001.18000\build.dat…
> > BUILD: Computing Include file dependencies:
> > BUILD: Start time: Fri Apr 04 09:29:28 2008
> > BUILD: Examining c:\projects\echo directory for files to compile.
> > c:\projects\echo
> > BUILD: Saving c:\winddk\6001.18000\build.dat…
> > BUILD: Compiling c:\projects\echo directory
> > _NT_TARGET_VERSION SET TO WINXP
> > BUILD: Linking for c:!projectsone_now_c\echo directory
> > _NT_TARGET_VERSION SET TO WINXP
> > BUILD: Finish time: Fri Apr 04 09:29:30 2008
> > BUILD: Done
> > =============== build warnings ======================
> >
> >
> > build complete status 0
> >
> > echo.sys - 0 error(s), 0 warning(s)
> >
> >
> > That’s it.
> >
> >
> >
> > > -----Original Message-----
> > > From: xxxxx@lists.osr.com [mailto:bounce-319920-
> > > xxxxx@lists.osr.com] On Behalf Of FarmerJo
> > > Sent: Friday, April 04, 2008 7:25 AM
> > > To: Windows System Software Devs Interest List
> > > Subject: Re:[ntdev] Hollistech DDKBUILD problem
> > >
> > > Does anyone use the standard build.bat file with visual studio? If so
> > > could
> > > you tell me how to configure a visual studio project? I am usnig V6
> > of
> > > VS
> > > and run windows XP.
> > >
> > > FarmerJo
> > >
> > >
> > >
> > > —
> > > NTDEV is sponsored by OSR
> > >
> > > For our schedule of WDF, WDM, debugging and other seminars visit:
> > > http://www.osr.com/seminars
> > >
> > > To unsubscribe, visit the List Server section of OSR Online at
> > > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
> >
> >
> > —
> > NTDEV is sponsored by OSR
> >
> > For our schedule of WDF, WDM, debugging and other seminars visit:
> > http://www.osr.com/seminars
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Mark Roddy

OSR_Community_User · April 4, 2008, 5:45pm

Hi,

Thanks for the detailed reply. Initially I followed the setup instructions
on the Hollistech web site but have not been able to get a connection to it
for several days now.

In their instruction they add build and rebuild options for the visual
studio project which were as follows respectively.

ddkbuild -WNETXP checked .
ddkbuild -WNETXP checked . -cZ

The build worked fine but the rebuild had problems with the -cZ option which
if you provide directly to build.exe works fine.

Regards FarmerJo

Mark_Roddy · April 4, 2008, 6:12pm

Hmmm my browser works fine. That site could really use an upgrade though

The docs try to be clear about this but frequently fail. The specification
for build and ddk type are combined in one command argument. “-WNETXP” means
“use the W2K3 DDK to build an XP binary object”. If you are using the Vista
or W2K8 WDKs you need to use “-WLHXP” instead. That means “use the WDK 6000
or WDK 6001 to build an XP binary object”. Furthermore you have to set the
appropriate environment variable that goes with the DDK or WDK release you
want to use. WLHBASE for the WDK (the help file has a freaking typo it is
not WHLBASE) in this case, or if for some reason you insist on using the
ancient W2k3 DDK WNETBASE.

So from my current build environments I have “set
WLHBASE=C:\WinDDK\6001.18000” and I might use “ddkbuild -WLHXP checked .
-cZ”
Which works just fine.

I’ll update the help file to correct the WLHBASE error.

On Fri, Apr 4, 2008 at 5:46 PM, FarmerJo wrote:

> Hi,
>
> Thanks for the detailed reply. Initially I followed the setup instructions
> on the Hollistech web site but have not been able to get a connection to
> it
> for several days now.
>
> In their instruction they add build and rebuild options for the visual
> studio project which were as follows respectively.
>
> ddkbuild -WNETXP checked .
> ddkbuild -WNETXP checked . -cZ
>
> The build worked fine but the rebuild had problems with the -cZ option
> which
> if you provide directly to build.exe works fine.
>
> Regards FarmerJo
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Mark Roddy

OSR_Community_User · April 5, 2008, 5:43am

Many thanks,

It is now sorted. For me it would have been easier if the batch file help referenced the DDK by version (i.e. 6001.18000) aswsell. I was not aware that the DDK I am using is known as Longhorn.

Anyway its not a criticism and I think it is good that you have taken the time to contribute to the community with the DDKBUILD script and I thank you again for you help.

Regards FarmerJo

Mark_Roddy · April 5, 2008, 10:00am

If the WDK ever settled down enough to have consistent naming and version
numbers I would do that. It just recently grew a standard version xml page,
which over time should allow scripting to just make all the version specific
decisions internally rather than forcing the user to whack it with a clue
stick.

On Sat, Apr 5, 2008 at 5:46 AM, FarmerJo wrote:

> Many thanks,
>
> It is now sorted. For me it would have been easier if the batch file help
> referenced the DDK by version (i.e. 6001.18000) aswsell. I was not aware
> that the DDK I am using is known as Longhorn.
>
> Anyway its not a criticism and I think it is good that you have taken the
> time to contribute to the community with the DDKBUILD script and I thank you
> again for you help.
>
> Regards FarmerJo
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

–
Mark Roddy