ReactOS

ReactOS 0.3.14 Desktop
Company / developer	ReactOS Foundation
Programmed in	C, C++
OS family	Microsoft Windows-like (Windows NT-like)
Working state	Alpha
Source model	Free and open source software
Initial release	0.0.7 / July 20, 1998 (1998-07-20)
Latest stable release	0.3.14 / February 7, 2012; 4 months ago  (2012-02-07)
Latest unstable release	(daily)
Marketing target	Personal computing
Available language(s)	Multi-lingual
Update method	Re-Installation
Supported platforms	IA-32, x86-64
Kernel type	Hybrid
Default user interface	Graphical (ReactOS Explorer)
License	GNU GPL, LGPL and BSD licenses[1]
Official website	www.reactos.org

ReactOS is an open source computer operating system intended to be binary compatible with application software and device drivers made for Microsoft Windows NT versions 5.x and up (Windows 2000 and its successors). A spin-off of a previous attempt to clone Windows 95, development started in early 1998, and has continued with the incremental addition of features already found in Windows.

ReactOS is primarily written in C, with some elements, such as ReactOS Explorer, written in C++. The project has been ported to the ARM and AMD64 processor architectures, and partially implements Windows API functionality. The latter is assisted by including parts from the Wine compatibility layer for Unix-like operating systems, but other functionality is implemented by the developers themselves. However, progress has been hampered by a lack of developers with the relevant skill-sets.

An extensive code audit is in place to protect against legal problems, such that implementation of the Windows API is only done by means of a complete clean room reverse engineering process. This has been in place following claims made in 2006 by a former developer that the project contains disassembled assembly code from Windows, an allegation that has had no adverse legal consequences to the project.

ReactOS has been noted for its information on undocumented Windows APIs and more generally as an open-source drop-in replacement for Windows. "The main goal of the ReactOS project is to provide an operating system which is binary compatible with Windows ... such that people accustomed to the familiar user interface of Windows® would find using ReactOS straightforward. The ultimate goal of ReactOS is to allow you to remove Windows® and install ReactOS without the end user noticing the change."^[2]

Etymology[link]

The name ReactOS was coined by project founder Jason Filby, an Oracle developer from Durban, South Africa. While the term "OS" stood for Operating System, the term "react" referred to the group's dissatisfaction with - and reaction to - Microsoft's monopolistic position.^[3]

History[link]

Early development: FreeWin95 to ReactOS[link]

Around 1996, a group of free and open source software developers started a project called FreeWin95 to implement a clone of Windows 95. The project stalled in discussions of the design of the system.

While FreeWin95 had started out with high expectations, there still hadn't been any builds released to the public by the end of 1997. As a result, the project members, led by coordinator Jason Filby, joined together to revive the project. The revived project sought to duplicate the functionality of Windows NT. In creating the new project, a new name, ReactOS, was chosen. The project began development in February 1998 by creating the basis for a new NT kernel and basic drivers.^[4]

Internal audit[link]

A claim was made on January 17, 2006 by now former developer Hartmut Birr on the ReactOS Developers mailing list (ros-dev) that ReactOS contained code derived from disassembling Microsoft Windows.^[5] The code that Birr disputed involved the function BadStack in syscall.S^[6] as well as other unspecified items.^[7] Comparing this function to disassembled binaries from Windows XP, Birr argued that the BadStack function was simply copy-pasted from Windows XP, given that they were identical. Alex Ionescu, the author of the code, asserted that while the Windows XP binary in question was indeed disassembled and studied, the code was not merely copy-pasted, but reimplemented; the reason why the functions were identical, Ionescu claimed, was because there was only one possible way to implement the function.^[8]

On January 27, 2006, the developers responsible for maintaining the ReactOS code repository disabled access after a meeting was held to discuss the allegations. However, when approached by NewsForge, Microsoft declined to comment about the incident. Since ReactOS is a free and open source software development project, the claim triggered a negative reaction by the free software community; in particular, Wine barred several now inactive developers from providing contributions and formal high level cooperation between the two projects still remains difficult.^[9] Contributions from several active ReactOS developers, however, have been accepted post-audit, and low level cooperation for bug fixes still occurs.

