If you really are mad about some "unethical" FUD posted to CompuServe twenty-five years ago, I'd suggest you move on.
I know it is too late, but my point is that these unethical tactics were worse than working with IBM on OS/2, and I am not defending this JDA. I can dig out other sources if you like.
Sorry for that, there has several mentions of OS/2 recently, and I want to refer to the blog post instead of typing it up again. And there is a reason why I mentioned DR-DOS at the end of the blog post, BTW.
On the technical reasons, I wrote before that "the big difference between plain D3D9 with XPDM and D3D9Ex with WDDM BTW is that WDDM allows multiple apps to use the GPU at the same time. With XPDM, if another app tried to use the GPU, the other app would receive a lost device error on the next DirectX call. The missing "hardware scheduler" in the i915 probably refers to the hardware needed for this."
I think the problems with oversharing should be fixed if possible. Of course, some of the problems are more difficult or impossible to fix, but we should try to fix as many as we can.
Ah, Embedded Standard 2009 and POSReady 2009 is supported until 2019, and is based on XP. When WEPOS SP2 support ended after plain XP SP2 support, they just put up the plain custom support patches without any checks at all. I wonder what MS will do about it this time.
Slashdot Mirror
If you really are mad about some "unethical" FUD posted to CompuServe twenty-five years ago, I'd suggest you move on.
I know it is too late, but my point is that these unethical tactics were worse than working with IBM on OS/2, and I am not defending this JDA. I can dig out other sources if you like.
I linked "Microsoft Munchkins" in the blog article for that reason, and keep in mind that is only one example.
PS: please stop spamming your blog
Sorry for that, there has several mentions of OS/2 recently, and I want to refer to the blog post instead of typing it up again.
And there is a reason why I mentioned DR-DOS at the end of the blog post, BTW.
Well, the unethical tactics was not so good.
Don't forget the MS OS/2 2.0 fiasco, or why did it take 10 years after the 386 was introduced before 32-bit programming became popular:
http://yuhongbao.blogspot.ca/2012/12/about-ms-os2-20-fiasco-px00307-and-dr.html
(notice the mention of DR-DOS in the end)
Yea, MS turned what was originally the OS/2-386 project into an entire fiasco:
http://yuhongbao.blogspot.ca/2012/12/about-ms-os2-20-fiasco-px00307-and-dr.html
Shader Model 3.0 is not required for WDDM.
On the technical reasons, I wrote before that "the big difference between plain D3D9 with XPDM and D3D9Ex with WDDM BTW is that WDDM allows multiple apps to use the GPU at the same time. With XPDM, if another app tried to use the GPU, the other app would receive a lost device error on the next DirectX call. The missing "hardware scheduler" in the i915 probably refers to the hardware needed for this."
And I think that will probably be good enough. For example, would you rather open a Metro app or spit out the unknown file type message?
My personal favorite is the MS OS/2 2.0 fiasco (notice the mention of DR-DOS in the end): http://yuhongbao.blogspot.ca/2012/12/about-ms-os2-20-fiasco-px00307-and-dr.html
Think RDP.
Funny that Google recently acquired Motorola.
Summary is incorrect.
Win8.1 will be released soon, before this will release I think.
I think the problems with oversharing should be fixed if possible. Of course, some of the problems are more difficult or impossible to fix, but we should try to fix as many as we can.
Has anyone modelled the potential impact of XP end of support over time?
Win8.1 fixes some of the problems, and will be released before XP ends support.
Well, more precisely, I think XP entered extended support around Vista SP2 release, and Win7 was months away by then.
Ah, Embedded Standard 2009 and POSReady 2009 is supported until 2019, and is based on XP. When WEPOS SP2 support ended after plain XP SP2 support, they just put up the plain custom support patches without any checks at all. I wonder what MS will do about it this time.
http://www.reddit.com/r/IAmA/comments/1j6qo4/i_am_joseph_bonneau_2013_nsa_award_winner_for/
Early versions of WinNT did support it.
by MS, who took ownership of the 32-bit follow-on OS.
Of course, this was before they turned this OS/2 2.0 project into an entire fiasco that I have very bad words against MS about.
Looks like Activision was almost bankrupt back in 1990:
http://www.nytimes.com/2012/12/16/business/bobby-kotick-of-activision-drawing-praise-and-wrath.html
Ah the MS OS/2 2.0 fiasco. FYI, even MS never intended OS/2 NT to replace OS/2 2.x initially.
Unfortunately, the GitHub interface seems to make this more difficult than selecting one version.