Jump to content

ReactOS

From Wikipedia, the free encyclopedia
(Redirected from ROS Explorer)

Not to be confused with React (JavaScript library).
ReactOS
ReactOS 0.4.14 desktop
DeveloperCommunity contributors
The ReactOS developers
Written inC, C++[1]
OS familyWindows NT-like
Working stateAlpha
Source modelOpen-source[2]
Initial release(partial) 1998; 26 years ago (1998)
Latest preview0.4.14[3] / 16 December 2021; 2 years ago (2021-12-16)[3]
Repository
Marketing targetPersonal computing
Update methodCD-ROM ISO image, QEMU image, VirtualBox image, VMware image, or source code[4]
PlatformsIA-32, x86-64
Kernel typeHybrid (designed to be compatible with Windows NT family)
Influenced byMicrosoft Windows
Default
user interface		Graphical (ReactOS Explorer)
LicenseGPL-2.0-or-later[a]
Official websitewww.reactos.org
ReactOS 0.4.14 running the Firefox web browser

ReactOS is a free and open-source operating system for i586/amd64 personal computers intended to be binary-compatible with computer programs and device drivers developed for Windows Server 2003 and later versions of Microsoft Windows.[5][6] ReactOS has been noted as a potential open-source drop-in replacement for Windows[7][8][9] and for its information on undocumented Windows APIs.[10]

ReactOS has been in development since 1996. As of April 2024, it is still considered feature-incomplete alpha software, and is therefore recommended by the developers only for evaluation and testing purposes.[11][12] However, many Windows applications are working, such as Adobe Reader 9.3, GIMP 2.6, and LibreOffice 5.4.[13][14]

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 AMD64 processor architecture.[15] ReactOS, as part of the FOSS ecosystem, re-uses and collaborates with many other FOSS projects,[16][17] most notably the Wine project, which presents a Windows compatibility layer for Unix-like operating systems.

History

[edit]

Early development

[edit]

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 on 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.[18] 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.[19][20] 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.[8]

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.[21] In 2015, the foundation was liquidated.[22]

Internal audit

[edit]

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.[23] 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.[24] The code that Birr disputed involved the function BadStack in syscall.S,[25] as well as other unspecified items.[26] 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.[27]

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.[28]

In a statement on its website, ReactOS cited differing legal definitions of what constitutes clean-room reverse engineering as a cause for the conflict.[29] 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.[30][31] 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.[28] 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.[32]

Also, the 2004 leaked Windows source code[33] was not seen as legal risk for ReactOS, as the trade secret was considered indefensible in court due to broad spread.[34]

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.[35]

Google Summer of Code participation

[edit]

Starting in 2006,[36] the ReactOS project participated in several Google Summers of Code. For example, in the GSoC 2011,[37] ReactOS mentored a student project which integrated lwIP into the network stack.[38]

Lobbying for support in Russia

[edit]

Between 2007 and 2015, Russian ReactOS contributors representing the ReactOS Foundation made efforts at lobbying the Russian federal government. As of April 2019, these efforts have not yielded government support for ReactOS, and the Russia-based ReactOS Foundation has been dissolved since November 2015.[22]

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.[39]
  • 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.[40]
  • On 31 July 2012, Vladimir Putin was also given a demonstration during his visit as President of Russia to Seliger Youth Forum, attended by Marat Karatov, one of the development team members.[41]
  • 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",[42][43][44][45] placing it second among three named proposals.

Funding campaigns

[edit]

On 1 May 2012, a €30,000 funding campaign was started to finance additional development projects.[46][47] 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.[48] The money went to ReactOS Deutschland e. V.. As the tax law in Germany for this form of a registered voluntary association (Eingetragener Verein) makes it problematic to pay developers directly;[49] indirect possibilities like stipends were evaluated.

Thorium Core Cloud Desktop project

[edit]

When ReactOS was awarded as Project of the Month on SourceForge in June 2013, a crowdfunding campaign on Kickstarter was announced in an interview with the project's coordinator, Aleksey Bragin.[50] On 23 December 2013 the announced project was revealed as a Kickstarter campaign with the goal of US$120,000 was started.[51][52] 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.[53]

ReactOS Community Edition

