No IE7 for Win 2000?
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
it's been a while since Microsoft encouraged people to switch from 2000/NT to XP. now, same is gonna happend with Vista.
You don't know where to start ? ask a good friend
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
Windows 2000 is six years old. Microsoft's stated support lifecycle is five years of mainstream support, plus five years of extended support if you buy a support contract. (This appears not to apply to VS .NET 2003 on Windows Vista, but I've already complained about that). You can see the support lifecycle policy, and check the dates for a particular product, at http://support.microsoft.com/gp/lifecycle[^]. Mainstream support for Windows 2000 (Professional) ended on 30 June 2005. Microsoft are promising to put security updates on Windows Update for two years after mainstream support ends, and on the Microsoft download site until the end of extended support. That means that the last set of patches to go on Windows Update will be on 10 July 2007 (they have extended it to the next scheduled patch day after end of support, which is normally the second Tuesday of the month). IE7 is a bit of a half-and-half. It is mostly a feature, not security, update, although there are a number of defence-in-depth changes. I get the feeling that while the IE team has been recreated, it doesn't have the resources that it had five years ago, and therefore they've reduced the testing matrix to just the five operating systems listed. Since Windows XP has something over 80% of usage share according to most online web server statistics (with Windows 2000 below 10%), it's understandable that they would target the newer systems.
Stability. What an interesting concept. -- Chris Maunder
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
On the toolbar project I just finished, we targeted IE7 but also tested under IE6 for just this reason. Although W2K users won't be able to use multiple tabs because they're running IE6, the toolbar functionality is the same for both versions. My understanding is that the basic architecture hasn't changed since IE5.
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
There should be no reason it won't work on Win2K. The new FireFox doesn't have any problems with "legacy" versions of Windows (going all the way back to Win98). Maybe it's time for you to switch to FireFox.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
There should be no reason it won't work on Win2K. The new FireFox doesn't have any problems with "legacy" versions of Windows (going all the way back to Win98). Maybe it's time for you to switch to FireFox.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Given that you're a stickler for details, I feel compelled to amend your statement. :)
John Simmons / outlaw programmer wrote:
There should be no reason it won't work on Win2K.
You doubtless meant to say, "no technical reason," of course. Marketing strategy constitutes a reason. I may not agree with it, and I may be inclined to compare the ethics of such reasoning with that of a used car dealer, but a reason it is, nonetheless. If Microsoft was driven by technical rather than marketing considerations, we'd be looking at a very different operating system today. They'd probably also be out of business if they let the geeks do the driving.
Author of The Career Programmer and Unite the Tribes www.PracticalStrategyConsulting.com
-
There should be no reason it won't work on Win2K. The new FireFox doesn't have any problems with "legacy" versions of Windows (going all the way back to Win98). Maybe it's time for you to switch to FireFox.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001They claim that the technical reason is that it uses new APIs added in Windows XP SP2 - things like the Attachment Execution Services. There is of course no reason that that could not have been back-ported to Windows 2000, or the presence of the API tested for, but they simply decided that Windows XP SP2 would be the oldest version they would support.
Stability. What an interesting concept. -- Chris Maunder
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
We should remember that originally IE7 wasn't even gonna be available for XP, yet alone 2k! It was FF that made them change their mine. If you want tabbed browsing but still want to use IE you could always try Avant Browser http://www.avantbrowser.com/[^] BTW, MS stopped releasing new products for Win2k ages ago. VS 2005 was about the last.
Kevin
-
Select your operating system
Windows XP Service Pack 2
Windows XP Pro x64 Edition
Windows Server 2003 x64 Edition
Windows Server 2003 Service Pack 1 (SP1)
Windows Server 2003 ia64 EditionIs this step 1 in the planned obsolescence of Windows 2000? :suss:
-
They claim that the technical reason is that it uses new APIs added in Windows XP SP2 - things like the Attachment Execution Services. There is of course no reason that that could not have been back-ported to Windows 2000, or the presence of the API tested for, but they simply decided that Windows XP SP2 would be the oldest version they would support.
Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
There is of course no reason that that could not have been back-ported to Windows 2000
Following up on Duncan's comment; I think there is a financial reason not to have support W2k. Beyond Microsoft wanting people to upgrade, what demand is there really? W2K users already demonstrate an unwillingness to upgrade, would they even bother with IE7? Factor in the costs of testing and distribution and is it really worth it? (I've been faced with this same issue several times. In my case, it was consumer software so the economic decision was much easier to make. Technically, there are just enough truly useful APIs in XP that don't exist in W2K that worrying about the latter would have been a real pain in the neck--knowledge gleaned from actual experience, not theoretical.)
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Windows 2000 is six years old. Microsoft's stated support lifecycle is five years of mainstream support, plus five years of extended support if you buy a support contract. (This appears not to apply to VS .NET 2003 on Windows Vista, but I've already complained about that). You can see the support lifecycle policy, and check the dates for a particular product, at http://support.microsoft.com/gp/lifecycle[^]. Mainstream support for Windows 2000 (Professional) ended on 30 June 2005. Microsoft are promising to put security updates on Windows Update for two years after mainstream support ends, and on the Microsoft download site until the end of extended support. That means that the last set of patches to go on Windows Update will be on 10 July 2007 (they have extended it to the next scheduled patch day after end of support, which is normally the second Tuesday of the month). IE7 is a bit of a half-and-half. It is mostly a feature, not security, update, although there are a number of defence-in-depth changes. I get the feeling that while the IE team has been recreated, it doesn't have the resources that it had five years ago, and therefore they've reduced the testing matrix to just the five operating systems listed. Since Windows XP has something over 80% of usage share according to most online web server statistics (with Windows 2000 below 10%), it's understandable that they would target the newer systems.
Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
Since Windows XP has something over 80% of usage share according to most online web server statistics (with Windows 2000 below 10%), it's understandable that they would target the newer systems.
You mentioned that and I just checked my HintsAndTips.com site which shows for the Windows platform: XP 87.84% 2000 4.87% 2003 3.71% 98 2.43% Vista 1.02% Me 0.13% BTW, Windows is 96.18% of the hits followed by Macs at 3.08% and Linux at .49%.
Rocky <>< Latest Code Blog Post: ASP.NET HttpException - Cannot use leading "..".. Latest Tech Blog Post: Vista, IIS 7 and Visual Studio - Fixed
