reactos/reactos
Johannes Anderwald 7a92e8a9e6 - fix error status
svn path=/trunk/; revision=32124
2008-02-04 22:32:37 +00:00
..
base build unicode version 2008-02-02 22:49:24 +00:00
boot - Build FreeLdr the same way other modules are built, by using gcc -Wl. 2008-02-04 20:27:43 +00:00
dll return 0 when type is DWORD 2008-02-04 22:11:56 +00:00
drivers Get back DO_DIRECT_IO flag that has been removed in r31747 2008-01-27 13:51:48 +00:00
hal
include - rename member 2008-02-04 18:58:46 +00:00
lib Get inflib_host to build warning-free 2008-02-03 13:36:10 +00:00
media add font for codepage 775 by <cman at cman dot us> and 852 by <olaf_siejka at o2 dot pl> 2008-01-30 07:38:29 +00:00
modules
ntoskrnl - Wrap MmProbeAndLockPages invocations into SEH. 2008-01-30 13:33:16 +00:00
subsystems - fix error status 2008-02-04 22:32:37 +00:00
tools - Build FreeLdr the same way other modules are built, by using gcc -Wl. 2008-02-04 20:27:43 +00:00
apistatus.lst
baseaddress.rbuild
config-ppc.template.rbuild
config.template.rbuild enable KDBG as default 2008-01-19 18:11:12 +00:00
COPYING
CREDITS
depmap.xsl
Doxyfile
INSTALL
LGPL.txt
Makefile
proxy.mak
ReactOS-generic.rbuild
ReactOS-i386.rbuild Fno-strict-aliasing -> fno-strict-aliasing 2008-01-25 20:30:52 +00:00
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.