| All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
| Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
Windows Management Instrumentation
|
Logged in as: Guest |
| Users viewing this topic: none |
|
Login  |
|
|
 Windows Management Instrumentation - Jan. 27, '06, 1:45:49 PM
|
|
|
stevebardwell
Posts: 2
Joined: Aug. 22, '05,
Status: offline
|
Is there any information about using Microsoft's implementation
of event information (MS calls it "Windows Management Instrumentation")? I would like to be able to use it to communicate between our service (running in the Posix subsystem) and the rest of the machine.
_____________________________
Steve B
|
|
|
|
|
RE: Windows Management Instrumentation - Feb. 8, '06, 6:27:39 PM
|
|
|
jerker_back
Posts: 68
Joined: Jul. 7, '05,
From: Sweden
Status: offline
|
You mean that you want your service to have its own eventlog and you can view it in the "Event Viewer"? You will typically work with COM (ie ATL-classes) or the .NET Framework. I think it will be very difficult to implement this with Interix. There are however low-level ways to do this and the best source to find out how is the Windows DDK documentation. The kernel drivers are the ones that actually writes something useful in these logs.
If you don't have the Windows DDK, you can (for now) get it here:
Kernel-Mode Driver Framework
As an alternative, look at the "WPP Software Tracing" which I think would be more simple to implement with Interix.
best regards
Jerker Bäck
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
|
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|
Printable Version
