Author: hbelusca
Date: Tue Jan 5 19:52:35 2016
New Revision: 70497
URL: http://svn.reactos.org/svn/reactos?rev=70497&view=rev
Log:
[REACTOS]
Update the README files for 0.4.x releases.
Modified:
trunk/reactos/INSTALL
trunk/reactos/README
trunk/reactos/boot/bootdata/readme.txt
Modified: trunk/reactos/INSTALL
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/INSTALL?rev=70497&r1=70496…
==============================================================================
--- trunk/reactos/INSTALL [iso-8859-1] (original)
+++ trunk/reactos/INSTALL [iso-8859-1] Tue Jan 5 19:52:35 2016
@@ -1,28 +1,41 @@
1. Build environment
+--------------------
-To build the system you need either mingw32 installed on Windows or a mingw32
-cross compiler running on unix. You may obtain MinGW binaries that build
-ReactOS from http://www.reactos.org/.
+To build the system it is strongly advised to use the ReactOS Build Environment
+(RosBE). Up-to-date versions for Windows and for Unix/GNU-Linux are available
+from our download page at: http://www.reactos.org/wiki/Build_Environment/
+
+Alternatively one can use Microsoft Visual C++ (MSVC) version 2010+, together
+with separate installations of CMake and the Ninja build utility.
2. Building ReactOS
+-------------------
+
+A throughout guide for how to build ReactOS can be found at:
+ http://www.reactos.org/wiki/Building_ReactOS
+
+In the following we only make a quick overview.
+
2.1 Building the binaries
-To build ReactOS run 'make' (without the quotes) if you are building on Linux
-or 'mingw32-make' if you are building on Windows (or ReactOS) from the top
-directory. If you are using RosBE, follow on-screen instructions.
+To build ReactOS run 'ninja' (without the quotes), or alternatively run
+'make' if you are using the Make utility, from the top directory.
+NOTE: In the other examples listed in the following, similar modification
+holds if you are using the Make utility instead of Ninja.
+If you are using RosBE, follow on-screen instructions.
2.2 Building a bootable CD image
-To build a bootable CD image run 'make bootcd' (without the quotes) if you are
-building on Linux or 'mingw32-make bootcd' if you are building on Windows (or
-ReactOS) from the top directory. This will create a CD image with a filename,
-ReactOS.iso, in the top directory.
+To build a bootable CD image run 'ninja bootcd' (without the quotes) from the
+top directory. This will create a CD image with a filename, ReactOS.iso, in
+the top directory.
3. Installation
+---------------
ReactOS can only be installed on a machine that has a FAT16 or FAT32 partition
as the active (bootable) partition. The partition on which ReactOS is to be
@@ -41,13 +54,13 @@
follow the instructions to install ReactOS.
If you have an existing ReactOS installation you want to upgrade, then to
-install ReactOS after building it, type 'make install' or
-'mingw32-make install'. This will create the directory 'reactos' in the top
-directory. Copy the contents of this directory over the existing installation.
+install ReactOS after building it, type 'ninja install'. This will create
+the directory 'reactos' in the top directory. Copy the contents of this
+directory over the existing installation.
If you don't want to copy the files manually every time you run a
-'make install' or 'mingw32-make install', then you can specify the directory
-where the files are to be copied to during installation.
+'ninja install', then you can specify the directory where the files are
+to be copied to during installation.
Set the ROS_INSTALL environment variable. If you are on Windows this could be
done by:
@@ -58,8 +71,7 @@
export ROS_INSTALL=/mnt/windows/reactos
-Now run 'make install' or 'mingw32-make install' to install the files to the
-new location.
+Now run 'ninja install' to install the files to the new location.
3.2 Installation from bootable CD distribution
@@ -68,12 +80,13 @@
contents. Then burn the CD image, boot from it, and follow instructions.
-5. Help
+4. Help
+-------
If you run into problems or have suggestions for making ReactOS better, please
visit the address below. Mailing lists are available for a variety of topics,
bugs should be submitted to JIRA and general chat takes place in the forums,
-or #reactos on freenode
+or #reactos on freenode.
http://www.reactos.org/
Modified: trunk/reactos/README
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/README?rev=70497&r1=70496&…
==============================================================================
--- trunk/reactos/README [iso-8859-1] (original)
+++ trunk/reactos/README [iso-8859-1] Tue Jan 5 19:52:35 2016
@@ -1,29 +1,32 @@
========================
-ReactOS Version 0.3.x
-Updated Dec 16, 2006
+ReactOS Version 0.4.x
+Updated January 5, 2016
========================
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.
+ReactOS is an Open Source effort to develop a quality operating system that is
+compatible with applications and drivers written for the Microsoft® Windows NT
+family of operating systems (NT4, 2000, XP, 2003, Vista, Seven).
- 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.
+The ReactOS project, although currently focused on Windows Server 2003
+compatibility, is always keeping an eye toward compatibility with
+Windows Vista and future Windows NT releases.
-More information is available at http://www.reactos.org/.
+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.
Modified: trunk/reactos/boot/bootdata/readme.txt
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/bootdata/readme.txt?r…
==============================================================================
--- trunk/reactos/boot/bootdata/readme.txt [iso-8859-1] (original)
+++ trunk/reactos/boot/bootdata/readme.txt [iso-8859-1] Tue Jan 5 19:52:35 2016
@@ -1,6 +1,6 @@
========================
-ReactOS Version 0.3.x
-Updated March 3, 2013
+ReactOS Version 0.4.x
+Updated January 5, 2016
========================
1. What is ReactOS?
@@ -10,7 +10,7 @@
compatible with applications and drivers written for the Microsoft® Windows NT
family of operating systems (NT4, 2000, XP, 2003, Vista, Seven).
-Website: http://www.reactos.org
+More information is available at: http://www.reactos.org
2. Relationship with the WINE project
Author: gedmurphy
Date: Tue Jan 5 18:43:26 2016
New Revision: 70495
URL: http://svn.reactos.org/svn/reactos?rev=70495&view=rev
Log:
[FLTMGR]
- Fix a bug in FltpDetachFromFileSystemDevice so it correctly bails when we've walked the attached device list.
- FltpDispatch can come in at high IRQL. Thanks to Thomas for noticing that err.
- Add newlines to the end of DPRINTS (it's been a while...)
- The filter now loads and runs in the reactos FS stack.
Modified:
trunk/reactos/drivers/fs_minifilter/fltmgr/Interface.c
Modified: trunk/reactos/drivers/fs_minifilter/fltmgr/Interface.c
URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/fs_minifilter/fltm…
==============================================================================
--- trunk/reactos/drivers/fs_minifilter/fltmgr/Interface.c [iso-8859-1] (original)
+++ trunk/reactos/drivers/fs_minifilter/fltmgr/Interface.c [iso-8859-1] Tue Jan 5 18:43:26 2016
@@ -342,7 +342,6 @@
#pragma alloc_text(PAGE, FltpAttachToFileSystemDevice)
#pragma alloc_text(PAGE, FltpDetachFromFileSystemDevice)
#pragma alloc_text(PAGE, FltpFsNotification)
-#pragma alloc_text(PAGE, FltpDispatch)
#pragma alloc_text(PAGE, FltpCreate)
#pragma alloc_text(PAGE, FltpFsControl)
#pragma alloc_text(PAGE, FltpFastIoRead)
@@ -427,8 +426,6 @@
{
PFLTMGR_DEVICE_EXTENSION DeviceExtension;
- PAGED_CODE();
-
DeviceExtension = DeviceObject->DeviceExtension;
__debugbreak();
FLT_ASSERT(DeviceExtension &&
@@ -1807,7 +1804,7 @@
Status = FltpGetObjectName(DeviceObject->DriverObject, &FileSystemDeviceName);
if (!NT_SUCCESS(Status)) return Status;
- DPRINT("Found device %wZ, checking if we need to attach...", &FileSystemDeviceName);
+ DPRINT("Found device %wZ, checking if we need to attach...\n", &FileSystemDeviceName);
/* Build up the name of the file system recognizer device */
RtlInitUnicodeString(&FsRecDeviceName, L"\\FileSystem\\Fs_Rec");
@@ -1828,7 +1825,7 @@
&NewDeviceObject);
if (!NT_SUCCESS(Status))
{
- DPRINT1("Failed to create a DO for attatching to a FS : 0x%X", Status);
+ DPRINT1("Failed to create a DO for attatching to a FS : 0x%X\n", Status);
return Status;
}
@@ -1841,11 +1838,11 @@
&DeviceExtension->AttachedToDeviceObject);
if (NT_SUCCESS(Status))
{
- DPRINT("Attached to %wZ", &FileSystemDeviceName);
+ DPRINT("Attached to %wZ\n", &FileSystemDeviceName);
}
else
{
- DPRINT1("Failed to attach to the driver stack : 0x%X", Status);
+ DPRINT1("Failed to attach to the driver stack : 0x%X\n", Status);
goto Cleanup;
}
@@ -1862,7 +1859,7 @@
Status = FltpEnumerateFileSystemVolumes(DeviceObject);
if (!NT_SUCCESS(Status))
{
- DPRINT1("Failed to enumerate file system volumes for this file system : 0x%X", Status);
+ DPRINT1("Failed to enumerate file system volumes for this file system : 0x%X\n", Status);
IoDetachDevice(DeviceExtension->AttachedToDeviceObject);
}
@@ -1880,28 +1877,32 @@
LONG_PTR
FltpDetachFromFileSystemDevice(_In_ PDEVICE_OBJECT DeviceObject)
{
- PDEVICE_OBJECT AttachedDevice, LowestDevice;
+ PDEVICE_OBJECT AttachedDevice, NextDevice;
PFLTMGR_DEVICE_EXTENSION DeviceExtension;
LONG_PTR Count;
PAGED_CODE();
-
- /* Get the attached device and increment the ref count on it */
+ __debugbreak();
+
+ /* Get the top device in the chain and increment the ref count on it */
AttachedDevice = IoGetAttachedDeviceReference(DeviceObject);
- /* Loop through all attached devices until we reach the bottom (file system driver) */
- while (AttachedDevice == NULL ||
- AttachedDevice->DriverObject != DriverData.DriverObject)
- {
- /* Get the attached device */
- LowestDevice = IoGetLowerDeviceObject(AttachedDevice);
-
- /* Remove the reference we added. If it's zero then we're already clean */
+ /* Loop all attached devices looking for our file system driver */
+ while (AttachedDevice->DriverObject != DriverData.DriverObject)
+ {
+ FLT_ASSERT(AttachedDevice != NULL);
+
+ /* Get the next lower device object. This adds a ref on NextDevice */
+ NextDevice = IoGetLowerDeviceObject(AttachedDevice);
+
+ /* Remove the reference we added */
Count = ObfDereferenceObject(AttachedDevice);
- if (Count == 0) return Count;
+
+ /* Bail if this is the last one */
+ if (NextDevice == NULL) return Count;
/* Try the next one */
- AttachedDevice = LowestDevice;
+ AttachedDevice = NextDevice;
}
@@ -1929,7 +1930,7 @@
{
UNICODE_STRING DeviceName;
NTSTATUS Status;
- __debugbreak();
+
PAGED_CODE();
/* Set an empty string */
@@ -1939,7 +1940,7 @@
Status = FltpGetBaseDeviceObjectName(DeviceObject, &DeviceName);
if (NT_SUCCESS(Status))
{
- /* Check if it's attaching or detaching*/
+ /* Check if it's attaching or detaching */
if (FsActive)
{
/* Run the attach routine */
@@ -1970,7 +1971,7 @@
UNICODE_STRING SymLink;
NTSTATUS Status;
- __debugbreak();
+
RtlZeroMemory(&DriverData, sizeof(DRIVER_DATA));
DriverData.DriverObject = DriverObject;
@@ -1996,7 +1997,7 @@
&DeviceObject);
if (!NT_SUCCESS(Status))
{
- DPRINT1("fltmgr IoCreateDevice failed. Status = %X", Status);
+ DPRINT1("fltmgr IoCreateDevice failed. Status = %X\n", Status);
goto Cleanup;
}