Mainstream support for W2K ends, not support. All this means is that there will be no more functionality changes or enhancements.
Security patchas, phone support, and debug escalations are all still in place, exactly as they are today.
Stop the madness.
"Although Ford was not the first to build a self-propelled vehicle with a gasoline engine, he was, however, one of several automotive pioneers who helped this country become a nation of motorists."
What is more likely than MS delaying the patches is that the USAF (MS's largest customer) will be engaged in actively testing the patches at the same time MS is.
MS has to test for regressions, compatibility all of their products, 3rd party products, drivers, etc, on W2K, XP, 2003, with SQL, Exchange, Oracle, Yahoo, AOL, without all of that, etc. That takes a loooooong time.
Since the USAF has standard builds, they can get involved in the testing with MS and declare the patch safe for them (since they have a much much smaller set of scenarios to test against) before MS is able to declare it safe for most everyone else (remember, MS cannot possibly test every scenario).
So this is probably not MS giving preferential treatment to the USAF and holding out on the rest of the world, it is more likely that the USAF is stepping up and test with MS and is simply able to declare their build to be safe with patches. I would expect to see more large customers of MS get involved like this now that the door is open.
Slashdot Mirror
Really? Windows can't be used for Beowulf clusters? Guess the folks at the Cornell Theory Center are just making shit up. http://www.ctc-hpc.com/
Mainstream support for W2K ends, not support. All this means is that there will be no more functionality changes or enhancements. Security patchas, phone support, and debug escalations are all still in place, exactly as they are today. Stop the madness.
Actually, from your article...
"Although Ford was not the first to build a self-propelled vehicle with a gasoline engine, he was, however, one of several automotive pioneers who helped this country become a nation of motorists."
So no, he *didn't* invent the car.
Dumbass.
What is more likely than MS delaying the patches is that the USAF (MS's largest customer) will be engaged in actively testing the patches at the same time MS is. MS has to test for regressions, compatibility all of their products, 3rd party products, drivers, etc, on W2K, XP, 2003, with SQL, Exchange, Oracle, Yahoo, AOL, without all of that, etc. That takes a loooooong time. Since the USAF has standard builds, they can get involved in the testing with MS and declare the patch safe for them (since they have a much much smaller set of scenarios to test against) before MS is able to declare it safe for most everyone else (remember, MS cannot possibly test every scenario). So this is probably not MS giving preferential treatment to the USAF and holding out on the rest of the world, it is more likely that the USAF is stepping up and test with MS and is simply able to declare their build to be safe with patches. I would expect to see more large customers of MS get involved like this now that the door is open.