[edit]

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.[54] 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.[55][56] On 1 June 2014, the flexible crowdfunding campaign on Indiegogo ended, raising $25,141 for the development of the community edition,[57][58] and the voting process to support hardware and software was started shortly thereafter.[59]

ReactOS Hackfest

[edit]
First video of printing from ReactOS

The ReactOS project organized a hackfest from 7 to 12 August 2015, in the German city of Aachen.[60][61][62] 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.[63]

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.[64][65]

Release history

[edit]
System version Release date Release information
Old version, no longer maintained: 0.3.0 2006-08-27[66] First version to officially support networking
Old version, no longer maintained: 0.3.1 2007-03-10[67] Program manager included, start of kernel rewrite
Old version, no longer maintained: 0.3.2 skipped Branch created but never released[68]
Old version, no longer maintained: 0.3.3 2007-09-12[68] Kernel and win32k improvements
Old version, no longer maintained: 0.3.4 2008-01-22[69] Registry support rewrite, remote desktop client and Plug and Play
Old version, no longer maintained: 0.3.5 2008-06-30[70] Bug fixes only
Old version, no longer maintained: 0.3.6 2008-08-06[71] RTL support
Old version, no longer maintained: 0.3.7 2008-11-04[72] Improved x86-64; MSVC, new stacks
Old version, no longer maintained: 0.3.8 2009-02-04 Introduced PSEH and multi-partition HDD support in live CD[citation needed]
Old version, no longer maintained: 0.3.9 2009-04-26[73] 24 MB minimum RAM, faster hyperspace mapping, initial sound support
Old version, no longer maintained: 0.3.10 2009-07-05[74] Initial SATA support, USB keyboard/mouse support, Paint clone, initial MSVC.[75][76]
Old version, no longer maintained: 0.3.11 2009-12-16[77] Kdcom rewrite; Chinese/Korean fonts; compatibility updates; sound system improvements
Old version, no longer maintained: 0.3.12 2010-10-20[78] Trap handler rewrite; timer and message handling rewrite; NMI support; SxS support; partial EMS support[79]
Old version, no longer maintained: 0.3.13 2011-03-22[80] Heap manager rewrite, improved SATA support, fixed graphics issues[81]
Old version, no longer maintained: 0.3.14 2012-02-07[82] ACPI enabled by default, WiFi support (unencrypted and WEP), theme support, new TCP/IP driver (LwIP), MSVC compatibility, Scatter/Gather DMA operations supported, shell32 rewrite[83]
Old version, no longer maintained: 0.3.15 2013-05-30[84] 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[85]
Old version, no longer maintained: 0.3.16[86] 2014-02-06[87] CSRSS rewrite; theme support improved; network card driver for the RTL8139, allowing ReactOS to support newer versions of QEMU out of the box[88]
Old version, no longer maintained: 0.3.17[89] 2014-11-05[90] Inclusion of an NTVDM; font improvements;[91][92] bug fixes[93]
Old version, no longer maintained: 0.4.0[94] 2016-02-16[95] 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
Old version, no longer maintained: 0.4.1[96] 2016-05-17[97] Improved Activation Context, Btrfs support, improved Shell, USB bug fixes, support for Virtual Machine Shared Folders
Old version, no longer maintained: 0.4.2 2016-08-16[98] Improved Btrfs and extended file system support, ReiserFS and UFS/FFS, introduced .NET Framework 2.0 and 4.0 support, Shell fixes and improvements
Old version, no longer maintained: 0.4.3 2016-11-16[99] New Winsock library, initial sections support, usual bug fixes
Old version, no longer maintained: 0.4.4 2017-02-16[100] Initial print stack support, minor font fixes, usual improvements and bug fixes
Old version, no longer maintained: 0.4.5 2017-05-18[101] Improved rendering of fonts and font metrics, major fixes in kernel and drivers, Microsoft Office 2010 tested as functioning
Old version, no longer maintained: 0.4.6 2017-09-01[102] Several fixes for dual-boot issues, improved theming support, NFS driver added, several kernel and filesystem fixes
Old version, yet still maintained: 0.4.7 2017-12-06[103] 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.
Old version, yet still maintained: 0.4.8 2018-04-14[104] Balloon notifications, notification tray, shell autocompletion, a new NTFS driver, crash dump reporting and experimental support for NT6+ software.
Old version, yet still maintained: 0.4.9 2018-07-23[105] ReactOS is (again) self-hosting.
Old version, yet still maintained: 0.4.10 2018-11-06[106] Supports BTRFS booting.
Old version, yet still maintained: 0.4.11 2019-03-04[107] 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.
Old version, yet still maintained: 0.4.12 2019-09-23[108] Kernel improvements, window-snapping feature, font improvements, Intel e1000 NIC driver, user-mode DLLs, new themes.
Old version, yet still maintained: 0.4.13 2020-04-09[109] New USB stack, FAT driver from FreeLoader optimized, new software introduced: Accessibility Utility Manager.
Current stable version: 0.4.14 2021-12-16[3] "Send To" feature and Shell improvements, NEC PC-9800 boot support, ICMP improvements, Kernel improvements, NetKVM VirtIO bringup, miscellaneous changes & improvements
Future release: 0.4.15[110] — Support for x64 and UEFI, combines live CD and boot CD into a single GUI setup
Future release: 0.5.0[111] — Support for reading and writing the NTFS filesystem, support for the Windows Driver Model (including video card support), improvements to the printing subsystem and the DirectX Core.
Legend:
Old version, not maintained
Old version, still maintained
Latest version
Latest preview version
Future release

