I mentioned that Caldera actually sued MS based on the fact that Win9x was still based on DOS in my blog article on the OS/2 2.0 fiasco, because OS/2 never depended on DOS.
Actually IE6 is supported until July 2015 if you count Server 2003. And BTW IE7 is supported until January 2020 if you count Server 2008. I wonder how much it costs to support each version of IE for MS.
A security problem there is that since IE4, IE has been integrated with the system shell. Therefore, IE privileges are shell privileges - anything the user can do, the browser can do. For this reason, I much prefer a browser that is only a browser, not another view of the system shell. A browser that's just a browser can only screw up web pages, not the entire system.
Huh? All process you start after log in have the same privileges as the user you are logged into.
Yea, flash have limited write cycles, so this kind of failure can happen. What would be nice is if RAID controllers were aware of it and were able to rebuild RAID arrays by copying data.
The updated Outlook has to be manually requested as a hotfix, but that update they pulled shortly. The other patches only suffer issues related to failed installation and redetection, which is not a serious problem.
For example, look at the infamous kill OS/2 multi-boot antitrust exhibit. Doesn't matter if MS actually did it, if they were desperate enough to think about such tactics, that proves my point.
Slashdot Mirror
In fact, MS was the one who released the first OS/2 2.0 SDKs to developers in the first place. I wrote a blog article relating to what happened to the project: http://yuhongbao.blogspot.ca/2012/12/about-ms-os2-20-fiasco-px00307-and-dr.html
I mentioned that Caldera actually sued MS based on the fact that Win9x was still based on DOS in my blog article on the OS/2 2.0 fiasco, because OS/2 never depended on DOS.
I think they locked down the local machine zone in XP SP2: http://blogs.msdn.com/b/ieinternals/archive/2011/03/23/understanding-local-machine-zone-lockdown-restricted-this-webpage-from-running-scripts-or-activex-controls.aspx
That decision to combine the system shell with the browser is the underlying cause of the severity of many Explorer security issues.
Evidence?
Actually IE6 is supported until July 2015 if you count Server 2003. And BTW IE7 is supported until January 2020 if you count Server 2008. I wonder how much it costs to support each version of IE for MS.
A security problem there is that since IE4, IE has been integrated with the system shell. Therefore, IE privileges are shell privileges - anything the user can do, the browser can do. For this reason, I much prefer a browser that is only a browser, not another view of the system shell. A browser that's just a browser can only screw up web pages, not the entire system.
Huh? All process you start after log in have the same privileges as the user you are logged into.
Off topic, but I wonder what would happen if "profit margin fixing" or similar was legal under the law and allowed?
Yea, it reeks of fundamental flaws that needs to be fixed.
Fact: MS guarantees at least two years of mainstream support for the previous version after a new version of release.
Yea, flash have limited write cycles, so this kind of failure can happen. What would be nice is if RAID controllers were aware of it and were able to rebuild RAID arrays by copying data.
I think Dell had to rely on illegal payments from Intel to meet the mentioned EPS expectations of Wall Street:
http://www.sec.gov/news/press/2010/2010-131.htm
See this blog post:
http://blogs.technet.com/b/office_sustained_engineering/archive/2013/09/11/outlook-folder-pane-disappears-after-installing-september-2013-public-update.aspx
The updated Outlook has to be manually requested as a hotfix, but that update they pulled shortly. The other patches only suffer issues related to failed installation and redetection, which is not a serious problem.
http://www.techpowerup.com/190121/massive-fire-at-sk-hynix-facility-in-wuxi-china.html
http://www.reuters.com/article/2013/09/04/us-hynix-suspension-idUSBRE9830SP20130904
I am referring to the hot corners part, that is why I mentioned RDP.
I think it can be even more painful over RDP. Fortunately MS is going to restore the start button in 8.1.
it's to make (eg.) the next release of Direct3D Windows-8-only thereby "forcing" people to upgrade (LOL!)
The old DirectX redists are dead since XP SP2. Even the Platform Update for Vista is different.
MS was pretty generous and supported even Office 2010 under XP.
Not upgrading machines is one thing, banning them is another and I would not ban a OS just because of the UI.
And don't forget RDP too. Also, they added Shut Down/Restart to this right-click menu.
Customers measure support from time of purchase as does consumer law.
So basing it on the end of sales date? Which one?
then that is unlikely to support XP machines and peripherals.
Unlikely to support *all* XP machines and peripherals.
Posted the same link in a different thread, and got a different response: http://slashdot.org/comments.pl?sid=4126317&cid=44667241
They never intended it to work, just take the better ideas for themselves.
See no evidence for that, they only turned it into a fiasco after Win3.0 released.
For example, look at the infamous kill OS/2 multi-boot antitrust exhibit. Doesn't matter if MS actually did it, if they were desperate enough to think about such tactics, that proves my point.