71bffdcde9
cb4c1dc msi: Always return MSIDBSTATE_ERROR when MsiGetDatabaseState is called from a custom action. 04d242d msi: Create dummy thread to initialize COM for custom actions. 52fbaeb msi: Add support for ActionText table. 700ebc8 msi: Return the correct values from dialogs. a3dd99c msi: Return the current date and time. 4ccc82a msi: Use the Error table for more messages. 77e3d33 msi: Use MsiProcessMessage() to send error messages. 3ca2dfe msi: Avoid uninitialized pointer access on error path (Coverity). d631714 msi: Add a trailing linefeed to a FIXME() trace. 39c2ff0 msi: Send the dialog created message in dialog_create(). 14f865e msi: Don't queue a parent dialog to be shown in EndDialog. 8826584 msi: Process ShowDialog/EndDialog after all other control events. 44fb23d msi: Don't set _BrowseProperty. b4c39f4 msi: Avoid a null pointer dereference. 51bd884 msi: Properly parse empty format strings. 16f0dff msi: Return the correct values from custom actions. f348c7c msi: Rewrite dump_record(). f9c68df msi: Use the given record for INSTALLMESSAGE_ACTIONDATA. c788ed85 msi: Provide the result of the last action. 1505912 msi: Allow setting NULL in MsiSetInteger(). f9f53fe msi: Correctly format the template field for MsiProcessMessage(). 3033dae msi: Implement UI messages for dialogs. 5da9250 msi: Don't increment the refcount when creating dialogs. 48237e2 msi: Add a basic internal UI implementation. 39b841d msi: Fix a buffer overrun. 9032279 msi: Implement UI messages in MsiOpenPackage(). bcc4a04 msi: Implement INSTALLMESSAGE_INITIALIZE and INSTALLMESSAGE_TERMINATE. a388906 msi: Send the correct UI messages upon calling MsiDoAction(). de5246a msi: Don't reimplement record formatting. 4e49ae3cc msi: Pass the given record to the callback. df31a7c msi: Store string and record callback data separately. cef6799 msi: Use an external UI record handler before a string handler. |
||
---|---|---|
base | ||
boot | ||
dll | ||
drivers | ||
hal | ||
media | ||
modules | ||
ntoskrnl | ||
sdk | ||
subsystems | ||
win32ss | ||
.gitattributes | ||
.gitignore | ||
apistatus.lst | ||
CMakeLists.txt | ||
configure.cmd | ||
configure.sh | ||
COPYING | ||
COPYING.ARM | ||
COPYING.LIB | ||
COPYING3 | ||
COPYING3.LIB | ||
CREDITS | ||
Doxyfile | ||
INSTALL | ||
PreLoad.cmake | ||
README.md | ||
toolchain-clang.cmake | ||
toolchain-gcc.cmake | ||
toolchain-msvc.cmake |
ReactOS Project
Quick Links
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
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 use run configure
script in the directory you want to have builds. 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 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 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.
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. Also see 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.