DirectX 9.0c release failing [Solved]
_def_x_
15 May 2011
It looks like there is little more than a Bing toolbar (and a reworked installer) in the latest DirectX update - Version: 9.29.1974 / Date Published: 4/18/2011 - causing the DirectX Addon Pack to fail. If someone wants to confirm this it would be appreciated. My friend wants to update another easy script, DirectX would be great but not if this is the only change to DirectX 9.0c.
Now, if this is the case, your AutoPatcher DirectX download is giving you the 'Failed Verification' error, downloading the previous version and dropping it into the correct folder should fix the error. For now FileHippo and ZDNET has our version, and as long as the Name, Size, and Hash match the script this should correct the problem.
Note: The specific DirectX file is Microsoft DirectX Redistributable (June 2010) 9.29.1962
File Info:
Script Info:
You want to place the file in \modules\Components\directx_files\, you may need to overwrite the existing file (I would simply delete the wrong one first). Run APUP one last time updating this script if you need the .apm or .rti files. Once the release is Official you're done. If the DirectX release is mixed with other releases and you still have the Unofficial warning, start AutoPatcher - select About -> Release Info, you want to see True for DirectX Addon Pack. The failing releases are False.
If the Bing toolbar issue is incorrect, and it seems worthwhile to update DirectX, and my friend wants to give it a try I will help him - we'll cross that bridge when we get to it.
I figure this will likely matter most (if at all) to Windows XP, maybe 2K users.
Edited by gUiTaR_mIkE, 19 May 2011 - 07:44 PM.
Reason for edit:: Issue Resolved
Now, if this is the case, your AutoPatcher DirectX download is giving you the 'Failed Verification' error, downloading the previous version and dropping it into the correct folder should fix the error. For now FileHippo and ZDNET has our version, and as long as the Name, Size, and Hash match the script this should correct the problem.
Note: The specific DirectX file is Microsoft DirectX Redistributable (June 2010) 9.29.1962
File Info:
Name: directx_Jun2010_redist.exe /// Size: 100273008 /// Hash: 4E41372E8775E8025BE013480B0629B3
Script Info:
Item=directx_Jun2010_redist.exe DetectFile=autopatcher:\modules\Components\directx_files\directx_Jun2010_redist.exe DetectHash=4E41372E8775E8025BE013480B0629B3 DownloadFrom=http://download.microsoft.com/download/8/4/A/84A35BF1-DAFE-4AE8-82AF-AD2AE20B6B14/directx_Jun2010_redist.exe DownloadTo=autopatcher:\modules\Components\directx_files\directx_Jun2010_redist.exe ExpectedSize=100273008 ExpectedHash=4E41372E8775E8025BE013480B0629B3
You want to place the file in \modules\Components\directx_files\, you may need to overwrite the existing file (I would simply delete the wrong one first). Run APUP one last time updating this script if you need the .apm or .rti files. Once the release is Official you're done. If the DirectX release is mixed with other releases and you still have the Unofficial warning, start AutoPatcher - select About -> Release Info, you want to see True for DirectX Addon Pack. The failing releases are False.
If the Bing toolbar issue is incorrect, and it seems worthwhile to update DirectX, and my friend wants to give it a try I will help him - we'll cross that bridge when we get to it.
Edited by gUiTaR_mIkE, 19 May 2011 - 07:44 PM.
Reason for edit:: Issue Resolved
Cristiano
17 May 2011
matching the old version with this one, those files have changed:
DSETUP.dll
dsetup32.dll
dxdllreg_x86.cab
DXSETUP.exe
dxupdate.cab
meaning that the old one has all the new files, but something has changed in those. matching the new version with the old one, those files have changed:
DSETUP.dll
dsetup32.dll
dxdllreg_x86.cab
DXSETUP.exe
dxupdate.cab
same files, none related to directx himself. so, any update to this one is to fix the unofficial issue
[]s
DSETUP.dll
dsetup32.dll
dxdllreg_x86.cab
DXSETUP.exe
dxupdate.cab
meaning that the old one has all the new files, but something has changed in those. matching the new version with the old one, those files have changed:
DSETUP.dll
dsetup32.dll
dxdllreg_x86.cab
DXSETUP.exe
dxupdate.cab
same files, none related to directx himself. so, any update to this one is to fix the unofficial issue
[]s
_def_x_
18 May 2011
Cristiano
18 May 2011
well, it's better fix it
i'm alive, i'm just away. my health has improved, my last exams didn't showed any increase in my kidney problem, so it should be related to stress.
[]s
i'm alive, i'm just away. my health has improved, my last exams didn't showed any increase in my kidney problem, so it should be related to stress.
[]s
_def_x_
18 May 2011
OK, after searching for a conclusive answer regarding the updated DirectX 9 (April 2011 v9.29.1974), I think (hope) I've found it - Article Here!.
Summary:
If the link (in article) produces the same file as the dx script only a small edit is needed.
This is what the directx script produces, is it the same file pointed to in the article?
Summary:
- DXSETUP bugfix only (compatibility issues, improved error handling etc)
- Changes only to dsetup.dll, dsetup32.dll, dxdllreg_x86.cab, dxsetup.exe, and dxupdate.cab (None of the REDIST CABs or the DLLs it deploys have changed from their June 2010 versions)
- The Bing Bar offer is limited to only the Web Installer. The stand-alone installer does not offer nor does it install the Bing Bar
If the link (in article) produces the same file as the dx script only a small edit is needed.
This is what the directx script produces, is it the same file pointed to in the article?
Name: directx_Jun2010_redist.exe / Size: 100271992 / MD5Hash: 7C1FC2021CF57FED3C25C9B03CD0C31AIf we're good to go, I'll have my friend update the directx script and upload it later, and delete this thread...?
Cristiano
18 May 2011
in here, those data match
about the thread, i don't know, close seems better
[]s
about the thread, i don't know, close seems better
[]s



