Re: DDK 3790

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

Date: Thu, 2 Sep 2004 12:53:59 -0400

If you had a xp\ntddk.h you weren't using the 2000 DDK. I don't normally
recommend using anything but the latest DDKs, but sometimes you have to do
it. By 'changes' I mean all the changes in the serial driver between the
2000 DDK's version of serial.sys and the 2003's. I keep all the DDKs from
NT4 onward on my hard drive. It makes life much simpler and you can use
tools such as fsync or Araxis Merge or Total Commander to see what files are
different. You need to be able to ignore time stamps for this to work well.
Examine those changes to see if new kernel routines are being used that
won't port back to 2000. Most of the earlier DDKs are located on various
MSDN CDs/DVDs. Some are on the download site.

"Robby Tanner" <rtanner@lightsource.ca> wrote in message
news:%23BQLvpQkEHA.3912@TK2MSFTNGP12.phx.gbl...
>
> "David J. Craig" <SeniorDriversWriter@shogunyoshimuni.com.net> wrote in
> message news:OCWnIDIkEHA.1800@TK2MSFTNGP15.phx.gbl...
>> Do a vdiff on the sources in the 2003 DDK and the old 2000 DDK. See if
> the
>> changes are needed.
>
> I'm not sure I follow. Which changes? I believe the problem is that
> something is the same, not different.
>
> In the copy of the "2000 DDK" I had to copy some contants from the
> xp\ntddk.h to the w2k\ntddk.h to get that version to compile. The issue
> of
> the missing constant declarations seems to persist in the later version,
> "2003" DDK.
>
>
>>Compile the sources from the 2000 DDK using the 2000
>> build environment of the 2003 DDK.
>
> I hadn't thought of that. Thanks.
>
> Rob
>
>
>
>>
>> "Robby Tanner" <rtanner@lightsource.ca> wrote in message
>> news:O%23Z5q4HkEHA.2544@TK2MSFTNGP10.phx.gbl...
>> >I have an old DDK, 2600.1106. When I tried to compile the serial source
> in
>> > the previous version, a bunch of constants were missing from ntddk.h.
>> > I
>> > got
>> > this latest one hoping some of those issues would have been cleared up.
>> > Here's a response I got from a January 2003 inquiry:
>> >
>> > ""Bryan S. Burgin [MS]" <bburgin@microsoft.com> wrote in message
>> >> > news:2d5301c2b8ef$a6dd9830$d5f82ecf@TK2MSFTNGXA12...
>> >> > > (reposting)
>> >> > >
>> >> > > Rob,
>> >> > >
>> >> > > I tested this for you and you're right. This is failing
>> >> > > in the Windows 2000 build environment because those
>> >> > > constants are only defined in the Windows XP header files
>> >> > > (inc\ddk\wxp) and not in the same header files in the
>> >> > > Windows 2000 environment (inc\ddk\w2k). The sample
>> >> > > builds properly in the Windows XP build environment.
>> >> > >
>> >> > > I'll test in the most recent internal release of the DDK
>> >> > > and if it is still failing I'll submit a bug against the
>> >> > > DDK to get this fixed in a future release.
>> >> > >
>> >> > > Bryan S. Burgin
>> >> > > bburgin@microsoft.com"
>> >
>> >
>> > Please see inline comments below.
>> >
>> >
>> > Rob
>> >
>> >
>> >
>> > "David J. Craig" <SeniorDriversWriter@shogunyoshimuni.com.net> wrote in
>> > message news:OF6ubQGkEHA.596@TK2MSFTNGP11.phx.gbl...
>> >> 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.
>> >
>> > I'm not sure, how would I find out?
>> >
>> >> 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.
>> >
>> > Wow, this just keeps getting better and better. I changed the makefile
> as
>> > suggested and it started to compile and I got the SAME ERRORS from Jan
>> > 2003.
>> > Apparently, the Win2k header files have not been fixed. Frankly, that
>> > moves
>> > me in to the unhappy customer arena.
>> >
>> > So, now what? Are the XP drivers backwards-compatible with 2000? Am I
>> > supposed to quit developing for 2000? Any high-level discussion here
>> > greatly appreciated.
>> >
>> >> Get the old DDKs and use the sources there.
>> >
>> > Where would I find these other DDKs?
>> >
>> > Thanks for the responses,
>> > Rob
>> >
>> >
>>
>>
>
>