In a statement on its website, ReactOS cited differing legal definitions of what constitutes clean-room reverse engineering as a cause for the conflict, as some countries, including the United States, require that reimplementation of disassembled code be written by someone other than the person having disassembled and examined the original code^{[citation needed]}, whereas other countries allow both tasks to be performed by the same individual. Consequently, ReactOS clarified that its Intellectual Property Policy Statement requirements on clean room reverse engineering conform to US law. An internal source code audit was conducted to ensure that only clean room reverse engineering was used, and all developers were made to sign an agreement committing them to comply with the project's policies on reverse engineering.^[9] Contributors to its development were not affected by these events, and all access to the software development tools was restored shortly afterward. In September 2007, with the audit nearing completion, the audit status was removed from the ReactOS homepage. Though the audit was completed, specific details were not made public as it was only an internal effort to ensure compliance with the project's own policies.^[10] Much of the assembly code that was allegedly copied has also been replaced as a natural progression in ReactOS development, with developers having reimplemented the functionality in C for portability reasons.

Version history[link]

Development[link]

ReactOS is primarily written in C, with some elements, such as ReactOS Explorer and sound stack, written in C++. The project relies on MinGW for compilation, and contributes to its development through the submission of patches to its components.^[16]

The developers aim to make the kernel more compatible with Windows NT version 5.2 (Windows Server 2003), the usermode APIs with Windows NT 6 (Windows Vista),^[17] and to add support for more applications and hardware. DirectX support is undertaken through ReactX, an in-house implementation. 2D hardware-accelerated rendering is done natively, while other drawing functionality is redirected to OpenGL as a stopgap solution.^[18]

Development progress is influenced by the size of the development team and the level of experience amongst them. As an estimate of the effort required to implement the Windows API, there are 1000 or so developers who worked on Windows 7 alone, organized into 25 teams, with each team averaging 40 developers.^[19] As of 2 September 2011 (2011 -09-02)^[update], in the ReactOS entry in Ohloh, the page followed through the "Very large, active development team" link lists 33 developers who have contributed over a 12-month period and a cumulative total of 104 present and former users who have contributed code to the project via Subversion since its inception.^[20] In his presentation at Hackmeeting 2009 in Milan, ReactOS developer Michele C. noted that most of the developers learn about Windows architecture while working on ReactOS and have no prior knowledge.^[21]

Dependencies[link]

ReactOS makes use of code from other projects where possible, so that developers can avoid duplicating readily available functionality and focus on binary compatibility with Windows.

Wine[link]

A simplified architecture diagram of ReactOS, with Wine dependencies indicated with the Wine logo.

ReactOS uses portions of the Wine project so that it can benefit from Wine's progress in implementing the Win32 API.^[22] Wine's NTDLL, USER32, KERNEL32, GDI32 and ADVAPI components cannot be used by ReactOS due to architectural differences, but the other parts of the code can be shared between both projects. Components that are not available from Wine, such as the kernel, are developed separately.^[16][21]

Separately, the experimental Arwinss branch was created as an alternative means to improve USER32 and GDI32 support through an alternative implementation of the Win32 API. Whereas ReactOS's original Win32 subsystem was closely modeled after its equivalent in Windows, Arwinss combines the architecture of that subsystem with the corresponding implementation in Wine. To this end, Arwinss uses Wine's GDI32 and USER32 libraries with few changes to take fuller advantage of Wine's existing software compatibility. Arwinss also allows the user to optionally use a remote X server instead of a local display.^[23]

Networking[link]

As part of its participation in the Google Summer of Code held in 2011,^[24] ReactOS mentored a student project which integrated lwIP into the network stack.^[25] This replaced a previous implementation built from an import of the TCP portion of OSKit's port of the network stack in FreeBSD, along with an internally developed implementation for packet-oriented protocols like IP.^[26]

USB[link]

ReactOS makes use of the USB stack from Haiku both as a reference and as a foundation for its USB support. The data structures used to define USB requests and messages were adapted to help plug holes in ReactOS' own USB stack.^[27]

Other[link]

FreeType is used for the rendering of fonts in the GUI, while Mesa 3D provides OpenGL rendering.^[16] Serial ATA drivers are provided by UniATA. The project has also experimented with using the FullFAT library in its rewrite of its FAT Installable File System.^[28]