Features

[edit]
ReactOS 0.4.14 desktop: left Start Menu and right ReactOS's own File Explorer
New shell in ReactOS (v0.4.0 and newer)
Command Prompt, Spider Solitaire, Calculator and WineMine
Device Manager in ReactOS 0.4.14

Programs

[edit]

Commands

[edit]
See also: Comparison of DOS operating systems and List of DOS commands
The ReactOS reg command

The following is a non-exhaustive list of commands that are supported by the ReactOS Command Prompt.[112][113][114]

On-going national language development

[edit]

Presently, ReactOS has active development in: Czech, English, Dutch, Finnish, French, German, Hebrew, Hungarian, Indonesian, Italian, Japanese, Mandarin Chinese, Norwegian, Polish, Russian, Spanish, Swedish, Thai, Ukrainian.

Development

[edit]

ReactOS core development

[edit]

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.[118]

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.[119] 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.[15][120]

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.[121] As of 2 September 2011, 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.[122] 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.[123]

While ReactOS targets mainly the x86/AMD64 PC platform,[124] an effort to port to the ARM architecture was at one point "under way",[15] while it did not produce much functionality and was abandoned[125] along with a port to PowerPC, that is no longer actively maintained.[11] Support for the Xbox and the NEC PC-9800, a variant IA-32 architecture, was added through the use of an architecture-specific HAL.[123][109][3] Improved 64-bit support for ReactOS is "being worked on", however, development seems to be going slowly.[126]

Collaboration and reuse

[edit]

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.[16] Conversely, projects like Wine,[17] and formerly Captive NTFS[127] and Longene re-use the open-source ReactOS code-base as well.[128]

Hardware driver stack

[edit]

On the hardware driver side, for instance the UniATA project provides Serial ATA drivers for ReactOS.[12][129] The project has also experimented with using the FullFAT library in its rewrite of its FAT Installable File System.[130] ReactOS makes use of the USB stack from Haiku both as a reference and as a foundation for its USB support.[131][132] Mesa 3D provides OpenGL rendering.[12][118]

Networking

[edit]

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.[133] Later, lwIP was integrated into the ReactOS network stack.[38]

Wine cooperation

[edit]
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.[17][134] ReactOS uses portions of the Wine project so that it can benefit from Wine's progress in implementing the Win32 API.[134] 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.[118][123]

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.[135]

Other

[edit]

The Tango Desktop Project initiative provides open-source design guidelines and resources (as icons) for applications on desktop environments. FreeType is an open-source software development library, used to render text on to bitmaps and provides support for other font-related operations.[12] The KernelEx project is a Windows-API extension and compatibility layer project, which provides open-source implementations of some Windows-APIs.[136] Other contributing projects are MinGW, SYSLINUX, adns, ICU, GraphApp, Ext2, GNU FreeFont, DejaVu fonts, and Liberation fonts.[137][138][139]

Forks

