Talk:ReactOS

This is the talk page for discussing improvements to the ReactOS article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1

/Archive 1: Feb 2005 - Oct 2006

On Portal:Free software, ReactOS is currently the selected article

(2006-09-22) Just to let you know. The purpose of selecting an article is both to point readers to the article and to highlight it to potential contributors. It will remain on the portal for a week or so. The previous selected article was PuTTY. Gronky 11:04, 22 September 2006 (UTC)[reply]

The selected article has rotated again and is now Wine. Gronky 22:41, 1 October 2006 (UTC)[reply]

ReactOS website down?

The official ReactOS website seems to be unreachable. Does anyone know why it's down? - Cire, Oct, 28 2006

The topic of the #reactos channel on Freenode currently says:

ReactOS server (DNS, svn and website cache) main server is down, sorry for any inconvenience | russian based webhoster cause the downtime, fireball will switch to another hoster probably on monday

-- intgr 16:32, 28 October 2006 (UTC)[reply]

The website works again. Cristan 15:08, 31 October 2006 (UTC)[reply]

Audit at 100%

The site currently states that the audit is complete. This is just a bug in the website:

IRC quote:
phoenix64: The audit is done? Woohoo... Very Happy
Christoph_vW: no
phoenix64: no?
phoenix64: "100.0% complete"
Christoph_vW: the progress bar is wrong
phoenix64: Neutral

Cristan 11:00, 2 November 2006 (UTC)[reply]

Currently the website states that the audit is at 95.9%, so it seems the progress bar works again. Cristan 12:16, 6 November 2006 (UTC)[reply]

Oh well; hopefully it won't be too long before its at 100% :) -- Limulus 06:37, 11 November 2006 (UTC)[reply]

Boot screen

There is now a screenshot at the page of the new ReactOS bootscreen. I think this one should be removed for now, because this new bootscreen won't be available until at least 0.3.1. Without an explanation, it will only make the article unclear. When the new bootscreen is available in ReactOS, the image should be uploaded in Wikimedia commons because it is GPL and when hosted there, it is available at other language wikipedia's as well. - Cristan 14:25, 6 November 2006 (UTC)[reply]

This bootscreen is currently available in any post-0.3.0 build which can be downloaded from ReactOS's servers as a binary/ISO or in source form. --74.56.173.109 04:20, 7 November 2006 (UTC)[reply]

That's what I meant: it isn't available yet in the current stable version. You can't expect every user in Wikipedia who downloads ReactOS to download an SVN build. I think it's confusing for people to not see this bootscreen after downloading and running ReactOS. The screenshot should either mention that it will be in 0.3.1 or the screenshot should be removed. - Cristan 09:07, 7 November 2006 (UTC)[reply]

Still no reaction back. I'm removing the image now. Cristan 11:43, 4 December 2006 (UTC)[reply]

ReactOS Server HDD Crash

From ReactOS website: Failure Note

ReactOS Project

Time Line and Status: (what we know so far)

   * Thursday 00.05 Raid Controller on HostSystem where Reactos Backend is running decided to do a Raid Rebuild.... (maybe triggerd by a dead hdd..unknown - Logfile is unclear about this)
   * Thursday 03.15 Raid Controller on Hostsystem Crashed the System, as it took Raidset offline
   * Thursday 09.00 Technicans investigated local to find the problem of the "crash" -- was unknown Why it crashed .. and came with the cool news "on reboot, the server writes: No operating system found..."
   * Thursday 15.00 It was clear, that the Raid controller inside the Server failed, and they "forgot" all Raid partitions. (reason unknown)

Background: Reactos is splitted into a frontend and Backup system, Backup System resides inside a Vmware Session. The problem is, that the Vmware Session (disk) is on this failed Raid Controller. (also the daily backups) -- only an old 1 Month backup is avaliabe but this is indeeed VERY old.

Atm we are dumping down the Data from the Raid Disks disk with dd to a Transfer disk manually.

The 3'rd.. 4'th .. attempt was already VERY successful, the filesystem mounted almost without errors, but it was still not 100%.

We are Sorry, that this takes long, but did you ever dd a 1TB system ? to a new hdd ?

Really, I have seen EVERYTHING in my life ... But we have never seen a Raidcontroller, who kills the Raidset so brutal, that not even a new Raidcontroller sees the Raid partition. (looks like a Software glitch in the Raidcontroller)

Future

We work hard, that over the Weekend the System comes up again. (all necessary Parts needed are bought already) The chance that all this happened everything without loosing any data is a clear 99%.

Even, if we could, we could give more details, Like: Type of Raidcontroller, and so. But i do not want to Release this public, as "Bugs" can happen everywhere, and even Raidcontroller Programmers are People who can do mistakes. (maybe it was a failure of the RAM on the Raidcontroller...)

