Which NT version does TinyKRNL Target?
TinyKRNL targets Windows NT 5.2.3790.1830, also commercially referred to Windows Server 2003 Service Pack 1.
^ TOPWhich compiler/build environment is used?
TinyKRNL is built in the "Dazzle" Build Environment, which is based on the WDK Build Environment. Builds 5308 and above are supported.
^ TOPWhen will the project be finished?
Final completion of the entire project is expected within a little bit over 3 years.
Is TinyKRNL a Windows replacement?
No. TinyKRNL by itself, even after Phase 3, will only provide a minimalist native-mode environment with a custom-made Command Line Interface for allowing basic networking, multimedia and storage access. The Win32 Components of Phase 3 will only display an empty desktop without support for any other graphical drawing. Win32 applications will be executable only through the Kernel Debugger and will only be able to output text through it.
This choice was taken for two reasons. First of all, TinyKRNL is an educational project with goals limited to the kernel and native-mode low-level system components. Providing the full richness of the Win32 platform that Microsoft has created is way beyond our goals and capabilities. Secondly, by attempting to provide a replacement for Windows, we feel that this would present itself as a potential competitive threat to Microsoft, which is also not a goal of this project.
If you do own a valid Windows license however, we will provide a mechanism to directly expand and copy your files to the TinyKRNL installation folder. The Windows components should be able to perfectly run on top of TinyKRNL. Additionally, you will be able top drop the TinyKRNL components (or any single one) on top of your Windows installation and they should work. We are aiming to create an environment which will support building an XP-compatible as well as 2003-compatible kernel, later on.
Where can I obtain the source code?^ TOP
<FILL ME IN>
I want to help, who do I contact?^ TOP
<FILL ME IN>
How can I monitor TinyKRNL's status? How far has it come along?
<FILL ME IN>
Which license does TinyKRNL use?
Because our components are linked with static libraries from the DDK as well as because some of our driver components are based on Microsoft Distributable Code, whose license prohibits usage of an Excluded License (such as the GPL or LGPL), these TinyKRNL components are licensed under the BSD license.
Furthermore, because TinyKRNL is a research project as well as contains parts of Microsoft copyrighted or patented technologies or code, it cannot be used for commercial purposes in any form, nor be sub-licensed to a 3rd-party without this restriction. This restriction has led to the creation of the TinyKRNL Shared Source License, which is available in the root folder of the SVN server.
Always check the source file to verify which license it belongs to. ^ TOP
How is TinyKRNL related to other projects such as WINE, ReactOS or NDISWrapper?
TinyKRNL has an official relation to the ReactOS project through collaboration on various technical aspects and one-way source code sharing. Although TinyKRNL is free to merge ReactOS Kernel code which has been licensed under our license, ReactOS cannot directly share code with TinyKRNL because of its exclusive license (GPL). However, it is the project's hope that our technical documentation and expertise will become a valuable tool to ReactOS and other projects as they strive to create compatible implementations of Windows NT.
Furthermore, some of these projects are or have commercial usage and attempt competition with Microsoft as direct Windows replacements, as well as attempt to provide a user-mode Win32 environment. These goals are very different from TinyKRNL, and contrast the project's core philosophy as being quite different.
Will Microsoft sue me if I use TinyKRNL?^ TOP
In our opinion, TinyKRNL does not (and never will) pose a threat to Microsoft. If anything, it increases the number of people and developers that will become familiar with the NT Operating System, and perhaps even create some new users, which will realize the true beauty of Windows NT if given the chance to try out something like TinyKRNL instead of a full-fledged OS like Windows Vista. TinyKRNL has no commercial aspirations and prohibits usage of its code in any commercial application. Because the code is not GPL or another similar exclusive license, open source projects will generally be unable to use TinyKRNL's code for their own purposes, and Microsoft's algorithms or features will not disseminate. We see TinyKRNL no different then a living, dynamic version of Inside Windows NT, which will only help NT Developers and users alike, and we hope Microsoft will see the project in the same light.
That being said, we make no guarantees on what legal action Microsoft could bring against us or any user. If any should arise, TinyKRNL will fully cooperate with any demands, but we have no control over any users, much like most Linux distributions cannot offer indemnisation for their users against SCO or other patent suits.