A free Windows-compatible Operating System - mirrored from GitHub
Go to file
Cameron Gutman cf3234d59c - Allocate send and receive buffers from paged pool (saves 32KB of non-paged pool per socket)
svn path=/branches/aicom-network-branch/; revision=44369
2009-12-02 22:38:10 +00:00
base - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
boot - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
dll - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
drivers - Allocate send and receive buffers from paged pool (saves 32KB of non-paged pool per socket) 2009-12-02 22:38:10 +00:00
hal - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
include - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
lib - Revert 44301 2009-12-02 03:29:17 +00:00
media - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
modules - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ntoskrnl - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
subsystems - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
apistatus.lst - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
baseaddress.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
config-amd64.template.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
config-arm.template.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
config-ppc.template.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
config.template.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
COPYING - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
COPYING.ARM - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
COPYING.LIB - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
COPYING3 - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
COPYING3.LIB - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
CREDITS - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
depmap.xsl - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
Doxyfile - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
INSTALL - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
Makefile - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
proxy.mak - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ReactOS-amd64.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ReactOS-arm.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ReactOS-generic.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ReactOS-i386.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
ReactOS-ppc.rbuild - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
README - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
rosbuild.bat - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00
vreport.xsl - Create another branch for networking fixes 2009-12-02 03:23:19 +00:00

========================
ReactOS Version 0.3.x
Updated Dec 16, 2006
========================

1. What is ReactOS?

   ReactOS is an Open Source effort to develop a quality operating system
that is compatible with Windows NT applications and drivers.

   The ReactOS project, although currently focused on Windows XP/2003
drivers compatibility, is always keeping an eye toward compatibility with
older version of Windows NT family ( NT 4.0, 2000 (NT 5.0)) and new
Windows NT releases (Vista, etc). Applications (Win32 API) compatibility
focus is Windows XP.

More information is available at http://www.reactos.org/.

2. Building ReactOS

See the INSTALL file for more details.

3. More information

See the media\doc subdirectory for some sparse notes.

4. Who is responsible

See the CREDITS file.