Error in 6001.18000 ntddk.h

NTDEV
1

Hi folks,

Just come across what look like an error in the ntddk.h.

I’ve seen it in ddk versions:
5744
6001.17051
6001.18000

and the issue is …

#if (NTDDI_VERSION >= NTDDI_WIN2K)

typedef ULONG NODE_REQUIREMENT;

#define MM_ANY_NODE_OK 0x80000000

NTKERNELAPI
__out_bcount_opt (NumberOfBytes) PVOID
MmAllocateContiguousMemorySpecifyCacheNode (
__in SIZE_T NumberOfBytes,
__in PHYSICAL_ADDRESS LowestAcceptableAddress,
__in PHYSICAL_ADDRESS HighestAcceptableAddress,
__in_opt PHYSICAL_ADDRESS BoundaryAddressMultiple,
__in MEMORY_CACHING_TYPE CacheType,
__in NODE_REQUIREMENT PreferredNode
);
#endif

There is no way that call is supported on NTDDI_WIN2K. Perhaps
NTDDI_WIN6 or later? We just came across this when one of our devs
assumed that if it linked with the 2k3 build environment, it was
probably going to load on 2k3. Alas, his assumptions were not confirmed
by experience.

Oh well. Back to MmGetSystemRoutineAddress. Hopefully that won’t crash
on most versions of 2k3…

MH.

2

Martin Harvey wrote:

Just come across what look like an error in the ntddk.h.

I’d suggest to submit the issue at connect.microsoft.com

They are something like an official support site,
this list here is a free service from OSRonline.

3

That isn’t an official support site either. I don’t know what is, but
someone else here will. The ones on connect.microsoft.com are no more,
in any case, and Microsoft explicitly stated that they are/will be
removing the addresses for posting bugs on that site, now that it is
RTM. I don’t recall the e-mail’s that announced this stating what you
are supposed to do.

Good luck,

mm

Hagen Patzke wrote:

Martin Harvey wrote:
> Just come across what look like an error in the ntddk.h.

I’d suggest to submit the issue at connect.microsoft.com

They are something like an official support site,
this list here is a free service from OSRonline.

4

Martin O’Brien wrote:

That isn’t an official support site either. I don’t know what is, but
someone else here will. The ones on connect.microsoft.com are no more,
in any case, and Microsoft explicitly stated that they are/will be
removing the addresses for posting bugs on that site, now that it is
RTM. I don’t recall the e-mail’s that announced this stating what you
are supposed to do.

What about the online “Feedback” system at http://connect/microsoft.com/?

(Recently I even got an invitation to a survey about the site, even if
feedback processing by MS seems to be pretty “dead”.)

If that one is not “official”, what options are left to give feedback to
Microsoft?

5

connect.microsoft.com is not for production software, and there are no
entries in the ‘Feedback’ section for Vista/S2008, which is where I
assume you mean. Right after the beta program ended, they sent out an
e-mail to participants that said that all aspects of the Vista and
Server 2008 programs (on connect only, of course) would not be supported
any longer, and to not submit bug reports.

===

Dear MARTIN,

We owe you a big THANK YOU for all your great work helping test Windows
Vista SP1. As you might have read, we released Windows Vista SP1 to
manufacturing on February 4, 2008. Today, our hardware partners are hard
at work making new PCs based on Windows Vista SP1.

Special thanks to those of you who tested SP1 RC Refresh 2 (6001.18000).
That was our very last release candidate and it was, in fact, the very
same bits as the final release. (It was a Release Candidate in the
truest sense of the word.) Those of you who installed the SP1 RC Refresh
2 will not need to update to the final version-you already have it.

Please note, we are not providing any support via the beta channels
(newsgroups, email, etc.) for any issues you encounter. The following
images are available for download. For additional downloads, please
visit the downloads section on Connect.

[LINKS TO ISO’s REMOVED FOR BREVITY…]

With the announcement of RTM, we will be closing the current beta
program down. Please take a few minutes to note the following changes
that will happen on March 1, 2008.

  1. All Windows Vista SP1-related content on Connect will be removed
    (programs, downloads, surveys, content, keys, etc). If you wish to keep
    a permanent copy of any information or images you must download and save
    them locally.

  2. All SP1 newsgroups will be deleted. If you wish to archive any
    information you must complete this prior to March 1.

  3. All beta feedback channels will be discontinued.

In order to provide the best upgrade experience possible to our
customers we are starting a new, short-term beta program (4 weeks) aimed
at refining the final experience. NOTE: There will be no change to the
RTM bits.

===

This makes sense, as connect it not for production; however, I’ve never
seen anything like this from connect before, and moreover, where one it
supposed to send these things, I do not know. I’m hoping that someone
else here does.

Personally, I found this whole e-mail (the one from MS) rather strange
as nowhere in it does it say where to go for further information, or
even just “buy MSDN.” It also documents that not only did the last RC
not change in response to any bug reports (assuming that there were any,
which seems unavoidable), but also that there will be a new program that
one can participate in to submit feedback that will also be ignored. It
kind of reads like they are disavowing the product. Clearly, this is
not the case, and I think it’s just a poorly written e-mail that fails
to take in to account that these days, there are many people out there
who know only connect.microsoft.com and nothing about MSDN, et. c.
Considering that everything you need to get started writing drivers has
been free for about two years, and that, in practice, I at least have to
download literally everything I need from MSDN anyway, as nothing comes
on disc in any sort of useful time frame, I can understand why one
doesn’t have any interest in paying for MSDN, assuming that one is just
using the kernel related parts, and that one isn’t particularly choosy
about which OS version to use. In any case, I’ve mentioned the lack of
any further information or links on the WDK/S2008/Vista on connect with
someone from Microsoft.

