Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

ReactOS 0.3.1 Released

Posted by kdawson on Sun Mar 11, 2007 06:01 PM
from the fresh-bits dept.
fireballrus writes with news of the release of ReactOS 0.3.1 — press release, changelog, download packages. ReactOS is "an open source effort to develop a quality operating system that is compatible with applications and drivers written for the Microsoft Windows NT family of operating systems (NT4, 2000, XP, 2003)." The press release notes: "Please don't forget this is an alpha-stage operating system, which means it is not suitable to replace your main OS. Also, this release is aimed to be run mostly in virtualizers / emulators (like QEmu, VMWare, Parallels, etc): because of the big amount of changes, our development team was not able to test/fix all problems which arise when running ReactOS on real hardware."
+ -
story

Related Stories

[+] ReactOS Reviewed in Depth 220 comments
An anonymous reader writes "NeoSmart Technologies has an incredibly detailed (6 long pages!) and mostly positive review of ReactOS, The Open Source Windows. The review covers the goals of ReactOS and how well it meets them, system stability, application compatibility, kernel design and development, and the networking stack. It discusses the use of WINE in ReactOS' kernel and the effect on both its compatibility and development times." For the visual learners, here are some screenshots."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by dreamchaser (49529) on Sunday March 11 2007, @06:04PM (#18310842) Homepage Journal
    I've messed with ReactOS on and off for awhile. They really deserve some kudos for what they've accomplished to date, even if the system isn't really usable yet. I strongly encourage you to check them out if you're at all interested in the project; they've done some nice coding to date but can use all the help they can get.

    As mentioned, it's perfect to diddle with in a VM environment, though I have loaded it on a dedicated test machine before and that was a lot of fun too.
    • Is there a possibility of running this XP clone on non x86 hardware?

      • "Is there a possibility of running this XP clone on non x86 hardware?"
        maybe if you were running it through an emulator...
        • Re: (Score:3, Interesting)

          NT is designed to be portable, and Microsoft has ported it to MIPS, Alpha, PPC, x86, Itanium and AMD64 each at one time or another.

          That's stretching the truth a bit.

          The AMD64 'port', for starters, isn't in the same category as other 'ports' as it doesn't actually require any porting! There are optimisations that can be done. But is this a full-blown 'port'? Doubt it.

          Next in terms of completeness is the Alpha port, which was abandoned long, long ago. Was it NT3.5 that used to run on Alpha? Something like t

      • Re: (Score:3, Insightful)

        It doesn't seem that you know that ReactOS and WINE share a lot of work. For example, the wine Task Manager was created for ReactOS and then integrated into wine. So far, ReactOS has benefitted more from the sharing, but as ReactOS gets more complete, the extent of the sharing increases.
      • It is unlikely that you will find an application that will work on ReactOS that dos not work on wine or vice versa. Both projects share API code and research. Compiling ReactOS for other architectures other than 64bit x86 extensions would be doable but fairly useless as windows application binaries wouldn't work on it. For example, Linux runs happily on powerpc, macromedia has a flash plug in for Linux, but it will not run on my Linux ppc box, because it is compiled for Linux x86.

        While I was excited in
  • Cool project (Score:5, Informative)

    by 26199 (577806) * on Sunday March 11 2007, @06:06PM (#18310852) Homepage

    The legal issues are kinda scary but it looks like they have them under control [reactos.org]. All respect to them for attempting the impossible... and from the look of it, they're a good way to succeeding :)

    • Re:Cool project (Score:5, Interesting)

      by Anonymous Coward on Sunday March 11 2007, @06:13PM (#18310902)
      The legal issues associated with reverse engineering an operating system to run programs originally written for windows should not be any scarier than those associated with reverse engineering (clone) the hardware to run software written for IBM PC. IBM had deep pockets and a penchant for enforcing its large IP portfolio, but the cloners won.
      • Re:Cool project (Score:5, Insightful)

        by ScrewMaster (602015) on Sunday March 11 2007, @06:40PM (#18311088)
        On the other hand, at that point in time IBM wasn't really all that interested in stopping the development of clone PCs, for a variety of reasons. Had they really chosen to throw their weight around, they most certainly could have, in which case someone else would have taken over (which might have been a good thing for world of personal computing, when you get right down to it.)

        Apple, in fact, spent far more time in court suing the likes of Franklin Computer (who, in many ways, had a better product.) Granted, that may have been simply because IBM didn't perceive the personal computer as being a big part of their future, at that point in time, since big iron was still their bread-and-butter. However, if you want to get into the history of anticompetitive behavior at IBM, check out out how they dealt with anyone making plug-compatible components for their mainframe systems in the 60's and 70's. That was a very different story. There's a guy named Amdahl that would be happy to enlighten you.

        Besides, the legal climate for reverse-engineering is decidedly less friendly to cloners than it was in, say, 1981.
        • The comparison between Apple and IBM is simply not valid. Franklin didn't simply reverse engineer the Apple computer. They copied Apple's design down to the individual electrons. The BIOS and OS was simply stolen from Apple. There was even several places in the Franklin's ROM and in the OS where the string "Copyrighted by Apple Computer" was there for all to see. Even Franklin had to admit they copied the ROM and OS. Franklin tried to use the argument that since the OS and ROM was not in a readable form, it
        • All I can say is God Bless these people for trying to do what is so badly needed in the world of computing right now. Until we get a real competitor to the Microsoft/Apple hegemony that can actually run the professional programs that people need, we users are going to continue to suffer under hobbled applications, less-than-stellar interfaces and substandard quality control (and that's just Windows - Apple has their own problems with being able to bring a product that gives good value to the market - and n
          • I believe it was the brief threat of OS/2 that made MS and Apple get their acts partially together way back when. We saw both those companies put out products that were far more sturdy and usable in the period after OS/2 hit the market.

            At the time when OS/2 "hit the market" (and for some years thereafter), it was a Microsoft product.

            What timeframe are you actually thinking of ?

  • by Arceliar (895609) on Sunday March 11 2007, @06:10PM (#18310878)
    does it run cygwin?
  • While Microsoft drags their feet with compatibility both with the Justice Dept here in the US and with the European Commission, it's nice to see people working on projects like this which potentially will enhance the interactivity between all platforms. Macs and Linux get along fine but Windows doesn't want to get along with anyone. Maybe ReactOS (being an open source project) will finally force Microsoft compatibility without their consent.
  • Screenshots (Score:3, Informative)

    by Anonymous Coward on Sunday March 11 2007, @06:13PM (#18310904)
  • Awesome (Score:4, Informative)

    by MrP- (45616) <rob@NospAm.elitemrp.net> on Sunday March 11 2007, @06:30PM (#18311018) Homepage
    Wow, it's just like Windows.

    I installed it under Parallels, ran Solitaire and it rebooted and then disconnected my network outside of Parallels.

    Seriously though, yeah it's alpha but it's pretty cool. Great work!
    • It would be interesting to compare Reactos' interpretation of Alpha vs Microsoft's. What's the BSOD rate?
      • Patent 6,379,553: Method to Display Failure Information

        A method and system are provided for displaying failure information on a limited resource computing device. Unparseable textual messages are displayed upon failure. ...

        4. The method of claim 3, in which the screen is blanked before the message is displayed.

        5. The method of claim 4, in which the message is displayed on a blue background.

        ---

        As you see, React cannot legally implement the Blue Screen of Death.
  • How to Avoid Vista (Score:5, Insightful)

    by rueger (210566) on Sunday March 11 2007, @06:51PM (#18311130) Homepage
    The only reason why a lot of us would upgrade to Vista is because Microsoft will stop supporting our current OS with bug fixes and security updates. Vista to me looks like a nightmare of DRM and restrictions on what I would want to do, but I can see my current Win 2K install becoming as outdated and unsupported as Windows 98.

    If React OS can keep me running my current Windows apps in a sensible, secure, and supported environment, then I can avoid Vista. That means less headaches, and less expense.

    Really, these folks may have found a really nice niche.

    (Honestly, looking at Vista make me think that this is the time when someone, whether Linux, Mac, or something else, could make significant inroads.)

    • by RLiegh (247921) * on Sunday March 11 2007, @06:57PM (#18311172) Homepage Journal
      >If React OS can keep me running my current Windows apps in a sensible, secure, and supported environment, then I can avoid Vista. That means less headaches, and less expense.

      Which is exactly why Microsoft will dig deep into it's legal fund and patent portfolio and nuke reactos off the face of the planet the very second that ReactOS becomes a practical alternative to Windows.
      • by MBGMorden (803437) on Sunday March 11 2007, @07:21PM (#18311320)
        Doubtful. Reactos has been around a LONG time. They've always been very careful to avoid any actions that would be legally unsound. If you play the game right, you can legally clone a system and there's nothing that they can do to you. BTW, if they happened to sue ReactOS, WINE is in trouble too. Most of the Windows API code that actually deals with running programs they closely model on each other.

        In any event, the whole topic is moot. If they sue based on software patents, then ReactOS can simply move the servers to a country that doesn't recognize them (and there are will plenty of those).
        • And will the developers move to Outer Elbonia too? If MS had a (e.g.) U.S. court declare that Reactos was an Unclean Abomination That None May Look Upon, I'm pretty sure that the courts would frown on a U.S. resident developer who continued to work on it and claimed US laws didn't apply because they submitted the patches to a server in Outer Elbonia.

          IANAL
      • I doubt they would be able to. The guys producing ReactOS went through a self-imposed code audit awhile back, because someone informed them that some patents might have been violated. The way they have been running things, about the only thing they could possibly nail them on at any point would be violating their trade dress for Windows.
    • by linguizic (806996) on Sunday March 11 2007, @07:01PM (#18311206)
      I'm betting that Apple is making significant inroads. The idea of running XP for 7 more years drove me to buy a macbook.
  • I just don't understand.

    an open source effort to develop a quality operating system that is compatible with applications and drivers written for the Microsoft Windows NT family of operating systems

    but

    this release is aimed to be run mostly in virtualizers / emulators

    So it won't run (or at least won't run well) on actual hardware, so that's the driver issue nullified. I'm not running ReactOS for the drivers, it's running with virtualisation under my already free OS. So I'm running it so i can run Windows pro

    • I try to use only free software, but if I had to use some software under Windows, I'd run Windows. Creating an alpha environment to run proprietary software just seems wrong.

      But what if you were running Windows, and wanting to move to another OS such as Mac or Linux....but you realize you have to keep Windows for one or two apps? Or maybe you don't HAVE to, but if you have to give up those apps, you'll lose some productivity.

      Nothing is outright STOPPING you from moving to the new platform, but it sure becomes a lot harder to justify it. Something like WINE or ReactOX can help a lot in making the switch economically practical and smoothing the transition. (I think someone

    • So I'm running it so i can run Windows programs under my free OS?

      No, you're running it so you can help develop and test it. No one is advocating running it in a VM in a production environment. It's a testing and development release. Obviously the real thing will run on the bare metal; it's just not ready for that yet.

      Creating an alpha environment to run proprietary software just seems wrong.

      This is just stupid as hell. They don't make it alpha on purpose. It's not finished yet.

      • WTF do you expect? It's version 0.3.1.
        Thank you Mr. Anonymous Coward, I know it's version 0.3.1. Is that a reason to use it though? You didn't really answer my question.
        • Thank you Mr. Anonymous Coward, I know it's version 0.3.1. Is that a reason to use it though? You didn't really answer my question.

          you use it for testing? that sounds like a pretty good reason for using alpha software.

  • by sentientbrendan (316150) on Sunday March 11 2007, @07:39PM (#18311418)
    my understanding is that their compatibility with win32 is largely based on wine, and so it has most of the same bugs running win32, and then some.

    What I'd really like to see is some major company getting behind reactos and wine. Getting a portable win32 layer really working to the point where it's no longer just a toy is going to take a major effort, more of an effort than the open source community seems willing to put forward at this time. Working win32 is a real possibility, but it needs a lot of people to get behind it.
    • Re: (Score:3, Interesting)

      my understanding is that their compatibility with win32 is largely based on wine, and so it has most of the same bugs running win32, and then some.

      No. The projects are working together, and code goes back and fourth... That's kinda the point of Open Source, isn't it? If somebody else does it better, you use what they've written, in your own project.

      A few of the reasons to use ReactOS instead of WINE:

      Drivers. How well does WINE load that WinXP dll/ocx driver for your WiFi card? Display driver? etc.
      Perf

      • by catbutt (469582) on Sunday March 11 2007, @10:09PM (#18312146)

        To be fair to WINE, it is already more than just a toy. I am able to run the full Starsiege Tribes
        Yes, and to back up the statement that it's not a toy, I should point out that here at NASA, we are using Starsiege Tribes to design the next Mars rocket.
  • I've been running this in a virtual machine on Windows and haven't seen anyx938U#Jklx j *** NO CARRIER *** Well, I guess I was wrong. At least Windows allowed me to save what I had previously typed, and Windows is so stable tha83jkJKLEv &#j3kR *** NO CARRIER ***
    • If there are hidden API's, then that means nobody knows about them, which means, nobody uses them (apart from MS software, but lets be honest, if you're running a free NT clone, you aren't going to be running MS office are you?), which means that it won't affect them in the slightest.

      And if there are any hidden API's, the DOJ and EU will hit MS with the antitrust stick.

      API changes might be an issue, but again, if the API's are in use, they can't do this without breaking other software. Hiding stuff from a
      • (apart from MS software, but lets be honest, if you're running a free NT clone, you aren't going to be running MS office are you?)

        Yes, actually.

      • It also wouldn't make much business sense; who would want to develop for a platform where the goalposts are constantly moving?

        You just described everyone who's been developing on the Microsoft bandwagon for the past twenty-five years or so, me included. The goalposts not only move, but they have JATO units attached to them that fire at random intervals. Now ... does that make much business sense? No, not really: but that's how things work in the world of Microsoft operating systems.
    • by Jartan (219704) on Sunday March 11 2007, @06:44PM (#18311102)

      Why? Such wasted effort to duplicate a flawed system of software.


      Well it would be interesting to see if the effort allows them to fix some of the flaws and continue to run a lot of the software. For me personally I look at this sort of an effort as a perfect solution to the main thing that keeps me from ditching MS: games.
    • by catbutt (469582) on Sunday March 11 2007, @06:55PM (#18311166)
      Because most applications that people use are written for Windows.

      Once you give people other options for running those apps, that aren't controlled by a company trying to protect their monopoly, you open up a lot of possibilities for the industry to move away from Microsoft lock-in.
    • Why? Such wasted effort to duplicate a flawed system of software.

      Just like Linux was, you mean ?

    • What if, as it becomes closer to a release product, it becomes decentralized. Anyone who had done enough work on the original ReactOS walks away from the project perhaps with a public request not to use their work. What if there is no one person or entity to sue? Patches could be written for specific issues by the user community, so support would be distributed as well. Basically, is there a way to spread the legal vulnerability/liability between so many people, that MicroSoft would have to resort to suing
      • a) by the time ReactOS is usable, there will be. Also, american law is enforcable overseas; cf AllOfMp3 closure and The Pirate Bay raids.

        b) you're assuming that they'll be acting alone; they have novell's help on the Linux front, and slapping a Cease-And-Desist on ReactOS would be trivial.

        c)the only thing useable in an antitrust suit would be the undocumented apis...which have nothing to do with ReactOS. Anything done in ReactOS can easily be found and studied via MSDN.
      • No one has ever gone after MS's meat and potatoes before. Also, what do you think MS is preparing to do with all the patent noise over "linux IP violations"?
      • Re: (Score:3, Insightful)

        mod my comments down all you like, but it's a fact that once ReactOS becomes any sort of threat (real or percieved) to Microsoft, Microsoft will break out the lawyers and the software patent lawsuits.

        Hide your heads in the sand all you want to...it's your time you're wasting, not mine.

        Maybe these people will be able to get jobs as system programmers as a result of this. Maybe they want to see how far they can go before they get sued. Maybe they are hoping that by the time this get to that point the world will be more reverse engineer friendly. Maybe this is just civil disobedience.

        In the 70's and 80's UNIX was a product developed by a big company, the phone company to be precise. it has since become an idea replicated many times, always poorly, sometimes less poorly than K&R's

    • Of course... Microsoft made a new driver system and API for Vista, which could be considered a force in the opposite direction, as things written specifically for Vista are not cited as being compatible with ReactOS.