But i can garantee you here, that the Hardware is not a kind of <10k$ system ....

So keep cool, stay tuned, and do not panic, and do some X-Mas Party

(Thats indeed one of the problems we have, as all people needed to work on this are logically "on holiday", "drunk", ... --- > as always .. - and logically we are hit by Murphy's Laws (Anything that can go wrong, will go wrong.)...) Preeeemo 16:31, 17 December 2006 (UTC)[reply]

ReactOS Website back online again: http://www.reactos.org/en/news_page_29.html

ReactOS is not a current event.

According to the information available, the {{current}} is for articles that are undergoing massive changes in traffic due to being a truly current thing. That would imply that it has to be new, popular, etc. Examples of things that were at one point or another current events were things like Hurricane Katrina and Execution of Saddam Hussein—neither of which are current events any longer because they’re “yesterday’s news”.

That having been said, if there is a section that becomes active in this article, it certainly should get the {{current|section}} tag. Perhaps when the next release comes out or whatever. Then it would be appropriate, at least for a short time. —Mike Trausch (fd0man, Talk Page) 21:00, 19 January 2007 (UTC)[reply]

Latest stable release

Should 0.3.0 really be called stable? This isn't even beta yet. Is it referred to as (relatively) stable within the project? It seems to me that calling any version stable could be misleading, to those who don't know what alpha software is. Jobarts^-Talk 06:42, 22 January 2007 (UTC)[reply]

I think you're right. 0.3.0 is far from stable. We should do it like Beryl. With latest stable version "N/A" and latest preview version (in this case) "0.3.0". Cristan 11:08, 22 January 2007 (UTC)[reply]

I don't know if this was changed and reverted, but I'm going to make the change. Althepal 02:29, 11 August 2007 (UTC)[reply]

Patent issues

If no one has any comments or suggestions, I'm going to add a section about the possible patent infringement in ReactOS. I plan on using [1] for a reference, and likely this quote from that page, "As a rule, patents are fundamentally incompatible with Free Software..." With the multiple acussations leveled from Microsoft against patent infringment in the opensource community I think this deserves at least a mention in the article. --Android Mouse 04:27, 30 May 2007 (UTC)[reply]

Error screenshots

All the current screenshots play out the idea that the OS is working fine. This is far from true, with system crashes around every corner. Can there be one screenshot of an error happening? And maybe fewer other screenshots? Althepal 02:29, 11 August 2007 (UTC)[reply]

What's the point?

Don't worry, this comment isn't as negative as it looks :-) . I just wanted to suggest that the article would be better with a section discussing why ReactOS is being built. What is the goal of the project, who are the intended users, what is the reason for reimplementing an operating system that's already widely (if not freely) available? PeteVerdon 16:13, 19 August 2007 (UTC)[reply]

I'm sure this info could be found on their site, but I'm pretty sure it was made to provide a non-unix (completely Windows-compatible) operating system under a free license. Because, not everybody wants to use Linux (and Linux with wine cannot support every program for windows), and it is for people who want a free alternative. Those who can afford windows will probably stick with them for a better guarantee of it working + the ability to run Microsoft software that won't install on anything other than genuine Windows, but this os is for everybody else. Althepal 03:47, 21 August 2007 (UTC)[reply]

Which Windows is this supposed to clone?

9x, NT, XP, what? 66.28.178.67 16:53, 28 August 2007 (UTC)[reply]

I've heard "NT", "Serve 2003," and "XP" float around the forum. I think it is NT. Althepal 17:38, 28 August 2007 (UTC)[reply]

XP is part of the NT family. I heard they were aiming for the feature level of Windows 2000, though. - Sikon 03:27, 29 August 2007 (UTC)[reply]

"The ReactOS architecture is based on that of Microsoft Windows NT 4.0" and "The original target for ReactOS, with regards to driver and application compatibility, was Microsoft Windows NT 4.0. Since then, Microsoft Windows 2000 and Windows XP have been released. Microsoft Windows 2000 and Windows XP are both descendants of Windows NT. As such we can gradually shift our compatibility target without worrying about the architecture changing too much. In fact, internally, Windows 2000 reports version information as Windows 5.0 and Windows XP as Windows 5.1. The ReactOS team have decided to maintain Windows NT 4.0 as the official compatibility target. This is because most of the resources, articles and books on Windows NT/2000/XP technology are written for Windows NT 4.0. This does not mean that features present in later versions of Windows NT based operating systems will not be implemented in ReactOS."[2] -- Limulus 07:11, 29 August 2007 (UTC)[reply]

Its NT4 asSAMBA (on which they will be basing the networking) is based on the NT4 style domain model rather than the newer XP style Active Diretcory model.