pooltag and W2K?

NTDEV
1

I tried tagging pool as per the PoolTag value in MemoryManagement
under W2K and it seems to act differently (as opposed to under NT4).
Specifically, once set, a previously succeding call to
MmAllocateContiguousMemory now fails (returns NULL).

Anyone else see this and have a workaround? I got one of those
memory corruptors and having a devil of a time trying to find
it (especially with a “tool” looking like it has now become
unusable).

Thanks in advance.

Pete

2

> I tried tagging pool as per the PoolTag value in

MemoryManagement
under W2K and it seems to act differently (as opposed
to under NT4).

Under Windows 2000, “The Right Way” is to use the much more powerful Driver
Verifier (just type “verifier” in the Run box). The behavior of the PoolTag
is incorporated into Driver Verifier, but it is more flexible since it can
be set per-driver.