[RELEASE] DirectX 9.0c November 2007 AddOn 0.3.4 - CNC
What does d3dx10.dll do? The installer doesn't install that file so I don't see a reason to include it myself.
There must be a reason they include D3DCompiler_33 and d3dx10_33, it is a DX 9c redistributable and the package is meant for 2000 and XP. Some new games might use them, but not sure about that d3dx10.dll since it doesn't install that.
There must be a reason they include D3DCompiler_33 and d3dx10_33, it is a DX 9c redistributable and the package is meant for 2000 and XP. Some new games might use them, but not sure about that d3dx10.dll since it doesn't install that.
The redistributable is also intended for use on Windows Vista, redxii, which also gets regular DirectX updates for versions 9.0L and 10.
Unless I'm mistaken, d3dx10.dll does not belong on an XP installation.
Unless I'm mistaken, d3dx10.dll does not belong on an XP installation.
Thanks, anyway I have added the file to the addon, then if ever a soft need it, it will find it... but you're right d3dx10.dll is for vista...
BUT
if you open the d3dx10.dll INF file, you will find a reference to the CAB file "DEC2006_d3dx10_00_x86.cab". So it's an old file, build when microsoft was thinking it could run DX10 on XP. If you do some search on google, you will find that this file can be used in order to test some DX10 functions on XP (I find some infos here: http://www.fallingleafsystems.com/forum ... owtopic=97).
So included it it's not a complete mistake because the file was for XP and VISTA at the begining...
but maybe it's only a legend...
BUT
if you open the d3dx10.dll INF file, you will find a reference to the CAB file "DEC2006_d3dx10_00_x86.cab". So it's an old file, build when microsoft was thinking it could run DX10 on XP. If you do some search on google, you will find that this file can be used in order to test some DX10 functions on XP (I find some infos here: http://www.fallingleafsystems.com/forum ... owtopic=97).
So included it it's not a complete mistake because the file was for XP and VISTA at the begining...
but maybe it's only a legend...
File not Found [DirectX 9.0c November 2007 AddOn 0.3.3 - CNC]
and its mirror is referring to a different file [http://rapidshare.com/files/69326093/Di ... NC.7z.html]
And so with "DirectX 9.0c End-User Runtime November 2007 AddOn 0.1 - redxii "
its referring to http://rapidshare.com/files/69315191/Di ... NC.7z.html
and its mirror is referring to a different file [http://rapidshare.com/files/69326093/Di ... NC.7z.html]
And so with "DirectX 9.0c End-User Runtime November 2007 AddOn 0.1 - redxii "
its referring to http://rapidshare.com/files/69315191/Di ... NC.7z.html
Seems rather pointless to put the dx10 files on unless you're a developer coding for that, which I highly doubt any of you are....
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
-
- Posts: 506
- Joined: Sun Feb 26, 2006 4:13 am
Link to my addon:
http://red.caek.org/addons/DirectX_9.0c ... _redxii.7z
MD5: 7FD209CCC268F7188BA3A0CA96ED4151
http://red.caek.org/addons/DirectX_9.0c ... _redxii.7z
MD5: 7FD209CCC268F7188BA3A0CA96ED4151
Re: [RELEASE] DirectX 9.0c November 2007 AddOn 0.3.3 - CNC
Nico, new dx10 test addon haven't 8.3 filenames but 9.3.
About the renaming: the original setup package is for install under windows so the filenames didn't respect the 8.3. As we use it during a half DOS - half windows install part, the renaming is not an option in order to be sure to avoid copy error. Anyway, it's not a real problem ?
For the destination of the d3dcompiler files, it was a mistake, it's fixed now, really thanks for your help.
For the destination of the d3dcompiler files, it was a mistake, it's fixed now, really thanks for your help.
I hope people realize that the only files in the Redists for DX available for download are libraries for 9.0c.
As a result, files with the number 10 in them are not to be confused with being DX 10 files. They just happen to have the number 10 in them.
So, if you are leaving out any files, then you do not have a complete DX 9.0c install.
If it's in the M$ 9.0c Redist, then it is ment for 9.0c, period.
As a result, files with the number 10 in them are not to be confused with being DX 10 files. They just happen to have the number 10 in them.
So, if you are leaving out any files, then you do not have a complete DX 9.0c install.
If it's in the M$ 9.0c Redist, then it is ment for 9.0c, period.
I'm in no position to know for certain, but you may be right about "files with the number 10 in them." They do exist in my XP x64 installation when using the redist. And the following section exists in jun2007_d3dx10_34_x86.inf, which would seem to suggest that they are not for DirectX10.
Also, this may be just a matter of semantics, but the redist is not solely for 9.0c. Vista includes 9.0L and 10, not 9.0c, yet the redist updates Vista too. The last time Microsoft specifically differentiates DirectX redist version numbers is for the October 2005 release. From December 2005 on, it's been more generally named "DirectX End-User Runtimes." 
Code: Select all
; ---- Windows 2000 ----
[4.09.00.0904.00-4.09.00.0904.00_Win2K]
NumberOfFiles=6
Size=1503 ;approximately total file size (Size * 1024 bytes)
CopyCount=2
d3dx10_34_x86_xp.inf, x86_Install

No, the redist IS solely for 9.0c. 9.0L updates may be found in common with 9.0c for some files (in regards to the filenames only), but the files packaged in the redist are exclusive to 9.0c, but the inf's are general purpose.
That's the other difference between the Redist and the Web Update. The Halo 2 cd I have has 9.0L updates for 2 DX files found on an XP machine, but while the version numbers are the same the hashes, checksums and filesizes are different. A web update can more tightly control distribution based on OS detection. And since DX 9 requires some modifications to work on Vista, you won't find a redist for those files, they will only propigate via web update, or including on a Vista-Only DX application that requires it.
Now, once SP1 for Vista goes live, I expect to see some progress in getting DX10 more capable in XP outside of an SDK test gizmo. I want Crysis and Hellgate: London and CoH in DX 10, but I am not shelling out for Vista.
As it stands, incorperating the DX10 addon files to your system will accomplish nothing for those apps which use DX 10. They will not even work for doing SDK stuff. There are too many other core files missing and lets not forget the Driver/Kernel seperation mode and the fact that DX10 in vista wraps OpenGL so you would end up with the same broken OpenGL that Vista has.
That's the other difference between the Redist and the Web Update. The Halo 2 cd I have has 9.0L updates for 2 DX files found on an XP machine, but while the version numbers are the same the hashes, checksums and filesizes are different. A web update can more tightly control distribution based on OS detection. And since DX 9 requires some modifications to work on Vista, you won't find a redist for those files, they will only propigate via web update, or including on a Vista-Only DX application that requires it.
Now, once SP1 for Vista goes live, I expect to see some progress in getting DX10 more capable in XP outside of an SDK test gizmo. I want Crysis and Hellgate: London and CoH in DX 10, but I am not shelling out for Vista.
As it stands, incorperating the DX10 addon files to your system will accomplish nothing for those apps which use DX 10. They will not even work for doing SDK stuff. There are too many other core files missing and lets not forget the Driver/Kernel seperation mode and the fact that DX10 in vista wraps OpenGL so you would end up with the same broken OpenGL that Vista has.
If you're correct then MS is wrong to include Vista under the supported OSes for the redist as stated on the download page. It wouldn't be the first time they've made such mistakes though. 

Microsoft wrote:System Requirements
- Supported Operating Systems: ...Windows Vista; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Business N; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic; Windows Vista Home Basic 64-bit edition; Windows Vista Home Basic N; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Starter; Windows Vista Starter N; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition...
-
- Posts: 65
- Joined: Sun Jun 11, 2006 8:06 am
- Location: Asia
Thanks for keeping this one up to date since Ryan and C64k have been away. Only problem is that the addon is not hiding in the add/remove components accessory.
[sysoc]
DirectX9=ocgen.dll,OcEntry,%maininf%,HIDE,7
^
this
and...
[Optional Components]
DirectX9c
^
this
These must match or the the addon will not HIDE as specified, Easiest fix is to change the entries files, as only one edit is neccesary for the change to take effect instead of two. Good job otherwise. I wouldn't make a disc without it,
[sysoc]
DirectX9=ocgen.dll,OcEntry,%maininf%,HIDE,7
^
this
and...
[Optional Components]
DirectX9c
^
this
These must match or the the addon will not HIDE as specified, Easiest fix is to change the entries files, as only one edit is neccesary for the change to take effect instead of two. Good job otherwise. I wouldn't make a disc without it,
Re: [RELEASE] DirectX 9.0c November 2007 AddOn 0.3.4 - CNC
Updated my package.
DirectX 9.0c End-User Runtime November 2007 AddOn 0.2.1 - redxii
This AddOn contains both DirectX 9.0c and DirectX 10 files (d3dx10.dll not included)
LINK: Download - Mirror
MD5: 962470372C7ADD2844D69594B972CD4F
Size: 5,32 MB
0.2.1: Removed completely unnecessary CAT and INF files; changed case on one file to match web installer
0.2: Fixed the Optional Components to be hidden
0.1: Initial release
Tested also with RVM Integrator 1.5RC2, also works with XP SP3.
DirectX 9.0c End-User Runtime November 2007 AddOn 0.2.1 - redxii
This AddOn contains both DirectX 9.0c and DirectX 10 files (d3dx10.dll not included)
LINK: Download - Mirror
MD5: 962470372C7ADD2844D69594B972CD4F
Size: 5,32 MB
changelog:Builddate: 2008/01/15
Version: 0.2.1
8.3 Names: Yes
0.2.1: Removed completely unnecessary CAT and INF files; changed case on one file to match web installer
0.2: Fixed the Optional Components to be hidden
0.1: Initial release
Tested also with RVM Integrator 1.5RC2, also works with XP SP3.
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
- RogueSpear
- Posts: 1155
- Joined: Tue Nov 23, 2004 9:50 pm
- Location: Buffalo, NY
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
-
- Posts: 1131
- Joined: Wed Sep 14, 2005 11:31 am
Not until March, newsposter. 

It makes no difference to you. Windows XP cannot do anything with DX10. If you have a DX10 card, then the only way to use it's DX10 features, is to use Windows Vista.pen25jf wrote:Hiya, got a question, maybe just because I don't understand:
Got a video card that supports DX10 but running on XPSP2 - which should I use, the normal DX update or the pack with "both" DX9 and 10??
Thanks
There is no reason to have any DX10 files in Windows XP.
Great, thanks for the explanation!Stimpy wrote:It makes no difference to you. Windows XP cannot do anything with DX10. If you have a DX10 card, then the only way to use it's DX10 features, is to use Windows Vista.pen25jf wrote:Hiya, got a question, maybe just because I don't understand:
Got a video card that supports DX10 but running on XPSP2 - which should I use, the normal DX update or the pack with "both" DX9 and 10??
Thanks
There is no reason to have any DX10 files in Windows XP.
A normal installation of dx9 november update installs those files automatically. IMO u should use addon with dx10 files. (Just my opinionStimpy wrote:It makes no difference to you. Windows XP cannot do anything with DX10. If you have a DX10 card, then the only way to use it's DX10 features, is to use Windows Vista.
There is no reason to have any DX10 files in Windows XP.

- Zyx_Maiden
- Posts: 128
- Joined: Mon Mar 12, 2007 9:32 pm
- Location: Québec, Canada
7 posts up!!! 
Edit: Sorry for incomplete information...

Edit: Sorry for incomplete information...

Last edited by Zyx_Maiden on Wed Mar 05, 2008 12:27 am, edited 1 time in total.
If you see dinosaurs, stop using drugs. But, if you don't use drugs, GET THE HELL OUT OF THERE!
Zyx_Maiden wrote:7 posts up!!!
lol maybe YOU should read what i was asking about. i *KNOW* its in march. i was asking -when- in march.
7 posts up directs me to a link.. hmm lets see what it says shall we?
Starting after the August 2007 release of the DirectX SDK, Microsoft will deliver future updates four times per year. The next five releases now planned for delivery are:
* August 2007
* November 2007 (instead of October and December)
* March 2008 (instead of February and April)
* June 2008
* August 2008
interesting! wait.. no its not. it doesnt answer my question at all.
thanks for your help there Zyx_Maiden
Microsoft doesn't specify, ccl0. In fact, the source that I quoted that schedule from has been changed since I quoted it. The information has been removed. Who knows when it'll be updated...
Typically, Microsoft releases the update near the first of the given month. Sometimes a few days early, and sometimes a week or so late. Of course, this was when their schedule was predictable. If I had to hazard a guess, I'd say we should see it any day now.
Now watch as Microsoft makes me a liar.
Typically, Microsoft releases the update near the first of the given month. Sometimes a few days early, and sometimes a week or so late. Of course, this was when their schedule was predictable. If I had to hazard a guess, I'd say we should see it any day now.
Now watch as Microsoft makes me a liar.

Last edited by 5eraph on Fri Apr 02, 2010 5:51 pm, edited 1 time in total.