Hello List,
In trying to get VS.NET and Mark’s latest DDKBUILD.BAT to co-operate
with each other, I ran into a minor but annoying problem.
Just in case anyone else is struggling to understand why “we are sorry
for the inconvenience” when ddkbuild tries to create the bsc file, there
seems to be a conflict of interest along the path which ddkbuild
generates and uses locally.
Ddkbuild cheefully tacks the ddk directories onto the front of the path.
Unfortunately, bscmake.exe uses msvcr70.dll which happens to appear in
different versions in the ddk and in system32.
Hang on! Aren’t we supposed to have gotten over DLL Hell?
Perhaps my analysis of the problem is incorrect, but the following quick
and dirty fix certainly works for me, and keeps bscmake happy: just add
a couple of lines to ddkbuild:
After “setlocal ENABLEEXTENSIONS”:
set origpath=%path%
After “@echo build complete”
path %origpath%
YMMV a lot…
Mark: please accept my sincere thanks for ddkbuild - I never build a
driver without it!
Jim Spriggs