.Net DDK build environment

Well I finally got the entire project building under the .net ddk build
environment (3790) for w2k. Did sample testing with the debug versions.
Finally did a official build, installed the product, and it BSOD. Turns
out it can not load my driver because in the release build of the ddk it
trys to link _aulldvrm and _alldvrm, which are compiler support routines
for 64 bit math. I looked at the exports of ntoskrnl, and sure enough
it does not export them.

Is there a library I link to that includes them, or do I need to enable
intrinsic functions in release builds?

As a side note, it appears no one but my has ever built a w2k driver
under the .net environment as some header files have syntax errors,
others are completely missing. Once you do get a compile, .lib files
are missing. In the end Its still a better solution than before because
of all the new tools (PREfast rocks).

In case anyone on the ddk team is listening (Eliyas!) here are some of
the things I had to fix (I use the build to build all aspects of our
product, not just the drivers)

Inc\w2k\comdef.h, line 266, is missing an end parenthesis.

Lib\w2k\i386\netapi32.lib is completely missing

The following header files are missing

AccCtrl.h

AclAPI.h

ClusApi.h

COMIP.H

ComSvcs.h

COMUTIL.H

LM.H

LMACCESS.H

LMALERT.H

LMAPIBUF.H

LMAUDIT.H

LMCHDEV.H

LMCONFIG.H

LMCons.h

LMERRLOG.H

LMMSG.H

LMREMUTL.H

LMREPL.H

LMSERVER.H

LMSHARE.H

LMSNAME.H

LMSTATS.H

LMSVC.H

LMUSE.H

LMUSEFLG.H

LMWKSTA.H

MSTask.h

MSTErr.h

RICHEDIT.H

SoftPub.h

Transact.h

ZMOUSE.H

And the following lib

I386\COMSUPP.LIB

Thanks,

Rob

I just moved my driver into the VCNet .2003 and WNET IFSKIT environment
and had the same problem with _aulldvrm - solution is to steal
ulldvrm.obj from inside the VCNet .2003 tree and link to it.

  • Nick Ryan

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Rob Green
Sent: Saturday, May 03, 2003 9:41 AM
To: NT Developers Interest List
Subject: [ntdev] .Net DDK build environment

Well I finally got the entire project building under the .net ddk build
environment (3790) for w2k. Did sample testing with the debug versions.
Finally did a official build, installed the product, and it BSOD. Turns
out it can not load my driver because in the release build of the ddk it
trys to link _aulldvrm and _alldvrm, which are compiler support routines
for 64 bit math. I looked at the exports of ntoskrnl, and sure enough
it does not export them.

Is there a library I link to that includes them, or do I need to enable
intrinsic functions in release builds?

As a side note, it appears no one but my has ever built a w2k driver
under the .net environment as some header files have syntax errors,
others are completely missing. Once you do get a compile, .lib files
are missing. In the end Its still a better solution than before because
of all the new tools (PREfast rocks).

In case anyone on the ddk team is listening (Eliyas!) here are some of
the things I had to fix (I use the build to build all aspects of our
product, not just the drivers)
Inc\w2k\comdef.h, line 266, is missing an end parenthesis.
Lib\w2k\i386\netapi32.lib is completely missing
The following header files are missing
AccCtrl.h
AclAPI.h
ClusApi.h
COMIP.H
ComSvcs.h
COMUTIL.H
LM.H
LMACCESS.H
LMALERT.H
LMAPIBUF.H
LMAUDIT.H
LMCHDEV.H
LMCONFIG.H
LMCons.h
LMERRLOG.H
LMMSG.H
LMREMUTL.H
LMREPL.H
LMSERVER.H
LMSHARE.H
LMSNAME.H
LMSTATS.H
LMSVC.H
LMUSE.H
LMUSEFLG.H
LMWKSTA.H
MSTask.h
MSTErr.h
RICHEDIT.H
SoftPub.h
Transact.h
ZMOUSE.H
And the following lib
I386\COMSUPP.LIB

Thanks,
Rob


You are currently subscribed to ntdev as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com