ReactOS has been in development since 1996. As of February 2022[update], it is still considered feature-incomplete alpha software, and is therefore recommended by the developers only for evaluation and testing purposes.[9][10] However, many Windows applications are currently working, such as Adobe Reader 9.3, GIMP 2.6, and LibreOffice 5.4.[11][12]
ReactOS is primarily written in C, with some elements, such as ReactOS File Explorer, written in C++. The project partially implements Windows API functionality and has been ported to the AMD64processor architecture.[13] ReactOS, as part of the FOSS ecosystem, re-uses and collaborates with many other FOSS projects,[14][15] most notably the Wine project, which presents a Windows compatibility layer for Unix-like operating systems.
History
Early development
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 had not been any builds released to the public by the end of 1997. As a result, the project members, led by then coordinator Jason Filby, joined together to revive the project. The revived project sought to duplicate the functionality of Windows NT.[16] 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.[17][18] The name ReactOS was coined during an IRC chat. 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.[6]
In 2002, the ReactOS Foundation was established in Moscow with Maxim Osowski and Aleksey Bragin as executive officers and Vladimir Bragin, Saveliy Tretiakov and Alexey Ivanov on the board of directors.[19] In 2015, the foundation was liquidated.[20]
Internal audit
In order to avoid copyright prosecution, ReactOS had to be expressly completely distinct and non-derivative from Windows, a goal that needed very careful work.[21] A claim was made on 17 January 2006 by developer Hartmut Birr on the ReactOS developers mailing list (ros-dev) that ReactOS contained code derived from disassembling Microsoft Windows.[22] The code that Birr disputed involved the function BadStack in syscall.S,[23] as well as other unspecified items.[24] 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.[25]
On 27 January, 2006, the developers responsible for maintaining the ReactOS code repository disabled access after a meeting was held to discuss the allegations. When approached by NewsForge, Microsoft declined to comment on the incident. Since ReactOS is a free and open-source software development project, the claim triggered a negative reaction from the free software community; in particular, Wine barred several inactive developers from providing contributions[citation needed] and formal high level cooperation between the two projects remained difficult as of 2006[update].[26] Contributions from several active ReactOS developers have been accepted post-audit, and low level cooperation for bug fixes has been still occurring.
In a statement on its website, ReactOS cited differing legal definitions of what constitutes clean-room reverse engineering as a cause for the conflict.[27] To avoid potential litigation, companies sometimes enact a policy where reimplementation based on disassembled code must be written by someone other than the person having disassembled and examined the original code.[28][29] ReactOS clarified its Intellectual Property Policy Statement requirements on clean room reverse engineering to avoid potential infringement of United States 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.[26] 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.[30]
Much of the assembly code that was allegedly copied has also been replaced as a natural progression in ReactOS development, by the developers having reimplemented the functionality in C for portability reasons.[citation needed]
Also, the 2004 leaked Windows source code[31] was not seen as legal risk for ReactOS, as the trade secret was considered indefensible in court due to broad spread.[32]
Axel Rietschin, who is a kernel engineer at Microsoft, claimed that he recognized some specific bits in the ReactOS kernel that are unlikely to result from a clean room reimplementation. He suggests that the project took source code from the Windows Research Kernel, which was licensed to universities and has been leaked multiple times. Internal data structures and variable names have the exact same name in both ReactOS and the research kernel.[33]
Google Summer of Code participation
Starting in 2006,[34] the ReactOS project participated in several Google Summers of Code. For example, in the GSoC 2011,[35] ReactOS mentored a student project which integrated lwIP into the network stack.[36] ReactOS has to date participated seven times in GSoC: 2006, 2011, 2016, 2017, 2018, 2019, and 2021.
Lobbying for support in Russia
Between 2007 and 2015, Russian ReactOS contributors representing the ReactOS Foundation made efforts at lobbying the Russian federal government. As of April 2019[update], these efforts have not yielded government support for ReactOS, and the Russia-based ReactOS Foundation has been dissolved since November 2015.[20]
Former ReactOS project coordinator Aleksey Bragin (left) showing ReactOS to Viktor Alksnis
In 2007, then State Duma member and chairman of Russian Center of Free Technologies, Viktor Alksnis met with project coordinator Aleksey Bragin, who gave a presentation and demonstration of the project, showing ReactOS running with Total Commander and Mozilla Firefox.[37]
In 2011, a demonstration was given to then president Dmitry Medvedev during a visit to a high school in Verhnerusskoe, Stavropol, attended by one of the development team members.[38]
On 1 April 2015, Bragin attended an expert meeting of the Russian Ministry of Communications on reducing Russia's dependency from proprietary software imports. Its minutes name the "creation of an open source operating system based on ReactOS for PCs, laptops and other mobile devices", as well as the "creation of an open source operating system for servers based on ReactOS",[40][41][42][43] placing it second among three named proposals.
Funding campaigns
On 1 May 2012, a €30,000 funding campaign was started to finance additional development projects.[44][45] At the end of the year, approximately 50% of the funding goal was achieved and it was decided to continue the funding campaign without deadlines.[46] The money went to ReactOS Deutschland e. V.. As the tax law in Germany for this form of a registeredvoluntary association (Eingetragener Verein) makes it problematic to pay developers directly;[47] indirect possibilities like stipends were evaluated.
Thorium Core Cloud Desktop project
When ReactOS was awarded as Project of the Month on SourceForge on June 2013, a crowdfunding campaign on Kickstarter was announced in an interview with the project's coordinator, Aleksey Bragin.[48] On 23 December 2013 the announced project was revealed as a Kickstarter campaign with the goal of US$120,000 was started.[49][50] The Thorium Core Cloud Desktop dubbed cloud computing service would use ReactOS as core and could allow the use of Windows compatible applications from mobile devices (like smartphones, tablets), workstations, or any other connected device. On 21 February 2014, fundraising ended short of the target amount, with $48,965 of $120,000 raised, resulting in no transferred money.[51]
ReactOS Community Edition
In April 2014, the ReactOS project announced an Indiegogo campaign to launch ReactOS Community Edition, a version of ReactOS based on the 0.4 release. The flexible funding campaign had a goal of $50,000 with additional stretch goals beyond that.[52] Development of ReactOS Community Edition would be community-centric, with ReactOS users voting and funding to decide which software and hardware drivers the project will aim to support.[53][54] On 1 June 2014, the flexible crowdfunding campaign on Indiegogo ended, raising $25,141 for the development of the community edition,[55][56] and the voting process to support hardware and software was started shortly thereafter.[57]
ReactOS Hackfest
First video of printing from ReactOS
The ReactOS project organized a hackfest from 7 to 12 August 2015, in the German city of Aachen.[58][59][60] The Hackfest resulted in many features being added to ReactOS.
The second hackfest was organized by the ReactOS project from 14 to 18 August 2017, in the German city of Cologne.[61]
The third and fourth hackfests were organized by the ReactOS project from 16 to 21 August 2018 and from 15 to 20 August 2019 in Berlin respectively.[62][63]
USB support for mice, keyboard, and storage devices; rewritten session management; AHCI support with updated UniATA driver; alternate ReactOS Memory Management Module has taken over all memory management responsibilities except for sections; preliminary support for debugging ReactOS components using WinDbg; improvements based on results from the AutoHotkey application functionality test suite; Bugfixes based on running Driver Verifier on several bundled drivers[83]
Improved USB support, new file explorer shell and theming, improved VirtualBox and Virtual PC support, ext2 read/write support, NTFS read support and improved networking support
Improved version of the applications manager RAPPS, implementation of the "Quick-Launch" toolbar in the explorer; various bug fixes in the filesystem drivers, improvements in the RDBSS/RXCE and NFS support.
Drivers for battery management (its icon is located in the taskbar, in the bottom right of the screen, next to the clock). Support for updating an existing ReactOS installation. Improved SATA support.
This section needs expansion. You can help by adding to it. (October 2018)
ReactOS 0.4.14 desktop: left Start Menu and right ReactOS's own File ExplorerNew shell in ReactOS (v0.4.0 and newer)Command Prompt, Spider Solitaire, Calculator and WineMineDevice Manager in ReactOS 0.4.14
ReactOS is primarily written in C, with some elements, such as ReactOS Explorer and the sound stack, written in C++. The project compiles using both MinGW and Microsoft Visual Studio, and contributes to the development of the build systems used through the submission of patches to its components.[114]
The developers aim to make the kernel and usermode application programming interface (API) more compatible with Windows NT version 5.2 (Windows Server 2003) and to add support for more applications and hardware, with plans to target newer versions of Windows as development matures.[115]DirectX support is undertaken through ReactX, an in-house implementation. 2D and OpenGL 3D hardware-accelerated rendering is done natively, while other drawing functionality such as Direct3D is redirected to OpenGL as a stopgap solution, mostly using Wine's code such as WineD3D.[13][116]
The development progress is influenced by the size of the development team and the level of experience among them. As an estimate of the effort required to implement Windows 7, Microsoft employed 1,000 or so developers, organized into 25 teams, with each team averaging 40 developers.[117] As of 2 September 2011[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 Apache Subversion since its inception.[118] 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.[119]
While ReactOS targets currently mainly the x86/AMD64PC platform,[120] an effort to port to the ARM architecture was at one point "under way",[13] while it did not produce much functionality and was abandoned[121] along with a port to PowerPC, that is no longer actively maintained.[9] Support for the Xbox and the NEC PC-9800, a variant IA-32 architecture, was added through the use of an architecture-specific HAL.[119][107][3] Improved 64-bit support for ReactOS is "being worked on", however, development seems to be going slowly.[122]
Collaboration and reuse
While ReactOS has the aim to build a Windows-compatible kernel as open-source software, much of the surrounding required functionality to create a complete OS is already available in the greater open-source ecosystem.
When available and possible, ReactOS therefore builds on and collaborates with already existing open-source projects.[14]
Conversely, projects like Wine,[15] and formerly Captive NTFS[123] and Longene re-use the open-source ReactOS code-base as well.[124]
ReactOS's network stack is built on 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.[129] Later, lwIP was integrated into the ReactOS network stack.[36] Windows network services like LSASS, SAM, NETLOGON, and print spooling are already available as open-source alternative by the Samba/Samba TNG project. A fork of rdesktop is used as an implementation of a client software for Microsoft's proprietary Remote Desktop Protocol.
Wine cooperation
A simplified architecture diagram of ReactOS, with Wine dependencies indicated by the Wine logo. White boxes denote third-party binary software. Green boxes are "userland" components, red are kernel components.
The ReactOS and the Wine projects share the goal to run binary Windows software natively and can therefore share many dependencies and development.[15][130] ReactOS uses portions of the Wine project so that it can benefit from Wine's progress in implementing the Win32API.[130] While Wine's NTDLL, USER32, KERNEL32, GDI32, and ADVAPI32 components cannot be used directly by ReactOS due to architectural differences, code snippets of them and other parts can be shared between both projects. The kernel is developed by ReactOS separately as Wine relies here on existing Unix-like kernels.[114][119]
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.[131]
ReactOS NG (2015) – aiming for compatibility with Windows 8[143]
Greentea OS (2016-2018) – aiming for accelerated and simplified development[144][145]
Reception
Various people have acknowledged ReactOS and the implications of having a viable open-source drop-in replacement for Windows.[6] A 2004 article and interview of the German weekly magazine Der Spiegel describes ReactOS as directed at Windows users who want to renounce use of proprietary commercial software without having to switch to Linux.[6]DistroWatch, a Linux distribution's monitoring Web site, also lists ReactOS and describes it as "a free and open-source operating system based on the best design principles found in the Windows NT architecture."[146]
In his column for Free Software Magazine, David Sugar noted in 2006 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.[8]PC Magazine columnist John C. Dvorak remarked in 2008 that the Windows NT architecture had remained largely unchanged, making it an ideal candidate for cloning, and believed that ReactOS could be "a bigger threat than Linux to Microsoft's dominance".[7] In response to Dvorak's column, ZDNet technology journalist Dana Blankenhorn noted in 2008 that a lack of corporate sponsors and partners had rendered the project harmless to Microsoft.[147][148] Echoing this, Thom Holwerda of OSNews in 2009 categorized ReactOS under a family of hobby operating systems maintained only by small groups of developers working in their spare time, lacking the financial support of more mainstream operating systems and the legacy of formerly mainstream ones such as RISC OS.[149]
In October 2015, a Network World review of ReactOS v0.3.17 noted "It's just like running Windows 2000" and praised the application package manager, a feature the original Windows is missing.[150]
Jesse Smith from DistroWatch Weekly reviewed ReactOS v0.4.9, and noted that ReactOS "ultimately had a similar problem: limited hardware support" and is not yet a stable operating system.[151]
Awards
The ReactOS Project won on the annual Seliger Youth Forum "The Best Presentation" award with 100,000 Russian rubles ($2700) in 2011, attended by Alexander Rechitskiy, one of the development team members.[152]
ReactOS was a featured project on SourceForge for the weeks beginning on 27 February 2012, 25 April 2013,[153] and several others. It was Project of the Month on SourceForge for June 2013[154] and February 2019.[155]
eComStation and ArcaOS, two independent proprietary continuations of OS/2 (source code licensed from IBM), which IBM co-created with Microsoft and shares some design elements with MS-DOS and Windows
^ abcdRoyal, Simon (16 February 2014). "ReactOS: A Windows Compatible Alternative OS". lowendmac.com. Retrieved 10 January 2016. While the main core of ReactOS is built from scratch, it has some dependencies on existing software and protocols. It uses parts of Wine, networking in the form of lwIP, USB from Haiku, as well as FreeType, Mesa3D, and UniATA.
^ ab"ReactOS gets USB Stack, with Help from Us". Haiku. 20 February 2012. Retrieved 2 January 2016. The ReactOS and Haiku projects have had a friendly working relationship for several years now, with each group helping the other whenever possible.
^ abcVincent, Brian (15 May 2004). "Interview with Steven Edwards". winehq.com. Retrieved 6 January 2016. BV: Wine and ReactOS have had a mutually beneficial relationship. Is there anything Wine could do different that would help ReactOS development?[...] BV: You guys have certainly contributed a lot of your work back to Wine, including some of the utilities you've written. For instance, the task manager was recently ported from ReactOS. Do you guys have any plans in the works for developing more tools? Steven: I really want to see a solitaire clone make it in to Wine and ReactOS.[...] At some point we are going to have to develop replacement components for everything in Windows so if there is a program that Wine needs and ReactOS implements it then I will try to make sure it's released under a compatible license.
^Hancock, Terry (29 August 2008). "What if copyright didn't apply to binary executables?". Free Software Magazine. Retrieved 1 November 2020. (…) ReactOS aims to run actual Windows binary executable programs. This means that ReactOS must implement the entire Windows environment. Functions must do exactly what their Windows counterparts would do. In other words, like our notional parallel stew recipes, ReactOS and Windows should be functionally identical. In order to avoid copyright prosecution, though, ReactOS must be expressly completely distinct and non-derivative from Windows. This is a careful tightrope walk! ReactOS is a free, clean room re-implemented drop-in replacement for Windows. So, consider this, especially regarding extremely simple library calls: is it legal for ReactOS to produce identical binary code to Windows?
^Birr, Hartmut (18 January 2006). "Bye bye". ros-dev (Mailing list). Retrieved 3 January 2009.
^Schwartz, Mathew (12 November 2001). "Reverse-Engineering". Computerworld.com. Retrieved 23 June 2013. To protect against charges of having simply (and illegally) copied IBM's BIOS, Phoenix reverse-engineered it using what's called a "clean room," or "Chinese wall", approach. First, a team of engineers studied the IBM BIOS — about 8KB of code — and described everything it did as completely as possible without using or referencing any actual code. Then Phoenix brought in a second team of programmers who had no prior knowledge of the IBM BIOS and had never seen its code. Working only from the first team's functional specifications, the second team wrote a new BIOS that operated as specified.
^Hogle, Sean (23 October 2008). "Clean Room Defeats Software Infringement Claim in US Federal Court". Retrieved 23 May 2013. [...] dirty room reverse engineering should be done in conjunction with clean room development by using two physically and electronically isolated teams where one team does dirty room reverse engineering and the other does clean room development. If a dirty room team exists, the clean room engineers can write a description of the portion of the specification that needs elaboration or clarification. The dirty room engineers then use that request to create additional functional specifications or tests.
^Bragin, Aleksey (18 September 2007). "Audit". ros-dev (Mailing list). Retrieved 3 January 2009.
^Reset, Reboot, Restart, legal issues and the long road to 0.3 "Now as for the issue of leaked source code, I want to try to put all fears to rest. We don't know what the legal ramifications are for someone downloading and having leaked code, as the party that maintains copyright ownership of that code might still try to claim Trade Secrecy on information contained in the sources in a court of law. It is our point of view that the source code leaks of Windows have been spread to a broad enough audience that it would be impossible to claim the product is still under Trade Secrecy." on reactos.org by Steven Edwards (27 January 2006)
^"Google Summer of Code 2006". This is a page lists the students and organizations that participated in the Google Summer of Code 2006 program. [...] ReactOS
^"January 2013 Meeting Minutes". 7 February 2013. Archived from the original on 3 April 2013. Retrieved 19 June 2013. Late last year the German foundation learned that the contracts it was issuing for developers might not be compliant with German regulations involving non-profits. Due to this, the German foundation needed to temporarily halt payment to developers and consult with tax attorneys to determine how to proceed in a compliant manner.
^"Sourceforge POTM June 2013". Sourceforge.com. 17 June 2013. Retrieved 17 June 2013. Well I don't want to spread too many rumors, but I can say that we do have something in the works. If all goes well, it's going to be announced within a week. While I cannot go into too many details, I can say that it involves Kickstarter and what we believe to be a viable commercial product based off of [sic] ReactOS.
^Linux unified kernel 0.2.4.1 "The LUK project does not develop the Windows and the Linux userland libraries. Those libraries are offered by the Wine (or Microsoft Windows/ReactOS) project and the Linux project."
^reactos on distrowatch.comReactOS is a free and open-source operating system based on the best design principles found in the Windows NT architecture. (accessed January 2016)
^Lunduke, Bryan (28 October 2015). "Linux cousins Part 2: Reviewing ReactOS, the Open Source version of Windows". Network World. Retrieved 4 January 2016. In short: It's just like running Windows 2000. Except Free and Open Source. Which makes makes it feel both awesome. And dirty. And profound... also infuriating. If I'm honest, I really don't know how ReactOS makes me feel. But it's damned impressive that it exists and works so well. Beyond simply being Open Source, ReactOS has one cool features that Windows never really provided properly: An application manager that is laid out and structured like a Linux package manager. From within it you can even install a large number of FOSS software staples, such as Firefox, LibreOffice, and GIMP.
^"Russian president asked to Fund Windows Open Source Clone". Jordan Open Source Association. 12 September 2011. Archived from the original on 1 February 2014. Retrieved 18 June 2013. At the forum, ReactOS won "The Best Presentation" award and a grant of 100,000 rubles (approximately 2,400 JDs). In addition, around twenty large investors became interested in the project.
