This page contains a list of reference materials separated by topic. Most are relevant to ReactOS development and several others are related to Microsoft(C) technologies. They have been separated by category so you can better choose what materials are of interest to you. Some duplication of links may happen if the need to put them into two categories arose.
Before you can begin programming an operating system, you need to know how to program. The following are references and tutorials that one can use to learn various principles. As ReactOS primarily uses C, C++, and Assembly, we will only cover those in this section. The Assembly languages we will cover will be for Intel/AMD and PowerPC, as those are the only architectures ReactOS has code for. For C# and .NET related matters, scroll downwards. Each reference will be ranked as Introductory, Intermediate, or Advanced. Introductory assumes no knowledge of programming, Intermediate assumes you know how to use the language in question, and Advanced covers some of the more tricky topics in programming. Some may be more than one and a rare few will cover topics from all three.
|A general C++ tutorial that covers the first basic program to more advanced topics like templates.||visit||Introductory / Intermediate|
|This tutorial is huge. It covers a large range of topics in C programming and focuses a lot on its use on UNIX platforms. However, in doing so, it also teaches you a lot about what C is capable of and how it's used in an operating system.||visit||Introductory / Intermediate / Advanced|
|Pointers are some of the trickiest things to work with in C/C++. This tutorial provides examples of various techniques that take advantage of them.||visit||Intermediate / Advanced|
|A very nice reference to the C and C++ Standard Libraries. In order to do anything substantial or even trivial, you're likely to be using things from the Standard Libraries.||visit||Intermediate / Advanced|
|An introduction to IBM's PowerPC. If you've never seen assembly code before, I'd advise you start with learning the assembly for a RISC architecture like the PPC. Good PPC tutorials can actually be hard to come by, but these should get you started.||visit||Intermediate|
|These two are guides to Intel's assembly language. Both have their strengths and weaknesses, but they seem to complement each other well.||visit||Intermediate|
|Registers on Intel's architecture have a somewhat contrived naming convention compared to RISC architectures. These two references provide a breakdown of what they are and how they're used.||visit||Intermediate|
|How C/C++ code is transformed into assembly is also rather interesting. Function conventions define how a function is transformed into assembly code.||visit||Advanced|
|Intel also maintains a series of books on assembly programming. These things are fairly hefty and you'll want to be familiar with the basics of the x86 architecture before tackling them.||visit||Advanced|
|AMD also has a list of manuals for programming on its AMD64 architecture.||visit|
|A fairly verbose win32 tutorial. While not nearly as indepth as Petzold's book, this does cover a fair amount of material and is a great place to start learning the Windows API.||visit||Intermediate|
|SEH is how exceptions are handled in Windows. If you want to do system programming, you're going to need to learn it.||visit||Advanced|
|Some aspects of Windows use the Component Object Model extensively and a tutorial to to writing them in 7 parts is on CodeProject.||visit||Intermediate / Advanced|
|Description||Name / ISBN||Level|
|The book for the Windows API. ReactOS uses the win32 API extensively for any of its own graphical applications as well as support the various win32 applications written by third parties.||Programming Windows, 5th Edition||Intermediate / Advanced|
|The book for using the Microsoft Foundation Classes. While ReactOS does not support MFC, we could potentially do so in the future if someone were to implement it. Of course, one would have to be thoroughly familiar with MFC to do so.||Programming Windows with MFC||Intermediate / Advanced|
The intent of this section is to pick up where the programming section left off in getting people up to speed. As such, the links here are aimed at familiarizing people with OS fundamentals and then introducing the Windows NT architecture. It is not intended to provide links to every other operating system in existence. The references here are tagged as Introductory, Intermediate, or Advanced. However, the tags are in the context of operating system knowledge, not general computer science knowledge. In general, one should be at the Intermediate for programming to fully understand the Introductory material here. Introductory material tends to be concept explanations. By the time implementation begins being covered in depth, we're in the Intermediate range.
Programming topics here are usually in regard to systems programming not covered in the references above.
|A one stop reference site of sorts. It has a few holes, but provides some decent overviews.||visit||Introductory / Intermediate / Advanced|
|An excellent overview and introduction to the principles behind operating systems. This link contains much of the information the Minix OS book also has, but of course does not include OS specific implementations, just generalized ones. If you want an introduction to operating systems, this is the page to start with.||visit||Introductory / Intermediate|
|This explains the principles behind how a computer boots into an operating system. It doesn't delve into the code behind it, but provides the general outline of what is going on.||visit||Introductory|
|A tutorial on how to write your own simple kernel. Some of this won't make much sense unless you're familiar with the Introductory materials.||visit||Intermediate|
|WDM is the driver model used in 2000, XP, and Vista, though Vista is slowly transitioning it out. This provides an outline of WDM as well as links to getting the Driver Development Kit.||visit||Intermediate|
|WDF is the new driver model for Windows Vista. This provides an introduction and links to various resources. Also, the new Windows Driver Kit includes the various headers needed for filesystem drivers, which will come in handy once ReactOS can handle new filesystems.||visit||Intermediate|
|The online component of the book OS Concepts, this page has three online chapters talking about FreeBSD, Mach, and Windows 2000. They're great references for taking a peek at how these operating systems work.||visit||Intermediate|
|This is the first of several articles introducing how to write Windows drivers. Considering how rare such tutorials are, it's a good place to start.||visit|
|Description||Name / ISBN||Level|
|This book is perhaps the best reference one can find to learn the principles and fundamentals of operating systems. The text provides a decent amount of depth and provides examples from various operating systems in use today. The chapter on Windows XP is especially useful for grasping the basics before one moves onto the Windows Internal book.||Operating System Concepts, Seventh Edition||Introductory / Intermediate / Advanced|
|A book that covers the theory behind operating systems and also examines their implementation in Minix. It's a decent book for learning the fundamentals and immediately delve into how they're transformed into code. While this book does cover the basics, its implementation angle is based on a microkernel design, not the monolithic kernel in general use today.||Operating Systems: Design and Implementation (The Minix Book)||Introductory / Intermediate / Advanced|
|The book for learning about the Windows operating system. This book covers Windows Vista and Server 2008 and was co-authored by Alex Ionescu, a former ReactOS kernel developer. errata, more errata||Windows Internals, Fifth Edition||Intermediate / Advanced|
|The book for learning about the Windows operating system. This book covers 2000, XP, and Server 2003. errata||Windows Internals, Fourth Edition||Intermediate / Advanced|
|The third edition of the Windows Internals series, this book covers up to Windows 2000.||Inside Microsoft Windows 2000 Third edition|
|A book that details the undocumented kernel API in Windows 2000. Even if it is for Windows 2000, its content is still relevant as each Windows version is basically building upon previous releases. Even better, this book was released by its author online for free: http://www.rawol.com/?topic=41||Undocumented Windows 2000 Secrets||Advanced|
|A book that examines the internals of Windows NT. Pre-2000.||Undocumented Windows NT|
|A book that details the native API in Windows NT and 2000.||Windows NT/2000, Native API Reference||Advanced|
|This is perhaps the only book with detailed instructions on how to write a file system driver for Windows.||Windows NT File System Internals||Advanced|
|This book is the primary reference used by the ReactOS developers for implementing win32k. It has a lot of information and is a good book for learning how Windows draws things.||Windows Graphics Programming: Win32 GDI and DirectDraw||Intermediate / Advanced|
|This book covers some of the undocumented internal APIs in win32k. A good read and useful reference for seeing what happens inside the win32k subsystem.||Windows 2000 Graphics API, Black Book||Advanced|
|The user32 DLL handles windows messages and other related matters in relation with the Windows API. This book covers primarily the documented API calls for user32.||Microsoft Windows 2000 API, Super Bible||Intermediate / Advanced|
|A book on writing drivers for Windows 2000.||Windows 2000 Device Driver Book: A Guide for Programmers, 2nd Edition|
|WDM is the driver model used in 2000, XP, and Vista, though Vista is slowly transitioning it out. As ReactOS' aim is for XP compatibility, we will also be implementing WDM.||Programming the Microsoft Windows Driver Model, Second Edition||Advanced|
|WDF is the new driver model for Windows Vista. As Microsoft has tied in DirectX 10 to this, ReactOS will eventually need to implement it.||Developing Drivers with the Windows Driver Foundation||Advanced|
While ReactOS does not have any components to support .NET, it is the future of Windows application programming and will have to be dealt with. .NET is a remarkable piece of technology, though not without its own issues. Some of the more interesting ways to use C# have only begun to emerge as Microsoft begins releasing some of the technology they've developed as part of their Singularity project. While this section does include links to some things still in R&D, our primary focus will be on the underlying principles of what is in production use today. Unlike the programming section above, we won't bother linking intro tutorials on C# and the like. Instead we'll focus on the underlying technologies and concepts as well as some of its more interesting applications.
|The Introduction to MSIL by Kenny Kerr is a very nice set of tutorials on MSIL, the bytecode Visual Studio generates for .NET applications. While learning MSIL is not essential to learning how to use .NET, it is somewhat analogous to learning assembly in order to understand the foundations of C. The articles are in reverse order, bottom to top.||visit||Intermediate / Advanced|
|Another great article by Kenny Kerr, this one discusses C++ and how it fits into the .NET framework.||visit||Intermediate / Advanced|
|An article on LINQ.||visit||Intermediate / Advanced|
|A great article talking about data structures in C#. It's also a good general introduction to data structures, as much of the theory is applicable to other languages.||visit||Intermediate / Advanced|
|An article covering how .NET handles garbage collecting.||visit|
The operating system that got Microsoft off the ground, the 16-bit DOS is still with us today, acting as the command line interface for Windows. DOS was also the core of the Windows 9x family, which had thousands of applications written for it. The main reason for application breakage as people moved to 2000 and XP was because DOS allowed far more freedom in accessing hardware and other system resources. While DOS itself has long been made obsolete, knowledge of it is still useful and several projects exist trying to update it for the 21st century.
The early versions of Windows were in reality nothing more than a graphics layer sitting atop DOS. As DOS is a 16bit OS, non Version of Windows prior to Win 9x and NT used an application runtime known as win32s to run 32bit applications. This used a technique known as thunking between the 16 and 32 bit portions. The thunking approach was taken a stage further in Windows 9x which also implemented portions of the 32bit API's directly.
In modern versions of the Windows family, Microsoft has a variety of tools and applications that have allowed 16bit applications to continue to run on their 32bit operating systems. This compatibility is achieved through the combination of NTVDM and WOWEXEC. Neither approach is implemented in ReactOS today, but basic research has been done to explore the viability of these options.
| There are two primary open source DOS implementations. FreeDOS attempts to create a system completely compatible with MS-DOS while updating it for newer hardware. However, FreeDOS also duplicates some of the limitations that MS-DOS had. FreeDOS-32 attempts to expand upon what Microsoft created, producing a pure 32bit operating system capable of running 16bit DOS applications.
FreeDOS would in theory make a great foundation for reimplementation of the (DOS 7.1) base onto which any number of windowing environments could be placed. This could include clones of Windows 3.x or Windows 9x (the target of the now abandoned Freedows project).
|Even if one has a DOS system to work with, guides to use it are certainly useful.||http://www.nukesoft.co.uk/msdos/||Introductory|
|Batch files are basically command scripts. As DOS was a command line operating system, it figures you could chain commands together into a single script and then execute that script. Also, batch files can be used in 2000 and XP to do certain tasks.||http://home7.inet.tele.dk/batfiles/batfiles.htm||Intermediate|
|ECMA-234, which defines the API used just prior to Windows 95.||http://www.ecma-international.org/publications/standards/Ecma-234.htm|
|Description||Name / ISBN|
|Though deprecated, knowing an operating system's driver model exposes a lot about its kernel and internal architecture.||Writing Windows VxD and Device Drivers, Second Edition|
|Peitrek, Mark ; "Windows 95 System Programming Secrets"|