Slashdot Mirror


Microsoft Kills Support For XP SP2

Trailrunner7 writes "Microsoft's announcement this week that it is preparing to end support for machines running Windows XP SP2 not only represents a challenge for the thousands of businesses still running SP2, but also is the end of an era for both Microsoft and its customers. It wasn't until 2004 that the final release of XP SP2 hit the streets, but when it did, it represented a huge step forward in security for Windows users. It wasn't necessarily the feature set that mattered as much as the fact that the protections were enabled by default and taken out of the users' hands."

315 comments

  1. So what? by SanityInAnarchy · · Score: 5, Insightful

    What's wrong with SP3?

    --
    Don't thank God, thank a doctor!
    1. Re:So what? by Andorin · · Score: 4, Informative

      Way back when I had XP SP2, installing SP3 borked my machine. Had to do a System Restore.

      Just sayin'.

      --
      That Anonymous Coward guy is pretty annoying. Can we have the government censor him or something?
    2. Re:So what? by Anonymous Coward · · Score: 1, Informative

      It has WGA in it.

    3. Re:So what? by Anonymous Coward · · Score: 0

      really, you can download it for free and on even "old" machines it takes what 20 min?

    4. Re:So what? by Anonymous Coward · · Score: 5, Insightful

      Nothing wrong with SP3. Just another "security columnist" trying to make headlines by exaggerating a minor event. Title of his article? "End of Support for XP SP2 is End of an Era", give me a break.

    5. Re:So what? by Anonymous Coward · · Score: 2, Insightful

      It has WGA in it.

      But the "A" stands for "advantage", dude!

    6. Re:So what? by Monkeedude1212 · · Score: 1

      More like, why would you need support for SP2?

      In any case, I'm sure most Microsoft employees will tell you "Did you do the Windows Updates? Do you have all of them installed? No? Bye"

    7. Re:So what? by Mashiki · · Score: 4, Interesting

      MS never released it for XP64, this kinda leaves XP64 w/sp2 users going wtf.

      --
      Om, nomnomnom...
    8. Re:So what? by Anonymous Coward · · Score: 5, Funny

      Way back when I had XP SP1, installing SP2 borked *my* machine. Had to do a full reinstall.

      Just sayin'.

    9. Re:So what? by spidercoz · · Score: 3, Funny

      all 3 of them

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    10. Re:So what? by BitZtream · · Score: 5, Funny

      Anyone using XP 64bit has pretty much been doing that since the day they installed the OS anyway.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    11. Re:So what? by confused+one · · Score: 1

      Its death has also been foretold. Three years hence... tick. tick. tick.

    12. Re:So what? by Ephemeriis · · Score: 2, Insightful

      What's wrong with SP3?

      At my previous job they were still using a piece of software that did not like SP3 - only ran happily on SP2 and older systems.

      This wasn't a problem at the time because Microsoft still supported SP2 installs.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    13. Re:So what? by RobertLTux · · Score: 1

      ya know that bit is "fixable"

      --
      Any person using FTFY or editing my postings agrees to a US$50.00 charge
    14. Re:So what? by Ephemeriis · · Score: 1

      Anyone using XP 64bit has pretty much been doing that since the day they installed the OS anyway.

      Indeed.

      XP64 was always a mess. The only reason I liked Vista at all was the mainstream support for 64-bit systems.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    15. Re:So what? by strayant · · Score: 1

      Yessir.... that's in the part of their script that starts off: "Is it plugged in? Well plug it in first..."

    16. Re:So what? by Anonymous Coward · · Score: 0

      No, XP64 SP2 remains supported per the MS policy. This change only affects 32-bit SP2.
      http://support.microsoft.com/default.aspx?scid=fh;[ln];lifesupsps

    17. Re:So what? by Anonymous Coward · · Score: 0

      I had the same problem going from XP SP1 to SP2.

      Later, I tried installing SP3 clean to the same machine. It blue screened every time during the progress bar part of the install sequence.

    18. Re:So what? by Backward+Z · · Score: 2, Insightful

      I had the same problem going from XP SP1 to SP2.

      Later, I tried installing SP3 clean to the same machine. It blue screened every time during the progress bar part of the install sequence.

    19. Re:So what? by yeshuawatso · · Score: 0

      Yeah but the advantage of Vista for x64 users was XPx64 users got 64-bit drivers without the annoyance of Vista. Since the kernels were the same, you could use Vista drivers on your system. But honestly, if you were using x64 it was for RAM purposes and your machine most likely had support directly from the manufacture. What sucks is a few of those manufactures stop supporting drivers for their systems beyond XP x64 (I'm looking at you SUN MICROSYSTEMS!)

    20. Re:So what? by Anonymous Coward · · Score: 0

      Not exactly from TFA, but Microsoft's documentation on end of support and its ramifications:

      "There's no SP3 for the 64-bit version of Windows XP. If you're running the 64-bit version of Windows XP with SP2, you have the latest service pack and will continue to be eligible for support and receive updates until April 8, 2014."

    21. Re:So what? by WaroDaBeast · · Score: 1

      It is recommended that you slipstream the service pack(s) along with the OS onto a blank disc using software such as nLite instead of installing the OS and the service pack(s) separately.

      My €0.02.

      --
      "The body may heal, but the mind is not always so resilient." -- Deus Ex: Human Revolution
    22. Re:So what? by yotto · · Score: 1

      My job has a couple OS/2 machines, because a piece of software we rely on only runs on OS/2. We don't expect IBM (Or that program's creator, who has since moved on to operating systems made in the past decade) to support it. We support it ourselves.

      Move on with technology or be ready to work on it yourself.

    23. Re:So what? by ls671 · · Score: 1

      Same when trying to go from SP2 to SP3, the machine wouldn't boot after installation, I had to use System restore. Oh well, my machine configuration has changed since so I guess I have a couple months yet to give it another try.

      Machine is HP Pavillion a1450n - AMD Athlon 64X2 Dual Core 4200+ running in 32 bit mode. Anybody else experienced the same with this specific setup ?

      --
      Everything I write is lies, read between the lines.
    24. Re:So what? by TheLink · · Score: 1

      I'd go "WTF" at people who install XP64 for nonexperimental use.

      Hard for me to say which is worse: XP64 or vista. Like choosing which way to be tortured slowly to death.

      FWIW, I use Windows 7 64 bit at work (boss's bright idea), and I still prefer Windows XP SP3.
      Windows 7 had this annoying problem: "Windows Explorer may stop responding for 30 seconds when a file or a directory is created or renamed after certain applications are installed."
      It sure was longer than 30 seconds for me. I hope it's really fixed now: http://support.microsoft.com/kb/980408
      There are lots of other annoyances: it still takes a while to display certain folders, you can probably press Esc or something. You can't quickly close windows by right clicking on the task button and pressing C. And I currently can't think of any way it helps me do things faster or be more productive. The only thing that might be useful is the per app volume control, however this is a work machine so I normally just mute the sound or have everything at a low sound level.

      --
    25. Re:So what? by westlake · · Score: 4, Insightful

      Way back when I had XP SP2, installing SP3 borked my machine. Had to do a System Restore.

      The plural of anecdote is not data. How many upgrades to SP3 were successful on the first attempt?

    26. Re:So what? by BigDeek · · Score: 0

      mY dOOD. iM ALL tOtALLY DoWn wItH SP3. Rock on man.

    27. Re:So what? by Mr.+DOS · · Score: 1

      There was an issue with AMD processors right after release. AFAIK, they fixed it within a couple weeks of release. Still, do all other available updates before trying it, and you might want to try the offline installer - I've had better luck with that than the Windows Update site.

    28. Re:So what? by pilgrim23 · · Score: 0

      You take a typically crap MS opsys. loose it on a unsuspecting world. 6 months later you issue a patch, you then patch the patch. 7 years later it is a mass of duct tape, band aids and spot welds. but MAN it is robust! Windows 7: rinse and repeat 'tiss the Redmond Way.....

      --
      - Minutus cantorum, minutus balorum, minutus carborata descendum pantorum.
    29. Re:So what? by iamhassi · · Score: 1

      "Title of his article? "End of Support for XP SP2 is End of an Era", give me a break."

      It is the End of an Era. XP was the first Microsoft OS that didn't suck. If XP wasn't released and Apple became the dominate player they have become, there's a good chance 50% of PCs would be Macs and Linux would be fair more popular than it is today.

      I remember the daily struggle with 95/95b. OS was such crap I did nightly backups to a $250 1.6/3.2gb TR3 tape drive and could restore 95 and all data in a few hours. It was like a old car that's always breaking down when you need to be somewhere. 98 wasn't much better, and we all know the jokes about ME. 2000 was amazing, but couldn't run games. In 2001 XP finally brought everything together, 2000's stability and 98's gaming, and we could finally stop buying a new OS every 2-3 yrs because XP worked! Then, 6 yrs after XP was released, M$ gives us the flaming hunk of poop called Vista. It was such poo that M$ returned to it's old development schedule and replaced Vista in 2 years with 7.

      So anyone who felt the daily pains of working with 95/98/ME thank God everyday for XP and it really is the End of an Era. I will use XP until new programs don't work on it anymore.

      --
      my karma will be here long after I'm gone
    30. Re:So what? by sakdoctor · · Score: 5, Funny

      Way back when I had 2k, installing XP borked my machine. So I switched to Linux.

      Just sayin'.

    31. Re:So what? by Ralish · · Score: 2, Informative

      That's because XP x64 isn't actually XP (NT 5.1), it's Windows Server 2003 (NT 5.2). That is, it's really only XP in name as it is built off the Windows Server 2003 codebase. It has all the server functionality of its counterparts removed as well as some minor functionality present in XP but absent from the server releases included. Consequently, they share the same service packs and updates, with the latest service pack for Windows Server 2003 being SP2. Unless of course, you meant the original "XP" Itanium release, which really is built off of XP, but support for that was discontinued a long time ago.

    32. Re:So what? by Mister+Whirly · · Score: 2, Insightful

      And this is different from any other operating systems how exactly?

      --
      "But this one goes to 11!"
    33. Re:So what? by mollog · · Score: 2, Insightful

      Microsoft has no incentive to support older operating systems, especially the really good versions of older operating systems. Indeed, they have every reason to be careless about 'updates' to those older operating system and ignore problems caused by those 'updates' because their policy is to recommend their newest product. Obviously, the policy of recommending customers buy their newest product to fix problems with their previous product is a profitable policy.

      The reason that this article is newsworthy is because so many corporate customers balked at the Vista upgrade cycle. XP was known to work better with fewer resource requirements. Many of the PC's built that were claimed to be 'Vista Ready' (TM) were dogs with Vista but were perfectly usable with XP. Imagine, an 'upgrade' to a line of operating systems that performs worse than its predecessor. So, corporate customers demanded, en masse, that Microsoft continue to offer XP as an alternative to Vista.

      For the first time in my memory Microsoft blinked, and extended its support of the XP revision despite the obvious disadvantage to its profits. Its customers had learned to put their foot down and refuse Microsoft's self-serving upgrade recommendations.

      To my mind, XP is the most stable release of an operating system since MS-DOS 5. Everybody hailed it as uncharacteristically stable and usable.

      --
      Best regards.
    34. Re:So what? by elashish14 · · Score: 0, Offtopic

      Way back when I had Win98, installing WinME borked **my** machine. Had to do a full reinstall - and buy a toupee.

      Just sayin'

      --
      I have left slashdot and am now on Soylent News. FUCK YOU DICE.
    35. Re:So what? by dwiget001 · · Score: 1

      "2000 was amazing, but couldn't run games"

      Uh, I had a Win 2000 Pro system that I used for gaming back in the day, no problems, solid as a rock.

      It (Win 2000) was a better OS than XP ever was as far as stability in my direct personal experience with both OSes.

    36. Re:So what? by sa1lnr · · Score: 1

      Ok, who are the other two?

    37. Re:So what? by Bobfrankly1 · · Score: 1

      2000 was amazing, but couldn't run games.

      It *could* run games, but every time you went to update something, you ran the risk of the update hosing the whole system. Fun times!

    38. Re:So what? by Anonymous Coward · · Score: 0

      Uhmm, no offense, but 2k could run games just fine after they got around to the DirectX update (which I think was probably '01). How do I know this? Because I'd been using it for the last 5-7 years on a series of computers ranging from 2nd gen Pentium 4 up to a 2nd gen C2D :)

      Honestly as long as you avoid games for windows, and did some hunting for the right windows updates you can run 9/10s of 'XP only' software on 2k, and the best part is: If you've got a dual core instead of hyperthreading, there was no need for XP, because hyperthreaded cpu support was the only major thing it added :D

    39. Re:So what? by antdude · · Score: 0, Offtopic

      Way back when I had 9x (including Me), installing 2000 borked my machine. Had to do a clean install.

      Just sayin'.

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    40. Re:So what? by Anonymous Coward · · Score: 0

      OK, but at our corporation we deployed SP3 to 80,000 machines and nary a handful were "borked". Just sayin'

    41. Re:So what? by ThePlague · · Score: 0

      I concur, I used 2k back in the day as well. It could run anything XP could run, and usually faster and more stable. I still prefer it, really, since it's so lightweight and stable, but you haven't been able to update it (DirectX etc) in years, so it really can't be used as a cutting edge gaming platform anymore.

    42. Re:So what? by operagost · · Score: 1

      XP was the first Microsoft OS that didn't suck.

      I finally retired my last Windows 2000 server this year. 8 years of service; it pretty much only crashed when the power supplies failed.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    43. Re:So what? by zmollusc · · Score: 1

      Way back when I had Windows for Workgroups, installing Win 95 borked my machine. Had to replace everything except the monitor, mouse and keyboard.

      --
      They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
    44. Re:So what? by Movi · · Score: 1

      Waaaay back when i had an amiga, installing Win98 on my PC borked **both** machines. Had to sell the amiga, and do a clean install on the PC.

      Just sayin'

    45. Re:So what? by thoughtsatthemoment · · Score: 1

      For those who wants to stay with XP, one major reason for 64 bit is if you have a real need for a lot memory, like running a few VMs. Otherwise I agree that using 32 bit would avoid quite a few problems.

    46. Re:So what? by Hijacked+Public · · Score: 3, Insightful

      I'd do that, but my XP disc is stamped "DO NOT MAKE ILLEGAL COPIES OF THIS DISC" and I haven't yet finished reading USC Title 17 to determine whether your recommendation would be illegal.

      --
      "Sacrifice for the good of The State" - The State
    47. Re:So what? by prograde · · Score: 2, Informative

      That only counts as one bad experience. It sucks, to be sure, but it's anecdotal. I've done dozens of SP2 --> SP3 transitions, and zero machines got borked.

    48. Re:So what? by zmollusc · · Score: 1

      I ran quake 4 and doom 3 , half-life and battlefields 2 and 2142 and various command and conquer versions on win2000, you insensitive clod! Granted, I had to wrestle a couple of them on because the installers were written by retards, but still. Win2000 is still the one true operating system!

      --
      They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
    49. Re:So what? by calzakk · · Score: 1

      Way back when I had DOS, installing Windows borked my machine. I should have given up then.

      Just saying'.

    50. Re:So what? by enjerth · · Score: 4, Funny

      Everyone said I was daft to install Windows 3.1 (before WFW 3.11) on a 286, but I installed it anyways.

      At first, it borked my machine. So I did a reinstall which burned down and then borked my machine. The third install burned down, fell over and then borked my machine... but the fourth one stayed up!

      And that's what you'll get, lad.

    51. Re:So what? by MonsterTrimble · · Score: 1

      Actually, every game I ever tried worked on 2000, even the ones which said specifically for XP. In fact, I would never have upgraded to XP except 2000 wouldn't install on my Sempron rig when I put it together in 2006.

      Then that fall I switched to Linux. And now I use Lubuntu, which looks a lot like 2000 did...

      --
      I call it 'The Aristocrats'
    52. Re:So what? by Beorytis · · Score: 1

      MS never released it for XP64, this kinda leaves XP64 w/sp2 users going wtf.

      If you follow the links through to the official MS page, you'll see that XP64 SP2 support continues to 2014.

    53. Re:So what? by Mister+Whirly · · Score: 2, Insightful

      And so you think it is up to Microsoft to continue support for SP2 because you use some third-party software they have nothing to do with?? I think your beef should be with the software company not making their software work with the current patch to the operating system, and not vice-versa.

      --
      "But this one goes to 11!"
    54. Re:So what? by marky_boi · · Score: 1

      in that case, Ispose the XPSP1 machine I did an direct SP3 upgrade to and now won't update doesn't exist. Only valid way i have been able to do it is via SP2. ***sigh*** better fix it this weekend... I use Linux 100% of the time but XP keeps the wife happy playing SIMS....

    55. Re:So what? by BlackSnake112 · · Score: 1

      I thought the fourth one just disappeared and the fifth one stayed up?

    56. Re:So what? by Anonymous Coward · · Score: 0

      vmware + a stripped down winxp for each program you need. Works really well with network shares for storage.

    57. Re:So what? by MobileTatsu-NJG · · Score: 1

      Way back when I had 2k, installing Linux borked all my games. So I switched to Windows XP.

      Just sayin'.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    58. Re:So what? by Bengie · · Score: 1

      XP64 is considered as 2k3 as it derives from 2k3 while XP32 is derived from 2k

    59. Re:So what? by Zephiris · · Score: 1

      People always say that, but never explain "how it's a mess".
      This currently being written from XP x64, I've never seen what all of the fuss is about.

      The only thing (generically speaking) that it seems to lack vs. Vista as far as an Actual Problem, is direct support for various AHCI drivers, so assuming you CAN install it (not that hard to figure out), it's hard to see how it could be considered 'a mess' otherwise, given that everything works, everything's compatible aside from a few (rare) outliers.

      --

      "A Goddess rarely smiles for she is forced by others to be an island unto herself." - Zephiris
    60. Re:So what? by drsmithy · · Score: 1

      Everybody hailed it as uncharacteristically stable and usable.

      Er, no. They treated pretty much the same way they did Vista.

    61. Re:So what? by DarkKnightRadick · · Score: 1

      I actually have this problem on a Compaq Presario I bought used. I cannot install SP3 because it sends me into a BSOD at boot time, which causes the machine to reboot which brings me back to the BSOD during boot which causes me to reboot...you get the idea.

      Did a system restore back to spec and updated to SP2. Not touching SP3 with a ten foot pole.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    62. Re:So what? by nschubach · · Score: 1

      You laugh, but the three people still driving around in Ford Pintos/Chevrolet Chevettes can still fix and maintain their own cars.

      We all love comparing everything to cars.

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    63. Re:So what? by DarkKnightRadick · · Score: 0

      AMD Sempron 3000+ 1.81GHz

      I tried the update only several months ago. I guess they didn't fix the problems (though I have updated the "drivers" for the CPU).

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    64. Re:So what? by Shakrai · · Score: 3, Informative

      I'd do that, but my XP disc is stamped "DO NOT MAKE ILLEGAL COPIES OF THIS DISC" and I haven't yet finished reading USC Title 17 to determine whether your recommendation would be illegal.

      I know you are going for sarcasm, but Microsoft actually tells you how to do this. Also, it says "illegal copies", Microsoft has never much cared if you make copies for your own personal use. Hell, they don't even distribute media by default for their bulk licensed products. You have to download them or pay extra for the media.

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    65. Re:So what? by Anonymous Coward · · Score: 0

      Assuming that company is still around, wasn't aquired, still offers a similar product, etc.

      There's all kinds of weird niches out there, you're not going to throw out a perfectly good CNC lathe whose interface software only runs in Windows 3.1. The mechanical bits of the lathe might last another 10 years, oh god kill me now...

    66. Re:So what? by kiehlster · · Score: 1

      Way back when I had IBMDOS, installing MSDOS borked my machine. I had to switch back to my other floppy disks.

    67. Re:So what? by mister_playboy · · Score: 1

      Perhaps try the a install of XP with SP3 already integrated into the ISO?

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    68. Re:So what? by Mister+Whirly · · Score: 1

      Your mistake was buying a used Compaq Presario. I wouldn't touch one of THOSE with a ten foot pole. I re-installed Windows for a customer a few years back on one of these and he was bringing it to me to fix one thing or another at least twice a month for a few months. Until basically I had to tell him that the "free" customer service I offer on my work was not unlimited, and that his system was causing most of the problems. I ended up buying a new Dell for him and have not heard from him since.

      Anecdotal for sure, but was just answering one anecdote with another.

      --
      "But this one goes to 11!"
    69. Re:So what? by mister_playboy · · Score: 1

      Yeah but the advantage of Vista for x64 users was XPx64 users got 64-bit drivers without the annoyance of Vista. Since the kernels were the same, you could use Vista drivers on your system.

      XP64 shares kernels with Server 2003, not Vista. You can't use Vista drivers.

      Driver support for XP64 is a joke.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    70. Re:So what? by Mister+Whirly · · Score: 1

      My point was none of any of those problems relate to Microsoft. If you want to use old equipment and old software, more power to you. Believe me I understand the reasons why someone would want to do so. But don't complain that your out of support software isn't being supported anymore. You are doing so at your own risk and own support. In the specific example the software did run on XP SP2, so I don't think it would be a huge stretch to assume it wouldn't take an enormous amount of work to get it running on the same OS with some patches. Oh and if you are running old unsupported OS on machines for whatever reasons, for Christ sake DON'T hook them up to the internet. As long as they are only attached to whatever equipment they need to be attached to, you are probably ok.

      --
      "But this one goes to 11!"
    71. Re:So what? by pjfontillas · · Score: 5, Funny

      Way back when I had a typewriter, installing IBMDOS borked my machine. I couldn't figure out how to use the floppy disk. I put it in just like paper, right? The disk just jammed and I had to trash everything. I should have given up then.

      --
      Life. Is. Good.
    72. Re:So what? by oldhack · · Score: 1

      Don't leave us hanging. How did the 5th one go?

      --
      Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
    73. Re:So what? by Orbijx · · Score: 1

      Microsoft themselves give you the mechanism to slipstream service packs into your media. nLite and other applications just make the process easier for a first timer (so instead of manually expanding, copying, and creating the ISO, it's done for you), or a busy admin.

      Granted, I can imagine them saying "Here's the tool to make your administration jobs easier. However, if you use it, we're going to send you to Pound You In the Ass Prison", but I don't particularly think that's likely, since it's an option administrators have had since Windows 2000.

      My Win2000 and XP discs were stamped this way, but the mechanism for editing and modifying discs have been made available to anyone willing and patient enough to go through the steps by Microsoft themselves. You can create a disc for the purpose of legally installing the operating system and its patches.

      (On a personal note, I honestly think they'd want you to do it, too, so that it might lower the chance of another machine with their OS freshly installed on it becoming a 14 second zombie.)

      --
      One of these days, I am going to flip out. When I flip out, I'll be back in five minutes.
    74. Re:So what? by SpryGuy · · Score: 1

      You obviously haven't used Windows 7. It's remarkably more stable and usable than any flavor or SP of XP, even prior to SP1.

      There's really no good excuse for staying on XP any more. Really, for 99% of use-cases, there isn't.

      --

      - Spryguy
      There are three kinds of people in this world: those that can count and those that can't
    75. Re:So what? by Richard+Steiner · · Score: 1

      Well, for one we have the SOURCE for the mainframe operating system we run. And no, it isn't open source.

      --
      Mainframe/UNIX Bit Twiddler and long time Windows/Linux Hobbyist.
      The Theorem Theorem: If If, Then Then.
    76. Re:So what? by The+Grim+Reefer2 · · Score: 1

      To my mind, XP is the most stable release of an operating system since MS-DOS 5. Everybody hailed it as uncharacteristically stable and usable.

      Strange, that's not how I remember it. As I recall everyone hailed Windows 2K as uncharacteristically stable for a MS product. Compared to BSD, AIX, Solaris, etc. XP was seen as a bloated disaster until SP1. In all honesty I finally upgraded my Windows machines from 2K to XP around a year and a half ago.

    77. Re:So what? by Anonymous Coward · · Score: 0

      I'd wonder what stopcode you're getting at that point, because I've done plenty of SP2 to SP3 upgrades, as well as pure installs of SP3, and only ran into stupid issues like 0x7B, because I didn't have the AHCI drivers onhand.

      I really just want to say that it's you, doing it wrong, if anything.

    78. Re:So what? by ImprovOmega · · Score: 3, Informative

      XP64 SP2 is the same as Windows Server 2003 SP2. When there's an SP3 for Server 2003 there'll be an SP3 for XP-64. Further, any updates for Server 2003 SP2 x64 edition will patch directly into XP-64, so in actuality you'll probably have support for that long after XP-32 is dead and buried. Microsoft's support for Server OS's far outlasts their support for consumer OS's (generally).

    79. Re:So what? by orient · · Score: 1

      Installing SP3 requires validating your copy of Windows...

      --
      Laudele lor desigur m-ar mahni peste masura.
    80. Re:So what? by ImprovOmega · · Score: 1

      Which is really irrelevant if the device doesn't plug in to any network. If embedded devices really want to use DOS 4.0 as their OS of choice, then I don't really care because there's no vector in to exploit vulnerabilities.

    81. Re:So what? by Anonymous Coward · · Score: 0

      "You can't quickly close windows by right clicking on the task button and pressing C."
      Middle mouse button click on the app's preview thumbnail is faster and takes one less finger! Also drop the mouse hover time if you want those previews to come up faster (can be set to 0).

    82. Re:So what? by Anonymous Coward · · Score: 0

      yea, hell with Linux. XP is way more stable!

    83. Re:So what? by Ephemeriis · · Score: 2, Interesting

      And so you think it is up to Microsoft to continue support for SP2 because you use some third-party software they have nothing to do with??

      When did I say that?

      The original question was "What's wrong with SP3?" I indicated one example where SP3 would be a problem.

      I think your beef should be with the software company not making their software work with the current patch to the operating system, and not vice-versa.

      I never claimed to have a beef with anyone.

      I certainly don't have a beef with anyone about this particular piece of software, as I no longer work there. For all I know they may no longer use that software.

      And if I was going to have a beef with anyone, it would be with my former boss. He was too cheap to buy the new version of the software, which was why it didn't work with anything newer than SP2.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    84. Re:So what? by Anonymous Coward · · Score: 0

      If you have an illegal copy of windows why do you care what version they are supporting? I don't think a lot of software pirates call Microsoft support.

    85. Re:So what? by Anonymous Coward · · Score: 0

      I can think of plenty of reasons ("excuses").

      1) I haven't yet come across / needed software that only works on Vista/7 but not XP.

      2) Upgrading costs money.

      3) Vista / 7 dropped support for Virtual DOS Machine. Relevant if you want to play Tomb Raider, Carmageddon, Blood and other late DOS games (Dosbox is too slow for them at high resolutions).

      4) XP works.

    86. Re:So what? by Ephemeriis · · Score: 2, Interesting

      People always say that, but never explain "how it's a mess".

      XP x64 never seemed to be a real mainstream product. You never really saw Microsoft advertise it much... Nobody really advertised support for it...

      Some of the software I had to support would not run on XP x64. It would run fine on XP x86... It would run fine on 2003 x64... But it was not happy on XP x64. I don't know why that would be, since it was basically 2003 x64 repackaged... But some of the software wasn't happy with it.

      Then we had some vendors who flat-out refused to support their software on XP x64. It would run OK... But if we hit a bug and they heard we were running XP x64, they'd tell us to re-install with a supported OS.

      Drivers were another issue. I had a hell of a time tracking down drivers for some devices. Generally speaking, you had to use 2003 drivers. Which wasn't necessarily obvious since the OS said XP, not 2003. But sometimes the 2003 drivers wouldn't work either.

      The only thing (generically speaking) that it seems to lack vs. Vista as far as an Actual Problem, is direct support for various AHCI drivers

      The big benefit I personally saw with Vista wasn't some kind of technological change - it was simply the fact that Vista x64 was a mainstream product. You would see the x64 version advertised prominently along-side the x86 version. Hardware and software both would advertise support for the x64 version. Vendors stopped running away when you mentioned you were running x64.

      This currently being written from XP x64, I've never seen what all of the fuss is about.

      I guess I'm glad it's working for you.

      I personally gave up on XP x64 on my home computer when I had trouble finding working video drivers.

      That was a couple years ago... So maybe the problems I experienced no longer exist. Maybe it would be a piece of cake to run XP x64 these days. But I don't really have a reason to anymore.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    87. Re:So what? by Bassman59 · · Score: 1

      Everyone said I was daft to install Windows 3.1 (before WFW 3.11) on a 286, but I installed it anyways.

      At first, it borked my machine. So I did a reinstall which burned down and then borked my machine. The third install burned down, fell over and then borked my machine... but the fourth one stayed up!

      And that's what you'll get, lad.

      I wish mod points were in units of Great Tracts of Land!

    88. Re:So what? by Mister+Whirly · · Score: 1

      The problem wasn't SP3, the problem was whatever software you were using didn't work well with SP3.
      Actually, it sounded like the real problem was a boss who didn't understand technology. (Boy do I know that one all too well.)

      In your defense you didn't say it was Microsoft's fault, that was just something I may have wrongfully inferred. (But this is Slashdot so I just sort of expected some MS hatred.)

      --
      "But this one goes to 11!"
    89. Re:So what? by RealGrouchy · · Score: 1

      I tried a Linux live CD on my Windows 95 laptop, and it totally borked the floppy drive.

      - RG>

      --
      Hey pal, this isn't a pleasantforest, so don't waste my time with pleasantries!
    90. Re:So what? by Mister+Whirly · · Score: 2, Funny

      Wee, wee, wee all the way home.

      --
      "But this one goes to 11!"
    91. Re:So what? by Anonymous Coward · · Score: 0

      1) Office 2010, Microsoft Live Essentials wave 4, and IE9 will all run only on Vista-and-above OS's, for good reasons. XP lacks tons of modern technology (especially with respect to the graphics subsystems) that more and more software will be relying on in the very near future.

      2) Upgrading doesn't cost that much money, especially factoring in the opportunity cost of lacking any additional updates, support for new hardware and standards, etc. Never mind the additional usability improvements in Win7 which make it so much easier to use and support, the fact that it's much more stable and reliable, etc.

      3) Not a valid excuse. Dual boot is a solution for this exceptionally rare use-case.

      4) XP doesn't "work" as well as Win7 in a multitude of areas, and will continue to degrade over time relative to advancements in both software and hardware (already XP can't handle some of the newer high capacity hard drives, it's unlikely to have USB3.0 support any time soon, and the list will forever be growing). Installing Win7 "just worked". Installing XP was always a head-ache and nightmare of chasing down drivers and crap. All that pain and time spent have a "cost" to them too, you know.

      Sorry, but there's no excuse at this point other than laziness and whining.

    92. Re:So what? by GoochOwnsYou · · Score: 1

      Your machine was already borked if you had Me on it.

      --
      This sig has been distributed under the Creative Commons license.
    93. Re:So what? by Gr8Apes · · Score: 2, Interesting

      Everybody hailed it as uncharacteristically stable and usable.

      Er, no. They treated pretty much the same way they did Vista.

      IIRC, they lampooned it for its cartoonish look, and the fact that it was slower than Win98 and Win 2K, depending on where you were coming from. Win 2K was probably the "best" of the NT versions, solid and trim compared to all of its predecessors and descendants. And while XP was eventually accepted, Vista never will be, as Win 7 is now out (Vista SP2 really, renamed because "Vista" had such a bad rap)

      --
      The cesspool just got a check and balance.
    94. Re:So what? by jonadab · · Score: 1

      I think that's basically Microsoft's point. Windows XP is in extended support now, which basically means security updates for whatever issues Microsoft deems important. SP3, not to put too fine a point on it, pretty much *is* one of those updates (or incorporates a number of them, however you want to look at it). People who aren't willing to install SP3 don't appear to be very interested in taking advantage of the support that Microsoft is providing. So why would Microsoft feel obligated to continue putting special effort into supporting them, separately from everyone else?

      I'm not a big Microsoft fanatic, but this seems logical to me. SP3 has been out for a while now, plenty of time for IT departments to do whatever testing and whatnot they need to do. So at this point, hey, SP3 (and the updates that follow it) are the support that's available (for Windows XP). Take it or leave it.

      If you don't like XP SP3, you could always upgrade to Seven.

      (And, of course, if you don't like ANY of Microsoft's options, there are always also the other options; Microsoft understandably feels little compulsion to remind you of those, but you basically have to live in a cave with no internet connection to avoid hearing about them at all.)

      --
      Cut that out, or I will ship you to Norilsk in a box.
    95. Re:So what? by Anonymous Coward · · Score: 0

      Way back when I had IBMDOS, installing MSDOS borked my machine. I had to switch back to my other floppy disks.

      This? This is the best Slashdot can do? Are all of the greybeards dying?

    96. Re:So what? by treeves · · Score: 1

      What, the curtains?

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
    97. Re:So what? by HBoar · · Score: 1

      Many of the machines in our department at university (mech eng) are running XP64. Some of us need 4GB+ of RAM.

    98. Re:So what? by DarkKnightRadick · · Score: 0, Offtopic

      I don't know. As soon as the BSOD comes up, it reboots. Sometimes I don't even see the BSOD except for a blue blink.

      Doing it wrong? I was doing it via Windows Update after I had installed all the previous updates. Should I roll back again (not an option, I have the computer setup how I want it) and just install SP3? If so, why does Windows Update even bother me with all the other updates (like SP2)?

      You could say it's me doing it wrong, but you'd be wrong. I've done many SP2 to SP3 updates myself and this is the first time I've ever had this problem.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    99. Re:So what? by DarkKnightRadick · · Score: 0, Offtopic

      Don't really have that option. This computer has a pre-loaded restore point that is XP SP1 only. I'm not really wanting to mess with this setup as it provides me the only safety net I've had and with the problems I had when I bought the computer...

      The only way to do what you suggest is an install over on the C: leaving the D: as the factory created restore point.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    100. Re:So what? by DarkKnightRadick · · Score: 0

      Well I wasn't trying to present my anecdote as anything other then an anomaly.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    101. Re:So what? by ls671 · · Score: 1

      Thanks, I just successfully installed SP3 following your recommendations.

      --
      Everything I write is lies, read between the lines.
    102. Re:So what? by drsmithy · · Score: 2, Informative

      IIRC, they lampooned it for its cartoonish look, and the fact that it was slower than Win98 and Win 2K, depending on where you were coming from.

      Yes. Just like Vista.

      Win 2K was probably the "best" of the NT versions, solid and trim compared to all of its predecessors and descendants.

      Compared to NT4, Windows 2000 was "bloated" and slow - the former needing a 33Mhz 486 with 16Mb RAM and the latter a 133Mhz+ Pentium (~8x more) with 64MB RAM (4x more).

      Vista never will be, as Win 7 is now out (Vista SP2 really, renamed because "Vista" had such a bad rap)

      Windows 7 is as much "Vista SP2" as Windows XP was "Windows 2000 SP1". Certainly the changes weren't as large as Vista (probably the single biggest update to NT since its release), but definitely more than just a service pack.

    103. Re:So what? by Dumnezeu · · Score: 1

      I am one.

      --
      Yes, it's sarcasm. Deal with it!
    104. Re:So what? by HBoar · · Score: 1

      I completely agree, I've had a better experience using XP64 than 32. It boots faster, and seems to last longer before turning into a slow unstable mess. I've used it on a number of PCs. My office computer at uni (along with many others in the department) also runs XP64, and I've never had a problem with it at all. I have heard of some obscure devices not having drivers, but I've never come across any.

    105. Re:So what? by HBoar · · Score: 1

      I'd go "WTF" at people who install XP64 for nonexperimental use.

      But why? I've been using it for ~3 or 4 years and have honestly never had a better experience with a windows operating system. It has always seemed faster and less prone to crashing than the 32 bit XP. It also allows me to use a decent amount of RAM, which I need for fluids simulations. I would still use it over XP32, and Win7 any day.

    106. Re:So what? by commodore64_love · · Score: 1

      >>>Windows 7 is as much "Vista SP2" as Windows XP was "Windows 2000 SP1".

      You are correct sir. Windows 2000 == NT 5.0 while XP == 5.1 -(basically 2000 with bugfixes). Likewise Vista == 6.0 and Seven == 6.1, the bugfixed and memory-optimized version of Vista.

      Don't be duped. Remember this is the company that tried to trick people with "Windows Mohave" which was really just vista. They followed through with that plan.... "Seven" is just Vista SP2. "XP" is just 200 SP1.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    107. Re:So what? by commodore64_love · · Score: 1

      >>>There's really no good excuse for staying on XP any more

      My hardware didn't die yet.
      And I'm not going to spend $150 to buy Seven.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    108. Re:So what? by commodore64_love · · Score: 1

      It's not Microsoft I'm scared of. It's the US Government, the DMCA, and an overzealous prosecutor.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    109. Re:So what? by drsmithy · · Score: 2, Insightful

      You are correct sir. Windows 2000 == NT 5.0 while XP == 5.1 -(basically 2000 with bugfixes). Likewise Vista == 6.0 and Seven == 6.1, the bugfixed and memory-optimized version of Vista.

      A .1 release is not a Service Pack.

      Don't be duped. Remember this is the company that tried to trick people with "Windows Mohave" which was really just vista.

      Er, right. An anti-FUD experiment is "trying to trick people" ?

      Well, this is Slashdot I suppose...

    110. Re:So what? by Trogre · · Score: 1

      The fact that MS never released it for x86_64

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    111. Re:So what? by omni123 · · Score: 1

      SP2 for XP64 is essentially SP3 for XP32. They are off a different code base (XP64 is off Windows Server). I wonder how this affects support?

      I would guess that it shares product support lifetime with 2k3.

    112. Re:So what? by Anonymous Coward · · Score: 0

      Installing MS-DOS 6.22 borked my MS-DOS 5 install.

      Just sayin'.

    113. Re:So what? by ajlisows · · Score: 1

      I remember having problems during the XP SP1 to XP SP2 transition, but that is long enough ago that I don't recall how severe or frequent the problems were. As recent as last week I was trying to apply SP3 to an XP SP2 box and it simply failed. I've seen this issue quite a bit every since SP3 was released. I think it is probably worth noting that many of the computers I was trying to apply SP3 to had some pretty bad malware/virus infections so I'm guessing the problems I have experienced are more of the "This computer has holes punched in its registry and system files missing" than a "SP3 really sucks" type of issue.

    114. Re:So what? by ajlisows · · Score: 2, Insightful

      XP SP2 did seem stable, but now when I compare it to Windows 7, it was really buggy. I've been using Windows 7 since the Beta and the only time I had problems was early on with a Toshiba laptop running the 64-bit version. Toshiba eventually released a BIOS update that allegedly would solve that problem...but I had gotten rid of that laptop by that point. I did try running Vista for awhile but had all sorts of issues with it.

      Compared to others around here I am not that big of a Linux fan. Don't get me wrong, I do really like Linux but I am not as vested in it as others. Back when I was using XP (SP2 and SP3) I probably was using Linux 60% of the time and XP 40% of the time. Since I became acclimated to Windows 7, I've probably shifted to 25% Linux/75% Windows (Mind you I work at a place that is almost exclusively Microsoft so that has a big impact on what OS I want to use when.) Windows 7 is responsive, sleep mode works properly, the interface is nice, it hardly ever crashes, and it doesn't have to be rebooted all the time. Right now the Windows 7 machine I am on has an uptime of 39 days. Yes, that is pretty standard for Linux but in my experience...not for XP.

      I truly believe that Microsoft's newest offering is its most stable since the DOS days.

    115. Re:So what? by Anonymous Coward · · Score: 0

      Everyone borked when I Installed Windows 3.1 on my i7.

    116. Re:So what? by billcopc · · Score: 1

      Back when I had an Atari 800XL, installing Atari DOS 4.0 borked my machine.

      Die in hell, Jack Tramiel!

      Oh, Just sayin'.

      --
      -Billco, Fnarg.com
    117. Re:So what? by DigiShaman · · Score: 1

      XP64 suffered lack of application and device driver support. But, it was used by a few employees for one of our clients. They needed to break past the 4GB limit with CAD drawings and geo-science apps that worked with sidescan bathymetry data.

      Vista 64 was a mature 64bit platform, even if the OS itself sucked. MS should have made Windows 7 64bit *only* however. We are getting to the point were all new workstations and laptops are already being shipped with 4GB of RAM. If you want to address more than that concurrently, you have no choice but to use a 64bit platform.

      --
      Life is not for the lazy.
    118. Re:So what? by Wayne247 · · Score: 1

      SP3 causes a rotation issue with a whole lot of ATI video card drivers (for video cards 2-3 years old, at most), making it impossible to have a rotated screen on SP3.

      The very same graphic cards are unsupported in Windows 7 because ATI hates their customers.

    119. Re:So what? by TheLink · · Score: 1

      > Middle mouse button click on the app's preview thumbnail is faster and takes one less finger!

      1) The previews often get in the way if you overshoot the mouse to the taskbar, when that happens they slow me down. Also, I used to have to deal with documents that looked similar - the thumbnails then became rather useless, so in the end I turned them off - better to just distinguish them by title.
      2) My left hand is already on the keyboard ready to press "C". So hovering over a task button than changing hover to the thumbnail preview then pressing middle click is not going to really be faster than right click on task button then "C".
      3) Anyone who knows how to play a piano or use keyboard properly will know it is usually faster to use multiple fingers than one finger to press keys. But of course only if the fingers are already close to the right places.

      So no Windows 7 is not faster at all for me.

      From a "UI for skilled users" perspective, Windows 7 is worse than Windows XP. Windows 7 is better than Windows XP from a "UI for noob users" - e.g. Win7 stuff like winkey+[number] can be useful when you only have one document open per application. Otherwise that feature is not useful.

      With Windows 9x/2K/XP it's easy to use "classic mode" and then create a folder named "1 Explore" in the start menu and put shortcuts like "C Explore C", "D Explore D", "E Explore E" in the "1 Explore" folder, and also create folders/shortcuts called "2 Tools", "3 Favs", "4 Command prompt" etc.

      Then you end up with:
      winkey, 4 will launch the command prompt
      winkey, 1, d = Explore D drive
      winkey, 2, c could be calculator
      winkey, 3, 3 = email
      winkey, 5, 1 = ssh to site #1
      winkey, 5, 2 = ssh to site #2

      In contrast "Windows 7" it's winkey, c,a,l,c, enter key, for calculator. You cannot easily customize your start menu to use it that way anymore.

      I'm all for making a GUI better for "noob users", but hey, do put in or retain features that make things better for skilled experienced users too.

      --
    120. Re:So what? by FatdogHaiku · · Score: 1

      Many AMD systems (Compaq and HP that I know of) got hammered by a registry error dealing with the intelppm.sys registry key. Because an Intel disk image was used on AMD machines, SP3 thought it was an Intel system and activated power management that it should not have. The resulting BSOD at reboot freaked a lot of people out. It's a two minute fix if you can use the registry editor but it cost a lot of end users money because they had to take the box to a shop.

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    121. Re:So what? by harryjohnston · · Score: 1

      The 64-bit version of Windows XP is based on Windows 2003, so it receives service packs when Windows 2003 does.

      The end of support for Windows XP SP2 does not apply to the 64-bit version.

    122. Re:So what? by rtyhurst · · Score: 1

      Oh, oh, oh!

      I am very, very, very, very, very, very angry of this!

      And also: enraged!

      SP2 has a deep inner beauty that only we the illuminati can appreciate; SP3 sends secret mind-twisting brain rays that can only be intercepted by my tin foil beanie.

      Oh it's: shameful!

    123. Re:So what? by SCPRedMage · · Score: 1

      The 64-bit is pretty much the "standard" for Windows 7; I've yet to see a system available that's sold with the 32-bit version.

      And Microsoft has stated that 7 will be the last 32-bit OS they make, so they're getting there.

      --
      My sig can beat up your sig.
    124. Re:So what? by SCPRedMage · · Score: 1

      As has been said many times above, XP-x64 is based off of Server 2003, and uses the same service packs that it does. Since the latest 2k3 service pack is 2, that's the latest for XP-x64, and is still being supported.

      --
      My sig can beat up your sig.
    125. Re:So what? by Anonymous Coward · · Score: 0

      "And that's what you'll get, lad."

      Huge tracks of ... RAM?

    126. Re:So what? by Shakrai · · Score: 1

      Yes, because the US Attorney has nothing better to do than charge you for copying a Microsoft CD when Microsoft itself tells it's customers to do this. I can completely understand why you are worried.

      --
      I want peace on earth and goodwill toward man.
      We are the United States Government! We don't do that sort of thing.
    127. Re:So what? by DigiShaman · · Score: 1

      I've yet to see a system available that's sold with the 32-bit version.

      Agreed. Minor nitpick however. Netbooks. They're Atom processors are x86 and thus run Windows 7 Starter edition. Granted, I wouldn't expect them to be used with a heavy work load compared with someone using a desktop or laptop. Plus, they usually have no more than 2GB of RAM installed anyways.

      While a company could perform a rolled out upgrade installation of Windows 7 x86 on existing hardware, that's really hard to justify in this bare market. Companies don't want to spend money these days. If (and when) the economy picks back up, enough time will have passed to make it worthwhile to procure all new computers with Windows 7 64 pre-loaded.

      --
      Life is not for the lazy.
    128. Re:So what? by rtyhurst · · Score: 1

      Back when I was using Roman numerals, I tried to use an abacus, and it borked my Roman numerals.

      Just sayin'...

    129. Re:So what? by ffreeloader · · Score: 1

      Yeah, you crushed it. I knew better, but let you sit on it anyway.

      --
      "while democracy seeks equality in liberty, socialism seeks equality in restraint and servitude." de Tocqueville
    130. Re:So what? by Anonymous Coward · · Score: 0

      HP portables come with SP2 installed and when problems occur, they specifically tell us not to change to SP3. It might work, but then HP will not support it. Which law would you like me to break? I don't know if they are the only companies to do this.

    131. Re:So what? by Anonymous Coward · · Score: 0

      Way back when I had no computer, I went to a pron convention, got my machine borked and I've never looked back.

      Just sayin'

    132. Re:So what? by bell.colin · · Score: 1

      Try slipstreaming SP into CD and install fresh from that, Had BS issues when trying XP RTM and then installing SP2 to build image a few years back but sliptreaming worked fine.

    133. Re:So what? by Zephiris · · Score: 1

      Random utility/security software used to be an issue (in particular; in some cases still is), but that's true of any non-mainstream, non-workstation edition of Windows as well.

      Drivers were more of an issue -before- Vista came out, since people were still trying to figure out x64 drivers in general. About the same time Vista/WDDM x64 drivers stopped flaking out constantly, so did 64-bit XP drivers.

      I wouldn't want to try to connect a random WLAN USB plug to XP x64 (or Vista, for that matter), mind. I never had issues with 'drivers in general', though. Everything I've tried to run with it that was supported by Server 2003 and/or Vista has been well supported on the 64-bit version too. Why, there was even one odd ancient analog brooktree TV tuner that strangely worked fine on XP x64 (using direct capture) but not on Vista (using anything).
      (And strangely, all of my video playback software insists on internally/externally using NV12 on Vista/W7 instead of RGB32, sure makes screenshots unhappy.)

      Vista advertising (for x64) was virtually mandated. To get almost anything certified (of which seemingly all companies have to care about), you had to support it. And if you had to support it, of course you're going to loudly trumpet the fact that you're cool and hip and on the cutting edge of innovation in OS support. People are predictable, and Microsoft knew what it was doing. XP x64 was merely an OEM product, so while it didn't have the mainstream coverage, it certainly wasn't XP Embedded.

      I'm glad Vista/etc work for you. For me, it actually loses track of memory during runtime (not boot), on a remarkably standard classification gaming machine.
      Having 4GB of RAM, and having to consult Available memory table to be able to run anything more than basic IM (and still going OOM frequently on games, web browsers, etc) was enough for XP x64 to reclaim its old spot, and make me consider buying a CRT (and conversion) just to avoid the rock and hard place of "windows classic" LCD issues vs. "windows new-style" memory "disappearing" issues.

      But, at any rate, every time the mere version is mentioned, people seem to get some kind of complex about how horrible it -must- be, when it's merely middle ground somewhere somewhere between running XP SP3 and Vista x64 SP2.
      All available RAM, without having to spend at least 800MB-1GB of it (more in my case) on services just booting to the desktop.

      Consistent, unremarkable behavior tends to be considered a feature that most OSes strive for in new and improved versions.

      --

      "A Goddess rarely smiles for she is forced by others to be an island unto herself." - Zephiris
    134. Re:So what? by zmollusc · · Score: 4, Funny

      Back when I was using Vista, I .. Oh, wait, this is the wrong end of the thread.

      --
      They whose government reduces their essential liberties for temporary security, receive neither liberty nor security.
    135. Re:So what? by mirix · · Score: 1

      Compared to NT4, Windows 2000 was "bloated" and slow - the former needing a 33Mhz 486 with 16Mb RAM and the latter a 133Mhz+ Pentium (~8x more) with 64MB RAM (4x more).

      Somewhat true, but it also brought things that were kind of necessary in the 21st century, like, say... USB support, for example.

      Then XP came along, and didn't really add anything of substance to 2k, mostly just fluff.

      --
      Sent from my PDP-11
    136. Re:So what? by SCPRedMage · · Score: 1

      Considering that the 32bit and 64bit versions have exactly the same price, there's NO reason to load Win7 32bit on a new system that has an x64 proc in it. Upgrades, of course, are another story.

      --
      My sig can beat up your sig.
    137. Re:So what? by Z00L00K · · Score: 1

      Nothing is wrong with SP3. Of course - some machines may barf on it, but a reinstall fixes that. The problems are usually caused by some third-party software that has done something inappropriate.

      As a general rule there is no need for an extreme worry about using SP3, it is much less of a trouble than SP2 ever was.

      And for whatever reason - it may be time for the yearly reinstall anyway so why delay SP3 further?

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    138. Re:So what? by TheRealGrogan · · Score: 1

      Try renaming c:\windows\system32\drivers\intelppm.sys to something else when that happens on a system with an AMD processor.

      A lot of lazy OEMs ship an image with support for both intel and amd processors (which are normally detected by setup). Installation of the service pack causes that intel power management driver to load, and AMD machines blue screen.

      I check for that file on AMD systems before installing a service pack, but it can be renamed after the blue screen if you boot to Safe Mode (where it won't load). Reboot normally and the service pack install will complete (you'll be at that "Please Wait..." screen with the windows logo on it)

    139. Re:So what? by Anonymous Coward · · Score: 0

      Easily fixed. Just make a legal copy.

    140. Re:So what? by dave420 · · Score: 1

      Win + # where # is the number of the icon in the task bar. Seems to work perfectly in Windows 7. You can also add your own customised shortcuts to the task bar, negating your whine entirely ;)

    141. Re:So what? by Anonymous Coward · · Score: 0

      You'd rather read the constitution than the Microsoft pages and blogs that all say "you should slipstream your disc"?
      Well of course you would, then you wouldn't get to make dickhead remarks about evil piracy laws.

    142. Re:So what? by alexchorny · · Score: 1

      SP2 on Win64 will be supported till 2014.

    143. Re:So what? by Anonymous Coward · · Score: 0

      Nobody expects the microsoft's death panel.

    144. Re:So what? by commodore64_love · · Score: 1

      >>>A .1 release is not a Service Pack.

      Neither is +0.1 a whole new OS. It's Vista renamed "Mohave" (in the ads) and then "Seven" (in real life). It's just the same OS with reworked code to use less RAM. It's part of the NT 6.x family. - It should have been a service pack provided free of charge.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
    145. Re:So what? by AmiMoJo · · Score: 1

      The rules on slipstreaming are not too difficult to understand.

      Basically if you have an actual Windows disc you can make a slipstreamed version to use. If your PC came with a "restore" disc/partition (i.e. not a standard Windows disc, usually some kind of disk image based recovery) then you are not allowed to make one or to even install from someone else's disc.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    146. Re:So what? by AmiMoJo · · Score: 1

      In the early days XP x64 had really poor driver support which is why it got such a bad rep. These days though you can usually just install the Vista x64 driver and it will work without problems.

      I am one of those 3 guys using XP x64. The only thing I have ever been unable to get drivers for is an old RFID card reader and I have yet to find an app that works on XP x86 but not on x64. For a while there were problems with things like WinRAR or Opus which put stuff in the Explorer context menu but all that was resolved years ago, again in no small part thanks to Vista x64.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    147. Re:So what? by Theoboley · · Score: 1

      ACK!!! Too Many Acronyms!!!!

      --
      Stupidity only gets you so far, then you've gotta try
    148. Re:So what? by Civil_Disobedient · · Score: 1

      I personally gave up on XP x64 on my home computer when I had trouble finding working video drivers.

      What's the video card? I'm honestly curious. As a XP64 user myself, I see this canard repeated all the time but never any real evidence to support it.

    149. Re:So what? by Anonymous Coward · · Score: 0

      XPSP3 makes some fundamental changes to the OS that breaks compatibility with some (poorly) written apps. The sort of apps that large companies write for themselves and rely heavily on. I know in my company (fortune 100), we have several applications that simply break under SP3. They've been working on testing and fixing these apps, but we're not a software company so the work is going slow.

    150. Re:So what? by Ephemeriis · · Score: 1

      I personally gave up on XP x64 on my home computer when I had trouble finding working video drivers.

      What's the video card? I'm honestly curious. As a XP64 user myself, I see this canard repeated all the time but never any real evidence to support it.

      At the time, it was an nVidia GeForce 5xxx of some sort.

      --
      "Work is the curse of the drinking classes." -Oscar Wilde
    151. Re:So what? by Anonymous Coward · · Score: 0

      Completely satisfied XP64 user here. Reinstalled recently due to upgrading to an SSD for the operating system, so it's not exactly an old installation, but had been running it for a couple of years up until then.

      I admit to being a bit nervous about hardware support, but either I've been lucky with my hardware (Phenom, Creative Labs, ATI card, Intel network) or it's sufficiently generic that I've not had an incident.

      Captcha: concurs.

    152. Re:So what? by TheLink · · Score: 1

      If you bothered read and understood what I wrote, you'd realize that I'm already aware of winkey+# and its limitations, and why it wouldn't be an improvement over the XP behaviour. I actually did mention it in my post.

      Judging from your response, I'm sure Windows 7 is well-suited for you.

      --
    153. Re:So what? by SanityInAnarchy · · Score: 1

      It might work, but then HP will not support it.

      Well, by doing this, HP's demonstrated how little their support is likely worth.

      Which law would you like me to break?

      Law? There's no law involved here.

      --
      Don't thank God, thank a doctor!
    154. Re:So what? by Anonymous Coward · · Score: 0

      You know, I never could figure out why the fuck people don't right-click the damn shortcut, go down to properties, and run the fucker in compatibility mode for SP2. Works in all of the rare instances I've encountered this.

    155. Re:So what? by Bungie · · Score: 1

      I never had an experience with that particular config but if you blue screened I'd blame HP's drivers...for their portables they are pretty crummy. I think HP seriously spends 10% of their time getting the low level (critical) features working and the other 90% implementing things like detecting when you're low on ink or disconnected from the internet.

      For example the HP media keys driver can bork any other keyboards connected to the system. If it fails for whatever reason, you have to boot into safe mode to type in your password. I've never seen any other media key driver () that can bork the system keyboard driver completely. Most other media key drivers use a service or user mode application...I suspect that HP is using a filter driver which doesn't cascade the information down to the lower drivers properly.

      I've also seen them release ATI display drivers which are completely custom built and don't match (or work with) the components of the regular ATI release drivers...and it's not for optimization. The ATI release drivers work better in every way, and the HP ones will often have random hardware acclerated features disabled in their drivers for no apparent reason (maybe the video peformance is too good?).

      Their uninstallers often lock up or crash the system entirely outside of safe mode too, which shows how stable their driver packages are, and how well they're tested. The list of bad drivers and software included with the Pavillion is huge. Any service pack upgrade with their stuff installed is a serious game of chance. A clean install of SP3 would probably work. Just make sure you preserve your OEM activation if your model uses it. Also make sure your SATA controller's text mode drivers are included in your Windows XP install disk because you can only install them from a floppy in text mode setup. You can slipstream them with nLite if they aren't included.

      --
      The clash of honour calls, to stand when others fall.
    156. Re:So what? by DarkKnightRadick · · Score: 1

      Thanks, I'll give that a run, eventually. (:

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    157. Re:So what? by drsmithy · · Score: 2, Informative

      Then XP came along, and didn't really add anything of substance to 2k, mostly just fluff.

      This is false.

    158. Re:So what? by Anonymous Coward · · Score: 0

      Where in hell is the "Score:6, Hilarious" when you need one?...

    159. Re:So what? by Anonymous Coward · · Score: 0

      I don't know anyone who's used Windows 7 and hails XP as superior, except for Slashdot. Somehow XP gained a reputation for being such a great system on here. ATI, Creative, Intel and NVIDIA finally stabilized their drivers after more than half a decade of blue screening XP systems constantly. Everyone who's used XP has seen a blue screen at some point in time. You rarely see one in Windows 7 or Vista ever.

      Microsoft is shaking their heads because they over engineered Vista, thinking people wanted an improved Windows system. They could have released Vista with the same shitty security and driver model as XP and just included some new themes, and people would have loved it.

    160. Re:So what? by drsmithy · · Score: 1

      Neither is +0.1 a whole new OS.

      I never suggested it was. Nor did anyone else outside of a marketing department.

      It's Vista renamed "Mohave" (in the ads) and then "Seven" (in real life).

      This is false. "Mojave" used Vista. Windows 7 is not Windows Vista, no matter how much you want to try and argue otherwise.

      It's just the same OS with reworked code to use less RAM. It's part of the NT 6.x family. - It should have been a service pack provided free of charge.

      They're all "the same OS with reworked code [...]". No version of Windows NT since 3.1, in 1993, is "a new OS", any more that OS X was "a new OS" (rather than a Vista-like overhaul of NeXT) or any release of Linux since 1991 was "a new OS".

      A .1 release is not a Service Pack. Windows 2003, was a .1 release, as was Windows 3.51, and no-one rational would try and argue they were "just a service pack" for previous releases. Service Packs (generally speaking) fix existing bugs, they don't introduce new features, functionality, or major changes.

    161. Re:So what? by Bungie · · Score: 1

      lol USB? NT4 didn't even support plug and play by default.

      --
      The clash of honour calls, to stand when others fall.
    162. Re:So what? by Bungie · · Score: 1

      Vista / 7 dropped support for Virtual DOS Machine. Relevant if you want to play Tomb Raider, Carmageddon, Blood and other late DOS games (Dosbox is too slow for them at high resolutions).

      32-bit editions of Vista and Windows 7 still come with NTVDM and run DOS applications just fine. They didn't include it in 64-bit Windows because it uses the processor's virtual 8086 mode which isn't available on 64-bit processors. They would have had to rewrite the entire subsystem to emulate the x86 real mode hardware under x64, which is what Virtual PC already does.

      Most people don't run DOS or 16-bit Windows applications very much anymore. If they needed to most of their apps don't have heavy requirements and would run fine with Virtual PC's emulated hardware.

      --
      The clash of honour calls, to stand when others fall.
    163. Re:So what? by Anonymous Coward · · Score: 0

      No man, there were no drivers for XP x64. It shared the kernel with Windows Server 2003 which had a variety of good storage and other server related drivers.

    164. Re:So what? by Bungie · · Score: 1

      There is a hard division between all 32-bit and 64-bit programs and DLL's. For example, you have 64-bit and 32-bit versions of Internet Explorer. 32-bit Internet Explorer will be emulated so you want to use 64-bit Internet Explorer which should perform better. But 64-bit IE can only run 64-bit plugins. So if you have one plug-in (*cough* Flash) that doesn't have a 64-bit version, then you have to use the 32-bit version of IE. The 32-bit version of IE only runs 32-bit plugins, so you also have to install the 32-bit versions of your 64-bit plug-ins for 32-bit IE. In the end you have to install both versions of every plugin (so you'll have both the 32-bit and 64-bit versions of the Java runtime installed for example). You even have a 32-bit and 64-bit version of Explorer, depending on if you have 64 or 32-bit shell extensions. You end up using the 32-bit version anyway because of one plugin (like Flash) and hoping you can use the 64-bit version and fully enjoy the performance benefits.

      Windows XP x64 was a complete test by Microsoft to try and figure out a way of doing a 64-bit client. I don't think they really intended for anyone besides developers to actually use it. They took all of their lessons from XP x64 and used it to make Vista 64-bit work well. The whole OS experience feels like an incomplete and abandoned project. Microsoft also didn't provide support for it for very long, and just wanted people to move onto Vista. You can't get a lot of software for it, and because of it's version (5.2) a lot of software assumes you're not running a client OS. Even 32-bit Windows Live Messenger requires clever trickery to get it installed and running.

      --
      The clash of honour calls, to stand when others fall.
    165. Re:So what? by jesset77 · · Score: 1

      And that's what you'll get, lad. Our last, best hope for peace.

      Now if you'll excuse me, it's going to take me a cartographer to figure out what the original topic was supposed to be. 8I

      --
      People willing to trade their freedom of expression for temporary entertainment deserve neither and will lose both.
    166. Re:So what? by Anonymous Coward · · Score: 0

      What's wrong with SP3?

      I have to reapply my WPA crack.

    167. Re:So what? by Gr8Apes · · Score: 1

      IIRC, they lampooned it for its cartoonish look, and the fact that it was slower than Win98 and Win 2K, depending on where you were coming from.

      Yes. Just like Vista.

      Not really. While Vista was bad enough to require rebranding and kept everyone on the 10 year old XP, it was never lampooned for being a clown interface. Needled for being slow, bloated, and less capable, yes.

      Win XP had a slower uptake than desired, but took off after 2 years as games designed for XP started coming out in large numbers. Vista will die an ignoble death as a footnote in MS's history.

      Win 2K was probably the "best" of the NT versions, solid and trim compared to all of its predecessors and descendants.

      Compared to NT4, Windows 2000 was "bloated" and slow - the former needing a 33Mhz 486 with 16Mb RAM and the latter a 133Mhz+ Pentium (~8x more) with 64MB RAM (4x more).

      Having run NT 4 in beta onward it used about the same resources to run well as 2K or XP. I can say that NT 4.0 running on a 486DX2-66 with 64MB of RAM was barely serviceable. I should mention that XP out of the box is dog slow. Removing services is required both for performance and some semblance of security.

      Windows 7 is as much "Vista SP2" as Windows XP was "Windows 2000 SP1". Certainly the changes weren't as large as Vista (probably the single biggest update to NT since its release), but definitely more than just a service pack.

      Actually - the biggest update to NT was the 3.1->3.5 release, where biggest change was that the GDI layer was inserted and essentially all separation of the kernel/user space was tossed out the door for the sake of a semi usable UI. WIn 2K added the new modular driver framework, among other things. What exactly did Vista add? (It certainly wasn't the promised rewrite, but it did add the TPM and DRM pieces. Hooray!)

      But, I'll agree that Win XP was Win 2K SP 2 plus a lunatic GUI. Note that Win 2K had a total of 4 SPs plus a final rollup SP post SP4. It also had the capability to run all DX iterations that came out up to DX9, which could be hacked as MS tried to kill off Win 2K by denying it the latest DX versions, much like DX 10 and XP.

      Windows 7 has some fixes that will never show up in VIsta, primarily to separate the 2 products because Vista is viewed so negatively. Note that Vista is only 2 years old, and already is being shoved out the door.

      So yes, there are similarities, but there are also significant differences.

      --
      The cesspool just got a check and balance.
    168. Re:So what? by drsmithy · · Score: 1

      Having run NT 4 in beta onward it used about the same resources to run well as 2K or XP. I can say that NT 4.0 running on a 486DX2-66 with 64MB of RAM was barely serviceable.

      Sorry, but utter rubbish like this destroys your credibility. Ignoring for a minute how unlikely it would be to find a 486 with 64MB of RAM, NT4 was quite usable - and I spent over a year using it - on a Pentium ~75Mhz with 32MB. To say nothing of the 486DX2/66 being a 4-year old, 2 generation old CPU at NT4's release - you wouldn't expect blistering performance out of it in the first place.

      I should mention that XP out of the box is dog slow. Removing services is required both for performance and some semblance of security.

      More rubbish.

      Actually - the biggest update to NT was the 3.1->3.5 release, where biggest change was that the GDI layer was inserted and essentially all separation of the kernel/user space was tossed out the door for the sake of a semi usable UI.

      This is flat-out false. Moving GDI into kernel space - a change which, incidentally, happened with NT 3.51 to 4.0, not 3.1 to 3.5 - didn't "essentially toss out all separation of the kernel/user space".

      WIn 2K added the new modular driver framework, among other things. What exactly did Vista add? (It certainly wasn't the promised rewrite, but it did add the TPM and DRM pieces. Hooray!)

      Vista added much more than any revision before it.

      A completely new display system and window manager, new audio stack, new printing stack, new networking stack, new driver model, significant overhauls to memory management, scheduling and IO, .NET...

      Vista was as close to a "rewrite" as NT is likely to get (and probably need) for another 15 years.

      Windows 7 has some fixes that will never show up in VIsta, primarily to separate the 2 products because Vista is viewed so negatively. Note that Vista is only 2 years old, and already is being shoved out the door.

      Vista is 3 years old, as of January 2010. Further, if you look back at the history of Windows NT releases, if anything it was a bit later than expected - this is especially true if you consider things that probably should have been .1 releases but weren't for marketing and political reasons (like XP SP2 and Windows 2003 R2).

    169. Re:So what? by Gr8Apes · · Score: 1

      Having run NT 4 in beta onward it used about the same resources to run well as 2K or XP. I can say that NT 4.0 running on a 486DX2-66 with 64MB of RAM was barely serviceable.

      Sorry, but utter rubbish like this destroys your credibility. Ignoring for a minute how unlikely it would be to find a 486 with 64MB of RAM

      And TBBA (Truth by Blatant Assertion) destroys any credibility you might have. These were Gateway 486DX2-66 EISA systems loaded with 64MB of RAM and 2 1GB SCSI-I disks that came in for about 10K each, I bought 7 of them. You really need to get off your high horse.

      NT4 was quite usable - and I spent over a year using it - on a Pentium ~75Mhz with 32MB. To say nothing of the 486DX2/66 being a 4-year old, 2 generation old CPU at NT4's release - you wouldn't expect blistering performance out of it in the first place.

      I spent about 3 weeks using it on the 486. A 486-33 was the minimum, pentium was recommended. Likewise, 16MB RAM was the minimum, 32MB RAM recommended, 64MB was the minimum usable amount for anything.

      I also ran a Pentium Pro 180 w 128MB RAM with NT 4 in multi-boot mode for 4 years, and it was still the biggest dog out of the OSes I ran on that one. If it hadn't been for work, I doubt I would have run it at all.

      I should mention that XP out of the box is dog slow. Removing services is required both for performance and some semblance of security.

      More rubbish.

      and your backing data would be?
      Or, I could just answer your entire post with "more rubbish". You seem to think it works for you.

      This is flat-out false. Moving GDI into kernel space - a change which, incidentally, happened with NT 3.51 to 4.0, not 3.1 to 3.5 - didn't "essentially toss out all separation of the kernel/user space".

      You are correct. It was NT 4 that broke the security model entirely. It was started in 3.5, because 3.1 was virtually unusable. But the full out breakage did not occur until 4.0.

      This change did break the security model completely since now a single thread ran all code through a single set of DLLs that was shared by all processes, and hence code here has full privileges. There are also other problems with this design. Does opening a 10MB email in Outlook over a slow connection essentially stop all other user interaction with other Office apps until it's completed the task? (I don't know - I don't run MS apps if I can avoid it these days)

      WIn 2K added the new modular driver framework, among other things. What exactly did Vista add? (It certainly wasn't the promised rewrite, but it did add the TPM and DRM pieces. Hooray!)

      Vista added much more than any revision before it.

      As I recall, NT 4.0 added a completely new display system and windows manager, new driver model, new display arhcitecture, new audio stack, new printing stack, and significant overhauls to memory, scheduling and IO. In many way ways far greater compared to the previous systems than Vista to XP.

      And .NET is not part of Vista.

      Vista was as close to a "rewrite" as NT is likely to get (and probably need) for another 15 years.

      Considering the recent validation of the DLL injection problem, I'd say NT required a rewrite about the time it compiled the first time. It's security model is upside down and fundamentally flawed. It cannot be fixed. It's a completely backwards system that requires a highest privs model compared to every other system out there that works off of a lowest privs model. Yes, I'm aware of MS's PR campaign on the 2008 R2 release, but I can assure you it's purely marketing spin and has no basis in reality.

      Vista is 3 years old, as of January 2010. Further, if you look back at the history of Windows NT releases, if anythin

      --
      The cesspool just got a check and balance.
    170. Re:So what? by drsmithy · · Score: 1

      And TBBA (Truth by Blatant Assertion) destroys any credibility you might have. These were Gateway 486DX2-66 EISA systems loaded with 64MB of RAM and 2 1GB SCSI-I disks that came in for about 10K each, I bought 7 of them. You really need to get off your high horse.

      I said unlikely, not impossible.

      I spent about 3 weeks using it on the 486. A 486-33 was the minimum, pentium was recommended. Likewise, 16MB RAM was the minimum, 32MB RAM recommended, 64MB was the minimum usable amount for anything.

      32MB of RAM was quite a usable configuration for NT4, and at 2.5x the minimum (which was actually 12MB) that's to be expected.

      I also ran a Pentium Pro 180 w 128MB RAM with NT 4 in multi-boot mode for 4 years, and it was still the biggest dog out of the OSes I ran on that one. If it hadn't been for work, I doubt I would have run it at all.

      Compared to what, providing the same functionality ? Heck, XP would have been ok with that sort of horsepower.

      and your backing data would be?

      The millions of people who managed to use Windows XP without having to resort to hacking around disabling services.

      This change did break the security model completely since now a single thread ran all code through a single set of DLLs that was shared by all processes, and hence code here has full privileges.

      Can you elaborate on this ?

      There are also other problems with this design. Does opening a 10MB email in Outlook over a slow connection essentially stop all other user interaction with other Office apps until it's completed the task? (I don't know - I don't run MS apps if I can avoid it these days)

      No, and I don't recall it ever doing so.

      As I recall, NT 4.0 added a completely new display system and windows manager, new driver model, new display arhcitecture, new audio stack, new printing stack, and significant overhauls to memory, scheduling and IO.

      Then you recall incorrectly. Probably the next biggest change to NT after Vista would have been NT 4.0 to NT 5.0.

      In many way ways far greater compared to the previous systems than Vista to XP.

      Which ways ?

      And .NET is not part of Vista.

      Vista is the first version of Windows to be distributed with .NET.

      Considering the recent validation of the DLL injection problem, I'd say NT required a rewrite about the time it compiled the first time. It's security model is upside down and fundamentally flawed. It cannot be fixed. It's a completely backwards system that requires a highest privs model compared to every other system out there that works off of a lowest privs model.

      Can you elaborate ?

      It was roughly 2.7 years old when Win 7 replaced it. So yes, older than 2 years, but not 3 when they shoved its still warm carcass out the back door.

      Which is quite close to the average:

      3.1 - July 1993
      3.5 - September 1994: +14 months
      3.51 - May 1995: +10 months
      4.0 - July 1996: +11 months
      5.0 (2000) - February 2000: +42 months
      5.1 (XP) - October 2001: +18 months
      5.2 (2003/XP64) - March 2003: +18 months
      6.0 (Vista) - January 2007: +46 months
      6.1 (Win7/2008R2) - October 2009: +30 months

      Average time between releases is ~20 months, though more importantly, the time between subsequent minor releases after a major one, tends to be <2 years. If anything, at 2.5 years after Vista, Windows 7 was somewhat behind schedule.

    171. Re:So what? by Gr8Apes · · Score: 1

      And TBBA (Truth by Blatant Assertion) destroys any credibility you might have. These were Gateway 486DX2-66 EISA systems loaded with 64MB of RAM and 2 1GB SCSI-I disks that came in for about 10K each, I bought 7 of them. You really need to get off your high horse.

      I said unlikely, not impossible.

      "It's not impossible that you're an ass."

      Somehow that just doesn't sound like it's not an insult, does it?

      32MB of RAM was quite a usable configuration for NT4, and at 2.5x the minimum (which was actually 12MB) that's to be expected.

      Guess it depends on what your needs are. I'm sure some could have run a 12MB system and been happy.

      I also ran a Pentium Pro 180 w 128MB RAM with NT 4 in multi-boot mode for 4 years, and it was still the biggest dog out of the OSes I ran on that one. If it hadn't been for work, I doubt I would have run it at all.

      Compared to what, providing the same functionality ?

      Linux and OS/2 both provided far more functionality while requiring fewer resources. Solaris was a different story.

      and your backing data would be?

      The millions of people who managed to use Windows XP without having to resort to hacking around disabling services.

      Those would be the same millions that are currently part of botnet X, Y, or Z?

      Seriously, XP to be semi functional and secure requires serious configuration. MS provided some of this OOB with SP2. If you removed a bunch of the extraneous crap XP runs by default, you can actually get down to a pretty slim system that's quite responsive and functional, albeit not in the "MS way". I got a VM down to 4or 5 processes and less than 50MB RAM. My standard install of XP with SP3 runs about 12 processes and under 70MB RAM IIRC. It's been a while since I loaded either one.

      This change did break the security model completely since now a single thread ran all code through a single set of DLLs that was shared by all processes, and hence code here has full privileges.

      Can you elaborate on this ?

      I did, above, where I stated but did not link to the AV bypass story posted here just a few days ago. The short story is that thanks to DLL code injection, you can execute arbitrary code at SYSTEM privs and even the AV won't find it. DLL code injection was actually the one way that a third party can achieve true privilege escalation in Server 2008 R2, as all token manipulation APIs are now "broken".

      There are also other problems with this design. Does opening a 10MB email in Outlook over a slow connection essentially stop all other user interaction with other Office apps until it's completed the task? (I don't know - I don't run MS apps if I can avoid it these days)

      No, and I don't recall it ever doing so.

      Extremely common issue from NT 4 all the way through XP SP 3. Very noticeable when opening a 10MB attachment through a VPN link that's been choked down to 56Kbps. Once clicked, no Office app will respond in and of those systems. I have not tried this in Vista or Win 7.

      And .NET is not part of Vista.

      Vista is the first version of Windows to be distributed with .NET.

      It may be distributed with, but that doesn't make it "part of" Vista. That's like saying iTunes is part of OSX, when it's clearly it's own product.

      It was roughly 2.7 years old when Win 7 replaced it. So yes, older than 2 years, but not 3 when they shoved its still warm carcass out the back door. ...

      Average time between releases is ~20 months, though more importantly, the time between subsequent minor releases after a major one, tends to be <2 years. If anything, at 2.5 years after Vista, Windows 7 was somewhat behind schedule.

      Let me fix that for you and put i

      --
      The cesspool just got a check and balance.
    172. Re:So what? by drsmithy · · Score: 1

      Guess it depends on what your needs are. I'm sure some could have run a 12MB system and been happy.

      My needs are a stable, responsive, easy to use system. NT4 was that.

      Linux and OS/2 both provided far more functionality while requiring fewer resources. Solaris was a different story.

      Please. OS/2 was (relatively) unstable, barely supported and not even multiuser, though it did have a nice GUI. Linux was a PITA to setup, use and maintain, and its cutting edge GUI of the time was fvwm95. I switched FROM OS/2 to NT4 in the beta cycle (early 1996) precisely because it was so much better than OS/2 even then.

      Seriously, XP to be semi functional and secure requires serious configuration.

      You mean like turning on the firewall and not running trojans ?

      MS provided some of this OOB with SP2. If you removed a bunch of the extraneous crap XP runs by default, you can actually get down to a pretty slim system that's quite responsive and functional, albeit not in the "MS way". I got a VM down to 4or 5 processes and less than 50MB RAM. My standard install of XP with SP3 runs about 12 processes and under 70MB RAM IIRC. It's been a while since I loaded either one.

      The original XP release is quite responsive and functional on a P2 class system with 128MB of RAM. 256 and it's flying.

      I did, above, where I stated but did not link to the AV bypass story posted here just a few days ago.

      You didn't mention any about that story.

      The short story is that thanks to DLL code injection, you can execute arbitrary code at SYSTEM privs and even the AV won't find it. DLL code injection was actually the one way that a third party can achieve true privilege escalation in Server 2008 R2, as all token manipulation APIs are now "broken".

      Oh wow. A local-execution-only privilege escalation bug in third party software. Now there's a fundamental design flaw if ever I've seen one .</SARCASM>

      Extremely common issue from NT 4 all the way through XP SP 3. Very noticeable when opening a 10MB attachment through a VPN link that's been choked down to 56Kbps. Once clicked, no Office app will respond in and of those systems. I have not tried this in Vista or Win 7.

      Can't be that common if I've never even heard of it. Though as described it's clearly an application level problem, not an OS-level problem.

      It may be distributed with, but that doesn't make it "part of" Vista. That's like saying iTunes is part of OSX, when it's clearly it's own product.

      Actually, no, it's like saying Cocoa is part of OS X, which is pretty much exactly what .NET is to Windows.

      Let me fix that for you and put it in proper perspective regarding major releases as we know them of the core OS:

      You left out Windows 2003/XP64/NT 5.2. That's at least as significant a release as XP or Windows 7, and quite arguably more so since it became the base from which Vista was built after the development "reset" in 2004.

      As per Microsoft's support lifecycle, Vista will enter "extended support" in 2012 and close out support in 2017. Note that the timeline is set by policies that were created before it was even released, so trying to argue it's being retired any earlier than expected is flat out false.

    173. Re:So what? by Gr8Apes · · Score: 1

      Linux and OS/2 both provided far more functionality while requiring fewer resources. Solaris was a different story.

      Please. OS/2 was (relatively) unstable, barely supported and not even multiuser, though it did have a nice GUI. Linux was a PITA to setup, use and maintain, and its cutting edge GUI of the time was fvwm95. I switched FROM OS/2 to NT4 in the beta cycle (early 1996) precisely because it was so much better than OS/2 even then.

      And your veracity suffers even more. NT 4 was more stable in the beta cycle? Really? You weren't affected by the 42 day timer bug? Or the 20/32 bit page counter pointer bug that wasn't fixed until SP1? Did you even run either of these systems? How about the ever present guaranteed fragmentation problem that MS refused to acknowledge with NTFS until XP?

      While Linux did have a painful GUI at the time, it just ran. OS/2 likewise ran and ran - I had a system at work that was used heavily in the processing of large files (at the time files up to 500MB), ran FTP, Gopher, SMTP (yep - back in those days we ran local mail servers if you didn't want to login to the mainframe for mail) etc, and this machine stayed up 6 months at a time. Better yet, when OS/2 finally got a defragger because of all the NT fanboys clamoring that it was a toy os because it didn't even have a defragmentation utility, it turned out that after 4 years of continuous operation with hundreds of thousands of file writes and deletes my system's fragmentation level was .... <4%.

      Meanwhile, NT 4.0 on a second system had to be rebooted weekly, and required defragmentation weekly and was used only for the file modeling pieces.

      Later on, NT 4.0 became rather solid as far as uptime went, and could be rebooted monthly under the loads we put them under. BTW, MS's recommendation was weekly reboots, circa 97/98.

      The original XP release is quite responsive and functional on a P2 class system with 128MB of RAM. 256 and it's flying.

      Then we have different definitions of flying.

      The short story is that thanks to DLL code injection, you can execute arbitrary code at SYSTEM privs and even the AV won't find it. DLL code injection was actually the one way that a third party can achieve true privilege escalation in Server 2008 R2, as all token manipulation APIs are now "broken".

      Oh wow. A local-execution-only privilege escalation bug in third party software. Now there's a fundamental design flaw if ever I've seen one .</SARCASM>

      You're not getting the picture. Due to NT's kernel architecture, basically any arbitrary code can be forced to be run by SYSTEM from any process and even AV can't stop it. All your sarcasm can't change the fact that this is a major security hole.

      It may be distributed with, but that doesn't make it "part of" Vista. That's like saying iTunes is part of OSX, when it's clearly it's own product.

      Actually, no, it's like saying Cocoa is part of OS X, which is pretty much exactly what .NET is to Windows.

      I'd argue that it's more like Java being listed as part of the OS. After all, it's an installable component, doesn't come installed by default (at least not on Server 2008 R2), and is not required for operation.

      Let me fix that for you and put it in proper perspective regarding major releases as we know them of the core OS:

      You left out Windows 2003/XP64/NT 5.2. That's at least as significant a release as XP or Windows 7, and quite arguably more so since it became the base from which Vista was built after the development "reset" in 2004.

      I did that on purpose. Almost no one used XP64 which actually was released across 2 years with Server 2003 being released in between. The interesting part is that the 32 bit and 64 bit versions of 2003 were released a year apart. There was also the Server 2003 R2 release which I'm not sure what the status is compared to Server 2008 R2 which is really a new release with a different core than 2008 and requires a license upgrade.

      --
      The cesspool just got a check and balance.
    174. Re:So what? by drsmithy · · Score: 1

      And your veracity suffers even more. NT 4 was more stable in the beta cycle? Really?

      Absolutely. I was happy to get a week out of OS/2 before something (usually related to the good old SIQ) necessitated a reboot to recover. NT4 would run happily for weeks (though my reboots were usually planned). Heck, for the whole ~4 years I ran it I think I had less than half a dozen BSODs, and most of those were caused by hardware failures or bad drivers.

      You weren't affected by the 42 day timer bug? Or the 20/32 bit page counter pointer bug that wasn't fixed until SP1?

      Not that I know of, and after some googling around I can't even find anything resembling the bugs you're talking about. Can you link me to a KB article ?

      Did you even run either of these systems?

      I ran OS/2 for about 3 years - mostly Warp 3, but I had also messed around with 2.0 and 2.1. I ran NT4 for about 4 years. I briefly tried Warp 4, but by then I was sold on NT4 and didn't see any reason to switch back to what was clearly a dying platform.

      How about the ever present guaranteed fragmentation problem that MS refused to acknowledge with NTFS until XP?

      The "fragmentation problem" in NTFS is grossly overstated for all but corner cases. I did (and subsequently have done again) numerous benchmarks, both with software tools and with a stopwatch, and could never detect any meaningful difference in performance between drives purportedly having 50% or more fragmentation, and drives having less than 10% fragmentation.

      BTW, MS's recommendation was weekly reboots, circa 97/98.

      Where is this recommendation ?

      You're not getting the picture. Due to NT's kernel architecture, basically any arbitrary code can be forced to be run by SYSTEM from any process and even AV can't stop it. All your sarcasm can't change the fact that this is a major security hole.

      That's not what the article described. Can you link to some material elaborating on this "architectural" flaw ?

      I did that on purpose.

      I'm sure. Doesn't make it any less wrong. There's no justifiable reason for including XP or 7, but not including 2003/XP64.

      Almost no one used XP64 which actually was released across 2 years with Server 2003 being released in between.

      However, a helluva lot of people are using Windows 2003.

      The interesting part is that the 32 bit and 64 bit versions of 2003 were released a year apart. There was also the Server 2003 R2 release which I'm not sure what the status is compared to Server 2008 R2 which is really a new release with a different core than 2008 and requires a license upgrade.

      Server 2008R2 is NT 6.1. Server 2003 R2 was a relatively minor update, most of its "improvements" basically just a collection of userspace tools.

    175. Re:So what? by Gr8Apes · · Score: 1

      You weren't affected by the 42 day timer bug? Or the 20/32 bit page counter pointer bug that wasn't fixed until SP1?

      Not that I know of, and after some googling around I can't even find anything resembling the bugs you're talking about. Can you link me to a KB article ?

      Wish I could, the best I could find was a snippet from a PCWorld article about this. Then again, nothing like the web existed back in those days....

      The "fragmentation problem" in NTFS is grossly overstated for all but corner cases. ...could never detect any meaningful difference in performance between drives purportedly having 50% or more fragmentation, and drives having less than 10% fragmentation.

      You and I could not be more diametrically opposed on these topics. First off, OS/2 2.1 onward was never unstable for me and ran on three different architecture/CPUs that I used, flawlessly and reliably, unless I pushed it by running the win32 subsystem.

      Second, only with massive tweaking and running only specific software could I ever get a month out of NT 4.0. If I deviated, it would fail faster. Before SP1, you were guaranteed to BSOD in 42 days or whenever your page counter overflowed 20 bits and tried to reference a page above the 20 bits or in the overflow range. The memory there was corrupted.

      BTW, MS's recommendation was weekly reboots, circa 97/98.

      Where is this recommendation ?

      Well, a quick google search indicates that there is no real documentation left on the web before SP4 regarding NT 4.0 if you're looking for specifics such as bug fixes etc. I'm pretty sure I still have an NT 4.0 SP1 disk somewhere around here, but it'll be at the bottom of a box if it hasn't been thrown out already. Otherwise I'd link it for you. NT 4.0 was a massive pile of crap when it came out. SP1 fixed a ton of major issues. SP2 added features and broke everything again. SP3 fixed the breakage. It was the source of the "only apply and run odd service packs" mantra that was around for years. Since there's no easily or even not so easily found data for anything prior to SP6, feel free to either accept these statements or not. It really doesn't matter for something that is more than 10 years in the past. However, a brief brainstorm shows that the memory and stability problems were not rare.

      Server 2008R2 is NT 6.1. Server 2003 R2 was a relatively minor update, most of its "improvements" basically just a collection of userspace tools.

      Really? So there would be no core changes? Perhaps an almost usable Server Core installation, for starters? And I suppose IIS 7.5 and .NET 3.51 are also minor changes? And we won't get into the innards where all the token manipulation routines have been greatly restricted. I don't recall when they created the 4 base security tokens, maybe they showed up in 2008. They certainly took effect in 2008 R2.

      --
      The cesspool just got a check and balance.
    176. Re:So what? by tehcyder · · Score: 1

      The plural of anecdote is not data. How many upgrades to SP3 were successful on the first attempt?

      All of them except the GP's I should think.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    177. Re:So what? by tehcyder · · Score: 1

      And this is different from any other operating systems how exactly?

      Hey! Everyone knows that UNIX was hand-crafted like a Faberge egg in 1969 and has remained the same simple, elegant piece of software that it always was and always will be.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
    178. Re:So what? by Anonymous Coward · · Score: 0

      Even if all this is true, you're talking about XP without regard to service packs, not XP SP2. Either your era ended when support for XP with no SPs ended, or your era will end when support for XP SP3 ends. End of support for XP SP2 is not the end of an era.

  2. Too late, Redmond by Dystopian+Rebel · · Score: 5, Funny

    I ended support for Microsoft products a few years ago.

    --
    Rich And Stupid is not so bad as Working For Rich And Stupid.
    1. Re:Too late, Redmond by BitZtream · · Score: 1, Interesting

      wow ... aren't you witty and trendy.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:Too late, Redmond by Anonymous Coward · · Score: 0

      wow ... aren't you witty and trendy.

      No, no. The word you're looking for is "smug".

    3. Re:Too late, Redmond by Kjella · · Score: 1

      Oh, I'm sure Redmond is trembling over having lost Dystopian Rebel (714995) and less than 2% of the desktop market in the last two years. They're 3.5% down on web browser stats because users use cell phones to surf the net more but if you look only at the Win/Mac/Linux shares the change is minimal.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Too late, Redmond by elashish14 · · Score: 1

      I'm officially obsolete now. Last system I ever ran and now it's done.

      Damn it feels good.

      --
      I have left slashdot and am now on Soylent News. FUCK YOU DICE.
    5. Re:Too late, Redmond by Anonymous Coward · · Score: 0

      No, no. The word you're looking for is "smug"

      And I bet he doesn't own a TV.

    6. Re:Too late, Redmond by Anonymous Coward · · Score: 0

      Same here over 10 years ago.

  3. nooooo by Mekkah · · Score: 1

    NooooooooooO OOOOOOOOOOOoooooo

    --
    ~Mekkah
  4. XPSP2? by Anonymous Coward · · Score: 0

    I know this is a nerd site, but still. Is it really that hard to write Windows XP SP2? Or at the very least, put a fucking space between XP and SP2?

    1. Re:XPSP2? by Anonymous Coward · · Score: 0

      I know you're just trying to be annoying but is it really that hard to write Microsoft Windows XP SP2?

    2. Re:XPSP2? by coniferous · · Score: 1

      See, You misunderstand. Microsoft and Sony have teamed up to create a new portable gaming device called XPSP2. This is just part of their viral advertising campaign designed to shock and confuse people! You fell right into it!

    3. Re:XPSP2? by spidercoz · · Score: 3, Insightful

      I know you tried to make the OP look foolish but is it really that hard to write Microsoft Windows XP Service Pack 2?

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    4. Re:XPSP2? by kirk444 · · Score: 1

      a new portable gaming device called XPSP2

      With a name like that, it seems more likely to be a Dell/Sony combination, XPS P2.

    5. Re:XPSP2? by Anonymous Coward · · Score: 0

      Yadda yadda... Microsoft Windows eXPerience Service Pack Two?

    6. Re:XPSP2? by strayant · · Score: 1

      You FOOLS! You forgot the build number... now no one will have any idea what you're talking about!

    7. Re:XPSP2? by Pentium100 · · Score: 1

      No, it's still wrong. The only way to write it is:

      Microsoft(R) Windows(R) XP Service Pack 2

      Or are the spaces before "(" also needed?

    8. Re:XPSP2? by spidercoz · · Score: 1

      close, should be Windows(TM)

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    9. Re:XPSP2? by Pentium100 · · Score: 1

      thanks :)

    10. Re:XPSP2? by Anonymous Coward · · Score: 0

      I know you tried to make that other guy look foolish but is it really that hard to write 01001101 01101001 01100011 01110010 01101111 01110011 01101111 01100110 01110100 00100000 01010111 01101001 01101110 01100100 01101111 01110111 01110011 00100000 01011000 01010000 00100000 01010011 01100101 01110010 01110110 01101001 01100011 01100101 00100000 01010000 01100001 01100011 01101011 00100000 00110010.

    11. Re:XPSP2? by Trogre · · Score: 1

      I do like how Windows XP, possibly the most pirated Windows of all time, has build number 2600.

      It just seems appropriate somehow.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  5. "Kills" by Anonymous Coward · · Score: 0

    Why not say "Murders"? Or is that a little too over the top for /.?

    1. Re:"Kills" by Beelzebud · · Score: 4, Funny

      MS bludgeons XPSP2 to death like a small defenseless kitten.

    2. Re:"Kills" by spidercoz · · Score: 2, Funny

      "assassinates" would be better

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    3. Re:"Kills" by LoverOfJoy · · Score: 2, Funny

      Why not say "Murders"? Or is that a little too over the top for /.?

      I prefer decapitates.

    4. Re:"Kills" by Anonymous Coward · · Score: 0

      Mod Parent Up!!

      - the Slashdot Hivemind

    5. Re:"Kills" by Anonymous Coward · · Score: 0

      MS bludgeons XPSP2 to death like a small defenseless kitten.

      Then Steve Ballmer eats the corpse raw (amirite Slahsbots?)

    6. Re:"Kills" by halivar · · Score: 1

      With a candelabra. In the Library.

    7. Re:"Kills" by powerlord · · Score: 1

      Considering this IS Microsoft and Windows we're talking about, I prefer:

      MicroSoft Defenstrates XP SP2 from From Support. Users told to take a flying leap.

      --
      This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
    8. Re:"Kills" by Yvan256 · · Score: 1

      Just because it's got the word "ass" twice in it doesn't make it better, you know.

    9. Re:"Kills" by FreonTrip · · Score: 1

      Or defenestrates. Eviscerates?

    10. Re:"Kills" by spidercoz · · Score: 1

      doesn't it?

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    11. Re:"Kills" by interval1066 · · Score: 2, Insightful

      "MS bludgeons XPSP2 to death like a small defenseless kitten."

      If you mean "...a small defenseless ZOMBIE kitten that refuses to finally die." I would tend to agree.

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    12. Re:"Kills" by syousef · · Score: 1

      MS bludgeons XPSP2 to death like a small defenseless kitten.

      ...with a chair!

      Woooooooooooooooooo! Woooooooooooooooooo! Developers Developers Developers! Woooooooooooooooooo!

      --
      These posts express my own personal views, not those of my employer
    13. Re:"Kills" by TimothyDavis · · Score: 1

      I don't consider Microsoft to be a small defenseless kitten.

      Anyway, I am not sure how effective a kitten is at bludgeoning.

    14. Re:"Kills" by ThatsNotPudding · · Score: 1

      MS bludgeons XPSP2 to death like a small defenseless kitten.

      No, no; you're thinking of the process used to make Service Packs.

    15. Re:"Kills" by tehcyder · · Score: 1

      MS bludgeons XPSP2 to death like a small defenseless kitten.

      No, it's "Microsoft bludgeons Microsoft Windows XP Service Pack 2 to death like a small defenseless kitten." Didn't you get the memo?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  6. Rediculous by Anonymous Coward · · Score: 1, Insightful

    No excuse to be running XP SP2 still.

    Upgrade to Windows 7 or install SP3.

    Thousands of business still running SP2? Your kidding right, what do they login to their NT 4 Server and connect to the network using token ring?

    1. Re:Rediculous by risinganger · · Score: 1

      I know of large companies that are still using NT so I wouldn't joke about that too much if I were you.

    2. Re:Rediculous by spidercoz · · Score: 1

      dude there's plenty of businesses still running 2000, and probably more than you want to think about running 98

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    3. Re:Rediculous by EdtheFox · · Score: 0

      Thousands of business still running SP2? Your kidding right...

      That's probably fairly accurate. Lot's of smaller businesses don't have paid IT support.

    4. Re:Rediculous by Anonymous Coward · · Score: 0

      I just don't see what SP2 has that gets lost as soon as SP3 is applied. It isn't like the PS3 where a major feature goes away permanently. The biggest issue I see is the migration, and of course, I highly recommend doing a backup (image based if you can) before doing this.

      Long term, XP as a whole going away (other than legacy hardware of course) is a good thing. Newer versions of Windows have a lot more inbuilt security, and are able to handle the threats of 2010 and newer, as opposed to being architected around what were bad issues in 2001, then explicit patches added to fix things (pop-up blockers, enabling the firewall by default, etc.) Don't forget that even though the OS needs may not change, security always is moving, and unless the machine is physically disconnected from the Internet, people have to either upgrade their operating systems to keep with the times, or use third party hardware/software that can defend against the latest threats, be it a bug with a Web browser add-on that allows untrusted code to run, an ad-rotating service which allows malformed Javascript feign an antivirus check and to get a user to download and run a Trojan, or some new incoming attack on the IPv6 stack that nobody expected (similar to land/ping of death/smurf in IPv4.)

    5. Re:Rediculous by Dog-Cow · · Score: 3, Interesting

      Ford Motor is still running SP2.

    6. Re:Rediculous by Yvan256 · · Score: 1

      Thousands of businesses still use IE6. That should tell you how much they care about new versions, upgrades and service packs.

    7. Re:Rediculous by BigDeek · · Score: 0

      Yah dude... Win2000sp4 ftw... Rock on!

    8. Re:Rediculous by Mister+Whirly · · Score: 1

      It doesn't take a dedicated IT staff to turn Automatic Updates on, which would have downloaded (and possibly automatically installed depending on the settings) SP3. Or even to manually visit Windows Update once in a while, and install the critical patches at the very least. Being an IT support person myself this is probably a biased opinion, but not having sufficient IT support is dumb no matter how small your business is. If you can't afford someone full time, at least get some outside consultants to occasionally look at your security and disaster recovery policies. If you don't have either of those, a catastrophic loss of data without adequate backups will probably spell the end of your company.

      --
      "But this one goes to 11!"
    9. Re:Rediculous by tehcyder · · Score: 1

      Thousands of business still running SP2? Your kidding right, what do they login to their NT 4 Server and connect to the network using token ring?

      Why not? Most small businesses will keep software/hardware going in the same way they would telephones or photocopiers. As long as it is still working, why change it?

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  7. Huh? by Anonymous Coward · · Score: 0

    The summary appears to be a bunch of random, disjoint sentences from the article. Which is OK, since the article itself appears to be just a bunch of sentence fragments cut and pasted together from more reputable news sources.

    Was this really the best article and submission Slashdot received on this topic?

  8. 64bit by Anonymous Coward · · Score: 0

    Can somebody tell if this covers 64bit version which only has SP2 ??

    1. Re:64bit by SCPRedMage · · Score: 1

      Just the 32bit version, 64bit XP is an entirely separate product.

      --
      My sig can beat up your sig.
  9. News? by toleraen · · Score: 5, Interesting

    Microsoft has had their end of life policy available on the web for ages now. Sp2 has been well known to be going EOL. If this threw any sysadmins off-guard...then wow.

    The only reason I can see sticking with SP2 is that SP3 hasn't gotten an EAL rating.

    1. Re:News? by MobyDisk · · Score: 3, Informative

      FYI: EAL ratings I had never heard of this before.

    2. Re:News? by Anonymous Coward · · Score: 0

      Microsoft has had their end of life policy available on the web for ages now. Sp2 has been well known to be going EOL. If this threw any sysadmins off-guard...then wow.

      The only reason I can see sticking with SP2 is that SP3 hasn't gotten an EAL rating.

      I agree with toleraen (831634),

      If any admins get surprised over this one, they're not really admins (well at least not current with MS Technology!)

    3. Re:News? by Anonymous Coward · · Score: 0

      There was a few stories on slashdot a while back. Massive butthurt occurred when lunix fanbois realized windows got the same rating as lunix.

    4. Re:News? by Anonymous Coward · · Score: 0

      hmmm this post remind me of the Hitchhiker's Guide to the Galaxy :)

    5. Re:News? by toleraen · · Score: 1

      Well it's not like Microsoft kept their EOL policy on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard', it is pretty easy to find.

    6. Re:News? by toleraen · · Score: 1

      I bet those fanbois also think that a higher EAL rating means the product is more secure.

  10. obviously... by alien9 · · Score: 1

    said that, is also necessary to state that the millions of XP desktops and ATMs and botnets will not stop working today nor anytime soon.

  11. Cost effectiveness by copponex · · Score: 2, Interesting

    I bought my copy of XP in 2002 for $150. My cost per day is down to about 5 cents, and since it's only a VM now, there's no compelling reason to upgrade to 7. All of the apps work just fine.

    I used to wonder why all of these huge businesses were still on Windows NT in the early naughties. It's because it worked, and the smartest CIOs know the real truth about IT: if it ain't broke, don't try to fix it. There will be unforeseen costs and bugs, and if there's not a "killer app" you're gaining for some competitive edge, you're just wasting time and money.

    1. Re:Cost effectiveness by spidercoz · · Score: 1

      There's a line between cost effective and fucking obsolete crap. Like the federally mandated software one department where I work has to use, designed for use in Windows 3.1, that they refuse to update or replace. And I have to support the shit. It barely runs in XP. We're trying to move to 7 and this fed shit is holding up the whole works.

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    2. Re:Cost effectiveness by denis-The-menace · · Score: 1

      In IT the "if it ain't broke, don't try to fix it" rule only works if your systems do not need to connect to other computers OUTSIDE of you company and do not need/want changes.

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    3. Re:Cost effectiveness by Yvan256 · · Score: 1

      Run it inside a virtual machine, on the OS the program is expecting.

    4. Re:Cost effectiveness by spidercoz · · Score: 1

      that's what we're trying to do now, getting everything to play nice is a pain

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    5. Re:Cost effectiveness by Khyber · · Score: 1

      DOSBox it with a Win3.1 install

      Works perfectly fine.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    6. Re:Cost effectiveness by Civil_Disobedient · · Score: 1

      There's a line between cost effective and fucking obsolete crap.

      Please define "obsolete." Because I always thought something was obsolete when you couldn't use it any more because current conditions are too different from when it came out. In this case, how is XP obsolete? Everything that runs on Vista and Windows 7 runs on XP.

    7. Re:Cost effectiveness by Anonymous Coward · · Score: 0

      No because I can still use MS-DOS 6.22 on my computer, and it might still be useful, but it is definately lacking some features that might be included in newer Windows. So I'd say it's fairly obsolete. And no, everything that runs on Vista and 7 doesn't run on XP, but you wouldn't know if you've only been running XP.

  12. end of MICROSOFT support only by Skarecrow77 · · Score: 1

    if you call microsoft asking for support for something that they have EOL'd, they will be very happy to point you towards a microsoft-trained and microsoft-certified consultant tech in your area who has the expertise to help you.

    Trust me, MS is still getting their money, one way or another.

    1. Re:end of MICROSOFT support only by petermgreen · · Score: 1

      IMO the most significant thing is if you don't upgrade to SP3 you will stop getting security updates. This may be acceptable for some systems that are low risk (e.g. systems that are not connected to a network that can take incoming connections from malicious systems and that do not connect outbound to untrusted machines) but I wouldn't want to be running a system that is not getting security updates as my main OS.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  13. Typical MS forcing their customers to be slaves by Dex1331 · · Score: 0, Troll

    The reason why this is a bad thing is because certain companies may have app compatibility issues with SP3 which is why they didn't install the upgrade in the first place if they were smart and discovered the incompatibilities during a beta phase of testing in their environment. Although I doubt there a many like that, they shouldn't be ignored and cut off simply because they have reasons to not upgrade their SP, especially when you consider the cost of MS corp licensing. This is the same reason why a LARGE majority of companies did not move to Vista and even now Win07 due to their 3rd party apps not working on those OS's. I've seen it first hand with financial software that costs literally millions of dollars to obtain corp licensing for. The developers of this software simply aren't ready on their end and there is no reason why a company should HAVE to upgrade just because MS wants more money or compliance (read slavery) from their customers.

    1. Re:Typical MS forcing their customers to be slaves by mister_playboy · · Score: 2, Insightful

      The developers of this software simply aren't ready on their end and there is no reason why a company should HAVE to upgrade just because MS wants more money or compliance (read slavery) from their customers.

      If you don't like the rules of Microsoft's game, then don't run their software. Other options exist.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    2. Re:Typical MS forcing their customers to be slaves by Anonymous Coward · · Score: 4, Insightful

      Maybe they should contact the company that supports their multi-million dollar financial software to get off their asses and fix their software.

      Microsoft, for all their faults, maintains their OS API quite well. You do not see this sort of API stability from almost any other vendor. API that worked in Windows 95 still works, more or less.

    3. Re:Typical MS forcing their customers to be slaves by macbiv · · Score: 1, Insightful

      Please tell us then, how long should a company support old software? Forever? Until the last user logs off? XP has been out since 2001. Are there other companies that offer support on products almost a decade old? A few of my clients run businesses on Macs, and I can tell you for damn sure that they don't. Maybe you should find fault with the 3rd party vendors that won't release software that works on new platforms. Vista has been out since 06 or 07 are you telling me that 3 years is too little time to get with the program?

    4. Re:Typical MS forcing their customers to be slaves by Dex1331 · · Score: 0

      You can't compare Win 95 to XP. MS was still laying the groundwork for what has been their best PC os, XP and because XP was/has been their best OS it is WIDELY deployed in all of its iterations through out the business world, particularly SP2. Again, most businesses can move to SP3 without issues but there are still some that can't. The ONLY reason they end support for their OS's is to get people to buy their latest and greatest. This is predatory business practice. The customer should be able to decide when they want to upgrade, they shouldn't be forced to do it because of a lack of support. It's sort of like when you buy a car, you can get parts and service for it almost forever and the maker doesn't force you to buy the new one, you buy it when you want to. Frankly I don't give much of a crap because what this business practice results in is more and more customers moving to alternative OS's which is what is necessary and needed. The more MS loses market share, the happier I am because they need to be taken down about a dozen peg and realize who their customers are and how making them spend more money on MS in this economy is a bad thing because when companies have to spend money, people lose their jobs...at least these days lately.

    5. Re:Typical MS forcing their customers to be slaves by Quirkz · · Score: 2, Insightful

      Seconded, more or less. There is no excuse for a business-critical app to not be compatible with SP3 at this point. Hell, there's no reason for it to not be compatible with Vista at this point. Those developers knew the end was coming, just like the rest of us.

    6. Re:Typical MS forcing their customers to be slaves by Dex1331 · · Score: 0

      We aren't talking about Quickbooks here, we are talking about the software that makes Wallstreet run. It is not a simple fix, it's a matter of revamping entire sectors of our financial system. Only an Anonymous Coward would speak of what they do not know and have no clue about. Let's put it this way, Wallstreet is invested in XP, whether it's SP2 or SP3, they are invested in it and THEY DO have a say in how the world goes around, if MS doesn't want to get on board, they could be left behind for such unthinkable things as Linux desktops that are more secure and less buggy connected to higher native environments that are even more realiable. MS drones need to wake up or get left behind...the future is now.

    7. Re:Typical MS forcing their customers to be slaves by Whuffo · · Score: 1

      You've tried to use those stable APIs across major releases? I thought not...

    8. Re:Typical MS forcing their customers to be slaves by cyber-vandal · · Score: 1

      Which cost nothing to migrate to and run everything your business depends on flawlessly I suppose.

    9. Re:Typical MS forcing their customers to be slaves by mr_da3m0n · · Score: 2, Informative

      You do not see this sort of API stability from almost any other vendor. API that worked in Windows 95 still works, more or less.

      Solaris has always done great in this regard. Sun in fact has maintained binary compatibility up to Solaris 10, the current production release. It's even a guarantee.

    10. Re:Typical MS forcing their customers to be slaves by tbuskey · · Score: 1

      Indeed. I've heard of Solaris 2.4 apps (1996ish) running on Solaris 10.

      Or an NFS v1 client on DOS running against an NFS v4 server on Solaris 10.

    11. Re:Typical MS forcing their customers to be slaves by Bungie · · Score: 1

      Dude, if they're not going to apply a stupid patch to Quickbooks so it runs on SP3, they sure as hell aren't going to migrate to Linux.

      --
      The clash of honour calls, to stand when others fall.
    12. Re:Typical MS forcing their customers to be slaves by shutdown+-p+now · · Score: 1

      The ONLY reason they end support for their OS's is to get people to buy their latest and greatest.

      You do realize that "support" means, among other things, patching stuff? Which means writing code. Which means spending money.

      Oh, and the date by which the support would end was immediately known to everyone at the date SP2 was first released - same as with every other Microsoft product.

      This is predatory business practice ... Frankly I don't give much of a crap because what this business practice results in is more and more customers moving to alternative OS's

      Go ahead, find me a software company that doesn't have cut-off dates for product support, OS or otherwise. Bonus points for finding one dealing with FOSS.

  14. July 13th, default option when booting up. by The+Assistant · · Score: 1

    Dear former Windows XP SP2 user:

    Please choose one of the following Linux Alternatives, since we will no longer be supporting Windows XP SP2:

    1) Linux Menu (Offers several effective Alternatives)

    2) Shut off computer, unplug and install you well tested door stop on the door of your choice.

    Thank You,

    Microsoft

  15. So, does that make it Abandonware, Legal to Crack? by Anonymous Coward · · Score: 4, Interesting

    "..the Library of Congress yesterday approved six exemptions to US copyright. The one most pertinent to gamers is that, for archival purposes, copy protection on software no longer being sold or supported by its copyright holder can be cracked.."

    - http://www.joystiq.com/2006/11/23/us-copyright-office-grants-abandonware-rights/

    if not, why not? Seriously, interested..

  16. BOOM HEADSHOT by angelwolf71885 · · Score: 0

    BAM!.. shot through the heart

    1. Re:BOOM HEADSHOT by spidercoz · · Score: 1

      and you're to blame

      --
      "I disapprove of what you say, but I will defend to the death your right to say it." - Evelyn Beatrice Hall, re Voltaire
    2. Re:BOOM HEADSHOT by denis-The-menace · · Score: 1

      you give love

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    3. Re:BOOM HEADSHOT by gstoddart · · Score: 1

      heartburn?

      --
      Lost at C:>. Found at C.
    4. Re:BOOM HEADSHOT by ksemlerK · · Score: 1

      And you're too late.
      Baby, You give love,
      A bad name.


      It made you smile,
      That's what you said.
      You promised me heaven,
      And put me through hell.


      Changed your look,
      Got a hold on me.
      But this is a prison,
      And you can't break free.


      Woahh, you're a loaded gun,
      Woahh, There's no where to run,
      No one to save me from the deed you have done.


      Shot through the heart,
      And you're too late,
      You give love,
      A bad name.


      You played my heart,
      You played your game.
      You give love,
      A bad name
      You give love,
      A bad name.

  17. Who the hell cares? by westlake · · Score: 1, Informative
    I ended support for Microsoft products a few years ago.

    OS Market Share

    Windows XP 63%
    Vista 16%
    Win 7 12%
    OSX 10.6 2%
    OSX 10.5 2%
    Linux 1%

    Windows ME 0.03%
    iPad 0.03%

    OS Share Trends

    Jun 2009 Win 7 1%. Linux 1%.
    Apr 2009 Win 7 12% Linux 1%

    1. Re:Who the hell cares? by Anonymous Coward · · Score: 0

      OS Share Trends

      Jun 2009 Win 7 1%. Linux 1%.

      Apr 2009 Win 7 12% Linux 1%

      Win 7 dropped 11% from Apr 2009 to Jun 2009. Excellent. Linux on the desktop, here we come.

  18. it's on life support by Anonymous Coward · · Score: 0

    I was in a meeting yesterday where I was told that we didn't have to go to sp3 because we got extended support for sp2 till 2012 so we just wait for win7....

    When you are not in an office environment things work differently.

    Hell we are still running NT4! but not for long hopefully...

  19. Oh, Noes! by lbalbalba · · Score: 2, Funny

    Next thing you know, they'll be dropping support for my MSDOS systems too!

  20. SP2 support is not dead... by fortapocalypse · · Score: 1

    It's merely a flesh wound!

  21. The Curse of the Installed Base by NicknamesAreStupid · · Score: 1

    Microsoft and Intel created a distinct competitive advantage by keeping so much software "backward compatible." I can still run DOS on my computer, but of course the only reason I do is to brag about it on /. Now, they are stuck with the monster they created, a giant albatross on their businesses, slowing every step and darkening every decision. Such is life.

    Do you know how God created the universe in six days? He did not have an installed base.

    1. Re:The Curse of the Installed Base by shutdown+-p+now · · Score: 1

      Now, they are stuck with the monster they created, a giant albatross on their businesses, slowing every step and darkening every decision.

      It's true, but at the same time this attention to backwards compatibility is, to a large part, what drives Microsoft's success. It's where you go if you want your solutions to keep working, with minimal effort, in 10 years, on software that's still officially supported by then.

  22. Good Headline by Anonymous Coward · · Score: 0

    A lot of Microsoft fan sites have been omitting the SP2 part from their headlines so it looks like support for XP is ending. The ever fanatical HardOCP used such a headline to try and generate sales for the beloved Microsoft

    http://www.hardocp.com/news/2010/05/10/microsoft_to_end_support_for_windows_2000_xp/

    Anyone who looks at HardOCP occasionally will know this is about par for the course.

  23. Using SP2 to install SP3 by tepples · · Score: 1

    More like, why would you need support for SP2?

    If you need to reinstall XP, and your XP disc didn't have SP3 slipstreamed, then you might need support for getting Windows XP pre-SP3 working in order to install SP3.

  24. On old cheap laptops, new SPs impact performance by cshay · · Score: 1

    My girlfriend had a cheap DELL Inspiron from around the 2003 or 2004 timeframe. When she upgraded to XP SP2 suddenly her performance became just terrible. She told me and I investigated, assuming a virus, or aggressive virus scanning software or something like that.. but nothing out of the ordinary was going on at all. The machine just lacked the horsepower it seemed. Google searches led me to find out that tons of other folks who bought cheap Dells were finding them crawling once they upgraded to XP2 because they could not handle all the additional services that XP2 added. So one reason not to jump to XP3 may be that you are running on very old slow hardware.

  25. still using 2k... by Anonymous Coward · · Score: 0

    ...until IPv4 runs out, that is. :(

  26. Not a Bad Idea by Kozar_The_Malignant · · Score: 2, Funny

    >Microsoft Kills Support

    I've often thought that death was the appropriate punishment for MS Support. I'm glad that they took care of it for us.

    --
    Some mornings it's hardly worth chewing through the restraints to get out of bed.
  27. Re:So, does that make it Abandonware, Legal to Cra by Ash-Fox · · Score: 1

    The only flaw in your plan, is that you can still buy Microsoft Windows 1.1 from Microsoft. You just can't get support for it.

    Windows XP is still sold, just no support is offered, just like all the other previously expired Microsoft OS products.

    --
    Change is certain; progress is not obligatory.
  28. XP did NOT replace 2000 by Matheus · · Score: 1

    Along with the fact the article makes no mention of SP3, Windows XP was NOT a replacement for Win2K. Windows had (and is continuing to preserve) 2 separate tracks:
    3 -> 95 -> 98 -> Me -> XP -> Vista -> 7
    NT -> 2000 -> 2003 -> 2008 -> 2008R2

    The fact they have consolidated the core (as of Vista/2008 as I recall) aside, the repeated mention of the 2000->XP lineage in the article is extremely poor reporting.

    1. Re:XP did NOT replace 2000 by mister_playboy · · Score: 1

      You don't know what you're talking about. The Win 9x line died and was buried with ME. XP, Vista, and 7 and the various server editions are all in the NT line just as 2000 was.

      --
      Do what thou wilt shall be the whole of the Law ::: Love is the law, love under will
    2. Re:XP did NOT replace 2000 by SpryGuy · · Score: 1

      Vista and Windows Server 2008 are from the same code-line/base.

      Windows 7 and Windows Server 2008R2 are from the same code-line/base.

      They have anything to do with the 3->95->98->ME codeline/base.

      --

      - Spryguy
      There are three kinds of people in this world: those that can count and those that can't
    3. Re:XP did NOT replace 2000 by Kalriath · · Score: 3, Informative

      The successor to Windows 2000 Professional was Windows XP. Not Windows Server 2003.

      Millenium was also a consolidation release, designed to make the consumer line look more like the business line so they could merge them. There are three tracks:

      3.x -> 95 -> 98 -> Me -> (Line ends. Continue from XP below)
      NT 4 Workstation -> 2000 Professional -> XP -> Vista -> 7
      NT 3.51 -> NT 4 Server -> 2000 Server -> 2003 -> 2008 -> 2008R2

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    4. Re:XP did NOT replace 2000 by g4b · · Score: 1

      wait

      where is win 2.1x, win32k, winxp home, winxp media center, winxp tablet, win vista home premium, win vista ultimate, os2 warp, mac os 9, ... waitaminute...

    5. Re:XP did NOT replace 2000 by petermgreen · · Score: 1

      Windows had (and is continuing to preserve) 2 separate tracks:
      Windows had two tracks (9x and NT) but the 9x track is dead (last release was ME).

      Windows XP was NOT a replacement for Win2K
      Windows XP professional was a replacement for windows 2000 professional.

      From a technical point of view there were two lines of windows, the conventional windows/9x line and the NT line.

      The conventional/9x line went 3.x --> 95 --> 98 --> ME and then died out. It was replaced by XP home (which is a stripped down version of XP pro)

      The NT line went from NT 3.1 --> NT 3.5 --> NT4 --> 2K -->XP --> 2K3 --> vista/2K8 --> 7/2K8R2 though XP never had a server edition and 2K3 didn't have a 32-bit desktop edition (there were a couple of 64-bit desktop editions released under the XP name but using the 2K3 codebase).

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    6. Re:XP did NOT replace 2000 by Kalriath · · Score: 1

      True. Windows 2 goes before Windows 3.x. OS2 Warp and Mac OS 9 aren't part of the Microsoft product family for obvious reasons, and there's no such thing as Win32k (you mean Win32s, the Windows 3.11 32-bit addon). XP home, tablet, and media centre are all XP. Vista home premium and Vista ultimate are both Vista.

      2000 and NT4 get split because there legitimately are two versions aimed at two different groups.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  29. Re:On old cheap laptops, new SPs impact performanc by Anonymous Coward · · Score: 0

    Google searches led me to find out that tons of other folks who bought cheap Dells were finding them crawling once they upgraded to XP2 because they could not handle all the additional services that XP2 added. So one reason not to jump to XP3 may be that you are running on very old slow hardware.

    Or to not buy cheap Dells in the first place.

  30. Re:On old cheap laptops, new SPs impact performanc by cshay · · Score: 1

    LOL. That was a helpful comment. She was a poor student. MS did add a lot of new services and processes between SP1 and SP2, and did the same between SP2 and SP3, so I felt I should point this out.

  31. More like.... by Anonymous Coward · · Score: 0

    More like "Murders" support!!!!

  32. Re:So, does that make it Abandonware, Legal to Cra by Khyber · · Score: 1

    I think we have a warranty act that would precede that. Maybe it's time it was tested in court.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  33. Re:On old cheap laptops, new SPs impact performanc by SpryGuy · · Score: 1

    SP3 did NOT add "a lot of new services and processes" as compared to SP2. SP3 was merely a roll-up of all the existing patches and fixes since SP2.

    And seriously, a 2004 PC that can't hack running XP SP2? Whatever she paid for it, she paid too damn much for it. That's pathetic.

    --

    - Spryguy
    There are three kinds of people in this world: those that can count and those that can't
  34. Win2K ftw by ReekRend · · Score: 1

    I know I'm not the only one who thinks Win2K was the peak of MS OS. All my computers... I even build a raid server recently with Win2K server.

    1. Re:Win2K ftw by Anonymous Coward · · Score: 0

      You're using 2k server, not 2k3 or -better yet- 2k8?
      How generous of you, the hackers appreciate you're making it easy for them!

    2. Re:Win2K ftw by mysidia · · Score: 1

      Actually, the peak of MS OS... is Windows 2008 Server, core install [CLI-managed, no GUI].

      Win 2k was so crappy, buggy, and had so limited hardware support... I cannot imagine anyone preferring it nowadays for a real workload.

      Server 2008 sure, 2003, ok, maybe... server 2000.. hellno.

      You ever try to do failover clustering or use the file replication service with Win2K in a large scale environment ?

      Actually Windows 2003 is basically Windows 2000 with a lot of Windows 2000's really annoying bugs and limitations fixed.

      I will agree Vista was a flop, but Microsoft has not done anything to screw up their server platform (yet), other than increase the price and licensing complexity.

  35. Re:So, does that make it Abandonware, Legal to Cra by Ash-Fox · · Score: 1

    I think we have a warranty act that would precede that. Maybe it's time it was tested in court.

    I doubt anything will happen since you're purchasing these licenses under the condition you understand it's not an supported product anymore.

    --
    Change is certain; progress is not obligatory.
  36. Options by sharkey · · Score: 2, Funny

    We can still call the Psychic Hotline, though, right?

    --

    --
    "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
  37. Re:So, does that make it Abandonware, Legal to Cra by Khyber · · Score: 2, Interesting

    That would depend upon where you were purchasing it from and whether or not the shop informed you of such at the time of purchase, I'd think. There is some degree of culpability that lies upon the retailer of a product.

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  38. XP Pro SP1: The Last u$oft product for me by seguelucre · · Score: 0, Flamebait

    XP Pro SP1 was the last of their junk I will ever buy. It actually was pretty good for me until SP2 came along and even that wasn't too bad at first, but eventually, because I couldn't keep up with the updates on my 56K line, it got beyond fixing. Even fresh installs didn't work unless I left the update cycle behind (what a concept!). I have never been able to get it up to SP3 level. It amazes me how folks keep clamoring for more of this junkware from u$oft, crapple and others that forces the customer to follow the manufacturer's business plan, OR ELSE! Thankfully I can still say effum! and build my own box with what I want running on it. I have to accommodate my customer's business plans and needs or die...how do these guys get away with reversing the relationship and make billions?

  39. XP DID replace 2000 by mjwx · · Score: 1

    Along with the fact the article makes no mention of SP3, Windows XP was NOT a replacement for Win2K. Windows had (and is continuing to preserve) 2 separate tracks:
    3 -> 95 -> 98 -> Me -> XP -> Vista -> 7
    NT -> 2000 -> 2003 -> 2008 -> 2008R2

    BZZZZT but thanks for playing, XP was not part of the DOS track, it was part of the NT track. The correct Windows lineage is:
    DOS: 1 -> 2 -> 3 (3.1 -> 3.11 -> 3.2 (it exists, check Technet) -> 4 (95 -> 98 -> 98 SE -> ME) -> Death (RIP).
    NT: NT3 -> NT4 -> NT5 (2000 Server, 2000 Workstation) -> NT5.1 (XP, 2003 Server) -> NT6 (Vista, 2008 Server) -> NT7 (Win7).

    XP was a replacement for Windows 2000 Workstation, which was a replacement for Windows NT4 Workstation. It's part of the NT stream and just because it replaced 98 on home machines does not make it part of the DOS/9x stream,

    --
    Calling someone a "hater" only means you can not rationally rebut their argument.
    1. Re:XP DID replace 2000 by ZOMFF · · Score: 1

      Since you're pointing out others mistakes, might as well point out yours: Win7 is not NT7, rather it is NT6.1

      --
      Launch every sig.
  40. Wow, Slashdot has changed a little. by Dex1331 · · Score: 0

    I must be doing something right to get a troll rating for a innocuous post that was only slightly critical of MS. My first post in several years even. I guess I'm behind the times, there once was a time when you could be critical of MS without being marginalized. Don't get me wrong, I've been a sysadmin in hybrid network environments for a few years now and I DO have a soft spot for Windows, regardless of what anybody around here thinks, but I also retain the capacity of having the ability to be critical of an OS and corporation that NEEDS to learn how to change with the times and give users credit for their loyalty even if they aren't buying the new hotness being served up at a price. I see this dumping of SP2 into the bit bucket as an inevitable trend of dumping the entire XP platform which I think is a grave mistake upon the part of MicroSoft and could have a extremely detrimental consequences for the EU as well as the provider. I would just like to see MS be a little less money grubbing and a lot more cognizant of their customers in the long term. Trends being what they are, MS days could very well be numbered in the big picture.

    1. Re:Wow, Slashdot has changed a little. by harryjohnston · · Score: 3, Informative

      Be aware that the end-of-support for SP2 isn't actually news. The date has been known ever since SP3 was released.

    2. Re:Wow, Slashdot has changed a little. by Dex1331 · · Score: 0

      I guess it just reminded me that XP days are numbered and I don't like the thought of it. I've worked in IT for several different companies over the last decade and most of them were XP based at the workstation and many of them may not be able to afford having to buy new corporate licenses. It could mean the loss of IT jobs, in this economy even IT guys like me are losing their jobs. I was one of those unemployed IT guys only a few short weeks ago and it was mainly due to IT downsizing when it happened. If a company is forced to into buying the new fangled MS license that will run them a few hundred thousand they will make up the difference by laying off IT personnel and make the survivors work 2-3 times harder to make up for it.

  41. That's what FreeDOS is for. by Anonymous Coward · · Score: 0

    Eventually XP may be replaced with ReactOS.
    Or better, simply Linux with Wine.

    There's less and less reason to use Windows for
    each passing day. Wine runs more and more
    previously Windows-only software. Every day
    new Linux-native applications replace those
    running in Wine.
    Reality is catching up with Microsoft, fast.

    Some day Vista/7/8/9 will be replaced too.

  42. OK, so can I have my money back? by Anonymous Coward · · Score: 0

    OK, so can I have my money back? I paid for the license and now you're taking it away from me. I gave you money for the license, so I'm taking THAT away. PS you've had plenty of use of my money, invested etc, so you've had use of it and made profit from my money. So we're even on that score.

    1. Re:OK, so can I have my money back? by shutdown+-p+now · · Score: 1

      All the rules - including support lifecycle - were spelled out upfront when you paid the money.

      So that you don't make similar mistakes in the future, here is the page which lists all released Microsoft products with their lifecycle. For example, Win7 mainstream support will be retired in 2015, and extended support for it, in 2020. Keep that in mind when you're shelling out $$$ for that box - though I dare you to find a more long-term policy for consumer desktop OSes.

  43. Who Cares? by Anonymous Coward · · Score: 0

    Its 2010 - Move to windows 7

  44. Re:So, does that make it Abandonware, Legal to Cra by PurplePhase · · Score: 1

    Uh, that was in 2006 - that exemption is now off the books. Unless you have proof that they renewed it.

    Anyone?

  45. Thank Linux by inflamed · · Score: 1

    XP was only available for so long due to the credible threat posed by the oncoming Year of Linux on the Desktop

    1. Re:Thank Linux by tehcyder · · Score: 1
      I thought it was more to do with it potentially becoming the Year of Linux on the Netbook?

      i.e. MS got panicky about Linux being on so many netbooks but they couldn't shoehorn Vista into being a realistic netbook OS so they had to stick with the relatively lightweight XP.

      --
      To have a right to do a thing is not at all the same as to be right in doing it
  46. Re:So, does that make it Abandonware, Legal to Cra by shutdown+-p+now · · Score: 1

    I very much doubt that you can buy Win 3.1 in a shop today.

  47. Re:So, does that make it Abandonware, Legal to Cra by shutdown+-p+now · · Score: 1

    The only flaw in your plan, is that you can still buy Microsoft Windows 1.1 from Microsoft. You just can't get support for it.

    No, you can't buy it, period. That's actually the third stage of support lifecycle for most MS products, of which most people aren't even aware:

    1. General support.
    2. Extended support.
    3. No support, but still available (this is only for products for which there's sufficient demand, so far as I know).
    4. Not available. No, really. Please dig out the body of the programmer who wrote your original app 30 years ago, and make him rewrite the code to work on something that's still supported.

    For example, Windows 3.11 went from #3 to #4 in 2008.