<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx</link><description>If you go through the history of DirectX, you'll see
that there is no DirectX 4. It went from DirectX 3 straight
to DirectX 5. What's up with that? After DirectX 3 was released, development on two
successor products took place simultaneously:
a shorter-term</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61651</link><pubDate>Thu, 22 Jan 2004 15:12:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61651</guid><dc:creator>Mike Dimmick</dc:creator><description>I always thought DirectX 4 was the bit-more-than-3 but not quite 5 version that came with Windows NT 4.0 (and couldn't be upgraded).&lt;br&gt;&lt;br&gt;Remarkably, in all the confusion, some games actually worked on NT 4.0 (I'm thinking particularly of Blizzard's Diablo and StarCraft).</description></item><item><title>Whatever happened to Directx 4</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61702</link><pubDate>Thu, 22 Jan 2004 19:58:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61702</guid><dc:creator>Neil's Smaller World</dc:creator><description>Raymond Cheng sheds some light on what happened to DirectX 4. And no, they didn't use NullSoft versioning logic.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61721</link><pubDate>Thu, 22 Jan 2004 17:24:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61721</guid><dc:creator>anon</dc:creator><description>&lt;br&gt;Not to mention the name of interfaces. DirectX6 introduced IDirectDraw4. DirectShow introduced IDirectDraw3 (with a separate direct draw factory object), and so on... What a mess!!&lt;br&gt;&lt;br&gt;</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61724</link><pubDate>Thu, 22 Jan 2004 17:27:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61724</guid><dc:creator>Raymond Chen</dc:creator><description>That's because COM interface conventions use sequential numbers for versions.  So IDirectDraw4 is the fourth version of IDirectDraw. If a version of DirectX doesn't change an interface, then the number doesn't go up.&lt;br&gt;&lt;br&gt;This is what happens when multiple groups have different version numbering schemes - they don't line up.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61725</link><pubDate>Thu, 22 Jan 2004 17:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61725</guid><dc:creator>denny</dc:creator><description>:-)  Sh*t happens, version numbering can be that way.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61731</link><pubDate>Thu, 22 Jan 2004 17:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61731</guid><dc:creator>MilesArcher</dc:creator><description>This is why projects in development should use code names and not version numbers. Then when the marketing dweebs decide on a completely new version numbering system, no one is confused. This has saved us numerous times when marketing has decided to change the number from 15 to 3.0 to 2002 all for the same project</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61829</link><pubDate>Thu, 22 Jan 2004 21:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61829</guid><dc:creator>Jack Mathews</dc:creator><description>Actually, with DirectX when there's a new interface added, it's numbered with the DirectX version number.  Finally.  Which is why there's an IDirectDrawSurface8 now.  I think they fixed that with DX6.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61840</link><pubDate>Thu, 22 Jan 2004 22:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61840</guid><dc:creator>quanta</dc:creator><description>Curiously, if you go into dxdiag, all DirectX versions are version 4 - DirectX 8 is called 4.08something, DirectX 9 is 4.09something, and so forth. I wonder why.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61892</link><pubDate>Fri, 23 Jan 2004 00:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61892</guid><dc:creator>Shane King</dc:creator><description>You should stop with the numbers and start with the codenames, me thinks. ;)&lt;br&gt;&lt;br&gt;Especially stop numbering things after years. That gets really embarassing when the schedule slips.&lt;br&gt;&lt;br&gt;Apple has it right I think: Panther, Jaguar, etc is the naming scheme to use. No matter how many versions get cancelled or how late it eventually slips, you're never left with a gap in your numbering scheme or having to rename a product.&lt;br&gt;&lt;br&gt;And Panther is a much cooler name than 2003. Why oh why didn't windows stick with Chicago, Memphis, etc?&lt;br&gt;&lt;br&gt;(PS: Yes, I know that Apple also calls their versions 10.0, 10.1, 10.2 etc).&lt;br&gt;</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#61925</link><pubDate>Fri, 23 Jan 2004 01:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:61925</guid><dc:creator>Scott</dc:creator><description>Shane,&lt;br&gt;&lt;br&gt;Where will Apple go next? OS 10.20 - calico?&lt;br&gt;&lt;br&gt;Would you buy a future version of windows named after Intercourse, PA?</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#62089</link><pubDate>Fri, 23 Jan 2004 13:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:62089</guid><dc:creator>Darren Winsper</dc:creator><description>Non-numbered versioning schemes can be confusing to, well, anyone.  After all, assume Microsoft end up calling Longhorn Windows FX.  Now, how does XP relate to FX, in the eyes of a user?  In the same vein, short of memorising the sequence, how would you know whether Panther is before or after Jaguar?&lt;br&gt;&lt;br&gt;Numbered versioning schemes have their problems too, unfortunately.  If you go with year-based versioning, what do you do if you're in a new software field and want to make a second release in a year?&lt;br&gt;&lt;br&gt;Just using straight numbers is nice in theory, but can ultimately have problems.  One major problem is there are so many ways to number something.    Another is that users think &amp;quot;the bigger the number, the better&amp;quot;, leading to version inflation.  Then there's no easy way of comparing version numbers.  IE6 vs. Mozilla 1.4, say.  There's differences, but they're both competing in the same field, user-oriented browsers.&lt;br&gt;&lt;br&gt;Versioning's a tricky thing, which is probably why MS keep changing their versioning scheme:)  </description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#62827</link><pubDate>Mon, 26 Jan 2004 01:48:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:62827</guid><dc:creator>Norman Diamond</dc:creator><description>Two questions:&lt;br&gt;&lt;br&gt;1.  Why are DirectX and Direct Draw coupled?&lt;br&gt;&lt;br&gt;In Windows 2000, the Trident 9385 video adapter has a driver built into the Windows 2000 CD, and it used to be listed as compatible.  (Please do not confuse this actual chip with the Trident 9385 reference design which never was listed as compatible.  Please also for the moment ignore the fact that Microsoft changed this listing after around 3 years.)&lt;br&gt;&lt;br&gt;In order to prevent this Microsoft-provided driver from causing Windows 2000 to blue screen, it is necessary to disable both DirectX and Direct Draw.&lt;br&gt;&lt;br&gt;Windows 2000 wasn't supposed to be a gaming platform so no one should care about disabling DirectX.  But why should we have to disable Direct Draw at the same time?&lt;br&gt;&lt;br&gt;(By the way the Trident 9385 video adapter has a working driver built into the Windows XP CD, a mostly working one built into the Windows NT4 CD, and a working one in the Windows 98 CD.  Whatever the bug is, it looks likely to be fixable.)&lt;br&gt;&lt;br&gt;2.  On the other hand, why are DirectX defaults and DirectX recommendations NOT coupled?&lt;br&gt;&lt;br&gt;In Windows Server 2003, the first time you open display properties and look at acceleration, you get to see the initial setting.  This is the amount of acceleration that Microsoft sets by default.&lt;br&gt;&lt;br&gt;If you experiment with moving the slider back and forth, eventually you'll get to see the recommended setting.  This is the amount of acceleration that Microsoft says is recommended.&lt;br&gt;&lt;br&gt;Windows Server 2003 isn't supposed to be a gaming platform, but nonetheless, why did Microsoft not default to its own recommendations?</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#62839</link><pubDate>Mon, 26 Jan 2004 02:39:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:62839</guid><dc:creator>Raymond Chen</dc:creator><description>Sorry I didn't work on that part of DirectX. I don't know the answer either. (Indeed I don't really understand the questions!)&lt;br&gt;&lt;br&gt;But DirectDraw is part of DirectX, isn't it?&lt;br&gt;&lt;br&gt;I think the slider recommendations are just leftovers from XP. I'll check on that part at least.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#63078</link><pubDate>Mon, 26 Jan 2004 18:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:63078</guid><dc:creator>Raymond Chen</dc:creator><description>Yup, the slider recommendation is a leftover from the days when everything was turned on full blast in Server. The recommendation text has been fixed for Longhorn, if that's any consolation. Another example of &amp;quot;That's an easy change&amp;quot; coming back to bite you.</description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#63187</link><pubDate>Mon, 26 Jan 2004 22:52:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:63187</guid><dc:creator>Brian Marshall</dc:creator><description>To answer quanta's question (note the apostrophe, so I'm not talking about the Australian airline....)&lt;br&gt;&lt;br&gt;The 4 is for the OS version. DX Files build as part of the core OS for new OS releases, and so the DX files that shipped with XP had a version that matched the shipped version of XP. All of those had a version of 5.X.X.X. DirectX builds are therefore kept in sync with the OS versions for the major version.&lt;br&gt;&lt;br&gt;I'm guessing you're not running XP. I think the 4 major version was for Windows 2000. </description></item><item><title>re: What happened to DirectX 4?</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#65954</link><pubDate>Mon, 02 Feb 2004 00:16:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:65954</guid><dc:creator>Norman Diamond</dc:creator><description>1/25/2004 6:39 PM Raymond Chen:&lt;br&gt;&lt;br&gt;&amp;gt; But DirectDraw is part of DirectX, isn't it?&lt;br&gt;&lt;br&gt;Sorry I keep forgetting to check.  In Windows 95 days, I thought that DirectDraw existed before DirectX did.  So I thought there was a chance that disabling either DirectDraw or DirectX by itself might provide a workaround for a blue screening driver, I thought it shouldn't be necessary to disable both together.  Of course the slider doesn't allow disabling either one by itself.  Anyway, sorry I keep forgetting to check if DirectDraw is part of DirectX now.&lt;br&gt;&lt;br&gt;1/26/2004 10:40 AM Raymond Chen:&lt;br&gt;&lt;br&gt;&amp;gt; Yup, the slider recommendation is a leftover&lt;br&gt;&lt;br&gt;Actually I've just noticed that the recommendation might even be reasonable.  I installed English language Windows Server 2003 from my personal MSDN subscription on one computer.  Ever since I obeyed this slider recommendation, Windows Explorer has not been getting shut down for access violations and unhandled exceptions.</description></item><item><title>Commenting on this entry is closed.</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#177347</link><pubDate>Thu, 08 Jul 2004 15:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:177347</guid><dc:creator>Raymond Chen</dc:creator><description>Comments close after two weeks. &lt;a target="_new" href="http://weblogs.asp.net/oldnewthing/archive/2004/02/21/77681.aspx"&gt;http://weblogs.asp.net/oldnewthing/archive/2004/02/21/77681.aspx&lt;/a&gt;</description></item><item><title>Pete&amp;#8217;s Latest Interweb creation  &amp;raquo; Blog Archive   &amp;raquo; Sound, and DX history</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#621728</link><pubDate>Thu, 08 Jun 2006 10:38:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:621728</guid><dc:creator>Pete’s Latest Interweb creation  » Blog Archive   » Sound, and DX history</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://www.recursim.com/?p=73"&gt;http://www.recursim.com/?p=73&lt;/a&gt;</description></item><item><title>D??z Kontak &amp;raquo; DirectX versiyonlar??</title><link>http://blogs.msdn.com/oldnewthing/archive/2004/01/22/61647.aspx#2850473</link><pubDate>Fri, 25 May 2007 00:05:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2850473</guid><dc:creator>D??z Kontak » DirectX versiyonlar??</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.duzkontak.com/?p=40"&gt;http://www.duzkontak.com/?p=40&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>