[edit]

Forks based on ReactOS exist:

Reception

[edit]

Various people have acknowledged ReactOS and the implications of having a viable open-source drop-in replacement for Windows.[8] 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.[8] 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."[143]

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.[10] 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".[9] 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.[144][145] 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.[146]

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.[147]

In August 2018, Jesse Smith from DistroWatch Weekly reviewed ReactOS v0.4.9, reporting that it suffered from limited hardware support and that it tended to lock up under load. He concluded: "[it] should be used with caution and probably not as a main, day-to-day operating system"[148]

Awards

[edit]

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.[149]

ReactOS was a featured project on SourceForge for the weeks beginning on 27 February 2012, 25 April 2013,[150] and several others. It was Project of the Month on SourceForge for June 2013[151] and February 2019.[152]

See also

[edit]

Notes

[edit]
  1. ^ GPL-2.0-or-later with parts under LGPL and BSD licenses

References

[edit]
  1. ^ "ReactOS on Open Hub". openhub.net. Black Duck Open Hub. Retrieved 24 October 2014.
  2. ^ "ReactOS on GitHub". GitHub. Retrieved 27 April 2019.
  3. ^ a b c d "ReactOS 0.4.14 released | ReactOS Project". reactos.org. 16 December 2021. Retrieved 18 December 2021.
  4. ^ "Download | ReactOS Project". www.reactos.org. Retrieved 28 July 2017.
  5. ^ Holwerda, Thom (5 March 2009). "ReactOS Targets Windows 2003, Vista". OSNews. Retrieved 14 October 2020.
  6. ^ vicmarcal (14 April 2018). "ReactOS 0.4.8 released!!". ReactOS.org Project News (Corporate blog). Archived from the original on 16 April 2018. Retrieved 14 October 2020. With software specifically leaving NT5 behind, ReactOS is expanding its target to support NT6+ (Vista, Windows 8, Windows 10) software.
  7. ^ Stahl, Louis-F. (23 June 2015). "Russland erklärt ReactOS zu favorisierter Windows-Alternative". heise online. Retrieved 14 October 2020.
  8. ^ a b c d Sixtus, Von Mario (20 February 2004). "ReactOS: Das Nicht-Windows" (in German). Spiegel Online. Retrieved 11 December 2009.
  9. ^ a b Dvorak, John C. (4 April 2008). "What A New OS Needs". PC Magazine. Retrieved 11 December 2009.
  10. ^ a b Sugar, David (31 January 2006). "A reaction to ReactOS". Free Software Magazine. Archived from the original on 10 August 2007. Retrieved 11 December 2009.
  11. ^ a b Kupfer, Matthias; Bragin, Aleksey (14 March 2010). ReactOS — Das zu Windows binärkompatible Open-Source-Betriebssystem. Chemnitzer Linux-Tage (in German). Chemnitz, Germany. Retrieved 15 March 2010.
  12. ^ a b c d Royal, 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.
  13. ^ Thom Holwerda (14 November 2007). "ReactOS Gets OpenOffice.org 2 Support; New Release Plans". OSNews.
  14. ^ Tests for 0.4.14 on reactos.org (February 2022)
  15. ^ a b c Holwerda, Thom (17 January 2009). "ReactOS: Looking Back Upon 2008". OSNews. Retrieved 18 April 2019.
  16. ^ a b "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.
  17. ^ a b c Vincent, 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.
  18. ^ Loli, Eugenia (16 October 2001). "Interview with Jason Filby from the ReactOS Project". OSNews. Retrieved 18 April 2019.
  19. ^ Loschwitz, Martin (March 2004), "Projects on the Move" (PDF), Linux Magazine, p. 87, archived from the original (PDF) on 19 May 2011, retrieved 18 November 2009
  20. ^ Speed, Richard (14 March 2022). "ReactOS now supports SMP". www.theregister.com. Retrieved 20 December 2022.
  21. ^ "ReactOS Foundation — ReactOS Wiki". www.reactos.org. Retrieved 6 March 2019.
  22. ^ a b "ФОНД АКТИВИЗАЦИИ КИБЕРПРОСТРАНСТВА, ФАК, РЕАКТОС — ФОНД, ФОНД РЕАКТОС, г. Саранск: ИНН: 1328170012, ОГРН: 1021301112876". egrulinfo.com. Retrieved 18 April 2019.
  23. ^ 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?
  24. ^ Birr, Hartmut (18 January 2006). "Bye bye". ros-dev (Mailing list). Retrieved 3 January 2009.
  25. ^ "BadStack in syscall.S". ReactOS. 17 January 2006. Archived from the original on 4 September 2017. Retrieved 4 August 2018.
  26. ^ Birr, Hartmut (18 January 2006). "Bye bye". ros-dev (Mailing list). Retrieved 16 November 2009.
  27. ^ Ionescu, Alex (18 January 2006). "Bye bye". ros-dev (Mailing list). Retrieved 16 November 2009.
  28. ^ a b Feller, Stephen (1 February 2006). "ReactOS suspends development for source code review". Linux.com. Retrieved 10 December 2009.
  29. ^ Reset, Reboot, Restart, legal issues and the long road to 0.3 on reactos.org by Steven Edwards (27 January 2006)
  30. ^ 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.
  31. ^ 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.
  32. ^ Bragin, Aleksey (18 September 2007). "Audit". ros-dev (Mailing list). Retrieved 3 January 2009.
  33. ^ Evers, Joris (12 February 2004). "Windows Code May Be Stolen". PC World. Archived from the original on 31 July 2013. Retrieved 20 November 2021.
  34. ^ 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)
  35. ^ Anderson, Tim (3 July 2019). "ReactOS 'a ripoff of the Windows Research Kernel', claims Microsoft kernel engineer". The Register.
  36. ^ "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
  37. ^ "TCP/IP driver replacement for ReactOS, using lwIP". Archived from the original on 21 March 2012. Retrieved 9 August 2011.
  38. ^ a b Gutman, Cameron (7 August 2011). "ReactOS is now using lwIP for TCP". lwip-devel (Mailing list). Retrieved 9 August 2011.
  39. ^ Alksnis, Viktor (6 June 2007). "Виктор Имантович Алкснис – Знакомство с проектом ReactOS" (in Russian). Retrieved 11 December 2009.
  40. ^ "Russian President Medvedev asked to fund Windows clone". BBC News. 13 September 2011. Retrieved 15 September 2011.
  41. ^ Z98 (5 August 2012). "ReactOS Presented to President Putin". ReactOS News. Retrieved 23 June 2013.
  42. ^ Minutes of the expert evaluation of projects on import substitution infrastructure software according to paragraph 4-8 of import substitution plan software, approved by order of the Ministry of Communications of Russia from 1 April 2015 №96 "On approval of import software" Archived 18 July 2015 at the Wayback Machine Russian Ministry of Communications "Direction "client operating system / Server Operating Systems" first place — the project "Corporate platform on the basis of domestic operating systems" [...] second place — the project "Creation of the operating system open source based on ReactOS for PCs, laptops and other mobile devices," "Creating the operating system open source-based server ReactOS" (Fund "Reaktos" MSTU. AN Bauman, LLC "Paral Plelz Research" and others.)." (2 June 2015, translated)
  43. ^ "ReactOS as a second OS in Russian government's software freedom effort | ReactOS Project". www.reactos.org. Retrieved 6 April 2019.
  44. ^ Russland-erklaert-ReactOS-zu-favorisierter-Windows-Alternative on heise online by Louis-F. Stahl (23 June 2015, in German)
  45. ^ Russland macht ReactOS zu bevorzugter Windows-Alternative on Der Standard (24 June 2015, in German)
  46. ^ Oliver Diedrich (3 May 2012). "ReactOS: Spenden gesucht". heise.de (in German).
  47. ^ A personal appeal from ReactOS Project Coordinator Aleksey Bragin, accessed on 15 April 2013
  48. ^ Spenderliste Archived 30 December 2013 at the Wayback Machine 24 December 2012, accessed on 15 April 2013 (in German)
  49. ^ "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.
  50. ^ "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.
  51. ^ ReactOS Wants To Bring Open-Source Windows To The Cloud on Phoronix by Michael Larabel (22 January 2014)
  52. ^ Oliver Diedrich (21 January 2014). "ReactOS: Freier Windows-Klon braucht Unterstützung]". heise.de (in German).
  53. ^ Aleksey Bragin; Steven Edwards (23 December 2013). "Thorium Core Cloud Desktop". Kickstarter.com. Retrieved 8 April 2014.
  54. ^ Torsten Kleinz (8 April 2014). "XP ist tot, es lebe Windows" [XP is dead, long live Windows]. Die Zeit (in German).
  55. ^ ReactOS Working On A Community Windows OS on Phoronix by Michael Larabel (19 April 2014)
  56. ^ Silviu Stahie (4 April 2014). "ReactOS goes to Indiegogo, will run Windows apps natively". softpedia.com. Retrieved 8 April 2014.
  57. ^ Hoffman, Chris (14 November 2014). "Why prominent 'hobbyist' operating systems face an existential crisis". PCWorld. Retrieved 29 December 2015. ReactOS raised more than $25,000 in an Indiegogo crowdfunding campaign earlier in 2014, for the development of a community edition of the operating system.
  58. ^ reactos-community-edition on Indiegogo (1 June 2014)
  59. ^ ReactOS: Große Fortschritte und Stipendien für Entwickler beim freien Windows-Nachbau Archived 7 June 2016 at the Wayback Machine on heise.de by Louis-F. Stahl (2 October 2014, in German)
  60. ^ Russland-erklaert-ReactOS-zu-favorisierter-Windows-Alternative on heise online by Louis-F. Stahl "Einen weiteren Schub in der Entwicklung erhofft sich die ReactOS-Community vom ersten ReactOS Hackfest, das vom 7. bis zum 12. August 2015 in Aachen stattfindet." (23 June 2015, in German)
  61. ^ Russland macht ReactOS zu bevorzugter Windows-Alternative on Der Standard "Von 7. bis 12. August lädt die Entwicklergemeinde in Deutschland zum ersten ReactOS-Hackfest, das in Aachen über die Bühne gehen wird." (24 June 2015, in German)
  62. ^ "ReactOS Hackfest in Aachen". ReactOS. 1 September 2015. Retrieved 18 April 2019.
  63. ^ "ReactOS Hackfest 2017". ReactOS Wiki. Retrieved 18 April 2019.
  64. ^ "ReactOS Hackfest 2018". ReactOS Wiki. Retrieved 18 April 2019.
  65. ^ "ReactOS Hackfest 2019". ReactOS Wiki. Retrieved 20 October 2020.
  66. ^ "ReactOS 0.3.0 Released!". reactos.org. Retrieved 25 April 2020.
  67. ^ "ReactOS 0.3.1 Released". reactos.org. Retrieved 25 April 2020.
  68. ^ a b "ReactOS 0.3.3 Released!". reactos.org. Retrieved 25 April 2020.
  69. ^ "ReactOS 0.3.4 Released". reactos.org. Retrieved 25 April 2020.
  70. ^ "ReactOS 0.3.5". reactos.org. Retrieved 25 April 2020.
  71. ^ "ReactOS 0.3.6". reactos.org. Retrieved 25 April 2020.
  72. ^ "ReactOS 0.3.7". reactos.org. Retrieved 25 April 2020.
  73. ^ "ReactOS 0.3.9 Released". reactos.org. Retrieved 25 April 2020.
  74. ^ "ReactOS 0.3.10 Released". reactos.org. Retrieved 25 April 2020.
  75. ^ "ReactOS 0.3.10". OS Revolution. Archived from the original on 12 December 2009. Retrieved 9 December 2009.
  76. ^ Holwerda, Thom (6 July 2009). "ReactOS 0.3.10 Released". OSNews. Retrieved 9 December 2009.
  77. ^ "ReactOS 0.3.11 Released". reactos.org. Retrieved 25 April 2020.
  78. ^ "ReactOS 0.3.12 Released". reactos.org. Retrieved 25 April 2020.
  79. ^ Holwerda, Thom (20 October 2010). "ReactOS 0.3.12 Released". OSNews. Retrieved 8 November 2010.
  80. ^ "ReactOS 0.3.13 Released". reactos.org. Retrieved 25 April 2020.
  81. ^ 0.3.13 — ReactOS, ReactOS Foundation, retrieved 10 February 2014
  82. ^ "ReactOS 0.3.14 Released". reactos.org. Retrieved 25 April 2020.
  83. ^ 0.3.14 — ReactOS, ReactOS Foundation, retrieved 10 February 2014
  84. ^ "ReactOS 0.3.15 Released". reactos.org. Retrieved 25 April 2020.
  85. ^ 0.3.15 — ReactOS, ReactOS Foundation, retrieved 10 February 2014
  86. ^ ReactOS review | LinuxBSDos.com
  87. ^ "ReactOS 0.3.16 Released". reactos.org. Retrieved 25 April 2020.
  88. ^ ReactOS 0.3.16 Released, ReactOS Foundation, retrieved 10 February 2014
  89. ^ DistroWatch Weekly, Issue 593, 19 January 2015
  90. ^ "ReactOS 0.3.17 Released". reactos.org. Retrieved 25 April 2020.
  91. ^ Gimp/GTK+ drawing problems, ReactOS Foundation, retrieved 5 October 2014
  92. ^ JRE installer and Winrar shows Marlett font instead the proper one, ReactOS Foundation, retrieved 5 November 2014
  93. ^ ReactOS 0.3.17 Released, ReactOS Foundation, retrieved 5 November 2014
  94. ^ DistroWatch Weekly, Issue 652, 14 March 2016
  95. ^ ReactOS 0.4.0 Released, ReactOS Foundation, retrieved 16 February 2016
  96. ^ ReactOS 0.4.1 review — Cold fusion, Dedoimedo
  97. ^ ReactOS 0.4.1 Released, ReactOS Foundation, retrieved 17 May 2016
  98. ^ ReactOS 0.4.2 Released, ReactOS Foundation, retrieved 16 August 2016
  99. ^ ReactOS 0.4.3 Released, ReactOS Foundation, retrieved 16 November 2016
  100. ^ ReactOS 0.4.4 Released, ReactOS Foundation, retrieved 16 February 2017
  101. ^ ReactOS 0.4.5 Released, ReactOS Foundation, retrieved 19 May 2017
  102. ^ ReactOS 0.4.6 released, ReactOS Foundation, retrieved 1 September 2017
  103. ^ ReactOS 0.4.7 released!, ReactOS Foundation, retrieved 6 December 2017
  104. ^ ReactOS 0.4.8 released!!, ReactOS Foundation, retrieved 14 April 2018
  105. ^ ReactOS 0.4.9 released, ReactOS Foundation, retrieved 23 July 2018
  106. ^ ReactOS 0.4.10 released, ReactOS Foundation, retrieved 6 November 2018
  107. ^ ReactOS 0.4.11 released, ReactOS Foundation, retrieved 20 October 2020
  108. ^ "ReactOS 0.4.12 released | ReactOS Project". reactos.org. Retrieved 23 September 2019.
  109. ^ a b "ReactOS 0.4.13 released | ReactOS Project". reactos.org. Retrieved 10 April 2020.
  110. ^ "0.4.15 - ReactOS Wiki". reactos.org. Retrieved 2 December 2023.
  111. ^ "0.5.0 - ReactOS Wiki". reactos.org. Retrieved 2 December 2023.
  112. ^ "reactos/base/shell/cmd at master · reactos/reactos · GitHub". github.com.
  113. ^ "reactos/base/applications/cmdutils at master · reactos/reactos · GitHub". github.com.
  114. ^ "reactos/modules/rosapps/applications/cmdutils at master · reactos/reactos · GitHub". github.com.
  115. ^ "reactos/base/applications/cacls at master · reactos/reactos · GitHub". github.com.
  116. ^ "reactos/base/applications/sc at master · reactos/reactos · GitHub". github.com.
  117. ^ "reactos/base/applications/shutdown at master · reactos/reactos · GitHub". github.com.
  118. ^ a b c Ionescu, Alex (26 February 2006). The ReactOS Project – An Open Source OS Platform for Learning (Speech). University of Waterloo, Canada. Retrieved 10 December 2009.
  119. ^ "ReactOS versioning". ReactOS. 7 March 2015. Retrieved 7 March 2015.
  120. ^ "ReactX". ReactOS Wiki. 28 May 2014. Retrieved 15 February 2022.
  121. ^ Sinovsky, Steven (18 August 2008). "The Windows 7 Team". Engineering Windows 7, MSDN. Retrieved 9 December 2009.
  122. ^ "ReactOS". Ohloh. Retrieved 2 September 2011.
  123. ^ a b c C., Michele (19 June 2009). ReactOS is (not) Windows (PDF). Hackmeeting 2009. Milan. Retrieved 20 October 2020.
  124. ^ "Installing". ReactOS. 20 January 2014. Retrieved 10 February 2014.
  125. ^ "ReactOS ports - ReactOS Wiki".
  126. ^ "ReactOS GitHub (Label: x64)". GitHub. Retrieved 11 August 2019.
  127. ^ Captive: NTFS Read/Write Filesystem Addon for Linux on OSNews by Eugenia Loli "They are using WINE and ReactOS code to emulate parts of Windows environment needed to make the driver work." (4 December 2003)
  128. ^ 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."
  129. ^ "Universal ATA/SATA/AHCI driver for Windows NT3.51/NT4/2000/XP/2003/7". Alter.org.ua. Retrieved 10 February 2014.
  130. ^ Walmsley, James (2009). "Features — Portability". Archived from the original on 23 April 2010. Retrieved 19 February 2010.
  131. ^ ReactOS gets USB stack with Haiku's help on OSNews by Thom Holwerda
  132. ^ "ReactOS gets USB Stack, with Help from Us". Haiku. 20 February 2012. Retrieved 2 March 2012.
  133. ^ "An interview with Art Yerkes, Network Developer for the ReactOS Project". Network Performance Daily. 28 March 2007. Archived from the original on 14 July 2011. Retrieved 22 February 2010.
  134. ^ a b "Acknowledgements". Wine. Retrieved 15 November 2009.
  135. ^ Holwerda, Thom (18 January 2010). "ReactOS Proposes Radical New Win32 Subsystem". OSNews. Retrieved 18 January 2010.
  136. ^ kernelex on sourceforge.net
  137. ^ "Third party libraries — ReactOS". www.reactos.org. Retrieved 8 January 2015.
  138. ^ "FishEye: Annotated — reactos/trunk/reactos/media/doc/3rd Party Files.txt". code.reactos.org. Archived from the original on 3 August 2016. Retrieved 8 January 2015.
  139. ^ "[reactos] Contents of /trunk/reactos/dll/win32/syssetup/syssetup.rc". svn.reactos.org. Archived from the original on 4 September 2017. Retrieved 8 January 2015.
  140. ^ Ekush Emulator and Its License Pains on OSNews by Eugenia Loli (10 November 2004)
  141. ^ Ekush OS – stolen source code/copyright violation (archived 2004)
  142. ^ Ekush The Next Generation Operating System on akshor.com (archived 2004)
  143. ^ reactos on distrowatch.com ReactOS is a free and open-source operating system based on the best design principles found in the Windows NT architecture. (accessed January 2016)
  144. ^ Blankenhorn, Dana (13 May 2008). "ReactOS no threat to Windows". ZDNet. Archived from the original on 25 September 2008. Retrieved 22 December 2009.
  145. ^ Blankenhorn, Dana (13 May 2008). "ReactOS needs a channel". ZDNet. Archived from the original on 28 June 2012. Retrieved 22 December 2009.
  146. ^ Holwerda, Thom (20 December 2009). "My OS Is Less Hobby Than Yours". OSNews. Retrieved 22 December 2009.
  147. ^ 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.
  148. ^ Jesse Smith. "Guix System Distribution 0.15.0 and ReactOS 0.4.9". DistroWatch Weekly (778). Retrieved 27 August 2018.
  149. ^ "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.
  150. ^ "Featured projects, February 27, 2012". SourceForge.com. 27 December 2012. Retrieved 20 December 2012.
  151. ^ "Sourceforge POTM June 2013". Sourceforge.com. 17 June 2013. Retrieved 17 June 2013.
  152. ^ "February 2019, "Staff Pick" Project of the Month – ReactOS". 8 February 2019. Retrieved 25 May 2021.
[edit]
Wikimedia Commons has media related to ReactOS.
Retrieved from "https://en.wikipedia.org/w/index.php?title=ReactOS&oldid=1255122695"