Slashdot Mirror


ReactOS Revealed

reactosfanboy writes "DRM Hacker Alex Ionescu explained the internals of ReactOS in a recent talk. Ionescu indicates that ReactOS is nearly 100% binary and API compatible with the Windows 2003 kernel, and that they are aiming for full Vista compatibility. Ionescu attempted to demonstrate ReactOS but only succeeded in installing it after two BSoDs. This alone should make it clear that ReactOS is still not ready for prime time." In what may be a red flag for Microsoft's lawyers, ReactOS is described as "an environment identical to Windows, both visually and internally." Here are slides from Ionescu's talk (PDF), which might prove more useful than the video offered in various forms at over 450 MB.

71 of 280 comments (clear)

  1. On the contrary... by Anonymous Coward · · Score: 5, Funny

    ...but only succeeded in installing it after two BSoDs ... the Windows emulation seems perfect !

    1. Re:On the contrary... by rwven · · Score: 3, Insightful

      Funny, I've had to install it hundreds of times and I'd say my attempts per success is very close to 1:1. I've very recently encountered my first failure when building a new computer. XP (SP2 slipstreamed as well) would bluescreen on the install. Had to use Vista instead (how's that for mildly ironic? Other than that I can honestly say I've never had any issues installing Windows...

      Windows is not nearly as unstable as the FUDDERS would like to make it seem.

    2. Re:On the contrary... by slackmaster2000 · · Score: 4, Insightful

      We're kind of ruining the top post which was actually pretty funny, but...

      I would almost agree with you, if only looking at a snapshot from about 2002 until 2006 during which I was no longer dealing with 9x and NT4 installations. Installation headaches were pretty commonplace prior to these years. Once hardware vendors had all gotten used to the ways of NT5, installing Win2K and XP became a total breeze. Rarely have I had trouble installing either operating system. They will choke occasionally on cheap and/or new hardware, but with typical stuff installation is usually a no-brainer.

      And now Vista is upon us, and it's not detecting a lot of real obscure hardware, like say, MY CDROM DRIVE. WTF. Once again it's become hit and miss...or would be, if I chose to install Vista in production at this time.

      Difficulty installing an OS isn't really a good measure of quality anyhow. I recently had a bad experience installing Ubuntu 6.05LTS to an array on an adaptec I2O controller. Rock solid once I got it fixed. That's just the way it goes sometimes.

    3. Re:On the contrary... by dargon · · Score: 2, Insightful

      Personally, if it's a Compaq, I'd blame Compaq, not Windows

    4. Re:On the contrary... by j00r0m4nc3r · · Score: 2, Insightful

      Kind of sad that in the entire history of Windows, there was only a 4-year window (no pun intended) of stable installation.

    5. Re:On the contrary... by AndrewNeo · · Score: 2, Insightful

      There's a difference between hardware detection and stable installation. Every time I've installed Vista it's gone out without a hitch, the image based installer failing on me less than XP's installer. (On the same note, I think my XP Pro CD is bad.) At least I can just re-burn the copy of Vista I got from Microsoft Connect legally as opposed to violating the law to make a backup of software I own that's labeled 'Do not make copies of this disc' just so I can install it.

    6. Re:On the contrary... by ignavus · · Score: 2, Funny

      Microsoft should ask him how he got the BSOD count down so low.

      --
      I am anarch of all I survey.
    7. Re:On the contrary... by x2A · · Score: 2, Insightful

      Please don't abuse the tags.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    8. Re:On the contrary... by rucs_hack · · Score: 2, Insightful

      oh come on. This is slashdot.

      Protocol requires that I leap to the wrong conclusion immediately and rant on about that whilst also having a go at Microsoft.

      Do you know nothing?

    9. Re:On the contrary... by mdwh2 · · Score: 2, Insightful

      Kind of sad that in the entire history of Windows, there was only a 4-year window (no pun intended) of stable installation.

      That's highly misleading - going by release dates, Windows 2000 was released in 2000, and Vista in 2007, giving us 7 years (presumably the OP was talking about when he had to deal with them, which includes beta releases and people still using an old version).

      That's the same timeframe which Mac OS has only offered a stable OS (things like memory protection), in the form of OS X.

      Of course, talking of "entire history of" is irrelvant anyway, since versions previous to NT were different operating systems, just as classic Mac OS has no connection to Mac OS X other than the name and company producing it.

  2. BSOD-OS by gardyloo · · Score: 5, Funny

    Ionescu attempted to demonstrate ReactOS but only succeeded in installing it after two BSoDs. This alone should make it clear that ReactOS is still not ready for prime time. Yeah, thank goodness the OS it's modeled after *never* does that.
    1. Re:BSOD-OS by El_Muerte_TDS · · Score: 4, Insightful

      On a serious note.
      Given the limited resources of the ReactOS team it's not even that bad. Even Microsoft had (serious) issues with pretty much every new Windows version presentation.

  3. Link? by russint · · Score: 5, Informative

    How about a link to ReactOS in the summary?

    --
    ^^
    1. Re:Link? by Tenebrarum · · Score: 4, Funny

      How about a link to ReactOS in the summary?

      This time, we don't want to take their website down.

  4. Doubt microsoft would care by stratjakt · · Score: 2, Insightful

    ReactOS would still be unsupported and untrusted in business, and it's proliferation would only add to MSFT's dominance of the market.

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:Doubt microsoft would care by 99BottlesOfBeerInMyF · · Score: 3, Interesting

      ReactOS would still be unsupported and untrusted in business, and it's proliferation would only add to MSFT's dominance of the market.

      ReactOS would be useful for companies looking for a way to move off of Windows but who have binaries that only run on Windows. Due to the proliferation of VM technology, a VM running ReactOS on top of your OS of choice could make migration away from Windows cheap enough to be an option. If ReactOS is cheap enough, it could displace Windows by itself for limited applications. A free OS Dell or someone can install that still lets them get paid for crapware and which still lets end users run games and junk software from Walmart could easily grab market share away from Windows. Anything that threatens MS's dominance with Windows, whether it detracts from Linux or your favorite OS or not, is good for motivating MS to make Windows better. If Windows is as good as other OS's, I don't care if it is dominant as much.

    2. Re:Doubt microsoft would care by drinkypoo · · Score: 4, Insightful

      Wine offers a much more compelling method of migrating from Windows. ReactOS would still require you to be running a full separate operating system. If you wanted to do that, you could run your current Windows XP licenses in virtual machines, and just run Linux on the host, or what have you. Granted, Wine isn't entirely there yet... but neither is ReactOS.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Doubt microsoft would care by 99BottlesOfBeerInMyF · · Score: 4, Interesting

      Wine offers a much more compelling method of migrating from Windows.

      WINE is an incomplete re-implementation of the Windows APIs, while ReactOS aims to be a complete one. I don't have any real confidence that WINE will ever work reliably for arbitrary software. It is a nice crutch for specific, common applications. It is a reasonable route to building a quick and dirty port. I don't think it will ever fill the role of a method of moving away from Windows and still running random (often proprietary or outdated) applications.

      ReactOS would still require you to be running a full separate operating system. If you wanted to do that, you could run your current Windows XP licenses in virtual machines, and just run Linux on the host, or what have you.

      That is pretty much what I am doing now, except most WinXP licenses are not portable to new hardware and such a move is often accompanied by a move to new hardware. ReactOS is likely to be more lightweight than the current version of Windows and less likely to cause headaches with licensing and registration and DRM shutting it down arbitrarily. It also would have save my company a hundred bucks a license and that adds up.

      Granted, Wine isn't entirely there yet... but neither is ReactOS.

      I actually looked at WINE and a couple of commercial WINE-based offerings and ReactOS before I chose to run WinXP in a VM. It was the most expensive solution by far (other than Windows outside a VM) but the only one that worked. In future I could see going either way, but I think the overhead from ReactOS is likely going to end up less of a consideration that the necessarily limited range of WINE.

    4. Re:Doubt microsoft would care by BorgDrone · · Score: 3, Informative

      WINE is an incomplete re-implementation of the Windows APIs, while ReactOS aims to be a complete one.
      From the linked PDF:

      Wine makes up the bulk of ReactOS'sWin32 Libraries, which are mostly left untouched.

    5. Re:Doubt microsoft would care by Shawn+is+an+Asshole · · Score: 2, Informative

      There is work towards Xen support. Though, Xen doesn't provide a GUI like VMWare or even Qemu so you'd have to run something like VNC to get the display.

      --
      "It ain't a war against drugs.it's a war against personal freedom" --Bill Hicks
    6. Re:Doubt microsoft would care by Stevecrox · · Score: 2, Insightful

      Umm didn't you make his point? Wine isn't a complete re-implementation of the Windows API's, sure much of reactOS can be made up from WINE but its still got more under its hood than just WINE as your qoute says.

  5. 100% Compatible? by MachineShedFred · · Score: 3, Funny

    Not until all the malware works too!

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  6. With no disrespect to the ReactOS developers... by EvanED · · Score: 2, Informative

    They might want to look up what "identical" means. There is still a very long way to go. (I could have put a traditional screenshot up there too, from W2K or even W95, and it would still be true.)

    1. Re:With no disrespect to the ReactOS developers... by RealGrouchy · · Score: 2, Insightful

      It's hard to hit a moving target.

      I know plenty of people who use the "Windows Classic" skin on XP, because that's what they're used to.

      When MS updates its software, there are two types of changes, with different audiences: minor to moderate performance/security upgrades (which require most people to upgrade in order to still communicate with each other, i.e. MSO), and major interface upgrades, to cater to the magpies that will only buy the new version if it is shinier than the previous one.

      Unfortunately, these interface "upgrades" require a certain degree of re-learning the same software. I would suspect that ReactOS, like OpenOffice.org, aims to cater to those people who want to be compatible with the rest of the world (who run the "updated" version), but who don't want to learn a new interface every time Microsoft chooses to impose a new one. ...or at least, the software can fork, and dev-users can CHOOSE how they want to interact with their software.

      - RG>

      --
      Hey pal, this isn't a pleasantforest, so don't waste my time with pleasantries!
    2. Re:With no disrespect to the ReactOS developers... by Handover+Phist · · Score: 2, Funny

      Whereas the Microsoft folk look at it the other way around...

  7. Re:Red flag? by squiggleslash · · Score: 4, Informative

    There was a minor scandal last year when the ReactOS project had to be suspended after it was found that some developers had been exposed to the real Windows source code (which is available under shared source licenses in some contexts), and after a thorough audit the project continued.

    The ReactOS people are taking the risk of copyright infringements very seriously.

    --
    You are not alone. This is not normal. None of this is normal.
  8. Wow! by pushing-robot · · Score: 5, Funny

    This has inspired me to create a ground-up 100% reimplementation of the AOL client, identical in looks and functionality. Wish me luck!

    --
    How can I believe you when you tell me what I don't want to hear?
    1. Re:Wow! by Anonymous Coward · · Score: 5, Funny

      The official aol client is like being poked in the eye by a sharp planet.

  9. BARF by Efialtis · · Score: 2, Funny

    I just had to wonder, WHY would anyone develop another OS that is "identical" to Windows?

    Windows is bad enough...why do it all over again?

    --
    --E--
    1. Re:BARF by Pantero+Blanco · · Score: 5, Informative

      I just had to wonder, WHY would anyone develop another OS that is "identical" to Windows?
      Windows is bad enough...why do it all over again?

      So you won't have to actually run Windows in order to run Windows programs such as Photoshop, AutoCAD, and most video games. WINE isn't good enough for everyone.
    2. Re:BARF by LiENUS · · Score: 3, Informative

      Unfortunately for the most part ReactOS is just wine that self boots. They borrow heavily from the wine codebase for their win32 api compatibility. Naturally the driver compatibility doesn't borrow from the wine codebase. The real point of ReactOS isn't software compatibility but environment compatibility. The goal is to be able to install all your windows apps on a machine that only supports windows (due to poor ACPI support in linux or poor video driver support or any of a number of incompatibilities). However windows application compatibility is rarely if ever better than wine with reactos.

    3. Re:BARF by jimicus · · Score: 2, Insightful

      WINE isn't good enough for everyone.

      So instead of an emulation layer which is almost adequate for most tasks, but needs careful testing with anything you're planning on using in production because any action you try performing may or may not work as designed, we'll have a full blown OS which is almost adequate for most tasks, but needs careful testing with anything you're planning on using in production because any action you try performing may or may not work as designed.

      Great. Thanks.

    4. Re:BARF by cyber-vandal · · Score: 2, Insightful

      Sounds like SOP for any IT system to me. Does Windows always work as designed or as expected?

  10. Non-Vista-compatible version? by rdmiller3 · · Score: 4, Insightful

    Having begun the struggle with adapting application installers to Vista, I think I'd be more interested in a version of ReactOS that ISN'T Vista compatible.

  11. You can imagine what the folks in Redmond are .... by 8127972 · · Score: 3, Funny

    Thinking about this:

    "In what may be a red flag for Microsoft's lawyers, ReactOS is described as "an environment identical to Windows, both visually and internally.""

    People at the Microsoft campus must be moving the furniture out of Ballmer's office as we speak.

    --
    This is my opinion. To make sure you don't steal it, it's covered by the DMCA.
  12. ironic by icepick72 · · Score: 5, Funny

    If ReactOS is almost a Windows clone, but a sub-par one, this begs the question of why do we need ReactOS anyway? Well, to find the answer I went straight to the source reactos.org, but apparently they haven't figured out the answer yet either.

    1. Re:ironic by Laur · · Score: 5, Insightful

      If ReactOS is almost a Windows clone, but a sub-par one, this begs the question of why do we need ReactOS anyway? Well, to find the answer I went straight to the source reactos.org, but apparently they haven't figured out the answer yet either.
      Honestly, can anyone tell me what advantages that ReactOS has over something like Linux+Wine? I've heard several reasons before, but they don't seem to stand up to an honest analysis, such as:

      Application Compatibility - Wine can never offer as much compatibility as ReactOS. Since ReactOS actually shares Wine's code base, it is highly unlikely that ReactOS will have significantly better compatibility than Wine.

      Speed - Wine, since it is an emulator, can never be as fast as ReactOS, a dedicated OS. This is usually advanced without any sort of benchmarks or other proof to back it up. First, Wine Is Not an Emulator, it is just an implementation of the win32 api. There is no technical reason why Wine couldn't be as fast as other "native" Linux APIs, such as QT or Gtk+. Furthermore, there have long been reports of Windows programs running faster on Wine than native Windows.

      Driver Compatibility - ReactOS can use native Windows drivers. Projects like NdisWrapper have shown that it is possible to use Windows drivers on Linux too, if enough people are interested. Of course, Linux already has drivers available for a great deal of hardware. There is also the huge issue of using binary drivers in an open source kernel. It still hasn't been settled whether or not this is ultimately a good or bad thing. However, it is generally accepted that open source drivers are much better than binary, and ReactOS would provide absolutely no motivation for hardware vendors to ever open their drivers, or even to target ReactOS as a platform.

      User Interface Familiarity - Windows users would feel right at home, with virtually no learning curve. This ignores the fact that anyone who has been through Win 3.1 -> Win 9x -> Win XP -> Vista will know that Window's interface is anything but consistent, things move around and change quite a bit between major releases. Also, if one desired you could rework something like KDE to be VERY similar to Windows, I believe that there are already distro's who try to do this (such as Linspire). There are still differences, but not really significantly more than between Win 98 & XP.

      Don't get me wrong, I think ReactOS is a pretty cool project, and it would be kind of neat to have an open source Windows clone, however as I said I can't really find much practical reason for it beyond the coolness factor. It seems like one would be better off just integrating Wine into Linux better. Please feel free to enlighten me. ;)

      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    2. Re:ironic by julesh · · Score: 5, Informative

      Application Compatibility - Wine can never offer as much compatibility as ReactOS. Since ReactOS actually shares Wine's code base, it is highly unlikely that ReactOS will have significantly better compatibility than Wine.

      Not true. ReactOS uses some of Wine's codebase, but many key areas (window management, memory management, thread support, etc.) are rewritten from scratch to be more compatible with Windows own implementations of these. I've seen Wine fail to run applications before because of some subtle difference in how Linux handles these tasks to Windows. ReactOS can eliminate these issues.

      Driver Compatibility - ReactOS can use native Windows drivers. Projects like NdisWrapper have shown that it is possible to use Windows drivers on Linux too, if enough people are interested.

      Yes. Unfortunately NdisWrapper doesn't really work very well (my limited experiments suggest only about half of the cards out there work with it), CaptiveFS is slow, and no other projects have produced useful results in this field. This is because running a Windows device driver without a Windows kernel is quite tricky. NDIS drivers are a simpler problem: NDIS was originally developed to be an open, cross-platform specification by 3Com. MS have embraced & extended it since then, but at its heart it is still much more portable than many other driver types used by Windows.

      There is also the huge issue of using binary drivers in an open source kernel. It still hasn't been settled whether or not this is ultimately a good or bad thing. However, it is generally accepted that open source drivers are much better than binary, and ReactOS would provide absolutely no motivation for hardware vendors to ever open their drivers, or even to target ReactOS as a platform.

      Frankly, there are a lot of us who have become fed up waiting for working open source drivers for our hardware and would rather just plug a black box in and be done with it.

      Also, if one desired you could rework something like KDE to be VERY similar to Windows, I believe that there are already distro's who try to do this (such as Linspire). There are still differences, but not really significantly more than between Win 98 & XP.

      Actually, there are very substantial differences that can be deeply annoying because they're about the way the basic system works. Details like which control panel applet you use to start or stop services (e.g.) aren't as annoying (to me) as the lack of feedback when a program is starting (KDE does have some feedback, but it doesn't show if the program wasn't started from the window manager, whereas Windows will show it however you start your program). This can't be fixed easily in Linux: it needs the kernel to provide feedback to the window manager to inform it when a graphical subsystem program is in the process of starting up. Linux doesn't have such a thing as a graphical subsystem program, and the window manager is not a special process that could easily receive such feedback from the kernel.

      I think a lot of people have missed the real point of ReactOS. Including the developers, by all appearances. Windows won't run under Xen paravirtualization. There's no reason ReactOS couldn't be ported to it, however.

    3. Re:ironic by Raideen · · Score: 2, Interesting

      The practical reason is that you've migrated away from Windows but need to run a Windows app that doesn't run under Wine (which does happen, despite the shared code base) or use a device that doesn't work under (enter alternate OS here). You fire up a virtual machine and load up ReactOS without sending a red cent to Redmond. You could accomplish this another way but that would amount to copyright infringement.

  13. FUD - ReactOs is legal by N3wsByt3 · · Score: 4, Informative

    "In what may be a red flag for Microsoft's lawyers, ReactOS is described as "an environment identical to Windows, both visually and internally."

    Oh, please... While I have no doubts MS will try to destroy ReactOs when it becomes too popular, the developers have made painstakingly difficult steps to ensure the proper reverse engineering is done ( http://en.wikipedia.org/wiki/Black_box_testing ). They can sue all they want, they can't win this. (They can however make it an expensive legal wrangling...but then again, since it's open source, it's difficult to imagine any single lawsuit will be able to end the project).

    --
    --- "To pee or not to pee, that is the question." ---
    1. Re:FUD - ReactOs is legal by julesh · · Score: 3, Insightful

      They can sue all they want, they can't win this.

      Except via patent claims, for which independent development is not an adequate defense.

    2. Re:FUD - ReactOs is legal by RLiegh · · Score: 2, Informative

      They don't have to get a ruling. They can shut it down for the duration of the trail and make it effectively illegal to host or distribute in any country where the US has any economic influence. That's the US, Austrailia, India and Europe, and parts of Asia

      Good luck hosting the project in timbuktu.

  14. Re:WTF??? by Programmer_In_Traini · · Score: 2, Insightful

    it seems a pretty obvious answer to me.

    put aside the fact that the softwares you mentionned are emulators, not OS,

    it would steal users from windows.

    imagine, having an OS the same as windows, friendly for computer illiterate ...but free, secure and open source...

    need i explain more ?

    --
    If you look like your passport photo, you're too ill to travel. - Will Kommen
  15. memory footprint by wonkavader · · Score: 3, Insightful

    OK, I don't need to know this, but I'm an old assembler-head: I remember how much SMALLER DRDOS was than MSDOS. Microsoft makes bloated things.

    I want to know how much memory ReactOS takes up versus WindowsXP. Has someone run it who can trivially answer? Did these guys make a smaller, lighter windows?

    1. Re:memory footprint by Anonymous Coward · · Score: 4, Informative

      The zipped vmware image is 19 megs. So I'd say its a bit lighter ..

    2. Re:memory footprint by Gothmolly · · Score: 2, Funny

      Absolutely. The addition of CALC.EXE and SOL.EXE are going to bloat it severely.

      --
      I want to delete my account but Slashdot doesn't allow it.
  16. slides unavailable by mrbobjoe · · Score: 3, Informative
  17. Re:Red flag? by despisethesun · · Score: 2, Informative

    No. As others have pointed out, they did a thorough audit to make sure ReactOS wasn't tainted. Much of the project's source is actually derived from WINE (though with many differences, since ReactOS is an OS and not a compatibility layer), and last I heard the two projects have a friendly relationship and source and documentation goes back and forth between them wherever it can be helpful.

    --
    This poo is cold.
  18. Re:WTF??? by exp(pi*sqrt(163)) · · Score: 2, Insightful

    we have VMware, we have 2007, we have everything necessary to run Windows programs without running Windows.
    Pls post instructions on how to run Windows without Windows using VMWare. thx.
    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  19. WINE by Aphex+Junkie · · Score: 5, Funny

    Wine
    Is
    Not
    Enough

    brilliant!

  20. Still too much in the kernel by Animats · · Score: 2, Interesting

    ReactOS still, apparently, has much of the graphics system in the kernel. Along with drivers. It emulates NT 4/2000/XP architecture, not NT 3.51, which actually had a cleaner kernel.

    But at least they didn't put in a 16-bit subsystem.

    1. Re:Still too much in the kernel by TheNetAvenger · · Score: 2, Insightful

      ReactOS still, apparently, has much of the graphics system in the kernel. Along with drivers. It emulates NT 4/2000/XP architecture, not NT 3.51, which actually had a cleaner kernel.

      So when they move to mimic Vista's kernel, this will all be moot then...

      But at least they didn't put in a 16-bit subsystem.

      Um, you act like an independent OS subsystem is a bad thing. The client/server kernel of NT is WHAT MAKES IT INTERESTING, and also is part of why the NT kernel gets the respect it does in spite of the Win32 shorcomings of Windows. PS You do realize that even Win32 is just 'a' subsystem and could be replaced at anytime?

  21. Facts badly wrong in parent, mod down by Anonymous Coward · · Score: 5, Informative

    The incident had nothing to do with Windows source and it was certainly not minor. It was due to certain parts having been implemented by the same programmer that had reverse-engineered them and was consequently "tainted" if the project was to adhere to its principle of black box testing only. That programmer was the very same Ionescu as here. The result of the unfortunate incident was that the programmer that found out about it (Hartmut IIRC) resigned from the project and the audit that is still going on was started. I read some of the discussion about it on the mailing list and apparently there was a great deal of concern about Ionescu's contributions since they came too quickly and were too good to be the result of just blax box testing (but not all is available for everyone so there could've been something else as well that resulted in the conflict between programmers - the whole project was to some extent in jeopardy, though). The only thing you're right about is that they take copyright infringement seriously but that has nothing to do with that incident.

  22. mimicking bill gates w/ win98 by Frogg · · Score: 3, Informative

    Ionescu attempted to demonstrate ReactOS but only succeeded in installing it after two BSoDs. This alone should make it clear that ReactOS is still not ready for prime time.

    hey, that sounds mighty familiar...

  23. Identical? by FunkyELF · · Score: 4, Interesting

    an environment identical to Windows, both visually and internally.
    I didn't get that from the screen shots. The text inside of cpu-z go beyond their container. The okay and cancel buttons here look as bad as 20 year old Unix, I'm thinking of CDE or Motif or whatever that is called. In fact, every single thing looks a bit off. Is that on purpose for legal reasons? ~Eric
    1. Re:Identical? by Anonymous Coward · · Score: 2, Informative

      The fonts Windows uses are copyrighted by Microsoft and you can only get them when you purchase either a Microsoft OS or Office for Mac.

      They're called the Microsoft TrueType Core Fonts and its one of the key points that non-technical Windows users have when they use Linux. (Their imported Word documents don't look right.) There are quasi-legal (legality depends on your country) packages for Linux distros to mitigate this, but no distro includes them by default.

      Obviously, this also applies to ReactOS.

      While I personally dislike SuSe, especially since Novell took them over, one thing they have gotten right is to include open fonts for serif, sans-serif, and monospacing where each letter has the same horizontal proportions as those of Times New Roman (serif), Arial (sans-serif), and Courier New (monospacing) so at least applications run in WINE don't run into issues as shown in the screenshots above, even if it still leaves the applications looking off. I wish Ubuntu (and ReactOS) would do the same.

  24. Re:Red flag? by Richard_at_work · · Score: 4, Informative

    Actually what happened was someone alledged that someone on the development team had decompiled actual MS Windows dll and binary files, and included the resulting code into the ReactOS codebase.

  25. Re:Red flag? by An+ominous+Cow+art · · Score: 5, Funny

    it was found that some developers had been exposed to the real Windows source code I hope they were able to return to society after thorough rehabilitation.
  26. Re:Red flag? by Anonymous Coward · · Score: 3, Funny

    Morbid curiosity. Kind of like when you drive past a car wreck.

  27. Re:WTF??? by chundo · · Score: 3, Insightful

    ...but free, secure and open source...

    That doesn't necessarily follow. Duplicating a broken API will retain some of the security problems designed into the original OS.

  28. Drivers by tepples · · Score: 2, Informative

    Windows is not nearly as unstable as the FUDDERS would like to make it seem. As I understand it, instability in Windows operating systems comes largely from defects in drivers, such as the VxDs of Windows 9x. The new Windows Driver Foundation framework, introduced with Windows Vista, attempts to contain these issues by providing a well-behaved abstract base class that other drivers can extend and by putting some drivers into user space. Under Linux, most of the drivers are Free and subject to the same scrutiny by the proverbial many eyes as the rest of the kernel.
  29. Preventing Bitrot by IllMnec · · Score: 2, Interesting

    This project can become very interesting for companies that rely on old equipment and software, which I think is a huge market.

    With Microsoft changing the driver model and the API of Windows with Vista, a lot of applications and devices will not be supported by the latest and greatest from Redmond. This means no security patches/bugfixes for old equipment and software.

    If ReactOS can emulate Win2k/XP, it could be used as a secure and supported replacement in those environments.

    --
    Illegal Mnemonic Character

    * Stay Simple *
  30. Old Hacker Rule by BillGatesLoveChild · · Score: 2, Insightful

    > Ionescu attempted to demonstrate ReactOS but only succeeded in installing it after two BSoDs.

    With alpha or beta software, before giving a demo, test what you are going to do in private.
    If it doesn't work, don't do it.

    Too bad. The world would be a better place with ReactOS. What we need is a fat ass investor with loads of cash and a grudge against Microsoft to donate to this thing.

    Linux has proven you can have a viable freeware OS. Now, while Vista makes everyones life miserable, there is an opening.

    1. Re:Old Hacker Rule by jmorris42 · · Score: 2, Insightful

      > The world would be a better place with ReactOS. What we need is a fat ass investor with loads of cash
      > and a grudge against Microsoft to donate to this thing.

      Nobody with that sort of cash is likely to be stupid enough to piss it away without a little thought. Just what problem is ReactOS trying to solve?

      Is it running Windows executables on a Free platform? Then just toss the money upstream to the Wine developers, they are making most of the progress anyway. Wine is already running major 3D games and the closed forks adding in closed/patented bits are even farther along.

      A Free platform able to run Windows device drivers? Huh? That just doesn't make sense. A platform that depends on closed drivers intended for a different (even if related) platform has no future. Especially as closed platforms are going to DRM Hell. ReactOS isn't ever going to be able to run DRM device drivers so wave goodbye to video, sound and probably mass storage.

      A Windows clone that doesn't cost anything? Ask a hundred Dell owners how much Windows costs, bet 99 of em say it was "free".

      And remember, Linux went from a tool to learn about interrupt driven programming to a viable OS kernel in a year or so. Drop the GNU tools and X on and bang, an operating system was born. ReactOS has been struggling for years and doesn't have a working kernel yet and Wine isn't nearly as feature complete as GNU and X were to plunk atop it.

      Remember also the chasing taillights problem. DosEMU did eventually have a 1.0 release. It even made it into a RedHat distro.... but was dropped because nobody gave a damn anymore. FreeDOS had it's 1.0 release even more recently.... and except for a few people nursing old industrial automation and some embedded folk, nobody cared anymore. 8086 hardware and DOS are far simpler designs than Win32 and aren't in constant motion. ReactOS never caught up to NT before XP shipped and are again trying to leapfrog to Vista without ever getting XP emulation stable. Anyone care to wager whether they will reimplement Vista's massive API before the next version lumbers forth from the bowels of Microsoft and moves the goalposts yet again?

      --
      Democrat delenda est
  31. software patents by N3wsByt3 · · Score: 2, Insightful

    "Except via patent claims, for which independent development is not an adequate defense."

    Well, in Europe we still don't have (enforcable) softwarepatents. Though it being an Open Source project, I'm not sure under what jurisdiction it falls.

    But you make a good point: more proof that softwarepatents suck.

    --
    --- "To pee or not to pee, that is the question." ---
  32. Windows clone? Why not go for OS X? by uop · · Score: 2, Insightful

    I would be much more interested in an OS X clone running on my PC, than in a Windows clone that I don't need.
    Why clone a bad interface when you can clone a good one that many people would like to use?

  33. Re:WTF??? by PopeRatzo · · Score: 5, Insightful

    What we DON'T have is a viable commercial product to compete with the PC/Mac control of the market for those of us who need to run professional programs. I mean no disrespect to Linux, and I plan to try out the UbuntuStudio as soon as it's out, but if you need to do video or audio/music production, for example, you're stuck with two platforms that continually underwhelm and have very little incentive to give users what they really want.

    Both Microsoft and Apple have held the marketplace hostage for so long, that they can get away with ignoring the demands of their users, which is the symptom of a market out of whack. I want to run OSX on a box I build, but I can't. I want to run Vista without DRM, but I can't. I can keep going like this for a long time. It's the lack of serious competition that has kept the entire desktop market moribund for decades now.

    We need another player, simple as that. We need a well-financed company to get into the desktop operating system game and stay there for a solid decade. Then we'll start seeing products and features that we REALLY want, at reasonable prices. Until then, it's going to be this silly charade of Bill and Steve, who we're supposed to believe are competitors, when they're really just enabling each other to abuse their customers, playing to their business partners in the entertainment-industrial complex. They may have done something at one time to move the status quo forward, but in the last decade they've just been a couple of jackoffs, doing zip for you and me.

    --
    You are welcome on my lawn.
  34. mitigating lawyers by CAIMLAS · · Score: 2, Insightful

    Aside from shooting the lawyers, the best way to mitigate the lawyers, I think, would be to get rid of the "MS GUI". That is, abstract it a little bit and make it an API-compatible theme engine, with the default looking different.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  35. Re:WTF??? by Stewie241 · · Score: 2, Informative

    But then how is that:
    we have VMware, we have 2007, we have everything necessary to run Windows programs without running Windows.

    Pls post instructions on how to run Windows without Windows using VMWare. thx.


    Not saying that is a bad solution, but that still doesn't allow you to run Windows programs without windows.

    Windows with snapshots is still Windows.

  36. Because ReactOS does it differently by EmbeddedJanitor · · Score: 4, Funny
    MS slowdown is caused by thousands of poor lines of code which require countless programmers. ReactOS achieves the same slowdown by just using a few lines of code in slow_down.c:

    /* Waste time to look like real Windows */

    int i;

    for(i = 0; i 1000; i++) {/*spin */}

    --
    Engineering is the art of compromise.
  37. Wouldn't work by Tony · · Score: 2, Funny

    /* Waste time to look like real Windows */

    int i;

    for(i = 0; i 1000; i++) {/*spin */}



    Most decent compilers would optimize that out. The ReactOS team would have to be *much* more clever to achieve the typical MS-Windows slowdown. If they programmed the whole thing in C#, it might just work.
    --
    Microsoft is to software what Budweiser is to beer.