mm

Hagen Patzke wrote:

Martin O’Brien wrote:
> That isn’t an official support site either. I don’t know what is, but
> someone else here will. The ones on connect.microsoft.com are no
> more, in any case, and Microsoft explicitly stated that they are/will
> be removing the addresses for posting bugs on that site, now that it
> is RTM. I don’t recall the e-mail’s that announced this stating what
> you are supposed to do.

What about the online “Feedback” system at http://connect/microsoft.com/?

(Recently I even got an invitation to a survey about the site, even if
feedback processing by MS seems to be pretty “dead”.)

If that one is not “official”, what options are left to give feedback to
Microsoft?

6

Martin O’Brien wrote:
> In any case, I’ve mentioned the lack of any further information or
> links on the WDK/S2008/Vista on connect with someone from Microsoft.

At least *some* official portal for product feedback is IMHO necessary.

7

Product support available via MSDN incidents can provide the path to report
problems. If the problem is Microsoft’s the incident/fee will usually be
returned/refunded.

“Hagen Patzke” wrote in message news:xxxxx@ntdev…
> Martin O’Brien wrote:
> > In any case, I’ve mentioned the lack of any further information or
> > links on the WDK/S2008/Vista on connect with someone from Microsoft.
>
> At least some official portal for product feedback is IMHO necessary.
>

8

David Craig wrote:

Product support available via MSDN incidents can provide the path to report
problems.

(So I try to be brief and it doesn’t work:)
At least *some* official portal for product feedback is IMHO necessary.
For every product, for every customer. Not just for developers.

The problem I see is that there is not even a site where you can report
a *resolved* problem (three days later, after you found a solution).

If the problem is Microsoft’s the incident/fee will usually be
> returned/refunded.

And which “independent trusted entity” determines that the problem is
Microsoft’s? (Answer: Microsoft)
Therefore this is someting like a “very last resort” to me.

9

Your choice. You want to play in Microsoft’s universe, you gotta play by
their rules. If you have access to ‘out of band’ channels, you can use
those to provide feedback but it isn’t easy to find that type of access.
Some people get to participate in weekly phone calls with one group or
another at Microsoft, but that is reserved for major players in specific
areas.

“Hagen Patzke” wrote in message news:xxxxx@ntdev…
> David Craig wrote:
>> Product support available via MSDN incidents can provide the path to
>> report problems.
>
> (So I try to be brief and it doesn’t work:)
> At least some official portal for product feedback is IMHO necessary.
> For every product, for every customer. Not just for developers.
>
> The problem I see is that there is not even a site where you can report a
> resolved problem (three days later, after you found a solution).
>
>
> > If the problem is Microsoft’s the incident/fee will usually be
> > returned/refunded.
>
> And which “independent trusted entity” determines that the problem is
> Microsoft’s? (Answer: Microsoft)
> Therefore this is someting like a “very last resort” to me.
>

10

Hagen Patzke wrote:

David Craig wrote:
> Product support available via MSDN incidents can provide the path to
> report problems.

(So I try to be brief and it doesn’t work:)
At least *some* official portal for product feedback is IMHO necessary.
For every product, for every customer. Not just for developers.

The problem I see is that there is not even a site where you can
report a *resolved* problem (three days later, after you found a
solution).

> If the problem is Microsoft’s the incident/fee will usually be
> returned/refunded.

And which “independent trusted entity” determines that the problem is
Microsoft’s? (Answer: Microsoft)
Therefore this is someting like a “very last resort” to me.

You have to look at it from Microsoft’s point of view. From YOUR point
of view, the problem you are facing is the most important thing in the
world today. However, Microsoft gets *millions* of support contacts
each and every day. Most of them are crap (“the cup holder on my
computer broke off”). It is fabulously expensive to staff a support
center with the kind of people who are qualified to handle real
problems, so most of the support staff are qualified to handle cup
holder problems. People who have serious problems are assumed to be
willing to front the money for a paid support incident, with the
assurance that it will be returned if it is not a cup holder failure.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

11

Tim Roberts wrote:

People who have serious problems are assumed to be
willing to front the money for a paid support incident, with the
assurance that it will be returned if it is not a cup holder failure.

We have different context:

  • Yes, everything you wrote is true (and I agree with it!) for driver
    development questions/“problems”.

  • No, I am actually not talking about problems, but about helpful
    feedback. Feedback about things you find out about the system.
    Assume you have a problem, investigate it, and because you are able to
    read, use a kernel debugger, have time to do it (and possibly 20+ years
    experience with some OSes and Windows, too) you finally find out the
    proper solution your yourself.
    In some rare cases this points to something MS should know. Or even publish.

And as far as I understood, there is no official way to give this kind
of “feedback”. (Opening a support incident for something you already
figured out a solution for is - IMHO - not justifiable.)