Re: DDK 3790

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David J. Craig (SeniorDriversWriter_at_shogunyoshimuni.com.net)
Date: 09/01/04 

Date: Wed, 1 Sep 2004 16:41:30 -0400

Ok, let's try a simple tutorial.

1. Run the build environment you are targeting.
2. Execute 'set' and look at the variables. You might want to redirect the
output to a file or a printer.
3. Look at the 'makefile' file in the serial directory.
4. Look at the test being done. It check for 0x0501 in a variable which
the 2k environment sets to 0x0500. Therefore it fails. Is it a bug in the
sample or is the sample restricted to XP and later? That is the question.
Looking at the DDK 2003 help, it has many references to Windows 2000 in the
docs. I suspect they haven't updated the docs in some time. Change the
makefile and see if it works. Get the old DDKs and use the sources there.

"Robby Tanner" <rtanner@lightsource.ca> wrote in message
news:OTmQ5pFkEHA.1712@TK2MSFTNGP09.phx.gbl...
> Hello all,
>
> I have just received DDK 3790 and tried to build the serial driver, as a
> verification of my installation. I opened the "Windows 2000 Checked Build
> Environment" and navigated to src/kernel/serial and ran "build -Zc"and got
> the following output:
>
> BUILD: Adding /Y to COPYCMD so xcopy ops won't hang.
> BUILD: Object root set to: ==> objchk_w2K_x86
> BUILD: Compile and Link for i386
> BUILD: Examining c:\winddk\3790\src\kernel\serial directory for files to
> compile.
> BUILD: Compiling c:\winddk\3790\src\kernel\serial directory
> BUILD: Linking c:\winddk\3790\src\kernel\serial directory
> BUILD: Done
>
> However, when I went to find serial.sys, it wasn't there.
> buildchk_w2K_x86.log showed:
>
> BUILD: Examining c:\winddk\3790\src\kernel\serial directory for files to
> compile.
> Compiling c:\winddk\3790\src\kernel\serial directory ********************
> 'nmake.exe /c BUILDMSG=Stop. -i NTTEST= UMTEST= NOLINK=1 386=1'
> BUILDMSG: Warning : The sample "C:\WINDDK\3790\src\kernel\serial" is not
> valid for the current OS target.
> Linking c:\winddk\3790\src\kernel\serial directory ********************
> 'nmake.exe /c BUILDMSG=Stop. -i LINKONLY=1 NOPASS0=1 NTTEST= UMTEST=
> 386=1'
> BUILDMSG: Warning : The sample "C:\WINDDK\3790\src\kernel\serial" is not
> valid for the current OS target.
>
> The message seems clear enough, I just don't know why I got it.
>
> Thanks for any tips.
>
> Regards,
> Rob
>
>
>
>
>

Relevant Pages

  • Re: MS DDK sample project
    ... method in command.cpp (oemps.dll - DDK sample) by adding something simple ... I can't get it to compile due to an unknown identifier error. ... When I mentioned VC6 in my build environment, I did so because I am under ... what do you mean by VC6.0 when you describe your build environment? ...
    (microsoft.public.development.device.drivers)
  • Re: driver install on XP 64bit edition
    ... to use that 64-bit driver you built with the XP DDK. ... > environment for the upcoming Microsoft® ... > To compile your driver with the 64-bit compiler, ...
    (microsoft.public.development.device.drivers)
  • Re: Embedded Linux cross compiler for arm target
    ... You have to compile it for you target on your host, ... environment, like the ELDK, provided by DENX. ... > crosscompiler for embedded linux for ARM target in linux environment. ...
    (comp.os.linux.embedded)
  • build -clean doesnt work
    ... When I used the Build utility inside the winddk build environment and typed ... make target 'clean'". ... the -clean switch is documented in the DDK ...
    (microsoft.public.development.device.drivers)
  • Re: Correct DDK Windows 2000 SP4
    ... however Usbview.c will not compile on my system, ... compile in the Windows 2000 environment. ... DDK' in order to compile Usbview.c on my system. ...
    (microsoft.public.development.device.drivers)