Slashdot Mirror


ReactOS Runs On The XBox

KJK::Hyperion writes "ReactOS (the open-source Windows clone) has been ported and successfully runs on the Microsoft XBox (screenshot), thanks to the interest and knowledge base of the XBox Linux project and the work of Gé van Geldorp (HAL and boot loader) and Hervé Poussineau (FATX driver)." (Read on for more.)

KJK::Hyperion continues "This port definitely establishes two facts: the XBox is nothing but a broken PC, and the kernel + HAL design that ReactOS inherited from Windows is sound - all of the changes to the core system necessary for the XBox port (namely, the blacklisting of a buggy PCI device and handling the fixed partition table on the built-in hard disk) were limited to the HAL. This is a first, important step towards better portability, as it has already underlined some shortcomings in our build system.

What the port is lacking is hardware support: especially, ReactOS has no USB support at the moment, so it basically just sits there being pretty, because mouse and keyboard won't work. The network and video cards should be mostly identical to their "real" counterparts, so the Windows drivers for them should work (except the video card, a modified GeForce - it's been established we need some HAL trickery to make the Windows driver load). We wouldn't mind some help :-)

To run ReactOS on the XBox you need our custom version of the Cromwell boot loader (not released yet) and the XBox HAL for for ReactOS."

7 of 289 comments (clear)

  1. ReactOS? by IO+ERROR · · Score: 3, Interesting
    ReactOS is intended to be a clean, open source reimplementation of Microsoft Windows NT 4.0.

    I'd never heard of ReactOS before this posting, and so I checked it out. I'm impressed by what they've done so far, but not the seven years it took them to do it. It's still VERY early pre-alpha software. Maybe now that all the basic pieces are in place it will pick up speed, but I suspect it will have the same trouble WINE runs into: it's chasing a moving target, and it's way behind. WINE, at least, decided to implement newer APIs found in Windows 2000 and XP. ReactOS has not. So even when they hit a 1.0 or stable release, they're going to be so far behind that not that much Windows software will run on it.

    --
    How am I supposed to fit a pithy, relevant quote into 120 characters?
    1. Re:ReactOS? by runderwo · · Score: 4, Interesting

      Yes, they will face many of the same challenges the WINE project does, which is why WINE and ReactOS liberally share patches. Why does everyone think they are just some peripheral group reinventing the wheel for no particular reason? The ReactOS project enjoys a symbiotic reliationship with WINE in which both projects benefit from each other's advances.

    2. Re:ReactOS? by evilviper · · Score: 4, Interesting
      it's chasing a moving target, and it's way behind.

      I must disagree there. NT4, despite lacking support for a few things, is still a modern OS, and highly usable. With the hundreds and hundreds of programs I use, the only one that I can recall not working on NT4 is MPC, and that's not a big problem.

      Namely, NT4 is lacking in USB support (oddly enough, I find NT4's lack of USB support better than Windows 98's USB support), only has DirectX6, and doesn't support FAT32 without a 3rd-party add-on. Those limitations can all be fixed easily, making an NT4 clone every bit as useful as, say, XP.

      In addition, they are in a very different place than WINE. If programming for ReactOS is vagely similar to recent Windows, and it has just a few thousand users, it would become a supported platform. There are probably less Windows 95 users out there than that, yet just about all modern Windows programs still run on 95. A small bit of extra effort to reach a few thousand more people is a great trade-off for most.

      Personally, I'd love to see it improve, as Windows is a constant headache for me. Having an Open Source version would make it far easier to solve problems (like why those dammed ATI drivers won't work).
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  2. Reaction? by methangel · · Score: 3, Interesting

    Yeah, I think ReactOS will make Microsoft "react" since it's a Windows clone. You are the weakest link, goodbye.

    I love it how the geeks will uproar about MS taking measures to prevent their console from doing things that it shouldn't ... Of course if Apple circumvents (Real) ... it's their RIGHT!

  3. How about porting Windows? by enosys · · Score: 3, Interesting

    So could you theoretically build a new HAL for XP and get it to work on an XBox? Or for that matter any weird x86 architecture? I suppose it may be hard to do this without using the source, but it's not impossible. It'd be an interesting project.

  4. Re:Hmm Running a.. by ottothecow · · Score: 4, Interesting
    See the problem with this news article is that I dont know what it it is really for.

    I mean I know it appears to me that its about ReactOS running on the xbox...but then I realized that the existance of ReactOS is the real news. Something running on the xbox is amazing but...where is the slashdot article for reactos?

    --
    Bottles.
  5. What a horrible idea by theantix · · Score: 3, Interesting

    Why would people spend their free time on a project to re-implement Windows? Their answer from their FAQ:

    "Reliability, subsystems, filesystem drivers, services and the registry
    are all good concepts which are implemented well in the NT kernel.
    Not everything is perfect, but without access to the source code, we can't fix it, so we're choose to clone it."

    WTF? I can understand WINE, if you have a legacy binary application that is windows-only. But poorly re-implementing windows? They will probably *never* get full compatibility with windows, so it will always be an inferior solution -- some "fix". I'm tempted to think these ReactOS people are clinically insane.

    If a ReactOS dev is listening here, explain this to me: why don't you just create drop-in replacement .dlls for mswindows in cases where you think it's broken? This is something you'd have to write in the first place if you're going to reimplement the whole goddamn system, and seems a lot more productive. Alternatively, why not work productively to improve Linux or a BSD variant so it has the supposed "advantages" that you find in mswindows?

    --
    501 Not Implemented