Slashdot Mirror


Running Windows With No Services

mattOzan writes "So how many of the almost 4 dozen default-enabled services does Windows XP really need in order to preserve basic functioning, like web surfing and running applications? Zero, as it turns out. Mark Russinovich at Sysinternals demonstrates that if certain steps are followed, Windows XP will still run with only two active processes: System and Csrss.exe. No Smss.exe, Winlogon.exe, Services.exe, Lsass.exe... And, contrary to the expectations of various lead engineers at Microsoft, even Internet Explorer will still work under such conditions."

4 of 619 comments (clear)

  1. Re:No Services on Boot? by Saeed+al-Sahaf · · Score: 5, Insightful
    Well Windows "shutsdown" on its own accord often enough

    Really? Does it? Isn't this just an old joke with not much fact to back it up anymore?

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  2. Re:No Thanks by ryanov · · Score: 5, Insightful

    That may be, but that means if you don't need ANY in order to run windows in this imperfect state, you probably only need a couple to run it in a perfectly passable state.

  3. I think... by JonN · · Score: 5, Insightful

    the majority of people reading this will not wonder even Internet Explorer will still work under such conditions but if Firefox will still work under such conditions

    --
    do.what.promptcmds
  4. Re:Feel "teh diference" by Sycraft-fu · · Score: 5, Insightful

    Well I doubt Russonivich has anything to worry about, he's one of the people that wrote the "Windows Internals" book from the Microsoft press.

    Now that aside Windows integration is considered a GOOD thing by most normal users. That's one of the frustrating thing about Linux/UNIX form their perspective. There's a million options, and they have no idea what they need or want. What's more, if they make the wrong choice something might not work, since it depends on something else.

    That's why Windows, and OS-X ship with so much integrated. They are targeted at users that want to be told how it is. They don't want a choice of 10 window managers, they want to have one that just comes up by default.

    Now if you like the BSD way of doing thigns, that's cool, but don't assume that it applies to everyone.

    Building from source is another great example. Linux people tend to see this as the best feature of Linux, that you custom compile things, and you don't have to worry about binary compatiblity. Newbies tend to see this is one of the worst features. Compiling is highly intimidating, as they don't understand what's going on. What''s worse, if something happens, they can't fix it, they don't know how to edit make files, or update headers, etc.

    The Windows method is more targeted at the masses, have an enriched OS that isn't just defined as it's kernel, but it's APIs, GUI, media layer, and basic apps. Linux is a minimal approach that defines only the kernel, leaving everything else up to the option of the user.

    Both are valid, and don't assume yours is the superior way.