mirror of
https://github.com/reactos/reactos.git
synced 2024-09-30 14:37:45 +00:00
d9633373f6
- Start using KCB locking/unlocking, usually shared first. - Support KCB lock promotion from shared to exclusive when value cache functions require it (SearchNeedExclusiveLock -- not yet used). - Add multiple checks for deleted KCBs so that operations on them fail. - Protect symlinks from being erroneously modified. - Remove a ReactOS symlink hack. - Add code to setup the KCB Value Cache (right now we use the node list since nobody was setting the value cache up). - Detect and assert on CM_KCB_SYM_LINK_FOUND, this is used by caching which we don't support. - Protect KEY_NO_DELETE nodes from deletion. - Lock the registry during hive flushing. - Respect CmpNoWrite if it's set. - Don't ignore Allocate flag sent to CmpLinkhivetoMaster during hive loading. svn path=/trunk/; revision=31262 |
||
---|---|---|
.. | ||
base | ||
boot | ||
dll | ||
drivers | ||
hal | ||
include | ||
lib | ||
media | ||
modules | ||
ntoskrnl | ||
subsystems | ||
tools | ||
apistatus.lst | ||
baseaddress.rbuild | ||
config-ppc.template.rbuild | ||
config.template.rbuild | ||
COPYING | ||
CREDITS | ||
depmap.xsl | ||
Doxyfile | ||
INSTALL | ||
LGPL.txt | ||
Makefile | ||
proxy.mak | ||
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.