none
WDK 6001.18001

    Question

  • Hi i was working on windows 2000 ddk . now i am trying to build my code on WDK 6001-18001 - WINDOWS VISTA AND WINDOWS SERVER X86 free build environment.

    i am using the following source file

    # SOURCES for use with BUILD command

    TARGETNAME=kmemserv
    TARGETPATH=obj
    TARGETTYPE=DRIVER
    DRIVERTYPE=WDM
    TARGETLIBS=$(DRIVERWORKS)\lib\*\$(DDKBUILDENV)\vdw_wdm.lib 

    # Put Win2K DDK specific defines in this section.
    !IF "$(LATEST_WIN32_WINNT_VERSION)" == "0x0500"

    # Put NT4/Win98 DDK specific defines in this section.
    !ELSE

    # Need to create the directory for the output in NT4/Win98
    ! IF [mkdir $(TARGETPATH)\i386\$(DDKBUILDENV)] > 1
    ! ERROR Failed to create output directory.
    ! ENDIF

    !ENDIF


    C_DEFINES=-DNTVERSION='WDM'
    # BROWSER_INFO=1
    NO_SAFESEH = 1
    RCNOFONTMAP=1

    INCLUDES=$(DRIVERWORKS)\include;\
       $(DRIVERWORKS)\source;\
       $(DRIVERWORKS)\include\dep_vxd;\
      
    SOURCES=Kmemserv.rc Kmemserv.cpp KmemservDevice.cpp

    when i try to build, I got the following error

    c:\kmemserv\sys\vdw_wdm.lib(cpprt.obj) : warning LNK4210: .CRT section exists; there may be unhandled static initializers or terminators
    LINK : error LNK1218: warning treated as error; no output file generated\

    Then i added

    TARGETLIBS=$(DRIVERWORKS)\lib\*\$(DDKBULDENV)\vdm_wdm.lib\

    $(CRT_LIB_PATH)\msvcrt.lib\ 

    $(CRT_LIB_PATH)\libcmt.lib\

    I got the following error . c:\winddk\6001.18001\bin\verify.src(57) : error U1050: BLD1004 : MSVCRT lib listed explicitly - use USE_MSVCRT=1 (c:\kmemserv\sys)
    Stop.

    Then i added USE_MSVCRT=1 in the source file . I am getting this error

    c:\winddk\6001.18001\bin\makefile.new(3022) : error U1050: USE_MSVCRT not compatible with UMTYPE=nt or ntss
    Stop.

    can anyone tell me what could be the problem .


    Tuesday, June 14, 2011 7:14 PM

Answers

  • Get rid of DriverWorks bu rewriting the driver.  It is not supported any more, and always was full of bugs.  I did an analysis of the source of DriverWorks for a client and stopped when I hit the 5000th bug.

    Seriously if you are going forward consider KMDF or UMDF depending on the type of driver this is.

     


    Don Burn (MVP, Windows DKD) Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr
    Tuesday, June 14, 2011 10:06 PM

All replies

  • Get rid of DriverWorks bu rewriting the driver.  It is not supported any more, and always was full of bugs.  I did an analysis of the source of DriverWorks for a client and stopped when I hit the 5000th bug.

    Seriously if you are going forward consider KMDF or UMDF depending on the type of driver this is.

     


    Don Burn (MVP, Windows DKD) Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr
    Tuesday, June 14, 2011 10:06 PM
  • More than likely, DriverWorks does not support the WDK build you are using, which is not surprising since DriverWorks has not been supported since a late SP for XP. Like Don said, throw that pice of crap called DriverWorks into a trash can and use KMDF.
    Gary G. Little NanoTelesis Systems, LLC
    Thursday, June 16, 2011 12:52 PM