WM5DevSpy

Here I've published the program intended to monitor device drivers of WM5. Actually, you don't need it if you are not a programmer-hacker. Thus you need it, if you are interested in an information about calls to a device drivers, such as function's arguments and a transferring data. The program has to be compiled before using (and yet again, if you don't know how, you don't need it). A device name is located in the WM5DevSpy.c and you would find it without extra work. I feel too lazy to write a good gui interface for it. As a bonus, this program describes each interrupt, showing a process and a thread of the process that handle interrupt. Feel free to ask.

Instance of log:

2007.02.22 00:15:32: Starting ------------------------------------------------------
2007.02.22 00:15:33: interrupt 5 (abs 13): event struct at 8ffb2818, thread struct at 8efb4024, owner proc at 8c5976d0, proc name=NK.EXE, thread start addr=8c215240
2007.02.22 00:15:33: interrupt 8 (abs 16): event struct at 8f7a5xf0, thread struct at 8e7a2a64, owner proc at 8c597ad0, proc name=gwes.exe, thread start addr=015c39b4
2007.02.22 00:15:33: interrupt 9 (abs 17): event struct at 8f796yc4, thread struct at 8e785400, owner proc at 8c597ad0, proc name=gwes.exe, thread start addr=01e944e4
[...]
2007.02.22 00:15:34: fsDev_t at: 06048c50
2007.02.22 00:15:34: LegalName: BAT1:
2007.02.22 00:15:34: DeviceName: BAT1
2007.02.22 00:15:34: BusName: BuiltInPhase1_0_26_0
2007.02.22 00:15:34: DeviceKey: Drivers\BuiltIn\Battery
2007.02.22 00:15:34: control (openData=0x00000001, code=0x00290400, inBuf=0x0806fa8c, inSize=0x00000004, outBuf=0x0806fa60, outSize=0x00000014, outUsed=0x0806fa20) -> 0x00000001
2007.02.22 00:15:34: [ *outUsed : 0x00000018 ]
2007.02.22 00:15:34: IN:
2007.02.22 00:15:34: 01 00 00 00 
2007.02.22 00:15:34: OUT:
2007.02.22 00:15:34: 00 08 5a 00 ff ff ff ff 
2007.02.22 00:15:34: ff ff ff ff 00 ff 00 00 
2007.02.22 00:15:34: ff ff ff ff ff ff ff ff 
2007.02.22 00:15:37: Calls to open function: 0
2007.02.22 00:15:37: Calls to close function: 0
2007.02.22 00:15:38: Calls to control function: 1
2007.02.22 00:15:38: Calls to read function: 0
2007.02.22 00:15:38: Calls to write function: 0
2007.02.22 00:15:38: Calls to seek function: 0
2007.02.22 00:15:38: Calls to powerup function: 0
2007.02.22 00:15:38: Calls to powerdn function: 0
2007.02.22 00:15:38: ----------------------- stop -------------------------