Looks like this text got clipped out of that thread when Stephen made his post (the original thread is quite long, and my post is somewhere in the middle). In case the named provider doesn’t work…
On back-level, you can manually enter the GUID {544d4c9d-942c-46d5-bf50-df5cd9524a50}.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Bob Kjelgaard
Sent: Thursday, July 26, 2007 9:23 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Using the Framework’s Event Logger with TraceView
http://www.osronline.com/showThread.cfm?link=111549
In case I screwed that up, I searched NTDEV for “KMDF CTL GUID” and it was the first entry.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Greg Coleson
Sent: Thursday, July 26, 2007 8:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Using the Framework’s Event Logger with TraceView
It is possible to do this on Windows XP?
If so please show me the steps or direct me to a post.
This is all MSDN has to say about it.
“The framework provides an event logger, sometimes called the framework’s
In-flight Recorder (IFR), that creates records for errors and other events.
You can view the records by using a debugger or TraceView.”
If you follow the traceview link you get standard traceview help.
I can see how to add the tracing to my driver, but I don’t want that. I
have other tracing methods that work fine for that. I just want to trace
KMDF.
Thanks,
Greg