A free Windows-compatible Operating System - mirrored from GitHub
Go to file
Joachim Henze 463f322ec0 [0.4.9][DESK][SHELLBTRFS] Backports 2024-09-10 (#7298)(#7213)(#6593)(#5764)
This ports back:

0.4.15-dev-8636-g 945e856031 [DESK] _countof and rc-trivia (#7298) <- and act on its FIXMEs

0.4.15-dev-8552-g 24517d5258 [DESK] Fix 3dtext screensaver restart after opening settings (#7213)

0.4.15-dev-7751-g 6185c66c61 [DESK] SetScreenSaver(): Remove remnant 'DeleteMode' variable (#6593)

0.4.15-dev-6727-g e4608f7450 [DESK][SHELLBTRFS] Fix typo in WIN32_NO_STATUS (#5764)

0.4.15-dev-6721-g f1cff6ef27 [DESK] Remove deprecated code. (MSVC hack) [no PR]

partially pick 0.4.15-dev-6765-g fd1e5d53a5 [DESK] Cleanup some functions.

0.4.14: Strip yet unused+unfinished IDD_THEMES, older rls-branches didn't have that. And it's still unused and inaccessible in releases/0.4.14
0.4.14 and older: Strip en-GB.rc
0.4. 9 and older: Strip he-IL.rc, because we don't have RTL-support there yet

This also ports back translations, tons of accelerator-fixes and a lot of small tweaks to the rc-controls-dimensions. especially on the screensaver-page.

desk.cpl shrinks on all branches:
desk.cpl master          RosBEWin2.2.2 GCC8.4.0 dbg x86             650.240 (0.4.15-dev-8636-g945e856)
desk.cpl releases/0.4.14 RosBEWin2.2.2 GCC8.4.0 dbg x86  587.776 -> 555.008
desk.cpl releases/0.4.14 RosBEWin2.1.6 GCC4.7.2 dbg x86  564.736 -> 531.968
desk.cpl releases/0.4.13 RosBEWin2.1.6 GCC4.7.2 dbg x86  546.816 -> 530.432
desk.cpl releases/0.4.12 RosBEWin2.1.6 GCC4.7.2 dbg x86  539.136 -> 523.776
desk.cpl releases/0.4.11 RosBEWin2.1.6 GCC4.7.2 dbg x86  539.136 -> 523.776
desk.cpl releases/0.4.10 RosBEWin2.1.6 GCC4.7.2 dbg x86  539.136 -> 523.776
desk.cpl releases/0.4. 9 RosBEWin2.1.6 GCC4.7.2 dbg x86  539.136 -> 515.584
desk.cpl releases/0.4. 8 RosBEWin2.1.6 GCC4.7.2 dbg x86  539.136 -> 515.584
desk.cpl releases/0.4. 7 RosBEWin2.1.6 GCC4.7.2 dbg x86  528.384 -> 504.832
2024-09-10 18:55:25 +02:00
.github Update pull request template with additional info 2017-11-06 19:28:12 +02:00
base [0.4.9][REGEDIT] Backports 2024-08-11, e.g. CORE-19576 2024-08-11 22:17:00 +02:00
boot [0.4.9][SHELL32][BOOTDATA] RC & Improve folder-options (2024-05-27) 2024-05-27 03:44:30 +02:00
dll [0.4.9][DESK][SHELLBTRFS] Backports 2024-09-10 (#7298)(#7213)(#6593)(#5764) 2024-09-10 18:55:25 +02:00
drivers [0.4.9][DD] Improve network driver infs 2024-06-20 02:45:42 +02:00
hal [HAL] Reset the stack pointer to the stack frame when calling second-entry interrupt handlers. CORE-14449 2018-04-13 09:04:52 +02:00
media [0.4.9] Backport: more flexibility for placing inf files 2024-06-17 23:04:15 +02:00
modules [0.4.9][CMD] Correctly honour the "short" path flag in %~var enhanced variables expansion (#5433) CORE-14096, [REACTOS] Cleanup CORE-18077 2024-06-02 20:22:34 +02:00
ntoskrnl [0.4.9][NTOS:MM] Fix Regression, "Precision" demo executable doesn't load CORE-12400 (#503), + follow-up (#5002) 2023-12-18 15:01:30 +01:00
sdk [0.4.9] Backport: more flexibility for placing inf files 2024-06-17 23:04:15 +02:00
subsystems [0.4.9][REACTOS] Optimize existing PNGs (#5486) (#5492) (#5506) 2023-09-08 19:28:01 +02:00
win32ss [0.4.9] Backport: more flexibility for placing inf files 2024-06-17 23:04:15 +02: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
.gitmessage [CONTRIBUTING] Update .gitmessage 2018-02-25 16:14:41 +02:00
.travis.yml [TRAVIS-CI] Increase the git clone depth a bit. 2017-10-19 22:33:24 +01:00
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] Disallow use of LOCATION. CORE-14509 2018-03-30 20:28:27 +02:00
configure.cmd [CONFIGURE] Add support for VS2017 Update 3. 2018-03-17 16:41:46 +01:00
configure.sh
CONTRIBUTING.md [CONTRIBUTING] Clean accidental garbage 2018-03-22 10:49:01 +02:00
COPYING
COPYING.ARM
COPYING.LIB
COPYING3
COPYING3.LIB
CREDITS [TRANSLATION] Translate Explorer into Finnish, by Lauri Ojansivu (#218) 2017-12-26 20:17:30 +01:00
Doxyfile
INSTALL [0.4.9][REACTOS] Backport "http://www.reactos" -> "https://reactos" and readme.txt 2023-03-19 12:41:27 +01:00
PreLoad.cmake
README.md [0.4.9][REACTOS] Backport "http://www.reactos" -> "https://reactos" and readme.txt 2023-03-19 12:41:27 +01:00
toolchain-clang.cmake
toolchain-gcc.cmake
toolchain-msvc.cmake [CMAKE/CLANG-CL] Force clang-cl's identity to be MSVC instead of the default Clang one as the latter results in skipping several MSVC related CMake checks/tasks. CORE-11799 2017-11-24 12:03:01 +01:00


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: https://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.