reactos/reactos at a56d746326a632c1f60593e032efc9e8732aa45f - reactos - ApfelTeeGit

ApfelTeeSaft/reactos

mirror of https://github.com/ApfelTeeSaft/reactos.git synced 2026-09-01 19:26:16 +00:00

Files

T

History

James Tabor a56d746326 Removed DPRINT1, 8^D

svn path=/trunk/; revision=20611

2006-01-06 14:50:56 +00:00

..

Remove the temp note. Gé is on fire !

2006-01-05 23:43:49 +00:00

Copy the correct value if the value is stored directly in the data pointer (in CmiExportValue).

2006-01-03 14:56:47 +00:00

add to the bootcd for the purpose of testing bug 1253

2006-01-05 23:00:54 +00:00

Don't keep overwriting the first address entry, give the others a chance too.

2006-01-05 23:11:51 +00:00

- Fix build.

2006-01-05 15:17:54 +00:00

- New ERESOURCE implementation: fixes the return value of some functions (VOID vs NTSTATUS, USHORT vs ULONG), as well as optimized the code loops and general structure of the code. Additionnaly, functions do not simply call other functions with similar names; the exact implementation of each function has now been properly separated (see the DDK for more information on this) to have the most optimized scenarios.

2006-01-05 16:24:32 +00:00

patch from GvG, it fixing the bug for calc = when it showing e-309, Bug 1195, it have even affected python and other apps trying writing out 0 as text string.

2006-01-05 22:54:30 +00:00

- Add information on new executive locks being worked on.

2005-12-27 03:06:35 +00:00

Support all optional modules and possibly a 'windows' one where every piece of code related to the Win32 subsystem will be stored (eventually to be voted on, I suppose).

2005-10-02 17:54:56 +00:00

fixed uninitialized variable warnings

2006-01-06 11:58:17 +00:00

WINSTA_ALL_ACCESS is now defined in winuser.h

2005-12-01 15:01:38 +00:00

Silence most of the msvc warnings

2005-12-27 18:05:53 +00:00

Removed DPRINT1, 8^D

2006-01-06 14:50:56 +00:00

fix build in unspecified build environment - patch by Reuben Perelman <[email protected]>

2006-01-05 16:35:08 +00:00

- New ERESOURCE implementation: fixes the return value of some functions (VOID vs NTSTATUS, USHORT vs ULONG), as well as optimized the code loops and general structure of the code. Additionnaly, functions do not simply call other functions with similar names; the exact implementation of each function has now been properly separated (see the DDK for more information on this) to have the most optimized scenarios.

2006-01-05 16:24:32 +00:00

apistatus.lst

Remove oleaut32 from api status

2005-12-18 17:40:51 +00:00

baseaddress.xml

Import oleacc from Wine. oleacc.xml provided by Christoph von Wittich

2005-12-12 20:41:27 +00:00

config.template.xml

- Add new configuration option "SARCH" to define the sub-architecture. Examples include i386-xbox, ppc-be/le (little/bigendian), or any other sub-types of the specified ARCH.

2005-11-13 06:34:51 +00:00

COPYING

Update GPL and LGPL licenses.

2005-11-23 07:07:40 +00:00

CREDITS

add myself to credits too.

2005-12-09 01:39:42 +00:00

Doxyfile

…

INSTALL

Update installation instructions

2005-05-13 19:47:30 +00:00

LGPL.txt

Update GPL and LGPL licenses.

2005-11-23 07:07:40 +00:00

Makefile

Add ROS_AUTOMAKE variable to determine the location of makefile.auto

2005-12-04 07:58:46 +00:00

proxy.mak

module_test proxy makefile support

2005-08-16 15:47:38 +00:00

ReactOS-ppc.xml

Added support for ROS_AUTOMAKE variable.

2005-12-04 12:02:45 +00:00

ReactOS.xml

- Tabs not spaces.

2006-01-05 16:30:20 +00:00

README

…

README

========================
ReactOS Version 0.2.x
Updated June 23rd, 2004
========================

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 NT 4.0
compatibility, is always keeping an eye towards compatibility with
future Windows NT releases, that is, Windows 2000 (NT 5.0) and
Windows XP (NT 5.1).

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

2. Building ReactOS

See the INSTALL file for more details.

3. More information

See the doc subdirectory for some sparse notes

4. Who is responsible

See the CREDITS file