A free Windows-compatible Operating System - mirrored from GitHub
Find a file
Joachim Henze 4d65489387 [0.4.13][SHELL32] Fix uninitialized variable usage. CORE-15251 (#3986)
This fixes log spam about NM_CUSTOMDRAW not being handled,
e.g. when interacting with the start-menu or filebrowsers menubar.
Less logging implies faster painting here with dbg-builds.

fix picked from commit 0.4.15-dev-3229-g 22e58e68aa

The bug was a regression of 0.4.9-dev-151-g 0aed0fd167 very likely,
The symptom with the logging can neither be observed in unpatched releases/0.4.8 nor in releases/0.4.7
2022-09-20 18:22:30 +02:00
.github
base [0.4.13][REACTOS] Fix '\n.' typos CORE-18103 2022-03-25 18:58:23 +01:00
boot [0.4.13][CMAKE][BOOTDATA] Fix LiveCD does not import caroots.inf into registry CORE-17739 CORE-17735 (#3930) 2022-01-21 23:09:10 +01:00
dll [0.4.13][SHELL32] Fix uninitialized variable usage. CORE-15251 (#3986) 2022-09-20 18:22:30 +02:00
drivers [0.4.13][UNIATA] Workaround random crashes on Virtual PC (#3377) CORE-12441 CORE-17371 2021-11-16 22:26:59 +01:00
hal [HAL] Update the PCI hardware IDs database. 2019-09-28 18:52:59 +02:00
media [0.4.13][MEDIA][FONTS] Delete SoureCodePro*.ttf, and most SourceSansPro*.ttf 2022-03-10 21:54:45 +01:00
modules [0.4.13][CYLFRAC] Fix 3 MSVC2010SP1 x86 dbg warnings C4305 CORE-18104 2022-03-31 06:13:20 +02:00
ntoskrnl [0.4.13][REACTOS] Fix '\n.' typos CORE-18103 2022-03-25 18:58:23 +01:00
sdk [0.4.13][CRT] Fix 2 MSVC compiler warnings CORE-17812 2022-03-18 21:27:44 +01:00
subsystems
win32ss [0.4.13][WIN32SS] Repaint the whole window frame on some style bits set (#3199) CORE-16827 2022-03-11 03:20:06 +01:00
.gitattributes
.gitignore
.gitmessage
.travis.yml
apistatus.lst
appveyor.yml
CMakeLists.txt
CODE_OF_CONDUCT.md
CODEOWNERS
configure.cmd
configure.sh
CONTRIBUTING.md
COPYING
COPYING.ARM
COPYING.LIB
COPYING3
COPYING3.LIB
CREDITS
Doxyfile
INSTALL
overrides-gcc.cmake
overrides-msvc.cmake
PreLoad.cmake
PULL_REQUEST_MANAGEMENT.md
README.md
toolchain-clang.cmake
toolchain-gcc.cmake
toolchain-msvc.cmake

ReactOS


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

WebsiteOfficial chatWikiForumJIRA Bug TrackerReactOS Git mirrorTestman

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.

ReactOS is currently an Alpha quality operating system. This means that ReactOS is under heavy development, things may not work well and it can corrupt the data present on your hard disk. It is recommended to test ReactOS on a virtual machine or on a computer with no sensitive or critical data!

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: "Build Environment".

Alternatively one can use Microsoft Visual C++ (MSVC) version 2010+. Building with MSVC is covered here: "Visual Studio or Microsoft Visual C++".

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.

You can always download fresh binary builds of bootable images from the "Daily builds" page.

Installing

By default, 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.

Starting 0.4.10, ReactOS can be installed using the BtrFS file system. But consider this as an experimental feature and thus regressions not triggered on FAT setup may be observed.

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 much 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: 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.