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.

280 comments

  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 Anonymous Coward · · Score: 0, Redundant

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

      The joke needs to die. It stopped being funny after Win9x. Win2k+ is nearly as stable as any Linux system I've ever used (if not moreso).

    2. 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.

    3. Re:On the contrary... by Anonymous Coward · · Score: 0

      You've apparently never installed Windows on a Compaq from it's restore set...

    4. 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.

    5. Re:On the contrary... by rucs_hack · · Score: 1

      Depends what you're actually doing.

      Hundreds of installs? You mean in an IT environment with mainly smiler hardware doing a standard install? If you don't then you must be the worlds richest home user to own that many machines.

      People who have to re-install often because windows is fundamentally unstable when its being asked to do a lot *do* tend to have problems. Gamers do find they have to re-install more often I find, but then they are pounding their machines a lot.

      My IT experience was heavily concerned with fixing borked windows and I saw a fair few crashes during installs.

      To be fair I have on linux too, it's a common problem, installing an OS is tricky. Automated installs just mean that you have less to do while you wait to see if it will work.

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

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

    7. 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.

    8. Re:On the contrary... by xarak · · Score: 1


      Wooosh!

      Thar blows another joke cap'n!

      --
      Atheism is a non-prophet organisation
    9. 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.

    10. 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.
    11. Re:On the contrary... by alexhs · · Score: 1

      And now Vista is upon us, and it's not detecting a lot of real obscure hardware, like say, MY CDROM DRIVE. <sarcasm> It's probably because it isn't HDCP-dis^Wenabled and as such isn't on the ..AA white list </sarcasm>
      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    12. Re:On the contrary... by kage.j · · Score: 1

      I've installed XP a number of times successfully, but I've had problems with 95 and 98 more than not

      --
      he demonstrated by A plus B minus C divided by Z that the sheep must be red, and die of the rot
    13. Re:On the contrary... by Anonymous Coward · · Score: 0

      Windows2000 is certainly not horrible, but I still wouldn't say it's as stable as a typical Unix. It's good enough for the majority of people. But I don't think that's the main problem. The OS itself is quite solid. If you play by the rules then there's very little chance that an application will take ths sytem down. The problem is that it's far too easy for misbehaving applications to do damage.

      Take video codecs for example. If one is bad it causes explorer.exe to crash. I have a folder with some video files. I can't even browse the directory and explorer crashes. It's not Windows' fault per se, but why should a video codec cause this issue? Hunting this problem down took hours and in the end I had to disable a handful of codecs that were pulled down automatically by Windows in the first place. That's borked whichever way you look at it.

      Then there's this freeze issue. If a network share goes unavailable, all the desktops suddenly freeze for 10 to 15 seconds. Try clicking Start|Run and opening a bogus share such as \\idontexist\foo. This happens randomly: On XP and 2K the whole explorer freezes until it times out. Sometimes it does it, sometimes not. I don't see what lets it background the check or not. In any case, it's annoying as hell.

      The Microsoft pre-loaded apps on the Dells is another problem. I have video of me clicking "Cancel" 20 times to clear the dialogs that popped up when I tried to launch a PPT file when Powerpoint wasn't loaded. It asked for the install disk. I click Cancel. It thinks for a second. Then asks for the install disk. Lather. Rinse. Repeat. That's annoying as hell.

    14. Re:On the contrary... by renegadesx · · Score: 1

      I haven't had a successful install yet, VMWare images on the other hand have been brilliant, mind you I haven't tried the install for 6 months, for some reason my gf has had problems wanting to part with Linspire

      --
      Make SELinux enforcing again!
    15. Re:On the contrary... by Captain+Splendid · · Score: 1, Flamebait

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

      Of course not, but you're still one lucky bastard.

      Sure, win2k was a huge step up (well, after SP2, anyway). But don't kid yourself into thinking it crashed less than previous versions, it's just that it didn't tend to fubar your data up when it did. You can talk all you want about how much more reliable its become (true), but that still doesn't change the fact that I've lost entire days of my life troubleshooting some random, obscure or simply illogical "hiccup".

      And don't even get me started on XP, it was fucking useless when it first came out. Yeah, yeah, I know, but it was a complete WTF for me: how and why would you want to release a shittified version of 2000?

      --
      Linux, you magnificent bastard, I read the fucking manual!
    16. Re:On the contrary... by JensenDied · · Score: 1

      Well I have systems that would not install windows no matter how many times I tried. The ratio there was about 0:5 before I decided to just make a disc image and write it in there from another machine. The ofcouse it needed to be re-activated and the guy on the phone didn't seem to understand that the installer doesn't work (Pre-SP2 Disc btw) on >~120GB Hard Drives. Phoned back and the activation code worked then from the automated service.

      --

      09:F9:11:02 - 9D:74:E3:5B - D8:41:56:C5 - 63:56:88:C0

    17. Re:On the contrary... by Pseudonym · · Score: 1

      I've very recently encountered my first failure when building a new computer.

      Did you forget to activate it? See http://reactosgenuineadvantage.com/ for details.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    18. Re:On the contrary... by Anonymous Coward · · Score: 0

      Because we all know that stability is measured by YOUR experience only.

      WE all worship you god of windows IT. Please give us more of your wisdom!

      Moron.

    19. 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
    20. Re:On the contrary... by x2A · · Score: 1

      "Hundreds of installs? You mean in an IT environment with mainly smiler hardware doing a standard install? If you don't then you must be the worlds richest home user to own that many machines"

      Or somebody who gets contracted out to many different businesses who don't have in-house IT staff, and also installs on request for friends/family, in which case has a lot of experience installing the OS on many different hardware combinations? Come on, that's a fairly common scenario.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    21. Re:On the contrary... by orasio · · Score: 1


      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.


      You don't seem to be able to tell the difference between the law and the words of ms.
      And you don't own the software. They own the software. You own a license to use it, maybe. If they let you.
      But about making copies, it's not illegal.

    22. Re:On the contrary... by Anonymous Coward · · Score: 0

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

      FUDDERS? Take it as ribbing; look at the BSD and Linux crowd, after a decade plus there is still some ribbing. Windows isn't the only OS that gets guff. MS / Windows BOSD, CTRL+ALT+DEL, etc have been around and used for over 20 years. They can still get a little more ribbing (imho). I paid for 20 years worth of upgrades of OS and applications. To be blunt; I have gone through 20 years of pain until MS made 2000 and XP right.

      Just my .02 cents worth.

    23. 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?

    24. Re:On the contrary... by laparel · · Score: 1

      I do, about 4 times a year (Compaq computers at home) for 6 years now.
      And i have yet to see any errors whatsover.

      I agree with rwven:
      "Windows is not nearly as unstable as the FUDDERS would like to make it seem."

      It's already sickening to hear most people in slashdot always bashing all of Microsoft's producs; sorry for generalizing, but most slashdotters do! And these people usually turn a blind eye or justify linux's shortcommings.

    25. Re:On the contrary... by Anonymous Coward · · Score: 0

      Hi. Aren't you supposed to be testing "windows Vienna" or something? Or porting VB to novell/linux? Why are you reading slashdot. Go back to work!

      But seriously, who needs another "Window's poor cousin"?
      We have ReactOS, Wine, Codewaverz, Novell/Mono-Linux which are almost as good as windows, but not quite there yet. In fact Novell linux makes windows look stable.

      Today with virtualization all these efforts seem wasted. Just virtualize a pirated CD with kqemu (not the novell virtualizer because it will call home and tell them about it), and you'll be just fine. ;)

    26. Re:On the contrary... by Khyber · · Score: 1

      Personally, if it's a Compaq, I blame HP (I have to work on both every day. Fucking shoddy ass hardware that breaks the second you tap it the wrong way...)

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    27. 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.

    28. Re:On the contrary... by GuyverDH · · Score: 1

      If you run commodity hardware with commodity drivers, you're stuck with commodity blandness and performance.

      If you decide to hand-craft your own from premium parts, that's where you start to run into problems.

      Windows has been designed for the masses, the commoners, the lowest common denominator.

      Try moving above that line and you'll see all kinds of funky not-so-fun stuff happen.

      --
      Who is general failure, and why is he reading my hard drive?
    29. Re:On the contrary... by Tim+C · · Score: 1

      software I own that's labeled 'Do not make copies of this disc'

      You were ripped off - mine says "Do not make illegal copies of this disc" (emphasis added).

    30. Re:On the contrary... by laparel · · Score: 1

      Oh, I've built my fair share of machines of my own. It may not have been "premium parts", usually just about a generation behind the beelding edge hardware, but they're not what you call 'commodity'.

      But I could have totally misunderstood your definition of premium parts and commodity... pls do define which stuffs are premium and which aren'tt

      Anyways, if we're talking about the lowest common denominator... which os has the most numerous selection of supported devices anyways?
      Im no OS guru, but from my limited experience, I think windows supports the most hardware out there.
      Based on my tinkering with a couple or more linux distros, I've had more driver issues in linux than in windows. (Unfair comparisson perhaps, but nevertheless true)

      Heh, and now I get the nick "win-hugger"

    31. Re:On the contrary... by GuyverDH · · Score: 1

      Well by premium, I mean the fastest, most powerfull currently available.

      Often times, with these components, you'll run into software timing glitches, where the developers assumed that nothing could respond faster than x, and built in waits, often missing interrupts, or corrupting data, causing BSODS.

      Other times, you may have multiple audio processors (ie USB headphones for voice commo in games, and regular sound card for game audio) and run into issues where the sound is directed to the wrong processor.

      These are but a few of the types of issues that can crop up.

      To answer to the driver section, Windows may have the lead in driver selection, but that's only because the vendors have seen that the install base of Windows is (was) much higher than Linux and BSD derived installs. They (the hardware vendors) wrote the drivers for the OS that was most likely to be used with the hardware.

      The folks that spend all of their time developing Linux/BSD based OSes also had to spend time writing their own drivers, often without any help from the manufacturer.

      So while Windows may have *more* drivers that the others, I'll give props to the others as they actually wrote their own. Aside from the hardware the MS had OEM'd, and which the drivers were written by the OEM to MS's specs, MS has yet, to my knowledge, to actually write their own hardware drivers for any modern components.

      --
      Who is general failure, and why is he reading my hard drive?
  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 julesh · · Score: 1

      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.

      One key advantage to ReactOS in this scenario is that with a little hacking it could be made to run under Xen's paravirtualization system, which is apparently rather more efficient than full virtualization (as is currently required in order to run Windows).

    6. 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
    7. 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.

    8. Re:Doubt microsoft would care by Echnin · · Score: 1

      This is not an entirely direct reply to your post, but I was wondering about something. What if you ran ReactOS inside a semi-transparent virtual machine, like Classic on PowerPC Macs? That worked pretty well; sure, it had some compatibility problems, but for the most part it was pretty good. Would this work for ReactOS within Linux as well?

      --
      Lalala
    9. Re:Doubt microsoft would care by JensenDied · · Score: 1

      >Feeding the troll That quote was referencing using WindowsXP in a VM. Try trolling accurately next time, you might get more bites.

      --

      09:F9:11:02 - 9D:74:E3:5B - D8:41:56:C5 - 63:56:88:C0

    10. Re:Doubt microsoft would care by aitikin · · Score: 1

      Classic really didn't work all that well. (IMHO) It was a horrible memory hog and, frankly, rather annoying. If you get an Macintel and Parallels, you'll find they have a nice little seemingly transparent version of the virtual machine working too. It's pretty cool, but it doesn't work great by any means. This being said, I'm sure you could do that with ReactOS, so there's a semi-answer to your semi-reply to the grandparent's post.

      --
      "Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup." ~ohcrapitssteve
    11. Re:Doubt microsoft would care by cheater512 · · Score: 1

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

      Uh sorry but I must be missing something here. Doesnt WINE aim to be a complete implementation too?

    12. Re:Doubt microsoft would care by BESTouff · · Score: 1
      Wine offers a much more compelling method of migrating from Windows.

      I'm not *that* desperate so as to go straight into alcoholism !

    13. Re:Doubt microsoft would care by 99BottlesOfBeerInMyF · · Score: 1

      Uh sorry but I must be missing something here. Doesnt WINE aim to be a complete implementation too?

      WINE aims to re-implement the "userland" APIs and the ones commonly used by regular software and provide a translation layer to another OS. As such, it will only achieve the complete implementation when it can do everything Windows can including boot, at which point it would be a complete OS like ReactOS. I don't think any of the WINE team will ever want to take it that far. Their goal seems to be "good enough" to run most normal software.

    14. Re:Doubt microsoft would care by oblivionboy · · Score: 1

      Has it ever occured to anyone that maybe someone doesn't have to want to bloat their computer with linux first just to run WINE? IIRC React OS can run in 32 megs of ram (great for older machines), and its got that just install and run attitude that Linux is so lacking. To run WINE you'd have to get Linux installed (which distro?), plus X, plus WINE, plus who knows what else, and then you'd STILL be running Linux, which -- while it is a great operating system and all that -- is not what alot of people want to do. Linux + WINE is probably fine for the Linux crowd, but there is another world beyond the parent's basement :) .o.

    15. Re:Doubt microsoft would care by Anonymous Coward · · Score: 0

      Maybe, maybe not. There are a ton of old machines out there running business-critical applications. Many are running operating systems that are no longer actively supported by Microsoft, and they are incapable of running Vista, which is the only OS that MS is selling. In those cases, there is zero difference between the amount of support you get from running the old MS software versus ReactOS, except that if a major vulnerability comes around, ReactOS is more likely to get patched. It's possible we'll see a community of consultants spring up around ReactOS that provides this type of extended-life support for old applications.

      And if ReactOS becomes the defacto standard for users falling off the MS treadmill, we may see MS improve their support for older systems (at least, until they figure out some other way to stop ReactOS). So it's win-win for end-users, even if not for ReactOS.

  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. Red flag? by MintyGreenMedia · · Score: 0, Troll

    Without RTFA (or any prior knowledge of ReactOS, honestly), my first thought came to the leaked Windows source code. Of course, no one would be that stupid...right?

    1. 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.
    2. Re:Red flag? by Anonymous Coward · · Score: 0

      the ReactOS project has been going for a long time before that leak. I'm pretty sure they wouldn't dare look at that code, knowing what a legal minefield that is.

      (For that matter, why would ANYONE other than malware writers or those tasked with working around bugs in Windows want to look at Windows source code?)

    3. Re:Red flag? by Andareed · · Score: 1

      They actually did a "code audit" a while back. You can get details here: http://www.reactos.org/wiki/index.php/Audit.

    4. 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.
    5. 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.

    6. 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.
    7. Re:Red flag? by Anonymous Coward · · Score: 3, Funny

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

    8. Re:Red flag? by Anonymous Coward · · Score: 0

      I looked at the mailing list when that story hit Slashdot, and it wasn't just alleged. Someone was clever enough to admit that they were disassembling Windows and using it for reference while coding Reactos. Said individual even defended the practice.

      Go figure.

    9. Re:Red flag? by SirTalon42 · · Score: 1

      Actually that is an acceptable practice. Long as the person disassembles and the writes documentation on what they learned. And a person that was never exposed to the disassembled code creates a different implementation. That method would be clean everywhere, and in some places person A and B being the same would be acceptable as well.

  7. 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 JoeCere65 · · Score: 1

      whats with all the criticism, this is in Alpha, its a 0.3 version "Please bear in mind that ReactOS 0.3.1 is still in alpha stage, meaning it is not feature complete and is not recommended for everyday use."

    2. Re:With no disrespect to the ReactOS developers... by Numbstruck · · Score: 1

      I'd think they're more concerned with functionality. The cosmetics will come later.

    3. 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!
    4. 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...

    5. Re:With no disrespect to the ReactOS developers... by nuzak · · Score: 1

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

      I use the classic skin on XP because Luna looks like something an intern slapped together in a week. I don't at home, because I have XP media center, and the skin on that actually looks halfway decent.

      Aero gives us the strangest window metaphor yet: the frame is translucent, and the window pane itself is opaque. Joy.

      (And no, I'm not really into OSX's unsubtle gaudy lickable widgets either)

      --
      Done with slashdot, done with nerds, getting a life.
    6. Re:With no disrespect to the ReactOS developers... by Raenex · · Score: 1

      I know plenty of people who use the "Windows Classic" skin on XP, because that's what they're used to. I use the Classic look on XP because the default XP colors are bright and distracting. I stare at the screen for hours a day. I don't want to stare at blaring colors that serve no other purpse than to say "look how cute and shiny I am!". Besides being hard on the eyes, the XP color scheme looks like it's designed for children (which it probably is, aimed at the masses in a patronizing way).

      The Vista color scheme looks a lot more mature and slick, though I find the transparency gimmicky.
  8. You asked for compatibility... by jmac1492 · · Score: 1, Funny

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

    Fixed.

    --
    Jenny's got a new number! 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  9. Re:With no disrespect to the PP by HomelessInLaJolla · · Score: 1

    How about another link?

    --
    the NPG electrode was replaced with carbon blac
  10. 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.

    2. Re:Wow! by danheretic · · Score: 1

      That's basically been done.

    3. Re:Wow! by rbochan · · Score: 1

      Please do so, but write it for Linux!

      --
      ...Rob
      The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
    4. Re:Wow! by wellingtonsteve · · Score: 1

      Hmm.. I'm interested. Where does one find one of these sharp planets? I checked out my local shop (Solar-Systems-R-Us) and could only find round ones...

  11. Is it more stable than XP/Win2003? by davidwr · · Score: 0, Troll

    1) Is it more stable than XP or Win2003? That should be easy :)
    2) Is it more stable WITH MY APPLICATIONS than the OS I'm using now? This is the really important question.
    3) What about security vulnerabilities?
    4) What about Microsoft application software security vulnerabilities?
    5) What about replacements for MS application software that won't download on "non-genuine Microsoft" operating systems?

    Remember folks, if your Microsoft Applications like IE6 have security vulnerabilities, and you run them on this platform, you may or may not be able to install the Microsoft patches.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:Is it more stable than XP/Win2003? by qazxswedc · · Score: 1

      Windows is not without its security vulnerabilities. I would never argue otherwise. However, XP is and has been blissfully stable for me for...5 years plus. My system runs 24x7...gets a lot of use for multiplayer games, teamspeak, photo/video editing, internet browsing, some office apps, occasional light development work...etc. I tend to reboot once every month or two - when I am forced to in order to add the incessant security updates caused by lazy ms programmers and lifeless twits who spank every time they find a new vulnerability. May not be a popular opinion here on /. but I've got no complaints about XP. It may be more about the fact that I don't run IE, outlook, most antivirus software, extra firewalls, etc. Been just fine whether proc has been intel or amd, no extra cooling (just the CPU fan).

    2. Re:Is it more stable than XP/Win2003? by Fordiman · · Score: 1

      Binary compatibility or not, why would you want to use MS's security patches on a non-MS product? You're far more likely to break it (I get the feeling that the ReactOS team actually bound-checks their code, unlike some Redmond fellows I can think of).

      Or, how about this: It's not done yet. Keep your peanuts to yourself.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    3. Re:Is it more stable than XP/Win2003? by nanoflower · · Score: 1

      The MSFT people are smart enough that they may catch stuff that other people don't. Plus they have a huge install so they will hear of problems long before anyone running Wine or ReactOS would. That said, I do think it's a good thing if it works as well as they said (eventually) and the source is out there for perusal. Some people will end up using it to try and find new holes to attack, but a lot of people will also find problems. So after a few years it could be much more secure than XP. Plus we all know that Microsoft will drop support for XP as soon as they can get people moved to Vista. It's going to take a while due to the hardware requirements of Vista but it will happen. With ReactOS people can still keeping going with XP compatability as long as they want.

    4. Re:Is it more stable than XP/Win2003? by Fordiman · · Score: 1

      Actually, I was talking about breaking the system by introducing foreign code. ReactOS tries for binary compatibility. That doesn't mean you can go dropping system files between them (like updates from MSFT). You're very likely to break something.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
  12. 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 Fordiman · · Score: 1

      Just think: like Linux you could run 'Windows' on your iPod ^_^

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    3. 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.

    4. 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.

    5. Re:BARF by Anonymous Coward · · Score: 0

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

      Because Windows is closed. And phones home.

      It's all about trust, not bsods or crashes. Any software that claims to be reliable and trustworthy must be available for checking to a wide audience with no strings or NDAs attached, which shows why the MS Shared Source initiative adds zero to Windows trustworthiness. The Interbase precedent should ring a bell.

      Windows backdoors were/are actively used by governments to spy on people/companies. While it can be a good thing when helping to catch criminals, I'm not sure any tech savy executive would put their sensitive data in a system that allows unrestricted access to some well chosen external entities.

      So the answer is: someone is developing an OS identical to windows because there is a huge need for it.

    6. Re:BARF by Anonymous Coward · · Score: 0

      Then ReactOS won't be good enough either. It uses WINE to provide the userspace Windows API support.

    7. 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?

    8. Re:BARF by Anonymous Coward · · Score: 0

      shut your fucking face unckle fucker

    9. Re:BARF by o2sd · · Score: 1

      Does Windows always work as designed or as expected?

      Windows was designed?????

      --
      - Nothing to see hear.
  13. 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.

    1. Re:Non-Vista-compatible version? by mgblst · · Score: 1

      I remember going from Windows 98 to Windows NT and 2000, suddenly you had to start preserving an extra register (I think it was bx/ebx), that you hadn't had to do before. This caused a lot of problems, Microsoft for some reason decided to change the pay all programs worked. I can only imagine what sort of hell one would have going to Vista (XP wasn't so bad, since it was just an ugly version of 2000).

  14. 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.
  15. Re:Solution to OS Disparity by Anonymous Coward · · Score: 1, Funny

    Or combine self-deprecation and blandness to create GAROFFOLO!

  16. 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 Anonymous Coward · · Score: 0

      Uh, as others have said...
      to run windows applications without having to have windows on your machine so you support people coming off of windows with their *must have* applications but they don't have to support MS as they move away from their XP customers. :)

    2. 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
    3. Re:ironic by ZeroConcept · · Score: 1

      So I can buy support from a 3rdParty and get off the Microsoft forced upgrade cycle for the thousands of Windows XP installs that have absolutely no business value in upgrading to Vista.

    4. 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.

    5. Re:ironic by Anonymous Coward · · Score: 0

      I think ReactOS is aimed at those users (about 90% of the desktop population) who do not want to run
      Linux with WINE.

    6. Re:ironic by mincognito · · Score: 1
      From the presenation:

      Motivation
      • [MS Windows] plagued by bad design decisions made early-on in 16-bit Windows 9x history but kept for compatibility.
      • Plagued by a myriad of hacks to support badly written applications and drivers from 3rdparty developers.
      • Plagued by bad design decisions still being made to maintain corporate agenda (DRM, Driver Signing, etc).
      • Plagued by bugs in bundled software (Internet Explorer/Windows Media Player/Outlook Express) and bad security decisions (users run as Administrators, etc) which undermined architectural security and reliabilty.
      • Closed source, costly, poorly documented in regards to system architecture and undocumented functionality (compared to competing FOSS operating systems).
      • Most extensibility features kept undocumented and not open to 3rd party modification.
      Goals
      • ReactOS aims to offer all of the features and performance of NT without all the hacks, restrictive design decisions and license restrictions.
      • It aims to offer no-cost Windows compatibility at a level no other solution can.
      • It aims to document the undocumented, and to provide binary-compatible components which would be used to provide extensibility.
      • Great teaching platform for academia. UNIX/Linux are good to learn from, but NT does some interesting and different things that deserve the same attention.
      • Will not include applications such as IE, OE or WMP. Users will be encouraged to install FireFox, ThunderBird, OpenOffice, Mplayer, etc.
    7. Re:ironic by jma05 · · Score: 1

      > Speed - Wine, since it is an emulator, can never be as fast as ReactOS, a dedicated OS

      Repeat after me.

      WINE stands for Wine Is NOT an Emulator.
      WINE stands for Wine Is NOT an Emulator.
      WINE stands for Wine Is NOT an Emulator.

      Did I mention that it is not an emulator :-) ? It is a compatibility layer.

      That said, I agree with the rest of the post. I tried the VMWare version a few minutes ago. It booted in about 10 seconds on my old computer (Athlon 2000+). I reduced the VM memory to 64 MB and it booted as quickly (although it crashed with 32MB). This makes it great for those very old computers.

      Driver compatibility sounds very promising if it actually works. The main problem is however that it still seems to crash a lot for now. A lot more than Win98 ever did for me.

    8. Re:ironic by jma05 · · Score: 1

      I have no idea about what you are saying. The Wine web site still says it is NOT an emulator.
      http://www.winehq.com/site/myths
      Perhaps you can point to where they did say it was an emulator.

      But you right about the Irony. I ranted needlessly when I saw the Wine myths and did not read carefully enough when the parent was in fact debunking those very myths. For that I apologize.

    9. Re:ironic by Laur · · Score: 1

      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.
      Do you have any proof that this is the case, i.e. is there currently an example of ReactOS running an application that Wine cannot? According to the slides, many of these functions are currently implemented very differently in ReactOS than in Windows as well, so the programs still won't run. Sure, ReactOS can re-write these parts, but I'm sure there are additional tricks that the Wine guys can pull to improve compatibility in these areas as well.

      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.
      Well, currently ReactOS doesn't really work all that well either. My point was to show that it is possible to run windows drivers in Linux, if enough people are motivated. I think the primary problem is that except for a few specific cases (wireless drivers and NTFS drivers), there isn't all that much interest in running Windows drivers since Linux has native drivers available for that type of hardware.

      This is because running a Windows device driver without a Windows kernel is quite tricky.
      It's also quite tricky to write a complete, near exact clone of the NT kernel just to get your wireless card working (or whatever other hardware you can't find a supported Linux version of).

      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.
      If you want a black box, then just run Windows. I'm not sure how this is an argument in favor of using ReactOS. In addition, it's unlikely that running binary drivers written for a different OS inside of ReactOS will improve reliability & stability, the opposite is far more likely to be true. Did you read in the slides about the hard coded kernel hooks that are in some drivers (such as nVidia's)?

      Actually, there are very substantial differences that can be deeply annoying because they're about the way the basic system works.
      And the differences between Win 9x (DOS based) and Win XP (NT based) are not differences between how the basic system works? Win NT is far more similar to Linux in its system design then it is to DOS/Win 9x.

      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).
      Not true, I've had Windows not give any indication, or a significantly delayed indication, that programs are starting. One example: try using CTRL-ALT-DEL & selecting the task manager while the system is pretty busy. It will just sit there, with no indication that you successfully launched task manager, until it finally appears.

      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.
      Yes, that'd be cool, however:
      - Driver compatibility would not be very important, since you would likely be using virtualized hardware, not the actual hardware.
      - The new extensions to Intel & AMD chips let you run Windows in Xen unmodified.
      So still, if ReactOS doesn't have significantly better application compatibility (which remains to be seen), you would probably still be better off with Linux+Wine, or even just Windows.
      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    10. Re:ironic by Lord+Ender · · Score: 1

      this begs the question of why do we need ReactOS anyway?
      It always amuses me when the uneducated try to pick up phrases they have overheard lawyers, scientists, or other educated people use, hoping to lend a false sense of respectability to their claims.

      Its ironic, because people who actually went to college immediately recognize that the person misusing academic or legal terminology is trying so hard to make a point that it probably can't stand on its own.

      Well, either that, or the speaker is an idiot.
      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    11. Re:ironic by Pseudonym · · Score: 1

      You're thinking like a slashdotter. Think like an open source businessperson for a moment, instead, and you'll see what's probably the most compelling reason, which is Checkbox completeness.

      I can sell you a solution with the "yes, your Windows admins don't need to be retrained" checkbox checked. I can do that without paying the Redmond tax, and like all other open source, I can diagnose and fix problems by myself without being at the mercy of someone else's support cycle, assuming they want to fix your problem at all.

      --
      sub f{($f)=@_;print"$f(q{$f});";}f(q{sub f{($f)=@_;print"$f(q{$f});";}f});
    12. Re:ironic by Anonymous Coward · · Score: 0

      to beg the question != to raise the question. It's entirely different.

    13. Re:ironic by paulmer2003 · · Score: 1

      Speed - Wine, since it is an emulator

       


      Wine

      Is

      Not (a)

      Emulator

    14. Re:ironic by Anonymous Coward · · Score: 0

      Just as amusing is when the seemingly educated prove by an immediate previous post that they do not normally use even proper capitalization in their posts. Lord Ender, we stop bowing before thee now. You are insufferable at times, but we can look past it.

    15. Re:ironic by jZnat · · Score: 1
      Well, if we're both thinking of the term in regards to an invalid method of proving something (e.g. in [mathematical] logic) where you assume the conclusion is true (or false), then I can see why you're annoyed by his invalid use of the term. Although, Wikipedia says this about the improper use of the phrase:

      Today, the phrase is also frequently seen in a different usage with the meaning "raise the question." In educated contexts this use is rare and widely regarded as incorrect, but it has nevertheless become very common in the news media.
      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
    16. 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.

    17. Re:ironic by Anonymous Coward · · Score: 0

      Where do you think projects like NdisWrapper and Captive came from? ReactOS, of course. The whole project is open source, so it contributes back to Linux by enabling things like driver wrappers and making improvements to WINE.

      dom

    18. Re:ironic by Micah · · Score: 1

      > 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.

      Of course, as soon as you take that attitude, you have lost the battle for Freedom.

      Granted, I got a new laptop with an nVidia chip (I couldn't find any high-res 17" laptops with an Intel GMA chip) and I use their proprietary kernel module, but I'm not happy about that in the least. Sure hope Nouveau(sp?) gets there this year.

    19. Re:ironic by ryanov · · Score: 1
    20. Re:ironic by Eivind+Eklund · · Score: 1

      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. Actually, this can be done using progressive loading and normal IPC (interprocess communication), outside the kernel. Basically, you have a tiny little program that start up and give the notification, and then that program continue loading the rest, using dlopen and friends.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    21. Re:ironic by Anonymous Coward · · Score: 0

      As can be seen on any Linux desktop near you, the form of basic notification only works when the application loads successfully. There is no way to trap errors that happen before the application load enough to produce it's own error messages I.e. a missing library that causes the application to fail to load will still leave the notification applet running, waiting for a notification that will never come. Eventually the notification applet will give up and die, leaving the user with no indication of why the application failed to load.

  17. Re:WTF??? by Marcus+K · · Score: 0

    Just for fun.

  18. 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 bockelboy · · Score: 1

      Yup, internally they're fine.

      If they start copying the visual aspects too closely, they are in danger of infringing on MS's copyrights on the look and feel. If not truely infringing, they may get close enough to get tied up in lawsuits for ... forever.

      Then again, it doesn't look like they're big enough to be on MS's radar.

    3. 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.

    4. Re:FUD - ReactOs is legal by LionMage · · Score: 1

      If they start copying the visual aspects too closely, they are in danger of infringing on MS's copyrights on the look and feel. If not truely infringing, they may get close enough to get tied up in lawsuits for ... forever.

      You mean like how Apple prevailed in its L&F lawsuits against Microsoft that dragged on for years? Oh wait, Apple didn't prevail, and eventually the two companies called a truce (with some money changing hands in the process). I seem to recall the EFF and/or FSF advocating boycotts on Apple products for years because of the bad legal precedent that "look-and-feel copyright" would have created.

      Then again, Adobe had more success suing Macromedia over various patented UI elements -- but in this case, the elements in question had the force of patent law and not mere copyright law.

      The upshot of what I'm saying is, the whole notion of a copyright on look-and-feel didn't hold up historically in courts, and the only way to successfully sue over infringing someone's L&F is to complain about "trade dress" infringement (related to trademark law IIRC) or violation of patents. The patent approach seems to work best.
    5. Re:FUD - ReactOs is legal by samkass · · Score: 1

      Apple didn't prevail because they'd signed away their rights by not reading the fine print while working with Microsoft, not because Microsoft didn't infringe or copy Apple.

      --
      E pluribus unum
    6. Re:FUD - ReactOs is legal by cp.tar · · Score: 1

      Then again, it doesn't look like they're big enough to be on MS's radar.

      Here's one from Going Postal:

      Miss Dearheart: "The Grand Trunk Company kills people, Mr. Lipwig. In all kinds of ways. You must be getting on Reacher Gilt's nerves."
      Moist von Lipwig: "Oh, come on! I'm barely a wasp at their picnic!"
      Miss Dearheart: "And what do people do to wasps, do you think?"

      Care to reconsider your position?

      --
      Ignore this signature. By order.
    7. Re:FUD - ReactOs is legal by FromellaSlob · · Score: 1

      Wasn't Microsoft's argument that Apple had no case because they both stole their GUI concepts from Xerox?

    8. Re:FUD - ReactOs is legal by bockelboy · · Score: 1

      You mean like how Apple prevailed in its L&F lawsuits against Microsoft that dragged on for years? Oh wait, Apple didn't prevail, and eventually the two companies called a truce (with some money changing hands in the process).
      That's the difference between open source and a big company.

      Companies can easily operate while dragging on lawsuits for years. I'd suspect that all but the biggest open source projects would fold quickly.

      I know if my hobby project got a big lawsuit from MS, I'd have no choice but to fold my cards -- unless EFF stepped in.
    9. Re:FUD - ReactOs is legal by Teancum · · Score: 1

      Shut what down and who to shut down? This was precisely the problem with the deCSS (DVD-Video decryption) software, as once one of the websites was shut down, a dozen more came up to take its place. It was literally impossible to shut it down entirely, even during the middle of a trial.

      Court injunctions have to be very specific, and in the case of ReactOS, you can get copyright permission (in the form of the GPL) to host it nearly everywhere. Those hosting the content are not violating copyright law, unless there is something that is alleged to have been source-code copied from Microsoft.

      Even in SCO vs. IBM, SCO hasn't been so stupid as to try and shut down Red Hat or any of the other distros during the trial. While they claim that Linux has violated their "IP" (whatever that means), they certainly have not sought a blanket ban to prohibit redistribution of Linux from any vendor. Indeed, they haven't even tried to stop IBM from selling Linux... or at least they havn't succeeded.

      I can't imagine that this would be any different, not to mention that most of the software developers for ReactOS (not all of them) are from Europe. Having a U.S. judge try to impose a temporary distribution injunction in Germany seems as stupid as it comes. It wouldn't even be in their juristiction. Or the other way around (assuming that Microsoft sues in Germany). A judge does not have super powers to prohibit distribution, and the free content license nature of ReactOS would make nearly any effort to block distribution pointless. A judge might be able to prohibit distribution of the content within the confines of his courtroom (as did happen with the deCSS software!), but that would really be the limit of his authority.

      This is more than simply moving the servers to another country. At best all that could be claimed is a patent violation. Even then, I can't imagine it would be something so critical that a judge would completely block distribution of the rest of the operating system not in dispute.

      In short, this is pure FUD you are mentioning here, and has no basis in reality.

    10. Re:FUD - ReactOs is legal by Teancum · · Score: 1

      On the contrary. Trying to do lawsuits against open source projects tend to drag on for years and years, and are a moving target, as once one person drops the project somebody else is more than willing to take it up.... especially if the software has any value at all. In addition, most open source software developers are about as poor as you can get (college students and other part-time volunteers), so even if the lawsuit succeeds, the plaintiff can't get any money. And the software development keeps going with the only consolation that one particular developer or a small team has been barred from participation on that particular project.

      An established company with fixed tangible assets is more likely to be the target of a lawsuit. I admit that small companies can be huge targets for some lawsuits, but in the case of an open source project that is hosted on some guy's DSL line on a 5-year-old computer running Linux, there isn't much in terms of assets to take. The value of that property is likely to be less than what is legally permissible with seizure and forfeiture laws, as that same Linux server could be considered personal property.

  19. 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
  20. 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 julesh · · Score: 1

      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?

      Almost certainly. But given that major features are missing, that's hardly surprising.

    3. 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.
    4. Re:memory footprint by Anonymous Coward · · Score: 0

      "Lighter" doesn't necessarily mean "better." Since they're trying to essentially replicate Windows, "lighter" in this sense can be equated to "missing features."

    5. Re:memory footprint by ceeam · · Score: 1

      A roughly 0.5% of Vista size. Ok, zipped - make that 1%. Indeed a _bit_ lighter.

  21. slides unavailable by mrbobjoe · · Score: 3, Informative
  22. Lawyers by dedazo · · Score: 1

    If ReactOS is a clean-room implementation, they probably can't do squat about it.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
    1. Re:Lawyers by rubycodez · · Score: 1

      what about PATENTS?

    2. Re:Lawyers by Anonymous Coward · · Score: 0

      Any patents in NT are probably quite close to expiring. They really haven't changed the internals much since NT 3.1

    3. Re:Lawyers by Anonymous Coward · · Score: 0

      If ReactOS is a clean-room implementation, they probably can't do squat about it.

      It's not.
    4. Re:Lawyers by dedazo · · Score: 1

      But that qualifies as reverse engineering, doesn't it? If so, then it's perfectly legal under current law.

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  23. 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.
  24. Re:WTF??? by Fordiman · · Score: 1

    Ah, WINE (rather specifically) Is Not an Emulator. It's a compatibility layer, as are all its derivatives.

    --
    110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
  25. Re:WTF??? by ClosedSource · · Score: 1

    Well, having a product that actually does what these products claim to do might actually be helpful, but I wouldn't hold my breath.

  26. WINE by Aphex+Junkie · · Score: 5, Funny

    Wine
    Is
    Not
    Enough

    brilliant!

    1. Re:WINE by discogravy · · Score: 1

      so have some beer.

    2. Re:WINE by Anonymous Coward · · Score: 0

      Video
      Cassette
      Recorder

  27. To run apps without Windows by ISoldat53 · · Score: 1

    The only reason I run Windows is to run Audible.com and iTunes. If I could get an OS to run these apps in a virtual machine under Linux, I would be Windows free.

    1. Re:To run apps without Windows by lakeland · · Score: 1

      Both of those work just fine on codeweaver's version of Wine. I wouldn't be surprised if they both work fine on the trunk version of wine too now...

    2. Re:To run apps without Windows by Ash-Fox · · Score: 1

      Both of those work just fine on codeweaver's version of Wine.
      iTunes 4 and older work, new versions will not (iTunes 7 is current).

      However, if the person in question does not rely DRM media. I would recommend they try Amarok which has far more features than iTunes.
      --
      Change is certain; progress is not obligatory.
    3. Re:To run apps without Windows by lakeland · · Score: 1

      Yeah, amarok is seriously cool.

      As soon as the mac port comes out (just a couple months now) I'm going to try and shift my wife away from iTunes to Amarok

  28. As the Bard might say: by ClosedSource · · Score: 1

    A compatibility layer by any other name, would still be unable to run many Windows applications.

    1. Re:As the Bard might say: by Anonymous Coward · · Score: 0

      I guess you're referring to Vista?

    2. Re:As the Bard might say: by ClosedSource · · Score: 1

      Well, Vista is one of the Windows versions these projects don't properly simulate, emulate, or whatever you want to call what they do.

    3. Re:As the Bard might say: by Fordiman · · Score: 1

      Fortunately, that's a target that's not yet commonly used.

      Anyways, ReactOS is sitting in _alpha_ at this point. Way to criticize the functionality of an unfinished project. I'm sure you can compare a student's quarter-finished thesis to a PhD's two year old peer-reviewed research, too.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    4. Re:As the Bard might say: by ClosedSource · · Score: 1

      Actually, if you read this sub-thread carefully you'll notice that I'm actually citicizing WINE not ReactOS. WINE doesn't fully implement any version of the Windows API, the introduction of Vista just means it's falling further behind.

    5. Re:As the Bard might say: by Fordiman · · Score: 1

      Well, criticizing WINE is alright, I suppose; they're chasing a moving target, after all, and will never achieve 100% compatibility. The goal is to implement a prioritized list of API groups that applications commonly use - as a result reaching good compatibility with a wide range of apps.

      So, technically you're not wrong - but I still consider it a worthy project, and useful (at least for me) in instances when I need the odd Windows software package. For example, Timeslice, the application one of my current clients prefers for his contracts' work-tracking, is a Windows app that works nigh perfect in WINE. For most things, though, Linux native apps work best for me.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    6. Re:As the Bard might say: by ClosedSource · · Score: 1

      I have no problem with WINE being described as a project that allows some Windows applications to run under Linux. The problem is that it is often promoted as a general solution to running Windows applications on Linux, which it is not.

  29. 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?

  30. 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.

    1. Re:Facts badly wrong in parent, mod down by Anonymous Coward · · Score: 0

      That's great and all, but at the time the ReactOS crew specifically referred to leaked Windows source-code:

    2. Re:Facts badly wrong in parent, mod down by Anonymous Coward · · Score: 0

      It's even greater that you bother to read stuff that you link to - especially that you take into account when the audit was started and when the source was leaked.

    3. Re:Facts badly wrong in parent, mod down by Anonymous Coward · · Score: 0

      Perhaps you'd like to read it, as you obviously haven't.

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

  32. 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: 0

      It's not on purpose. It's just that ReactOS isn't finished yet!

    2. Re:Identical? by Ant+P. · · Score: 0, Troll

      The bad dialog box rendering is on purpose - after all, they are trying to _accurately_ clone windows.

    3. Re:Identical? by TheThiefMaster · · Score: 1

      It's probably because it's not the same font as Windows uses, and cpu-z was designed at a fixed size and isn't resizing itself to fit the text. You could probably replicate the same on Windows by changing the font, font size, or the display's dpi setting.

    4. 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.

  33. Is ....eescu a Hungarian name? by Anonymous Coward · · Score: 0, Offtopic

    I remember vaguely that names ending in 'escu' are typical Hungarian or Bulgarian names, or other similar Slavic languages from Eastern Europe (Czech, Polish, Croatian, I am not sure which ones). Is 'escu' also used in other Slavic languages besides Hungarian (Bulgarian), for example Polish or Russian? What does it mean? I think that French people also use this kind of names, I believe that a French playwriter is named Ionesco.

    1. Re:Is ....eescu a Hungarian name? by dosius · · Score: 1

      Sounds Romanian to me

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    2. Re:Is ....eescu a Hungarian name? by Who235 · · Score: 1

      It is Romanian which is a Romance language, not a Slavic language. I suppose that would account for the similarity to French last names.

      Here is some information about naming conventions all over the world (anchored to Romania):
      http://en.wikipedia.org/wiki/Family_name#Romania

    3. Re:Is ....eescu a Hungarian name? by cp.tar · · Score: 1

      You remember wrongly.

      Last names ending in -escu are typically Romanian.

      As in, for instance, Nicolae Ceausescu.

      Also, Hungarian is not a Slavic language (it's Finno-Ugric) and is in no way at all related to Bulgarian. Romanian is a Romance language, therefore related to French and Italian etc.

      --
      Ignore this signature. By order.
  34. More importantly... by spoop · · Score: 1

    how tf did they get a 2.4ghz Pentium II?

    --
    I blame geof's speakers.
    1. Re:More importantly... by Taimoor · · Score: 1

      Qemu. They don't run it on real hardware most times.

    2. Re:More importantly... by RalphTheWonderLlama · · Score: 1

      I have a 1200 MHz Pentium Pro. At least that's what my POST says :)

      --
      simple, fast homepage with your links: http://www.ngumbi.com/
    3. Re:More importantly... by Zantetsuken · · Score: 1

      because thats the popular hardware emulated using virtual machine environments - thats not the real hardware, its just what cpuz is seeing from the vm software's emulated bios/etc...

  35. 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.

  36. I believe 'Ion" is Hungarian for John by Anonymous Coward · · Score: 0

    but I have no idea what does 'escu' mean. Hungarian slashdotters should help us on this one.

  37. Re:WTF??? by Anonymous Coward · · Score: 0

    Because when it's finished, they essentially open up all the hidden APIs/file formats/protocols, and being open source, make it a very good environment for reverse-engineering all the other stuff Microsoft hides away.

    This could conceivably allow full compatibility with Windows hardware and software in the future. Legally, it'll be interesting, because Bill will NOT be happy with that.

  38. Re:WTF??? by AusIV · · Score: 1

    VMWare on Linux.

  39. 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.
    1. Re:Drivers by orasio · · Score: 1

      As I understand it, instability in Windows operating systems comes largely from defects in drivers, such as the VxDs of Windows 9x.


      mswindows should be regarded as a whole, when comparing with other systems. without third party drivers, it does a lot less than gnu/linux, and in a much uglier way.

      With third party drivers in the picture, it has better hardware support, but it has a lot of instability issues.

  40. 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 *
  41. Why No Apple OSX Hacks? by BSDetector · · Score: 0

    I guess it's because Steve Jobs is only doing this for "Peace on Earth"? He doesn't profit from this I guess!

  42. It's not Emulating Windows good enogh!!! by itz2000 · · Score: 0

    Only 2 BSoD's? Come'on! In real windows there are much more!

  43. 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 Goodgerster · · Score: 1

      Linux is not freeware, you twat...

    2. Re:Old Hacker Rule by BillGatesLoveChild · · Score: 1

      It must take guts to call people names behind the safety of your keyboard. Linux is free. Use your brain.

    3. 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
    4. Re:Old Hacker Rule by Cederic · · Score: 1


      Free is not the same as freeware.

    5. Re:Old Hacker Rule by TeknoHog · · Score: 1

      You can get many distros of Linux for zero money, but IMHO calling it 'freeware' misses the point of Free Software. One of these is that it's developed by a community of volunteers, whereas companies hire people to write freeware all the time. Also, 'freeware' has all the negative connotations of being 'cheap'.

      --
      Escher was the first MC and Giger invented the HR department.
    6. Re:Old Hacker Rule by Alioth · · Score: 1

      On a point of pedantry, Linux is most certainly not freeware. Freeware generally means closed source, non-free utilities which are as proprietary as Windows itself - just distributed gratis. Linux is Free software - Free with a capital F. This doesn't necessarily mean you get it gratis - indeed, people charge for Linux distributions (see RedHat, Novell et al.) What the Free with a capital F means is 'freedom', not 'gratis'. It's quite an important distinction. Freeware, generally is non-free (i.e. you still don't have the freedom to modify or redistribute).

      Anyway...moving swiftly on.

      The success of Linux and ultimately doomed state of ReactOS is because Linus was not shooting for a 'clone' - he was just shooting for something POSIX. Most of Unix is really all about open(), close(), read(), write(), select() and ioctl(). Implement those syscalls and you are a long way there. Then just add GNU - the utilities and libraries already pretty much complete in 1992, when Linux first started getting useful.

      Win32 on the other hand... how many years has Wine been going without even getting close to decent compatibility with Windows? Win32 is a horrible, convoluted mess of an API, which certainly cannot be mostly boiled down to a handful of syscalls. Linus didn't have to write anything to do graphics - X already existed, and was already the standard for Unix. He didn't have to write standard C libraries or utilities - GNU already existed. ReactOS on the other hand have to implement equivalents of these from the ground up *and* the abortion that is Win32.

      ReactOS's goals are very noble, but they aren't even chasing a stable API - Vista changes the goalposts again and adds on yet another layer they have to chase. They don't even expect to have full kernel compatibility by next year, let alone compatibility with Windows 2000 (which is now 7 years old).

    7. Re:Old Hacker Rule by xero314 · · Score: 1

      Also, 'freeware' has all the negative connotations of being 'cheap'. Yea, call it what it is "Free Open Source Software" so that it can have the connotations of "zero accountability," "zero support," as well as "cheap." (there I go risking Karma for the sake of honesty).
    8. Re:Old Hacker Rule by BillGatesLoveChild · · Score: 1

      Depends on your definition. To my thinking, both Open Source and Public Domain are both "Freeware" (as in "Free Software"). Obviously some here disagree, but the Wiki definition of Freeware is closer to Open Source: http://en.wikipedia.org/wiki/Freeware

      Yeah ReactOS is chasing goal posts which Microsoft are constantly changing by design. It'd be nice if they succeeded, but as you say the odds are very much against them. They're a small team with little support. Linux is as much larger team with a lot of support, including big corporations.

      If I was a fat ass millionaire I'd sling some large wads of cash the way of ReactOS and WINE, just for the fun of it. Can you imagine Microsoft waking up one morning to discover their cash cow has a free rival? It'll never happen, but I can dream :-)

  44. OSX Hacks DO exist (www.osx86project.org) by Anonymous Coward · · Score: 1, Interesting

    By using these hacks you can install OSX on a plain, non-Apple computer. The hacks circumvent Apple DRM and thus they are illegal in America (I dont know about other countries). There is a wiki about all these illegal activities, http://www.osx86project.org/. Slashtot competitor, Digg, diggs everything about it.

    1. Re:OSX Hacks DO exist (www.osx86project.org) by Zantetsuken · · Score: 1

      IIRC, there was a "legal" way to have OSX86 run on white-box machines, except it involved disabling the GUI entirely, so you would just as well be running any other Unix terminal...

    2. Re:OSX Hacks DO exist (www.osx86project.org) by SirTalon42 · · Score: 1

      It was called 'Darwin'... i.e. all the OpenSource stuff in OS X (pretty much everything BUT OS X's GUI layer is OSS)

  45. no emulation by __aalwyc6372 · · Score: 0, Redundant

    reactos uses a great deal of wine code and certainly isn't an emulation.

  46. 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." ---
    1. Re:software patents by Raenex · · Score: 1

      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. The jurisdiction falls wherever it is being used. If you are a company (or anybody else) in the US using software that violates US patents, you can be sued. It doesn't matter where it was developed.
    2. Re:software patents by Anonymous Coward · · Score: 0

      If the US are really going to go down the route of enforcing their stupid laws on other countries, they will lose their position in international affairs even quicker that they are managing to do at the moment.

      It amazes me that, almost immediately the US had a effective dominant position in world affairs (I would guess they dominated the West by displacing the UK in the 1960s, and the East when Russia went down in the 1990s), they started to throw it all away.

      I reckon their model of unbridled corporate economic freedom with no class/feudal remenants, mediated by a 200-year-old set of rules based on an outdated view of human interaction, is currently falling apart. They really need to go back to a more durable leader culture like the classical and medaevial periods had, where the leader had personal responsibility for the well-being of his underlings. For instance, the leader was expected to go to war at the head of his troops.

      A good example is the UK Royal Family, where Prince Andrew fought in the Falklands War, and Prince Harry is about to go out to Iraq.

      Do you think the US would be a better place if Bush children were expected to go into the military?

    3. Re:software patents by TheVelvetFlamebait · · Score: 1

      But you make a good point: more proof that softwarepatents suck.
      Actually, if you think about it, this is exactly what software patents are good for. Microsoft has spent a lot of time and a lot of money on their product and have maintained a monopoly (sometimes through illegal means). Suddenly, after all these years, a group of developers mimic their intellectual property and piggy-back their success, with the potential to seriously damage Microsoft's sales. I would chalk this one up as one of the only sensible applications for software patents.

      /devils advocate

      Still, sucks to be the US.
      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    4. Re:software patents by N3wsByt3 · · Score: 1

      "Actually, if you think about it, this is exactly what software patents are good for."

      Well, that would depend on what you mean by 'good' and who it is it is good for. Rest assured, a *monopoly* is only good for the monopolist, not for the enduser, nor the public at large, nor for the stimulation of innovation. There hasn't been a monopoly since its existance which was beneficial for anyone BUT the monopolist; thus, if your viewpoint is that the benefits to the profits of microsoft (or any other monopolist) is the prime measurement for establishing how useful softwarepatents are, then you are right.

      However, since a patent is a monopoly granted by the state, and the state has a duty to provide the largest amount of benefits to its citizens as a whole, it is an equally (if not more) valid argument that softwarepatents should be abolished, since the populace doesn't benefit from it, and innovation isn't stimulated by it.

      Anyway, I already made an argumentation of the 'use' of softwarepatents (viewed in an EU context) here: http://newsbyte.blogspot.com/2005/07/software-pate nts-manifesto.html

      --
      --- "To pee or not to pee, that is the question." ---
  47. Re:WTF??? by Stewie241 · · Score: 1

    Okay... so we have a virtual machine... what runs on that virtual machine?

  48. Re:WTF??? by phrasebook · · Score: 1

    Windows with snapshots! Being able to save and load the vm's state makes Windows much more tolerable.

  49. 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?

    1. Re:Windows clone? Why not go for OS X? by slim-t · · Score: 1

      It's not the interface that matters, it's the application compatibility. Make it compatible with OS X and windows, then comes up with a unique interface that's better than either.

    2. Re:Windows clone? Why not go for OS X? by Vexorian · · Score: 1

      on my PC,
      huh?
      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    3. Re:Windows clone? Why not go for OS X? by RalphTheWonderLlama · · Score: 1

      Probably for the same reason that those people aren't using it now.

      --
      simple, fast homepage with your links: http://www.ngumbi.com/
    4. Re:Windows clone? Why not go for OS X? by Ash-Fox · · Score: 1

      Why clone a bad interface when you can clone a good one that many people would like to use?
      GNUStep, KDE-look (where you can find a tonne of different OS X look-alike themes, replicating the OS X interface).

      Oh, and, I don't fit into your 'many people' assumption. I don't want to use OS X's dumbed down interface style.
      --
      Change is certain; progress is not obligatory.
    5. Re:Windows clone? Why not go for OS X? by Anonymous Coward · · Score: 1, Interesting

      I would be much more interested in an OS X clone running on my PC,

      Go yell at the GNOME guys. They're the ones who, after Apple bought NeXT, decided to build a desktop on the Gimp toolkit instead of on the already-live GNUStep project. Imagine if the effort that had gone into GTK+ 1 and then GTK+ 2 development had instead been spent on getting GNUStep ready for prime time.

  50. Re:WTF??? by innocence18 · · Score: 1

    VMWare et al don't count. You still need a *legal* copy of Windows to install into the virtual machine. The main advantage of having something like ReactOS being API/Binary compatible is that you don't need to rewrite all the drivers, you can just run with the windows ones. Whether this is a good thing or not is questionable in itself given some of the dodgy 3rd party drivers out there.

    --
    Anonymity of the internet is responsible for the views expressed in my post.
  51. Re:WTF??? by BrokenBeta · · Score: 0

    The point is that you need a copy of Windows to run in it. Which costs the same as a copy of Windows to run natively.

  52. Hungarian and Romanian are similar languages by Anonymous Coward · · Score: 0

    Think Bucharest and Budapest sound about the same. I think they are both Slavic languages (all languages in that part of Europe are)

    1. Re:Hungarian and Romanian are similar languages by Anonymous Coward · · Score: 0

      hungarian language does not belong to slavic family of languages, it is an ugrofin type of language, more similar to scandinavian language than slavic

    2. Re:Hungarian and Romanian are similar languages by dosius · · Score: 1

      Romanian is of Romance stock same as French and Spanish, though with a bit of a Slavic bent (as French has a slight Germanic bent).

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    3. Re:Hungarian and Romanian are similar languages by hszp · · Score: 1

      Think Bagdad (Louisiana) and Baghdad (Iraq) sound the same. I think they (them Louisianians and them Iraqians or Iroquis or whatnot) are both frenchlike languages (they speak French in Louisiana don't they? It sounds just like that. It's like the Quebec of Texas, right?)

      What, you dare not believe me? You should, for
      I am a professor of geography at the ELTE, Budapest and a respected linguist and a%@2+gist at the Uni. of Bucharest, too.

      Sincerely, Essjay

  53. Most accurate description until now by pimpimpim · · Score: 1

    Ah, the genius! But where are modpoints when you need them...

    --
    molmod.com - computing tips from a molecular modeling
  54. 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.
  55. Re:WTF??? by maxwell+demon · · Score: 1

    Wine/cedega/crossover are application-level implementations. They allow you to run Windows applications. Reactos actually uses Wine code as well for this. Reactos however aims not only for app compatibility, but also for driver compatibility. That is, you can use the Windows drivers your hardware supplier gives you. In other words, if they achieve their goal, any hardware supported under Windows will automatically also be supported under Reactos, through the vendor-provided drivers. That's something you currently simply don't get with Linux.

    VMWare is a virtual machine. It's completely useless without an operating system to run on. That is, if you want to run Windows programs with VMWare, you need some OS to run Windows prorams on. That is, VMWare doesn't help you with this problem at all (nor does Xen, QEMU, Bochs, VirtualBox, ...).

    And 2007 of course doesn't help you even the least in running Windows programs without using Windows. :-)

    --
    The Tao of math: The numbers you can count are not the real numbers.
  56. 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
  57. Windows, sans FUD by Anonymous Coward · · Score: 0

    The only time a Windows NT/2000/XP install will fail is when there is a hardware problem. Despite the propagandist Slashdot FUD, Windows versions based on the NT kernel are really stable and reliable products, and always have been.

    I've installed Windows hundreds of times since Windows 95, and build and supported at least a hundred servers since NT4. If someone has a problem keeping Windows stable, their problem is between the screen and the keyboard, not in Redmond WA.

    It may be hard for your average 12 year old Slashdot MS hater, but granted they don't have a lot of understanding or experience. That's why they parrot the FUD... which /. is so ready and eager to provide. But they need to start learning that things work far differently once you get into the real world: sadly, Slashdot refuses to let the reality-based community intrude on their anti-MS agenda, truth be damned.

    How about less FUD, and more expert opinion? Ahhh... nevermind. There are actually better places to get that, which is why digg and del.icio.us are eating Slashdot's lunch: it's geek info, sans the constant anti-MS FUD and shrill, puling whine.

    1. Re:Windows, sans FUD by Ash-Fox · · Score: 1

      The only time a Windows NT/2000/XP install will fail is when there is a hardware problem.
      I couldn't complete installs tonnes of times because I lost the stupid key.

      I've installed Windows hundreds of times since Windows 95, and build and supported at least a hundred servers since NT4. If someone has a problem keeping Windows stable, their problem is between the screen and the keyboard, not in Redmond WA.
      Indeed, Redmond is perfect, that's why they don't release fixes for thei.. OH sorry, nevermind.
      --
      Change is certain; progress is not obligatory.
    2. Re:Windows, sans FUD by senatorpjt · · Score: 1

      The kernel itself is stable. The OS is not. The problem isn't between the screen and the keyboard, it's between the kernel and the screen. The kernel may still be running, but if the only way you can do anything is through a remote terminal... the kernel isn't crashed, but the OS is.

      I'm not even counting having to restart explorer.

    3. Re:Windows, sans FUD by DuckDodgers · · Score: 1

      Sorry, kiddo.

      My wife and I use XP at home. It's been five years, it only crashed when I had driver problems with a wireless card.

      At work, we have laptops and workstations running 2000 service pack 4 and XP. Likewise, they only ever fail with hardware problems.

      But the servers? 2000 Server and 2003 Server - hit them hard enough with constant loads, and down they go. Or they're technically still up, but they stop responding to pings and keyboard input until you get tired of waiting (10 minutes, half an hour, 24 hours) and reboot.

      You can run the CPU of Linux servers at 100% all day for days at a time, and user interface responsiveness is noticeably slow but they'll keep right on trucking.

  58. Romanian sounds VERY Slavic by Anonymous Coward · · Score: 0

    I visited a research institute of the Romanian Academy for a few weeks and Romanian sounds very Slavic to me (although they claim it is a Romance language - I dont know why). Many frequent words are obviously Slavic, for example they say 'da' for 'yes', which is the same as in Russian, you hear them say 'da', 'da' thousands of times a day, sounds nothing like any other Romance language (No Si, no Oui) They use vremya for weather (also the same as in Russian). The name of my host was Vlad (like in Vlad Drakula) which is short for Vladimir, obviously a Slavic name. Romance languages are very musical (think of Spanish or Italian) while Romanian sounds rough and it is anything but musical, sounds Slavic to me. Many names of cities, rivers and other places in Romania are almost impossible to pronounce (which is not the case with real Romance languages , say Italian or Portugese) Very often they contain two or three consonants one after another.

    1. Re:Romanian sounds VERY Slavic by Anonymous Coward · · Score: 0

      Of course there is a slavic influence. Probably many borrowed words.
      I understand just a very little romanian (being a Hungarian born in Romania), but just recently I saw something like this on a paperbag: viata este cel mai dulce cu noi (sorry for any inaccuracy). Dolce vita? C'est la vie? Notre Dame? Knowing only these international phrases (of latin origin) you can pretty easily decipher that the bakery claims that life is sweeter with them.
      On the other hand: other than pozor vlak, k*rva, and a few other words, I simply don't understand anything written or said in slavic languages.
      Just take my word on this: Romanian is a Romance language. I wouln't insist on this as a Hungarian were it not.

  59. BSODs by Ash-Fox · · Score: 1

    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.
    They better make it red, it'll be enough to convince people that it is a clone of Vista.
    --
    Change is certain; progress is not obligatory.
  60. 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.

  61. A link to the discussion? by Anonymous Coward · · Score: 1, Informative

    Are you referring to this discussion:

    http://www.reactos.org/archives/public/ros-dev/200 6-January/007393.html

    Here's a quote from one of the messages about the standard policy, which helps to put the discussion in perspective:

    ">From Section C of the ReactOS IP Statement (C. Copyrights of Others) ....Any source code produced by direct reverse engineering should be treated in exactly the same way as any other non-free source code useful for study and understanding of the system, but not permitted for inclusion in ReactOS."

  62. .escu used only in Old Romania,not in Transylvania by Anonymous Coward · · Score: 0

    I am a Romanian from Transylvania and I can clarify this problem. In Old Romania (The former Old Kingdom, which is made up of Southern Romania (Vallachia) and the Romanian half of Moldavia, but NOT Transylvania) the word ending ...escu is used to transform a christian name into a family name. From Ion (John) to Ionescu, from George to Georgescu, etc. In those parts of Romania family names were introduced quite recently, about 160 years ago, and there was need for a rule for transforming a first name into a last name. On the other hand, in Transylavania family names were used for many centuries and there was no need for such a rule. Due to migration now there are a few families from Transylvania with a name ending in ..escu; however they are no natives of Transylvania, but originate from other Romanian provinces. In fact, the presence of ...escu in a family name is an easy way of identifying a Romanian which is not a native of Transylvania.

  63. One major difference. by Mr+Z · · Score: 1

    By default, Wine translates Win32 calls to something a POSIX operating system can handle. With a Win32-aware kernel, the translation layer is much thinner. Wine only has to handle the user-space portion of the call, and not the adaptation between one kernel-space and another.

    --Joe
  64. 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.
  65. Re:WTF??? by Anonymous Coward · · Score: 0

    and please post instructions on how to Windows programs w/out windows using 2007.

  66. Re:WTF??? by crhylove · · Score: 0, Redundant

    MOD PARENT UP
    MOD PARENT UP
    MOD PARENT UP!!!

    Amen to that. I'm so glad somebody else has put what I've been thinking so succinctly! Nicely done!

    rhY

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
  67. Re:WTF??? by Anonymous Coward · · Score: 0

    Maybe he just has stored screenshots of every possible pixel configuration on the screen, and he loads them in order?

  68. Re:Its A "Neat" Academic Exercise by SirTalon42 · · Score: 1

    1. Theres more than 1 Slashdotter, not all of which despise Windows.
    2. Who said any of the ReactOS developers are Slashdotters?

  69. [OT] OS X + PC by SirTalon42 · · Score: 0, Troll

    OS X runs on PCs. Despite what the Apple commercials would lead you to believe, The 'Mactels' are pretty much normal PCs (the 'biggest' difference between a Mac computer and a Dell/HP/other-OEM is EFI other than the default OS).

    I'll repeat this again since a lot of people seem to have trouble realizing this: All new Macs that AREN'T running a PowerPC processor are PCs!!! So much for 'Think Different'!

  70. 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.
    1. Re:Wouldn't work by Anonymous Coward · · Score: 0

      I certainly hope they would NOT. At least not at reasonable optimisation levels.
      If I want my computer to 1000 compares, increments and jumps, then I want it to do 1000 compares, increments and jumps.
      At the worst I'd expect it to unroll to 1000 noops, but even that I'd want to have to tell the compiler to do.

    2. Re:Wouldn't work by kestasjk · · Score: 1

      I certainly hope they would NOT. At least not at reasonable optimisation levels.
      If I want my computer to 1000 compares, increments and jumps, then I want it to do 1000 compares, increments and jumps.
      At the worst I'd expect it to unroll to 1000 noops, but even that I'd want to have to tell the compiler to do.
      Well, any decent compiler that's told to optimize will take them out. They'll see that you're not doing anything with the data being processed, so it doesn't bother processing.

      If you want to wait a while use a timer; that way you don't hog up the processor.
      --
      // MD_Update(&m,buf,j);
    3. Re:Wouldn't work by Anonymous Coward · · Score: 0

      I certainly hope they would NOT. At least not at reasonable optimisation levels.

      Really? Then you're a fuckwit. I hope you're not in control of any important code. Or for that matter, any code at all. Look, numpty: if you enable any optimisation at all, the compiler will optimise your code. One of the things it will do is dead code analysis, and a loop that does nothing is prime candidate for removal. Even the most useless compiler will manage to work that one out.

      Holy fucking crap, it really worries me to see people like you who don't even have the must basic understanding of their tools.

  71. Re:WTF??? by arodland · · Score: 1

    Well in fact it is an emulator, regardless of the silly name. It's just not emulating a machine, which is what people tend to think of emulators doing.

  72. Re:WTF??? by Fordiman · · Score: 1

    You have a bit of a skewed view there.

    An emulator pretends to perform all the actions given to it, within a virtualized environment, whether it's a machine or an API. A compatibility layer provides real services between a piece of software and the underlying subsystem. The primary differences are speed (emulation is slower) and stability (a maliciously or badly written program, run in a compatibility layer, can do as much damage as a native one. Fortunately, Linux users are less likely to run programs as administrator/root), and compatibility (hardware emulation can achieve 100%, as it's not chasing a moving target).

    You may not care about the fundamental difference, but I assure you that your employer (assuming you have a job) would, given the appropriate information and choice.

    --
    110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
  73. Re:WTF??? by arodland · · Score: 1

    No, in the genral case an emulator pretends to be (or more accurately, "imitates the behavior of") something else. It doesn't pretend to do anything, it actually does something. A foo-emulator is a standin for foo that isn't actually foo, but which is (ideally) indistinguishable from the outside.

    Your "fundamental difference" is fundamentally founded in nothing. Emulation isn't necessarily slower -- it just usually is, because that's the way the universe works. And your point about security is just due to the design of "emulators" that you're familiar with -- i.e. hardware emulators, the most common "emulators", which are in fact entire virtual machines.

    WINE doesn't emulate a machine; it emulates a set of libraries. It isn't Win32 but it does its best to function just like Win32 (so that the apps can't tell the difference). It is, as such, a "Win32 Emulator" in the general sense of the word.

  74. BSoDs by drolli · · Score: 1

    Why do BSoD's indicate that it is not ready? Bill Gates has shown BSoD when presenting an new OS, or is this an urban legend? It seem that they are somewhere around Windows 2000 right know.... I remember BSoD during installing W2K, so a fully compatilbe OS should show BSoDs during installing. Other companies sell proiducts in such a state....

  75. I second that... by Anonymous Coward · · Score: 1

    > I can honestly say I've never had any issues installing Windows...

    Well, I can honestly say I haven't any issues in the last 8 years installing Windows... and I even installed it once during this time, for a 2 week-long use!

    I foresee Windows will continue to give me no problems in the coming years -- except maybe my curious daughter asking me to install it on one machine to play some idiotic game. But she's having a lot of entertainment with Linux, why spoil her fun? :-P

    OTOH, at work I have a marvellous 12-year old PC with Windows 98. Reboots by the minute. No, it's not funny. If installing Windows is easy, let me make this point clear, and it's not an opinion -- it's a fact I've learned the hard way: Windows is not easy to use, despite what marketeers parrot everyday.

    Linux is a lot more easier. And it's free and free. So, to all who say "you get what you pay for", I reply: "the fool and his money are soon parted".

    1. Re:I second that... by empaler · · Score: 1

      My father actually asked me to help out with his friend's PC yesterday but failed to disclose how old it was - I'd bought a Kubuntu DVD, only to find that it held more data than her hard drive could. She was sitting on a ca. 10 year old Win98 box with 2 gigs of HDD. I ended up cleaning the installation a bit instead. She didn't even have a DVD drive. (I'm making her a Xubuntu CD instead now)

    2. Re:I second that... by Yoozer · · Score: 1

      OTOH, at work I have a marvellous 12-year old PC with Windows 98
      What pointy-haired boss forces you to work with this abomination?

      Windows is not easy to use, despite what marketeers parrot everyday.
      Recently I was pondering on why Linux wasn't that obvious for me in a few cases, and I think I found out why; one's brain gets "wired" in a particular way after working for a longer time with either OS, and if it's miswired for what's in front of you things will be difficult.

      I use the word "wired", but I think in the case of Windows most people here on /. would prefer the term "bent", or "warped".
    3. Re:I second that... by mdwh2 · · Score: 1

      OTOH, at work I have a marvellous 12-year old PC with Windows 98. Reboots by the minute. No, it's not funny. If installing Windows is easy, let me make this point clear, and it's not an opinion -- it's a fact I've learned the hard way: Windows is not easy to use, despite what marketeers parrot everyday.

      A 12 year old PC running Windows 98 is relevant to the 21st Century how? In that case, let's completely ignore Mac OS X and start going on about how awful the joke of an OS that classic Mac OS was ... and I dare not ask what easy-to-use state Linux was in in 1998.

  76. Re:WTF??? by master_p · · Score: 1

    We need a well-financed company to get into the desktop operating system game and stay there for a solid decade

    If IBM, one of the biggest companies out there, does not dare enter the competition on a product that itself created, then nobody can...

    Of course there is another way out: a small group of well-financed programmers that use a more advanced programming language than C could produce a decent O/S not in a decade, but in a year.

  77. POSIX Subsystem by Nurgled · · Score: 1

    I think it'd be interesting to create a full POSIX subsystem on top of the ReactOS kernel. Microsoft has already proven that this sort of thing is possible in their architecture with Interix. You could then get the best of both worlds by running a GNU userspace (GNU/ReactOS?) on top of it. Presently the only real options are Windows+SFU (which works okay, but is not a complete solution) or Linux+Wine.

    There are some good design decisions in the NT kernel. Lots of the crap MS has piled on top of it is sub-par, but the core kernel design is on the whole very clean and malleable.

  78. Error in slides from Ionescu's talk by octogen · · Score: 1

    Ionescu's talk, page 8:
    "A secure and reliable OS, written for C2 security level certification, and updated to B1 for Vista."

    I am almost sure that this is wrong, because Windows Vista only implements mandatory integrity control (a derivate of the so-called "BiBa" model), but does not implement mandatory access control / information labeling as required by TCSEC B1, therefore not being eligible for B1 evaluation/certification.

    1. Re:Error in slides from Ionescu's talk by Alex_Ionescu · · Score: 1

      Thanks, originally Vista was going to have full MAC, not just Biba. I guess I never noticed that it changed for RTM. I will update the slides (at least my copy). Thanks!

  79. Re:WTF??? by TractorBarry · · Score: 1

    I couldn't agree more.

    I want a computer for running Audio programs (sequencer, VST software synths, WAV editor etc.) that is good enough for pro use. I don't want anything else at all running on that machine beyond basic network functionality (so I can upload/download files to a server for backup etc.) That means no internet connectivity, no "anti crapware", no unrequired services, and especially no DRM crap. I want every CPU cycle possible to be available for Audio work. In fact given the current rate of development of flash drives sod the network connectivity - I'll do my transfers vis USB drives.

    Currently the best tools I have available (Logic Audio 5.5.1, Sound Forge 7.0, Native Instruments Battery, Native Instruments Massive etc. etc.) all work on my Windows 2000 installation. A version of ReactOS that could run these tools will be enough for me to ditch Windows altogether.

    The rest of my computing I can do happily on Linux but the Audio/MIDI tools currently available aren't a patch on the Windows ones (yes I have tried them thankyou, I am aware of dyne::bolic, agnula, Ubuntu Studio, Rosegarden, MUSE, etc. and NO they are not yet as good as the Windows tools)

    So roll on ReactOS 1.0 !

    --
    Sky subscribers are morons. They pay to be advertised at !
  80. Re:WTF??? by Khyber · · Score: 1

    Read your own quote. RUN WINDOWS *PROGRAMS* WITHOUT RUNNING WINDOWS. Pls return to high school for English comprehension studies.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  81. Doctor, Doctor! by Anonymous Coward · · Score: 0

    Here comes the Waaaahmbulance!

    I'd could be snarky and make references to your idiocy, but let's keep this mildly friendly, shall we? There is precisely 1 pixel of border "shading" difference between a Windows button and what you show in ReactOS. 1 pixel. That's it. Dry your tears and realize Windows buttons have looked almost identical for a decade.

    And, please, don't even try to pretend the default Windows XP buttons are made of cotton candy and polka-dotted unicorns. They are ugly as sin and my first post-installation act was to disable that 'theme' from Playskool.

    Before you pretend Vista's Aero is worth the resources it consumes, wait until Beryl works on ReactOS, my friend.

  82. my interest in it its by the lightweightness by Z80a · · Score: 1

    lets just say i'm REALLY windows dependant,and this reactOS sounds like something much more lightweight than the real windows,and if this get secure,100% compatible with my apps and still be smaller than XP,i'm moving to it

  83. Interesting OS by Anonymous Coward · · Score: 0

    For people who are asking why make an open-source implementation of Windows, I could ask you this: why make an open-source implementation of Unix? Why make an open-source implementation of anything?

  84. Re:WTF??? by exp(pi*sqrt(163)) · · Score: 1

    I could just reply that you are a moron, which would be deserved given the ignorance you display in your obnoxious reply, but instead I'm going to be polite and point out that VMWare provides no facilities to run Windows programs that aren't already available on a PC without VMWare.

    --
    Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
  85. Re:WTF??? by Fordiman · · Score: 1

    An emulator pretends to do something, in the sense that what its doing doesn't actually occur at a hardware level, merely at a logical one. If you change screen resolution, for example, the window size changes rather than your screen. If you move your mouse, the movement is translated into the logical movement. It may have passthroughs to hardware, but the action is abstracted down to the emulated hardware, then passed onto the real stuff.

    The short of it is that an emulator is something that pretends to be hardware.

    A compatibility layer works rather directly on the hardware, or at least through the host system's HAL, with as little as possible going on in between the application and the low-level interface.

    Of course, you add to the confusion by adding Virtual Machines, which aren't emulators either; They're actually even more direct than a compatibility layer; the rather directly provide managed low-level machine services to a separate operating system, and aim to get as close to the real hardware as possible.

    I think the confusion here comes from the fact that you're using the canonical definition of 'emulator', rather than the jargon term that would be appropriate for this discussion.

    --
    110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
  86. Re:WTF??? by arodland · · Score: 1

    It's not my fault that I'm speaking English. And everything you've just said is still horribly confused and wrong. You're discussing one kind of emulator, and one (incredibly limited-scope) kind of virtual machine, and pretending that the words don't mean all of the other things that you're utterly ignorant of. But go ahead, reply, and show the world a little more of what you don't know.

  87. WHQL by tepples · · Score: 1

    With third party drivers in the picture, it has better hardware support, but it has a lot of instability issues. Which I'm guessing is why the WHQL warnings are scarier and scarier in each new version of Windows and Windows Vista 64-bit will not load unsigned drivers at all, to encourage users to place the blame on driver authors (where it generally belongs), not on Microsoft's own code.
  88. Re:WTF??? by phrasebook · · Score: 1

    Windows with snapshots is still Windows.

    Oh Stewie...

  89. Re:WTF??? by Fordiman · · Score: 1

    Wow, but you're a dick. I'm pointing out the differences in what projects that claim to be one, the other, or the new third are. It's not my fault if you can't comprehend a difference in scope.

    --
    110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
  90. Better Idea: by crhylove · · Score: 1

    FOSS Windows clone that runs 95% of windows software and LOOKS like mac os x, while having all the advantages of Linux and the FOSS world (beryl, firefox, etc. built in?). Which one day may be possible with ReactOS as the core. I mean, other than the nice Aqua GUI is there something THAT great about OS X that is not already implemented in Linux or somewhere else? Personally I think beryl+3dworld completely trumps most other GUIS anyway....

    rhY

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.