Microsoft Windows Internals (4th Edition): Microsoft Windows Server 2003, Windows XP, and Windows 2000

Author: Mark E. Russinovich, David A. Solomon
4.0
All Stack Overflow 7

Comments

by Dave Markle   2017-08-20

You can buy this (old) book, (the actual Windows architecture hasn't really changed much in 10 years) for a penny (used):

Inside Windows NT

Here's the up-to-date version:

MS Windows Internals

There's also Mark's Blog

As far as ONLINE resources go, I've found it to be pretty sparse, though :(

by RBerteig   2017-08-20

Device interrupts themselves are (usually) processed by whatever thread had the CPU that took the interrupt, but in a ring 0 and at a different protection level. This limits some of the actions an interrupt handler can take, because most of the time the current thread will not be related to the thread that is waiting for the event to happen that the interrupt is indicating.

The kernel itself is closed source, and only documented through its internal API. That API is exposed to device driver authors, and described in the driver development kits.

Some resources to get you started:

Note that source code to many of the common device drivers are included in the DDK in the samples. Although the production versions are almost certainly different, reading the sample drivers can answer some questions even if you don't want to implement a driver yourself.

by anonymous   2017-08-20

I found code for doing that in VB. I believe it won't be too hard to convert it to C++ code.

A good book about low level stuff is Microsoft Windows Internals.

And I agree with Peter Ruderman

This is not something you should do.