5 ms·
For Windows, there definitive source in book form is the Microsoft Windows Internals series. I worked with a guy that used to work at Microsoft and he prefered
by codeslinger 17y ago
For Windows, there definitive source in book form is the Microsoft Windows Internals series. I worked with a guy that used to work at Microsoft and he prefered this book to looking things up in the source code ;-)
http://www.amazon.com/Windows®-Internals-Including-Windows-PRO-Developer/dp/0735625301/ref=sr_1_1?ie=UTF8&s=books&qid=1253974832&sr=8-1 http://www.amazon.com/Windows®-Internals-Including-Windows-P...
If you're in school, Microsoft also has an academic program that allows universities (almost) full access to the source code of various Windows kernels. Its called the Windows Research Kernel program and might help you along if you can get ahold of it because it comes with a ton of documentation: the original NT design papers, proposed class materials and a full copy of the aforementioned Microsoft Windows Internals book in PDF form.
For Mac, the online kernel guides are pretty good. The Mac OS X Internals book isn't so great for driver or kernel development directly, but is a good reference for learning about how things work. Having said that, the book is a bit dated at this point and could use an update for the later kernels.
- pmjordan 17y agoWindows Internals looks good, thanks. I'll probably go with that. I'm no longer a student, so I'll have to make do without the source I guess. Given that there's more of an explicit public kernel API than in Linux, I'm hoping I'll have less need to poke through it. Your points on the OSX book are duly noted. I'll thoroughly 'look inside' on Amazon before deciding. It might still be useful to me as I'm relatively new to OSX, at least compared to my Linux/Windows exposure.