Jump to content
user_hidden

Microsoft DirectX 9.0c End User Runtime June 2010 9.29.1962 (x86)

Recommended Posts

Microsoft DirectX 9.0c End User Runtime June 2010 9.29.1962 (x86)

Based on Code65536's Directx installation method.

This is a SILENT installer addon for SVCPACK installation

Link: Addon_DirectX32_9.0c_Runtimes_201006.7z

CRC-32: 9c9bf646

MD4: df8c02780d3d436a8c24044297c49ae0

MD5: 9da4defd2975c985ae0aa3723932f266

SHA-1: 8a8f5c33e02c84e36b8caca0161bf789b0d31924

Date: 20100608

OS: WindowsXP (x86)

Size: 12.1 MB

Edited by user_hidden

Share this post


Link to post
Share on other sites

Microsoft DirectX 9.0c End User Runtime February 2010 9.28.1886 (x86)

Based on Code65536's Directx installation method.

This is a SILENT installer addon for SVCPACK installation

Link: Addon_DirectX32_9.0c_Runtimes_201002.7z

CRC-32: 0c7f02b7

MD4: 3e3054da6e55bd4dadaaefdd715aa8c1

MD5: 996644fcdc9102c4adb708223017e5f3

SHA-1: 3d4129a70d0bda0ffc20c3dc21c905b0ad4ee1ba

Date: 20100206

OS: WindowsXP_x86 (32bit only)

Size: 10.3 MB

The link is OFF (ERROR) :(

Share this post


Link to post
Share on other sites

Thank you for redirecting here from redxii.

Already download and its work fine.

Well i'm tried to get iscript(source code) from redxii and file not found.

And would you, please, explain about "Based on Code65536's Directx installation method." or at least link to view the explanation.

I'm newbie :-) and sorry for my bad english.

Thank you.

Share this post


Link to post
Share on other sites

Thank you for redirecting here from redxii.

Already download and its work fine.

Well i'm tried to get iscript(source code) from redxii and file not found.

And would you, please, explain about "Based on Code65536's Directx installation method." or at least link to view the explanation.

I'm newbie :-) and sorry for my bad english.

Thank you.

This installer is not NSIS script like Redxii.

If you are looking for his script package the download is here: RedDXRuntimes.7z

This installer is done using the INF method set out by Code65536.

here is a quote:

Once you peel away all the layers, the DirectX runtime installation is actually quite simple: copy the appropriate files to system32, register some files, and you're done. No security catalogs are needed as all of the DLLs have embedded signatures. There is nothing else in the Windows install process that depends on these runtimes, so it doesn't matter when these runtimes get installed. All these factors make these runtimes a perfect candidate for a switchless installer:

Much smaller integration size: adds just 6 MiB to the final CD size. With multiple versions of the same libraries, there is a lot of code duplication, which means that there would be significant compression wins when using a large continuous dictionary--a perfect showcase for 7zip's solid compression with a large dictionary size. Traditional integration would involve individually compressing each file, which means that you can't take advantage of all this code duplication (similarly, a small dictionary size, like that of RAR, also means that you can't fully take advantage of code duplication).

Simpler integration. Just one file in svcpack and one line to add to svcpack.inf.

Can be used in any context. Makes testing easier as you can run this on any system, at any time, not just during system setup. Can be used to install the runtimes on live systems, etc.

This is one case where a custom switchless installer via svcpack is a clear, unequivocally superior option to a "traditional"/"true" integration.

Share this post


Link to post
Share on other sites

This installer is not NSIS script like Redxii.

If you are looking for his script package the download is here: RedDXRuntimes.7z

This installer is done using the INF method set out by Code65536.

here is a quote:

Once you peel away all the layers, the DirectX runtime installation is actually quite simple: copy the appropriate files to system32, register some files, and you're done. No security catalogs are needed as all of the DLLs have embedded signatures. There is nothing else in the Windows install process that depends on these runtimes, so it doesn't matter when these runtimes get installed. All these factors make these runtimes a perfect candidate for a switchless installer:

Much smaller integration size: adds just 6 MiB to the final CD size. With multiple versions of the same libraries, there is a lot of code duplication, which means that there would be significant compression wins when using a large continuous dictionary--a perfect showcase for 7zip's solid compression with a large dictionary size. Traditional integration would involve individually compressing each file, which means that you can't take advantage of all this code duplication (similarly, a small dictionary size, like that of RAR, also means that you can't fully take advantage of code duplication).

Simpler integration. Just one file in svcpack and one line to add to svcpack.inf.

Can be used in any context. Makes testing easier as you can run this on any system, at any time, not just during system setup. Can be used to install the runtimes on live systems, etc.

This is one case where a custom switchless installer via svcpack is a clear, unequivocally superior option to a "traditional"/"true" integration.

Thank you for the link and explanation.

Thank you.

Regards.

Edited by mangade

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...