ReactOS: Difference between revisions

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
VisualWikitext
imported>Demonjunkie
m run-on sentence
 
imported>Avarai
Intro clarity
 
Line 28: Line 28:
}}
}}
[[File:ReactOS 0.4.14 Firefox 48 screenshot.png|thumb|ReactOS 0.4.14 running the [[Firefox]] [[web browser]]]]
[[File:ReactOS 0.4.14 Firefox 48 screenshot.png|thumb|ReactOS 0.4.14 running the [[Firefox]] [[web browser]]]]
'''ReactOS''' is a [[Free and open-source software|free and open-source]] [[operating system]] for [[i586]]/[[amd64]] [[personal computer]]s, intended to be [[binary-code compatibility|binary-compatible]] with [[computer program]]s and [[device driver]]s developed for [[Windows Server 2003]] and later versions of Microsoft Windows.<ref>{{Cite news|url=https://www.osnews.com/story/21087/reactos-targets-windows-2003-vista/|title=ReactOS Targets Windows 2003, Vista|last=Holwerda|first=Thom|date=2009-03-05|work=OSNews|access-date=2020-10-14}}</ref><ref>{{cite web |title=ReactOS 0.4.8 released!! |author=vicmarcal |website=ReactOS.org Project News |type=Corporate blog |date=2018-04-14 |url=https://www.reactos.org/project-news/reactos-048-released |access-date=2020-10-14 |archive-url=https://archive.today/20180416011852/https://www.reactos.org/project-news/reactos-048-released |archive-date=16 April 2018 |url-status=live |quote=With software specifically leaving NT5 behind, ReactOS is expanding its target to support NT6+ (Vista, Windows 8, Windows 10) software.}}</ref> ReactOS has been noted as a potential open-source [[drop-in replacement]] for Windows<ref>{{Cite news|url=https://www.heise.de/newsticker/meldung/Russland-erklaert-ReactOS-zu-favorisierter-Windows-Alternative-2722495.html|title=Russland erklärt ReactOS zu favorisierter Windows-Alternative|last=Stahl|first=Louis-F.|date=2015-06-23|work=heise online|access-date=2020-10-14}}</ref><ref name="Spiegel" /><ref name="dvorak" /> and for its information on [[undocumented feature|undocumented]] [[Windows API]]s.<ref name="undocumented" />
'''ReactOS''' is a [[Free and open-source software|free and open-source]] [[operating system]] for [[i586]]/[[amd64]] [[personal computer]]s that is intended to be [[binary-code compatibility|binary-compatible]] with [[computer program]]s and [[device driver]]s developed for [[Windows Server 2003]] and later versions of Microsoft Windows.<ref>{{Cite news|url=https://www.osnews.com/story/21087/reactos-targets-windows-2003-vista/|title=ReactOS Targets Windows 2003, Vista|last=Holwerda|first=Thom|date=2009-03-05|work=OSNews|access-date=2020-10-14}}</ref><ref>{{cite web |title=ReactOS 0.4.8 released!! |author=vicmarcal |website=ReactOS.org Project News |type=Corporate blog |date=2018-04-14 |url=https://www.reactos.org/project-news/reactos-048-released |access-date=2020-10-14 |archive-url=https://archive.today/20180416011852/https://www.reactos.org/project-news/reactos-048-released |archive-date=16 April 2018 |url-status=live |quote=With software specifically leaving NT5 behind, ReactOS is expanding its target to support NT6+ (Vista, Windows 8, Windows 10) software.}}</ref> ReactOS has been noted as a potential open-source [[drop-in replacement]] for Windows<ref>{{Cite news|url=https://www.heise.de/newsticker/meldung/Russland-erklaert-ReactOS-zu-favorisierter-Windows-Alternative-2722495.html|title=Russland erklärt ReactOS zu favorisierter Windows-Alternative|last=Stahl|first=Louis-F.|date=2015-06-23|work=heise online|access-date=2020-10-14}}</ref><ref name="Spiegel" /><ref name="dvorak" /> and has been of interest for its information on [[undocumented feature|undocumented]] [[Windows API]]s.<ref name="undocumented" />


ReactOS has been in development since 1996. {{As of|2025|4|df=US}}, it is still considered feature-incomplete [[Software release life cycle#Alpha|alpha software]], and is therefore recommended by the developers only for evaluation and testing purposes.<ref name="chemnitz">{{cite conference |last1=Kupfer |first1=Matthias |last2=Bragin |first2=Aleksey |date=2010-03-14 |title=ReactOS&nbsp;— Das zu Windows binärkompatible Open-Source-Betriebssystem |url=https://chemnitzer.linux-tage.de/2010/vortraege/detail.html?idx=424 |conference=Chemnitzer Linux-Tage |language=de |location=Chemnitz, Germany |access-date=2010-03-15 |conference-url=https://chemnitzer.linux-tage.de/2010/info/}}</ref><ref name="lowendmacreview" /> However, many Windows applications are working, such as [[Adobe Acrobat|Adobe Reader]] 9.3, [[GIMP]] 2.6, and [[LibreOffice]] 5.4.<ref>{{cite news |author=Thom Holwerda |date=2007-11-14 |title=ReactOS Gets OpenOffice.org 2 Support; New Release Plans |url=https://www.osnews.com/story/18921/ReactOS_Gets_OpenOffice_org_2_Support_New_Release_Plans |work=[[OSNews]]}}</ref><ref name="0.4.14-tests">[https://reactos.org/wiki/Tests_for_0.4.14 Tests for 0.4.14] on reactos.org (February 2022)</ref>
ReactOS has been in development since 1996. {{As of|2025|4|df=US}}, it is still considered to be feature-incomplete [[Software release life cycle#Alpha|alpha software]]. Therefore, it is recommended by the developers to be used only for evaluation and testing purposes.<ref name="chemnitz">{{cite conference |last1=Kupfer |first1=Matthias |last2=Bragin |first2=Aleksey |date=2010-03-14 |title=ReactOS&nbsp;— Das zu Windows binärkompatible Open-Source-Betriebssystem |url=https://chemnitzer.linux-tage.de/2010/vortraege/detail.html?idx=424 |conference=Chemnitzer Linux-Tage |language=de |location=Chemnitz, Germany |access-date=2010-03-15 |conference-url=https://chemnitzer.linux-tage.de/2010/info/}}</ref><ref name="lowendmacreview" /> However, many Windows applications are working, such as [[Adobe Acrobat|Adobe Reader]] 9.3, [[GIMP]] 2.6, and [[LibreOffice]] 5.4.<ref>{{cite news |author=Thom Holwerda |date=2007-11-14 |title=ReactOS Gets OpenOffice.org 2 Support; New Release Plans |url=https://www.osnews.com/story/18921/ReactOS_Gets_OpenOffice_org_2_Support_New_Release_Plans |work=[[OSNews]]}}</ref><ref name="0.4.14-tests">[https://reactos.org/wiki/Tests_for_0.4.14 Tests for 0.4.14] on reactos.org (February 2022)</ref>


ReactOS is primarily written in [[C (programming language)|C]], with some elements, such as ReactOS [[File Explorer]], written in [[C++]]. The project partially implements [[Architecture of Windows NT|Windows API]] functionality and has been ported to the [[x86-64|AMD64]] [[Instruction set architecture|processor architecture]].<ref name=2008review /> ReactOS, as part of the [[free and open-source software|FOSS]] ecosystem, re-uses and collaborates with many other FOSS projects,<ref name=collaboration /><ref name=collaboration2 /> most notably the [[Wine (software)|Wine]] project, which presents a Windows compatibility layer for [[Unix-like]] operating systems.
ReactOS is primarily written in [[C (programming language)|C]], with some elements written in [[C++]], such as the ReactOS [[File Explorer]]. The project partially implements [[Architecture of Windows NT|Windows API]] functionality and has been ported to the [[x86-64|AMD64]] [[Instruction set architecture|processor architecture]].<ref name=2008review /> ReactOS is part of the [[free and open-source software|FOSS]] ecosystem so it re-uses and collaborates with many other FOSS projects,<ref name=collaboration /><ref name=collaboration2 /> most notably the [[Wine (software)|Wine]] project that presents a Windows compatibility layer for [[Unix-like]] operating systems.


==History==
==History==
Line 52: Line 52:
| df = dmy-all
| df = dmy-all
}}
}}
</ref><ref>{{Cite web |last=Speed |first=Richard |date=2022-03-14 |title=ReactOS now supports SMP |url=https://www.theregister.com/2022/03/14/reactos_smp/ |access-date=2022-12-20 |website=www.theregister.com |language=en}}</ref> 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&nbsp;– and reaction to&nbsp;– Microsoft's [[Microsoft litigation|monopolistic position]].<ref name=Spiegel>{{cite web |url=http://www.spiegel.de/netzwelt/tech/0,1518,287199,00.html |last=Sixtus |first=Von Mario |title=ReactOS: Das Nicht-Windows |language=de |publisher=[[Der Spiegel|Spiegel Online]] |date=2004-02-20 |access-date=2009-12-11}}</ref>
</ref><ref>{{Cite web |last=Speed |first=Richard |date=2022-03-14 |title=ReactOS now supports SMP |url=https://www.theregister.com/2022/03/14/reactos_smp/ |access-date=2022-12-20 |website=www.theregister.com |language=en}}</ref> 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 inspired reaction to Microsoft's [[Microsoft litigation|monopolistic position]].<ref name=Spiegel>{{cite web |url=http://www.spiegel.de/netzwelt/tech/0,1518,287199,00.html |last=Sixtus |first=Von Mario |title=ReactOS: Das Nicht-Windows |language=de |publisher=[[Der Spiegel|Spiegel Online]] |date=2004-02-20 |access-date=2009-12-11}}</ref>


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.<ref name=":0">{{Cite web|url=https://www.reactos.org/wiki/ReactOS_Foundation|title=ReactOS Foundation&nbsp;— ReactOS Wiki|website=www.reactos.org|access-date=2019-03-06}}</ref> In 2015, the foundation was liquidated.<ref name="liquidated">{{Cite web|url=https://egrulinfo.com/8583363/|title=ФОНД АКТИВИЗАЦИИ КИБЕРПРОСТРАНСТВА, ФАК, РЕАКТОС&nbsp;— ФОНД, ФОНД РЕАКТОС, г. Саранск: ИНН: 1328170012, ОГРН: 1021301112876|website=egrulinfo.com|access-date=18 April 2019}}</ref>
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.<ref name=":0">{{Cite web|url=https://www.reactos.org/wiki/ReactOS_Foundation|title=ReactOS Foundation&nbsp;— ReactOS Wiki|website=www.reactos.org|access-date=2019-03-06}}</ref> In 2015, the foundation was liquidated.<ref name="liquidated">{{Cite web|url=https://egrulinfo.com/8583363/|title=ФОНД АКТИВИЗАЦИИ КИБЕРПРОСТРАНСТВА, ФАК, РЕАКТОС&nbsp;— ФОНД, ФОНД РЕАКТОС, г. Саранск: ИНН: 1328170012, ОГРН: 1021301112876|website=egrulinfo.com|access-date=18 April 2019}}</ref>


===Internal audit===
===Internal audit===
In order to avoid copyright prosecution, ReactOS had to be expressly completely distinct and non-[[derivative work|derivative]] from Windows, a goal that needed very careful work.<ref name="ExecutableCopyright">{{Cite web |last=Hancock |first=Terry |date=2008-08-29 |title=What if copyright didn't apply to binary executables? |url=https://freesoftwaremagazine.com/articles/what_if_copyright_didnt_apply_binary_executables/ |access-date=2020-11-01 |publisher=[[Free Software Magazine]] |language=en |quote=(…) ReactOS aims to run actual Windows binary executable programs.&emsp;This means that ReactOS must implement the entire Windows environment.&emsp;Functions must do exactly what their Windows counterparts would do.&emsp;In other words, like our notional parallel stew recipes, ReactOS and Windows should be functionally identical.&emsp;In order to avoid copyright prosecution, though, ReactOS must be expressly completely distinct and non-derivative from Windows.&emsp;This is a careful tightrope walk!&emsp;ReactOS is a free, clean room re-implemented drop-in replacement for Windows.&emsp;So, consider this, especially regarding extremely simple library calls:&ensp;''is it legal for ReactOS to produce identical binary code to Windows?''}}</ref> 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 [[disassembler|disassembling]] Microsoft Windows.<ref name="byebye">{{cite mailing list |last=Birr |first=Hartmut |title=Bye bye |mailing-list=ros-dev |date=2006-01-18 |url=https://marc.info/?l=ros-dev&m=118775346131642&w=2 |access-date=2009-01-03}}</ref> The code that Birr disputed involved the function BadStack in syscall.S,<ref>{{cite web |url=https://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/syscall.S?revision=20935&view=markup&pathrev=20935#l43 |title=BadStack in syscall.S |publisher=ReactOS |date=2006-01-17 |access-date=2018-08-04 |archive-url=https://web.archive.org/web/20170904111000/https://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/syscall.S?revision=20935&view=markup&pathrev=20935#l43 |archive-date=4 September 2017 |url-status=dead |df=dmy-all}}</ref> as well as other unspecified items.<ref>{{cite mailing list |first=Hartmut |last=Birr |url=http://marc.info/?l=ros-dev&m=118775346131646&w=2 |title=Bye bye |date=2006-01-18 |mailing-list=ros-dev |access-date=2009-11-16}}</ref> Comparing this function to disassembled binaries from [[Windows XP]], Birr argued that the BadStack function was simply [[Cut, copy, and paste|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.<ref>{{cite mailing list |last=Ionescu |first=Alex |title=Bye bye |mailing-list=ros-dev |date=2006-01-18 |url=https://marc.info/?l=ros-dev&m=118775346131654&w=2 |access-date=2009-11-16}}</ref>
In order to avoid copyright prosecution, ReactOS had to be expressly completely distinct and non-[[derivative work|derivative]] from Windows, a goal that needed very careful work.<ref name="ExecutableCopyright">{{Cite web |last=Hancock |first=Terry |date=2008-08-29 |title=What if copyright didn't apply to binary executables? |url=https://freesoftwaremagazine.com/articles/what_if_copyright_didnt_apply_binary_executables/ |access-date=2020-11-01 |publisher=[[Free Software Magazine]] |language=en |quote=(…) 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.&emsp;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 call: ''is it legal for ReactOS to produce identical binary code to Windows?''}}</ref> 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 [[disassembler|disassembling]] Microsoft Windows.<ref name="byebye">{{cite mailing list |last=Birr |first=Hartmut |title=Bye bye |mailing-list=ros-dev |date=2006-01-18 |url=https://marc.info/?l=ros-dev&m=118775346131642&w=2 |access-date=2009-01-03}}</ref> The code that Birr disputed involved the function BadStack in syscall.S,<ref>{{cite web |url=https://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/syscall.S?revision=20935&view=markup&pathrev=20935#l43 |title=BadStack in syscall.S |publisher=ReactOS |date=2006-01-17 |access-date=2018-08-04 |archive-url=https://web.archive.org/web/20170904111000/https://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/syscall.S?revision=20935&view=markup&pathrev=20935#l43 |archive-date=4 September 2017 |url-status=dead |df=dmy-all}}</ref> as well as other unspecified items.<ref>{{cite mailing list |first=Hartmut |last=Birr |url=http://marc.info/?l=ros-dev&m=118775346131646&w=2 |title=Bye bye |date=2006-01-18 |mailing-list=ros-dev |access-date=2009-11-16}}</ref> Comparing this function to disassembled binaries from [[Windows XP]], Birr argued that the BadStack function was simply [[Cut, copy, and paste|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.<ref>{{cite mailing list |last=Ionescu |first=Alex |title=Bye bye |mailing-list=ros-dev |date=2006-01-18 |url=https://marc.info/?l=ros-dev&m=118775346131654&w=2 |access-date=2009-11-16}}</ref>


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 [[Geeknet|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 movement|free software community]]: in particular, Wine barred several inactive developers from providing contributions{{Citation needed|date=August 2018}}<!-- wrong citation:<ref>{{cite web |url=http://www.winehq.org/interview/14 |title=Interview with Steven Edwards |access-date=2013-06-23 |first=Brian |last=Vincent |publisher=winehq.com |date=2004-05-25 |quote=''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.''}}</ref> --> and formal high level cooperation between the two projects remained difficult {{As of|2006|lc=y}}.<ref name=suspend>{{cite web |url=https://www.linux.com/news/reactos-suspends-development-source-code-review/ |first=Stephen |last=Feller |title=ReactOS suspends development for source code review |publisher=[[Linux.com]] |date=2006-02-01 |access-date=2009-12-10}}</ref>
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 [[Geeknet|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 movement|free software community]]: in particular, Wine barred several inactive developers from providing contributions{{Citation needed|date=August 2018}}<!-- wrong citation:<ref>{{cite web |url=http://www.winehq.org/interview/14 |title=Interview with Steven Edwards |access-date=2013-06-23 |first=Brian |last=Vincent |publisher=winehq.com |date=2004-05-25 |quote=''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.''}}</ref> --> and formal high-level cooperation between the two projects remained difficult {{As of|2006|lc=y}}.<ref name=suspend>{{cite web |url=https://www.linux.com/news/reactos-suspends-development-source-code-review/ |first=Stephen |last=Feller |title=ReactOS suspends development for source code review |publisher=[[Linux.com]] |date=2006-02-01 |access-date=2009-12-10}}</ref>


In a statement on its website, ReactOS cited differing legal definitions of what constitutes [[Chinese wall#Reverse engineering|clean-room reverse engineering]] as a cause for the conflict.<ref>[https://www.reactos.org/reset-reboot-restart-legal-issues-and-long-road-03 Reset, Reboot, Restart, legal issues and the long road to 0.3] on reactos.org by Steven Edwards (27 January 2006)</ref> 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.<ref name="cleanroom">{{cite web |last=Schwartz |first=Mathew |date=2001-11-12 |title=Reverse-Engineering |url=https://www.computerworld.com/s/article/65532/Reverse_Engineering?pageNumber=1 |access-date=2013-06-23 |publisher=[[Computerworld]].com |quote=''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&nbsp;— about 8KB of code&nbsp;— 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.''}}</ref><ref>{{cite web |last=Hogle |first=Sean |date=2008-10-23 |title=Clean Room Defeats Software Infringement Claim in US Federal Court |url=https://hoviblog.blogspot.de/2008/10/clean-room-defeats-software.html |access-date=2013-05-23 |quote=[...] 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.}}</ref> 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.<ref name=suspend /> 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.<ref name=audit>{{cite mailing list |first=Aleksey |last=Bragin |url=http://marc.info/?l=ros-dev&m=119018479822866&w=2 |title=Audit |mailing-list=ros-dev |date=2007-09-18 |access-date=2009-01-03}}</ref>
In a statement on its website, ReactOS cited differing legal definitions of what constitutes [[Chinese wall#Reverse engineering|clean-room reverse engineering]] as a cause for the conflict.<ref>[https://www.reactos.org/reset-reboot-restart-legal-issues-and-long-road-03 Reset, Reboot, Restart, legal issues and the long road to 0.3] on reactos.org by Steven Edwards (27 January 2006)</ref> 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.<ref name="cleanroom">{{cite web |last=Schwartz |first=Mathew |date=2001-11-12 |title=Reverse-Engineering |url=https://www.computerworld.com/s/article/65532/Reverse_Engineering?pageNumber=1 |access-date=2013-06-23 |publisher=[[Computerworld]].com |quote=''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.''}}</ref><ref>{{cite web |last=Hogle |first=Sean |date=2008-10-23 |title=Clean Room Defeats Software Infringement Claim in US Federal Court |url=https://hoviblog.blogspot.de/2008/10/clean-room-defeats-software.html |access-date=2013-05-23 |quote=[...] 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.}}</ref> 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.<ref name=suspend /> 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.<ref name=audit>{{cite mailing list |first=Aleksey |last=Bragin |url=http://marc.info/?l=ros-dev&m=119018479822866&w=2 |title=Audit |mailing-list=ros-dev |date=2007-09-18 |access-date=2009-01-03}}</ref>


Also, the 2004 [[Internet leak#Source code leaks|leaked]] Windows source code<ref>{{cite web |last=Evers |first=Joris |date=12 February 2004 |title=Windows Code May Be Stolen |url=https://www.pcworld.com/article/114771/article.html |url-status=dead |archive-url=https://web.archive.org/web/20130731034443/http://www.pcworld.com/article/114771/article.html |archive-date=31 July 2013 |access-date=20 November 2021 |publisher=[[PC World]]}}</ref> was not seen as legal risk for ReactOS, as the [[trade secret]] was considered indefensible in court due to broad spread.<ref name=tradesecret>[https://www.reactos.org/reset-reboot-restart-legal-issues-and-long-road-03 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)</ref>
Also, the 2004 [[Internet leak#Source code leaks|leaked]] Windows source code<ref>{{cite web |last=Evers |first=Joris |date=12 February 2004 |title=Windows Code May Be Stolen |url=https://www.pcworld.com/article/114771/article.html |url-status=dead |archive-url=https://web.archive.org/web/20130731034443/http://www.pcworld.com/article/114771/article.html |archive-date=31 July 2013 |access-date=20 November 2021 |publisher=[[PC World]]}}</ref> was not seen as legal risk for ReactOS, as the [[trade secret]] was considered indefensible in court due to broad spread.<ref name=tradesecret>[https://www.reactos.org/reset-reboot-restart-legal-issues-and-long-road-03 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)</ref>

Latest revision as of 17:15, 2 June 2025

Template:Short description Template:Use dmy dates Script error: No such module "Distinguish". Script error: No such module "Unsubst".Script error: No such module "Check for unknown parameters".

File:ReactOS 0.4.14 Firefox 48 screenshot.png
ReactOS 0.4.14 running the Firefox web browser

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

ReactOS has been in development since 1996. Template:As of, it is still considered to be feature-incomplete alpha software. Therefore, it is recommended by the developers to be used only for evaluation and testing purposes.[7][8] However, many Windows applications are working, such as Adobe Reader 9.3, GIMP 2.6, and LibreOffice 5.4.[9][10]

ReactOS is primarily written in C, with some elements written in C++, such as the ReactOS File Explorer. The project partially implements Windows API functionality and has been ported to the AMD64 processor architecture.[11] ReactOS is part of the FOSS ecosystem so it re-uses and collaborates with many other FOSS projects,[12][13] most notably the Wine project that 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 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.[14] 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.[15][16] 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 inspired reaction to Microsoft's monopolistic position.[4]

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

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.[19] 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.[20] The code that Birr disputed involved the function BadStack in syscall.S,[21] as well as other unspecified items.[22] 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.[23]

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 contributionsScript error: No such module "Unsubst". and formal high-level cooperation between the two projects remained difficult Template:As of.[24]

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

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

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

Google Summer of Code participation

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

Lobbying for support in Russia

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

File:Alksnis-Bragin.jpg
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.[35]
  • 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.[36]
  • 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.[37]
  • 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",[38][39][40][41] 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.[42][43] 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.[44] 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;[45] indirect possibilities like stipends were evaluated.

Thorium Core Cloud Desktop project

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.[46] On 23 December 2013 the announced project was revealed as a Kickstarter campaign with the goal of US$120,000 was started.[47][48] 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.[49]

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

ReactOS Hackfest

File:ReactOS printing for the first time.webm
First video of printing from ReactOS

The ReactOS project organized a hackfest from 7 to 12 August 2015, in the German city of Aachen.[56][57][58] 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.[59]

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.[60][61]

Release history

System version Release date Release information
Template:Version 2006-08-27[62] First version to officially support networking
Template:Version 2007-03-10[63] Program manager included, start of kernel rewrite
Template:Version skipped Branch created but never released[64]
Template:Version 2007-09-12[64] Kernel and win32k improvements
Template:Version 2008-01-22[65] Registry support rewrite, remote desktop client and Plug and Play
Template:Version 2008-06-30[66] Bug fixes only
Template:Version 2008-08-06[67] RTL support
Template:Version 2008-11-04[68] Improved x86-64; MSVC, new stacks
Template:Version 2009-02-04 Introduced PSEH and multi-partition HDD support in live CDScript error: No such module "Unsubst".
Template:Version 2009-04-26[69] 24 MB minimum RAM, faster hyperspace mapping, initial sound support
Template:Version 2009-07-05[70] Initial SATA support, USB keyboard/mouse support, Paint clone, initial MSVC.[71][72]
Template:Version 2009-12-16[73] Kdcom rewrite; Chinese/Korean fonts; compatibility updates; sound system improvements
Template:Version 2010-10-20[74] Trap handler rewrite; timer and message handling rewrite; NMI support; SxS support; partial EMS support[75]
Template:Version 2011-03-22[76] Heap manager rewrite, improved SATA support, fixed graphics issues[77]
Template:Version 2012-02-07[78] 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[79]
Template:Version 2013-05-30[80] 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[81]
Template:Version[82] 2014-02-06[83] CSRSS rewrite; theme support improved; network card driver for the RTL8139, allowing ReactOS to support newer versions of QEMU out of the box[84]
Template:Version[85] 2014-11-05[86] Inclusion of an NTVDM; font improvements;[87][88] bug fixes[89]
Template:Version[90] 2016-02-16[91] 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
Template:Version[92] 2016-05-17[93] Improved Activation Context, Btrfs support, improved Shell, USB bug fixes, support for Virtual Machine Shared Folders
Template:Version 2016-08-16[94] Improved Btrfs and extended file system support, ReiserFS and UFS/FFS, introduced .NET Framework 2.0 and 4.0 support, Shell fixes and improvements
Template:Version 2016-11-16[95] New Winsock library, initial sections support, usual bug fixes
Template:Version 2017-02-16[96] Initial print stack support, minor font fixes, usual improvements and bug fixes
Template:Version 2017-05-18[97] Improved rendering of fonts and font metrics, major fixes in kernel and drivers, Microsoft Office 2010 tested as functioning
Template:Version 2017-09-01[98] Several fixes for dual-boot issues, improved theming support, NFS driver added, several kernel and filesystem fixes
Template:Version 2017-12-06[99] 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.
Template:Version 2018-04-14[100] Balloon notifications, notification tray, shell autocompletion, a new NTFS driver, crash dump reporting and experimental support for NT6+ software.
Template:Version 2018-07-23[101] ReactOS is (again) self-hosting.
Template:Version 2018-11-06[102] Supports BTRFS booting.
Template:Version 2019-03-04[103] 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.
Template:Version 2019-09-23[104] Kernel improvements, window-snapping feature, font improvements, Intel e1000 NIC driver, user-mode DLLs, new themes.
Template:Version 2020-04-09[105] New USB stack, FAT driver from FreeLoader optimized, new software introduced: Accessibility Utility Manager.
Template:Version 2021-12-16[106] "Send To" feature and Shell improvements, NEC PC-9800 boot support, ICMP improvements, Kernel improvements, NetKVM VirtIO bringup, miscellaneous changes & improvements
Template:Version 2025-03-21[107] Plug and Play fixes, audio fixes, memory management fixes, registry healing, improvements to accessories and system tools, and shell improvements.
Template:Version — Current development version.Script error: No such module "Unsubst".
Template:Version[108] — 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.
Template:Version

Features

Template:Prose Script error: No such module "Unsubst".

File:ReactOS 0.4.14 start menu and explorer screenshot.png
ReactOS 0.4.14 desktop: left Start Menu and right ReactOS's own File Explorer
File:ReactOS 0.4.14 explorer and winver screenshot.png
New shell in ReactOS (v0.4.0 and newer)
File:ReactOS 0.4.14 applications screenshot.png
Command Prompt, Spider Solitaire, Calculator and WineMine
File:ReactOS 0.4.14 device manager screenshot.png
Device Manager in ReactOS 0.4.14

Programs

Commands

Script error: No such module "Labelled list hatnote".

File:ReactOS-0.4.13 reg command 667x434.png
The ReactOS reg command

The following is a non-exhaustive list of commands that are supported by the ReactOS Command Prompt.[109][110][111]

Template:Div col

Template:Div col end

On-going national language development

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

ReactOS core development

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

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.[116] 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.[11][117]

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.[118] Template:As of, 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.[119] 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.[120]

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

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.[12] Conversely, projects like Wine,[13] and formerly Captive NTFS[124] and Longene re-use the open-source ReactOS code-base as well.[125]

Hardware driver stack

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

Networking

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

Wine cooperation

File:Wine on ReactOS.svg
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.[13][131] ReactOS uses portions of the Wine project so that it can benefit from Wine's progress in implementing the Win32 API.[131] 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.[115][120]

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

Other

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.[8] The KernelEx project is a Windows-API extension and compatibility layer project, which provides open-source implementations of some Windows-APIs.[133] Other contributing projects are MinGW, SYSLINUX, adns, ICU, GraphApp, Ext2, GNU FreeFont, DejaVu fonts, and Liberation fonts.[134][135][136]

Forks

Forks based on ReactOS exist:

Reception

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

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.[6] 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".[5] 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.[141][142] 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.[143]

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

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"[145]

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

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

See also

Script error: No such module "Portal".

Notes

Template:Reflist

References

Template:Reflist

External links

Template:Sister project

Template:FOSS Template:Operating system Template:Russian operating systems Template:Authority control

  1. ↑ Script error: No such module "citation/CS1".
  2. ↑ Script error: No such module "citation/CS1".
  3. ↑ Script error: No such module "citation/CS1".
  4. ↑ a b c d Script error: No such module "citation/CS1".
  5. ↑ a b Script error: No such module "citation/CS1".
  6. ↑ a b Script error: No such module "citation/CS1".
  7. ↑ a b Script error: No such module "citation/CS1".
  8. ↑ a b c d Script error: No such module "citation/CS1".
  9. ↑ Script error: No such module "citation/CS1".
  10. ↑ Tests for 0.4.14 on reactos.org (February 2022)
  11. ↑ a b c Script error: No such module "citation/CS1".
  12. ↑ a b Script error: No such module "citation/CS1".
  13. ↑ a b c Script error: No such module "citation/CS1".
  14. ↑ Script error: No such module "citation/CS1".
  15. ↑ Script error: No such module "citation/CS1".
  16. ↑ Script error: No such module "citation/CS1".
  17. ↑ Script error: No such module "citation/CS1".
  18. ↑ a b Script error: No such module "citation/CS1".
  19. ↑ Script error: No such module "citation/CS1".
  20. ↑ Template:Cite mailing list
  21. ↑ Script error: No such module "citation/CS1".
  22. ↑ Template:Cite mailing list
  23. ↑ Template:Cite mailing list
  24. ↑ a b Script error: No such module "citation/CS1".
  25. ↑ Reset, Reboot, Restart, legal issues and the long road to 0.3 on reactos.org by Steven Edwards (27 January 2006)
  26. ↑ Script error: No such module "citation/CS1".
  27. ↑ Script error: No such module "citation/CS1".
  28. ↑ Template:Cite mailing list
  29. ↑ Script error: No such module "citation/CS1".
  30. ↑ 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)
  31. ↑ Script error: No such module "citation/CS1".
  32. ↑ Script error: No such module "citation/CS1".
  33. ↑ Script error: No such module "citation/CS1".
  34. ↑ a b Template:Cite mailing list
  35. ↑ Script error: No such module "citation/CS1".
  36. ↑ Script error: No such module "citation/CS1".
  37. ↑ Script error: No such module "citation/CS1".
  38. ↑ 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" Template:Webarchive 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)
  39. ↑ Script error: No such module "citation/CS1".
  40. ↑ Russland-erklaert-ReactOS-zu-favorisierter-Windows-Alternative on heise online by Louis-F. Stahl (23 June 2015, in German)
  41. ↑ Russland macht ReactOS zu bevorzugter Windows-Alternative on Der Standard (24 June 2015, in German)
  42. ↑ Script error: No such module "citation/CS1".
  43. ↑ A personal appeal from ReactOS Project Coordinator Aleksey Bragin, accessed on 15 April 2013
  44. ↑ Spenderliste Template:Webarchive 24 December 2012, accessed on 15 April 2013 (in German)
  45. ↑ Script error: No such module "citation/CS1".
  46. ↑ Script error: No such module "citation/CS1".
  47. ↑ ReactOS Wants To Bring Open-Source Windows To The Cloud on Phoronix by Michael Larabel (22 January 2014)
  48. ↑ Script error: No such module "citation/CS1".
  49. ↑ Script error: No such module "citation/CS1".
  50. ↑ Script error: No such module "citation/CS1".
  51. ↑ ReactOS Working On A Community Windows OS on Phoronix by Michael Larabel (19 April 2014)
  52. ↑ Script error: No such module "citation/CS1".
  53. ↑ Script error: No such module "citation/CS1".
  54. ↑ reactos-community-edition on Indiegogo (1 June 2014)
  55. ↑ ReactOS: Große Fortschritte und Stipendien für Entwickler beim freien Windows-Nachbau Template:Webarchive on heise.de by Louis-F. Stahl (2 October 2014, in German)
  56. ↑ 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)
  57. ↑ 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)
  58. ↑ Script error: No such module "citation/CS1".
  59. ↑ Script error: No such module "citation/CS1".
  60. ↑ Script error: No such module "citation/CS1".
  61. ↑ Script error: No such module "citation/CS1".
  62. ↑ Script error: No such module "citation/CS1".
  63. ↑ Script error: No such module "citation/CS1".
  64. ↑ a b Script error: No such module "citation/CS1".
  65. ↑ Script error: No such module "citation/CS1".
  66. ↑ Script error: No such module "citation/CS1".
  67. ↑ Script error: No such module "citation/CS1".
  68. ↑ Script error: No such module "citation/CS1".
  69. ↑ Script error: No such module "citation/CS1".
  70. ↑ Script error: No such module "citation/CS1".
  71. ↑ Script error: No such module "citation/CS1".
  72. ↑ Script error: No such module "citation/CS1".
  73. ↑ Script error: No such module "citation/CS1".
  74. ↑ Script error: No such module "citation/CS1".
  75. ↑ Script error: No such module "citation/CS1".
  76. ↑ Script error: No such module "citation/CS1".
  77. ↑ Script error: No such module "citation/CS1".
  78. ↑ Script error: No such module "citation/CS1".
  79. ↑ Script error: No such module "citation/CS1".
  80. ↑ Script error: No such module "citation/CS1".
  81. ↑ Script error: No such module "citation/CS1".
  82. ↑ ReactOS review | LinuxBSDos.com
  83. ↑ Script error: No such module "citation/CS1".
  84. ↑ Script error: No such module "citation/CS1".
  85. ↑ DistroWatch Weekly, Issue 593, 19 January 2015
  86. ↑ Script error: No such module "citation/CS1".
  87. ↑ Script error: No such module "citation/CS1".
  88. ↑ Script error: No such module "citation/CS1".
  89. ↑ Script error: No such module "citation/CS1".
  90. ↑ DistroWatch Weekly, Issue 652, 14 March 2016
  91. ↑ Script error: No such module "citation/CS1".
  92. ↑ ReactOS 0.4.1 review — Cold fusion, Dedoimedo
  93. ↑ Script error: No such module "citation/CS1".
  94. ↑ Script error: No such module "citation/CS1".
  95. ↑ Script error: No such module "citation/CS1".
  96. ↑ Script error: No such module "citation/CS1".
  97. ↑ Script error: No such module "citation/CS1".
  98. ↑ Script error: No such module "citation/CS1".
  99. ↑ Script error: No such module "citation/CS1".
  100. ↑ Script error: No such module "citation/CS1".
  101. ↑ Script error: No such module "citation/CS1".
  102. ↑ Script error: No such module "citation/CS1".
  103. ↑ Script error: No such module "citation/CS1".
  104. ↑ Script error: No such module "citation/CS1".
  105. ↑ a b Script error: No such module "citation/CS1".
  106. ↑ a b Script error: No such module "citation/CS1".
  107. ↑ Script error: No such module "citation/CS1".
  108. ↑ Script error: No such module "citation/CS1".
  109. ↑ Script error: No such module "citation/CS1".
  110. ↑ Script error: No such module "citation/CS1".
  111. ↑ Script error: No such module "citation/CS1".
  112. ↑ Script error: No such module "citation/CS1".
  113. ↑ Script error: No such module "citation/CS1".
  114. ↑ Script error: No such module "citation/CS1".
  115. ↑ a b c Template:Cite speech
  116. ↑ Script error: No such module "citation/CS1".
  117. ↑ Script error: No such module "citation/CS1".
  118. ↑ Script error: No such module "citation/CS1".
  119. ↑ Script error: No such module "citation/CS1".
  120. ↑ a b c Script error: No such module "citation/CS1".
  121. ↑ Script error: No such module "citation/CS1".
  122. ↑ Script error: No such module "citation/CS1".
  123. ↑ Script error: No such module "citation/CS1".
  124. ↑ 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)
  125. ↑ 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."
  126. ↑ Script error: No such module "citation/CS1".
  127. ↑ Script error: No such module "citation/CS1".
  128. ↑ ReactOS gets USB stack with Haiku's help on OSNews by Thom Holwerda
  129. ↑ Script error: No such module "citation/CS1".
  130. ↑ Script error: No such module "citation/CS1".
  131. ↑ a b Script error: No such module "citation/CS1".
  132. ↑ Script error: No such module "citation/CS1".
  133. ↑ kernelex on sourceforge.net
  134. ↑ Script error: No such module "citation/CS1".
  135. ↑ Script error: No such module "citation/CS1".
  136. ↑ Script error: No such module "citation/CS1".
  137. ↑ Ekush Emulator and Its License Pains on OSNews by Eugenia Loli (10 November 2004)
  138. ↑ Ekush OS – stolen source code/copyright violation (archived 2004)
  139. ↑ Ekush The Next Generation Operating System on akshor.com (archived 2004)
  140. ↑ 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)
  141. ↑ Script error: No such module "citation/CS1".
  142. ↑ Script error: No such module "citation/CS1".
  143. ↑ Script error: No such module "citation/CS1".
  144. ↑ Script error: No such module "citation/CS1".
  145. ↑ Script error: No such module "Citation/CS1".
  146. ↑ Script error: No such module "citation/CS1".
  147. ↑ Script error: No such module "citation/CS1".
  148. ↑ Script error: No such module "citation/CS1".
  149. ↑ Script error: No such module "citation/CS1".
  150. ↑ Template:GitHub
Retrieved from "http://debianws.lexgopc.com/wiki143/index.php?title=ReactOS&oldid=712278"