A free Windows-compatible Operating System - mirrored from GitHub
Go to file
Joachim Henze e9154dd63b [0.4.7][SDK/INCLUDE] Fix MSVC x86 warning LNK4078 CORE-18104
Fix the .code16 macro definition for MASM/ML.

Modify the .code16 macro so that the 16-bit code segment can get a
chance to be correctly merged with other (possibly 32-bit) code
segments, without keeping generating multiple .text segments with
different attributes and generating the corresponding LNK4078 warning.

This fixes the warning when compiling NTOSKRNL on MSVC2010SP1 x86 in dbg config:
"v86.S.obj : warning LNK4078: multiple '.text' sections found with different attributes (C0520040)".

And it even slightly shrinks the size of hal.dll, e.g. for releases/0.4.7 from 1.231.360 to 1.230.848bytes

fix picked from 0.4.12-dev-494-g 0ee02b2c4d
2022-03-27 10:28:14 +02:00
.github Create PULL_REQUEST_TEMPLATE.md 2017-10-17 21:44:07 +03:00
base [0.4.7][REACTOS] Fix '\n.' typos CORE-18103 2022-03-25 19:06:12 +01:00
boot [0.4.7][WIN32SS][RTL] Fix regression CORE-16769 + BSOD 0x50 CORE-13907 2022-03-17 14:04:28 +01:00
dll [0.4.7][SHELL32] Remove some unused members and comment out some unused Wine code 2022-03-26 22:56:30 +01:00
drivers [0.4.7][PCNET] Fix MSVC2010SP1 x86 dbg compiler warning C4146 CORE-18104 2022-03-26 16:17:22 +01:00
hal Add a small descriptive comment for the reason why the chosen files are specified in a .gitattributes file. 2017-10-08 15:48:07 +02:00
media [0.4.7][BCRYPT][CRYPT32][PSDK] Add ECDSA P256 to known algorithms CORE-16741 2022-02-02 22:20:49 +01:00
modules [0.4.7][REACTOS] Fix ', \n' typos in *.rc CORE-18103 2022-03-23 21:39:00 +01:00
ntoskrnl [0.4.7][REACTOS] Fix '\n.' typos CORE-18103 2022-03-25 19:06:12 +01:00
sdk [0.4.7][SDK/INCLUDE] Fix MSVC x86 warning LNK4078 CORE-18104 2022-03-27 10:28:14 +02:00
subsystems Add a small descriptive comment for the reason why the chosen files are specified in a .gitattributes file. 2017-10-08 15:48:07 +02:00
win32ss [0.4.7][WIN32SS][RTL] Fix regression CORE-16769 + BSOD 0x50 CORE-13907 2022-03-17 14:04:28 +01:00
.gitattributes Fix remaining text file line endings in the tree. (#18) 2017-10-06 15:00:36 +02:00
.gitignore Add modules/optional to .gitignore 2017-10-07 13:26:01 +02:00
.travis.yml [TRAVIS-CI] Increase the git clone depth a bit. 2017-10-19 22:33:24 +01:00
apistatus.lst
CMakeLists.txt [NDK] Improve NDK tests for KTHREAD and add them to build 2017-10-08 18:11:07 +02:00
configure.cmd [CONFIGURE] Add -VS_VER flag (#86) 2017-10-23 19:28:15 +03:00
configure.sh
CONTRIBUTING.md Create CONTRIBUTING.md (#46) 2017-10-17 21:12:17 +03:00
COPYING
COPYING.ARM
COPYING.LIB
COPYING3
COPYING3.LIB
CREDITS
Doxyfile
INSTALL
PreLoad.cmake
README.md Update README.md: Add CONTRIBUTING mention 2017-10-17 21:12:17 +03:00
toolchain-clang.cmake
toolchain-gcc.cmake
toolchain-msvc.cmake

ReactOS Project release.badge sfstats.badge travis.badge appveyor.badge

license.badge ghcontrib.badge ghstats.badge commits.badge coverity.badge

What is ReactOS?

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 Server 2003 compatibility, is always keeping an eye toward compatibility with Windows Vista and future Windows NT releases.

The code of ReactOS is licensed under GNU GPL 2.0+.

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+. Building with MSVC is covered here: https://www.reactos.org/wiki/Building_with_MSVC.

Binaries

To build ReactOS you must run the configure script in the directory you want to have your build files. Choose configure.cmd or configure.sh depending on your system. Then run ninja <modulename> to build a module you want or just ninja to build all modules.

Bootable images

To build a bootable CD image run ninja bootcd from the build directory. This will create a CD image with a filename bootcd.iso.

See "Building ReactOS" for more details.

Installing

ReactOS currently 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 installed (which may or may not be the bootable partition) must also be formatted as FAT16 or FAT32. ReactOS Setup can format the partitions if needed.

To install ReactOS from the bootable CD distribution, extract the archive contents. Then burn the CD image, boot from it, and follow the instructions.

See "Installing ReactOS" Wiki page or INSTALL for more details.

Testing

If you discover a bug in ReactOS search on JIRA first - it might be reported already. If not report the bug providing logs and as many information as possible.

See "File Bugs" for a guide.

NOTE: The bug tracker is not for discussions. Please use #reactos Freenode IRC channel or our forum.

Contributing

We are always looking for developers! Check how to contribute if you are willing to participate.

More information

ReactOS is a Free and Open Source operating system based on the Windows architecture, providing support for existing applications and drivers, and an alternative to the current dominant consumer operating system.

It is not another wrapper built on Linux, like WINE. It does not attempt or plan to compete with WINE; in fact, the user-mode part of ReactOS is almost entirely WINE-based and our two teams have cooperated closely in the past.

ReactOS is also not "yet another OS". It does not attempt to be a third player like any other alternative OS out there. People are not meant to uninstall Linux and use ReactOS instead; ReactOS is a replacement for Windows users who want a Windows replacement that behaves just like Windows.

More information is available at: https://www.reactos.org.

Also see the media/doc subdirectory for some sparse notes.

Who is responsible

Active devs are listed as members of GitHub organization. See also the CREDITS file for others.

Code mirrors

The main development is done on GitHub. We have an alternative mirror in case GitHub is down.

There is also an obsolete SVN archive repository that is kept for historical purposes.