A free Windows-compatible Operating System - mirrored from GitHub
Find a file
Victor Perevertkin 2ae1675208 [ASM] Fixed ".double" macro in asm.inc.
GAS uses ".double" symbol for declaring floating-point constants and
".quad" symbol for declaring 64-bit numbers.
This is not compatible with our macro for MASM and introduces bugs.
Now 64-bit constants are supposed to be declared using ".quad" macro.
2018-07-15 23:25:23 +02:00
.github
base [NTOSKRNL][NDK][UMPNPMGR] Define and use PLUGPLAY_CONTROL_PROPERTY_DATA.Properties values 2018-07-15 15:57:57 +02:00
boot [ASM] Fixed ".double" macro in asm.inc. 2018-07-15 23:25:23 +02:00
dll [WINDOWSCODECS] Fix an MSVC warning about get_decoder_info() (#684) 2018-07-14 02:50:23 +02:00
drivers [BLUE] Use ByteOffset.QuadPrt instead of ByteOffset.LowPart 2018-07-07 16:15:58 +02:00
hal [HALX86] Fix a Clang-Cl warning about KiUnexpectedInterrupt 2018-06-13 10:48:55 +02:00
media [FONTS] Delete 16px bitmap from Tahoma Bold 2018-06-05 15:57:45 +02:00
modules [ROSAPPS] Fix 64 bit issues 2018-07-08 10:59:16 +02:00
ntoskrnl [NTOSKRNL][NDK][UMPNPMGR] Define and use PLUGPLAY_CONTROL_PROPERTY_DATA.Properties values 2018-07-15 15:57:57 +02:00
sdk [ASM] Fixed ".double" macro in asm.inc. 2018-07-15 23:25:23 +02:00
subsystems [CMAKE] Fix command.com livecd.lst entry. CORE-14509 2018-03-30 21:22:33 +02:00
win32ss [USER32][WIN32SS] Fix display of owned popup windows (#683) 2018-07-13 16:03:45 +02:00
.gitattributes
.gitignore
.gitmessage
.travis.yml
apistatus.lst
appveyor.yml [APPVEYOR] Start with the MSVC x64 build so we can get to what breaks it a bit sooner. 2018-04-03 13:19:30 +01:00
CMakeLists.txt [CMAKE] Zap builddir.h.cmake and instead define macros globally 2018-06-30 13:26:56 +02:00
CODE_OF_CONDUCT.md Add a document on the rules we should follow while managing/reviewing PRs, 2018-06-24 17:00:00 +02:00
configure.cmd [CMAKE] Add support for VS 15.7.1 / CL 19.14.x 2018-06-24 11:42:43 +02:00
configure.sh
CONTRIBUTING.md Add a document on the rules we should follow while managing/reviewing PRs, 2018-06-24 17:00:00 +02:00
COPYING
COPYING.ARM
COPYING.LIB
COPYING3
COPYING3.LIB
CREDITS [CREDITS] Update the credits list 2018-06-03 20:32:39 +02:00
Doxyfile
INSTALL
PreLoad.cmake
PULL_REQUEST_MANAGEMENT.md Add a document on the rules we should follow while managing/reviewing PRs, 2018-06-24 17:00:00 +02:00
README.md Reflect latest release versions in README.md 2018-05-08 10:24:26 +03:00
toolchain-clang.cmake
toolchain-gcc.cmake
toolchain-msvc.cmake


ReactOS 0.4.8 Release Download ReactOS SourceForge Download License Donate Follow on Twitter

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.

Building

appveyor.badge travis.badge rosbewin.badge rosbeunix.badge coverity.badge

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 prwelcome.badge

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

You can also support ReactOS by donating! We rely on our backers to maintain our servers and accelerate development by hiring full-time devs.

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.