Any ideas?
Thank you.
--
Calvin Guan (Windows DDK MVP)
NetXtreme Longhorn Miniport Prime
Broadcom Corp. www.broadcom.com
"rbarned" <rba...@comcast.net> wrote in message
news:JqudnQhThdj...@comcast.com...
I call WPP_SYSCONTROL first in driver entry then WPP_INIT_TRACE in my
initialize function. I use the PDEVICE_OBJECT returned from
NdisMRegisterDevice
function. Is this correct?
Any commemts or samples would be greatly appreciated.
Thank you for your help.
Bob
"Calvin Guan" <hg...@nospam.broadcom.com> wrote in message
news:y8STe.5905$rj.1066@lakeread07...
There was a thread in NTDEV (www.osronline.com) yesterday where people
saying the latest DDK or WDK has new WPP template that makes driver binary
compatible with W2k and WXP.
HTH
--
Calvin Guan (Windows DDK MVP)
NetXtreme Longhorn Miniport Prime
Broadcom Corp. www.broadcom.com
"rbarned" <rba...@comcast.net> wrote in message
news:yMKdnRbDHKR...@comcast.com...
>I am trying to get WPP Trace functionality added to a NDIS miniport driver
> written for Windows 2000 in C++? Since my code was not compiliing I tried
> putting the WPP macros in a .C file. Then I called these function from the
> C++ code. The code compiles but I don't see any messages. I know I have
> the traceview configured properly. In addition, when I try to check if WPP
> is activated using WPP_LEVEL_ENABLED macro, it returns false.
>
> I call WPP_SYSCONTROL first in driver entry then WPP_INIT_TRACE in my
> initialize function. I use the PDEVICE_OBJECT returned from
> NdisMRegisterDevice
> function. Is this correct?
>
> Any commemts or samples would be greatly appreciated.
>
> Thank you for your help.
>
> Bob
>
>
> "Calvin Guan" <hg...@nospam.broadcom.com> wrote in message
> news:y8STe.5905$rj.1066@akeread07...