Architecture support[link]

ReactOS has been partially ported to the AMD64 and ARM architectures.^[18] Support for the Xbox, a variant IA-32 architecture, was added through the use of an architecture-specific HAL,^[21] although this, along with a port to PowerPC, are no longer actively maintained.^[29]

Usability[link]

At Chemnitz 2010, the ReactOS development team considered ReactOS 0.3.12 as alpha-stage software, not feature-complete and not suitable for everyday use.^[29] The kernel is incomplete, and only a few Windows applications run without problems. However, the operating system is considered quite stable, and has a very short installation and boot time.

The future 0.4 release series will also be in alpha stage; the 0.5 release series will be marked as beta, suitable for everyday use but not subjected to thorough quality control.

Reception[link]

ReactOS project coordinator Aleksey Bragin (left) shows ReactOS to Viktor Alksnis.

Dmitry Medvedev is given a demonstration of ReactOS.

Various people have acknowledged ReactOS and the implications of having a viable open-source drop-in replacement for Windows.

In his column for Free Software Magazine, David Sugar noted that ReactOS would allow the use of applications depending on older versions of Windows whose APIs have been deprecated. He also recognized its potential to expand the total deployed base of free software, and as a resource for developers wanting to know undocumented Windows APIs in the course of writing portable applications.^[30] PC Magazine columnist John C. Dvorak remarked that the Windows NT architecture has remained largely the same to this day, making it an ideal candidate for cloning, and believes that ReactOS could be "a bigger threat than Linux to Microsoft's dominance".^[31] Indeed, Aleksey Bragin has mentioned in a comment to German weekly magazine Der Spiegel that ReactOS is directed at Windows users who want to renounce use of proprietary commercial software without having to switch to Linux.^[3]

However, ReactOS has been observed to have challenges. In response to Dvorak's column, ZDNet technology journalist Dana Blankenhorn has noted that a lack of corporate sponsors and partners has currently rendered the project harmless to Microsoft.^[32][33] Echoing this, Thom Holwerda of OSNews categorized ReactOS under a family of hobby operating systems that are maintained only by small groups of developers working in their spare time, and lack the financial support of more mainstream operating systems as well as the legacy of formerly mainstream ones such as RISC OS.^[34]

Demonstrations of the operating system have been given, mainly to Russian political figures. Viktor Alksnis has met with current project coordinator Aleksey Bragin, who gave a presentation and demonstration of the project, showing ReactOS running with Total Commander and Mozilla Firefox.^[35] Dimitry Medvedev was also given a demonstration during a visit as President of Russia to a high school in Verhnerusskoe, Stavropol, attended by one of the development team members.^[36]

Related projects[link]

• ReactOS shares some dependencies with Wine.
• Samba/Samba TNG implements LSASS, SAM, NETLOGON, Print spooling and other Windows network services.
• NDISwrapper recreated a partial Windows NT kernel inside a Linux Kernel making it possible to execute modern Windows drivers in Linux. It consists of a NTOSKRNL API, a basic WDM controller, and a set of Windows call wrappers such as Wireless/NDIS/USB/PnP to Linux APIs.
• NTFS-3G, NTFS driver for Linux, Mac OS X, FreeBSD, NetBSD, OpenSolaris, QNX, Haiku, and other operating systems.

System requirements[link]

• x86-compatible processor, Pentium or later
• 24 MB RAM (128MB recommended)
• IDE hard drive of at least 150 MB
• FAT16/FAT32 Boot partition
• 2 MB VGA graphics adapter
• CD-ROM drive
• Standard keyboard
• PS/2 Compatible mouse or Microsoft Mouse-compatible serial mouse

See also[link]

Free software portal

• coLinux
• E/OS
• Freedows OS
• HX DOS Extender
• Binary code compatibility

References[link]

External links[link]

Wikimedia Commons has media related to: ReactOS

• Official website
• ReactOS on SourceForge.net
• ReactOS Explorer
• Screenshots of ReactOS
• Interview with Steven Edwards of ReactOS and Wine (WineHQ)
• Detailed review of ReactOS
• A reaction to ReactOS – David Sugar