reactos/reactos
2009-03-20 18:02:55 +00:00
..
base -allow to stop the service 2009-03-20 13:43:43 +00:00
boot - Implement boot drivers loading. 2009-03-16 20:56:07 +00:00
dll use ncalrpc instead of a named pipe 2009-03-20 13:44:06 +00:00
drivers - Implement NdisMapFile 2009-03-20 10:21:17 +00:00
hal
include add some new (incomplete) network headers 2009-03-20 15:08:12 +00:00
lib Sync CRT initialization code with mingw-w64 r690 2009-03-17 20:17:02 +00:00
media - Add mp3 codec from Wine 2009-03-15 15:54:15 +00:00
modules
ntoskrnl Merge from amd64 branch: 2009-03-18 17:03:58 +00:00
subsystems Rename GDIDEVICE to PDEVOBJ. Is seems ms uses both PDEV and PDEVOBJ, whith the latter being the C++ representation. But we don't use C++ and PDEVOBJ seems to be a more appropriate name, as PDEV is often used by display drivers. 2009-03-20 18:02:55 +00:00
tools Sync CRT initialization code with mingw-w64 r690 2009-03-17 20:17:02 +00:00
apistatus.lst
baseaddress.rbuild - Add httpapi, initpki, itircl, msisys.ocx, msnet32, pidgen, resutils, sccbase, slbcsp, softpub, traffic from Wine 2009-03-15 15:20:51 +00:00
config-arm.template.rbuild
config-ppc.template.rbuild
config.template.rbuild
COPYING
COPYING.ARM
CREDITS
depmap.xsl
Doxyfile
INSTALL
LGPL.txt
Makefile
proxy.mak
ReactOS-arm.rbuild
ReactOS-generic.rbuild
ReactOS-i386.rbuild
ReactOS-ppc.rbuild
README
vreport.xsl

========================
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.