I think the proper thing to do is to install the DirectX runtime / redistributable. It installs all the DLLs and registers them in the registry etc.
http://www.microsoft.com/downloads/details.aspx?FamilyID=740AC79A-5B72-447D-...
The newest redist is downloadable without issues, archived older ones need a WGA check. For installing the package, a mscoree="" override is needed, and wininet=builtin, as our wininet defaults to native, which doesn't work for this installer for some reason. You may also want to set ddraw, d3d8, d3d9, dsound, dinput etc. to native temporarily during the installation to have themselves register properly and create various registry entries apps may check. Don't forget to set them back to builtin afterwards...
Technically the application is required to install this, but many apps don't do this, or the installation fails.
Am Mittwoch, 21. Mai 2008 10:27:09 schrieb Tom Wickline:
You could update winetricks at each DX redistributable release the last one was in March. Me myself I would add all the d3d9x_* dlls rather then just two of them, there are older games and benchmark software that needs the older ones as well.
-Tom
On Wed, May 21, 2008 at 3:41 AM, H. Verbeet hverbeet@gmail.com wrote:
2008/5/21 Dan Kegel dank@kegel.com:
So... lots of people are going around installing all of directx, and maybe all they needed was, say, d3d9x_35. That's not good. This sounds like a job for winetricks! But I know nothing about direct3d. Could somebody have a look at this draft and see if it suffices? All I added was d3d9x_35 and d3d9x_36, is that the right set?
They're the right dlls (although the packages should probably be called d3d9x_35 and d3d9x_36 rather than d3d9_35 and d3d9_36), but the trouble with these dlls is that there are quite a few different versions, a new version is released every couple of months, and applications just use whatever is current when they're released/developed.