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?
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.
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.
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.
2008/5/21 Stefan Dösinger stefandoesinger@gmx.at:
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.
Isn't that what we're trying to avoid?
On Wed, May 21, 2008 at 4:45 AM, H. Verbeet hverbeet@gmail.com wrote:
2008/5/21 Stefan Dösinger stefandoesinger@gmx.at:
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.
Isn't that what we're trying to avoid?
From my many hours of looking at this, it seems to be a net positive
to install DirectX.
-Tom
Am Mittwoch, 21. Mai 2008 10:45:50 schrieb H. Verbeet:
2008/5/21 Stefan Dösinger stefandoesinger@gmx.at:
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.
Isn't that what we're trying to avoid?
In the long run we probably want to write a replacement for all the DLLs, mostly for licensing reasons. While the DX runtime can be installed on Linux/OSX, it can't be bundled with any app intended to run on non-windows plattforms.
But I personally prefer installing the full runtime over copying the selected DLLs, because it provides a proper setup for the libraries, like self-registration, other libs like dplay, etc. Self-registration is especially important for directplay, some games check the registry keys(of some DLLs we do not implement yet, hence there's no point in setting them in the wine registry)
What we want to avoid is giving the impression that it is possible to use the native d3d9.dll library with Wine. That's why Roderick didn't like Tom's HOWTO. Tom mentiones that d3d9 will only work builtin, but it is easy to miss this.
2008/5/21 Stefan Dösinger stefandoesinger@gmx.at:
But I personally prefer installing the full runtime over copying the selected DLLs, because it provides a proper setup for the libraries, like self-registration, other libs like dplay, etc. Self-registration is especially important for directplay, some games check the registry keys(of some DLLs we do not implement yet, hence there's no point in setting them in the wine registry)
Sure, but I was under the impression we only care about d3dx9 here, not dplay etc.
Am Mittwoch, 21. Mai 2008 12:40:05 schrieb H. Verbeet:
Sure, but I was under the impression we only care about d3dx9 here, not dplay etc.
That's up to Dan. He's maintaining winetricks, so I won't interfere with his decisions.
Me myself I install DX for these same reasons, but some people on IRC have had objections to me telling people to do it........
http://wine-review.blogspot.com/2008/03/directx-90c-march-2008-redistributab...
And they tell people it will fry their config if they install DX. When in fact if you do it right it only helps!
You will want to set Wine to win2k or dxdiag.exe wont be installed also.
Tom
On Wed, May 21, 2008 at 4:40 AM, Stefan Dösinger stefandoesinger@gmx.at wrote:
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.
On Wed, May 21, 2008 at 1:40 AM, Stefan Dösinger stefandoesinger@gmx.at wrote:
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.
Suits me. How's this look? I just threw in a guess at the dll overrides, I'm hoping you will have something to say there. - Dan
Am Donnerstag, 22. Mai 2008 01:44:33 schrieb Dan Kegel:
On Wed, May 21, 2008 at 1:40 AM, Stefan Dösinger stefandoesinger@gmx.at
wrote:
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.
Suits me. How's this look? I just threw in a guess at the dll overrides, I'm hoping you will have something to say there.
- Dan
Don't set mscoree to n, disable it entirely. The installer doesn't need .NET, but some library it uses(msi?) tries to load it and fails if it is available.
I think I was wrong about wininet: wintrust is the DLL that has to be forced to builtin.
Dan Kegel:
On Wed, May 21, 2008 at 1:40 AM, Stefan Dösinger stefandoesinger@gmx.at wrote:
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.
Suits me. How's this look?
Well, my Seamonkey refuses to show the attachment. ;) Reason is | Content-Type: application/octet-stream; name=winetricks
I have to copy the mail to another folder, close my SM and edit this line manually to
Content-Type: text/plain; name=winetricks
After restarting my SM i am now able to read the attachment. Am i the only one who suffers from application/octet-stream?
Hartmut
On Thursday 22 May 2008, Hartmut Figge wrote:
Dan Kegel:
On Wed, May 21, 2008 at 1:40 AM, Stefan Dösinger stefandoesinger@gmx.at
wrote:
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.
Suits me. How's this look?
Well, my Seamonkey refuses to show the attachment. ;) Reason is
| Content-Type: application/octet-stream; name=winetricks
I have to copy the mail to another folder, close my SM and edit this line manually to
Content-Type: text/plain; name=winetricks
After restarting my SM i am now able to read the attachment. Am i the only one who suffers from application/octet-stream?
Hartmut
Works for me in KMail. It offers to open it in KWrite or save it.
- Neil
-
Dan Kegel -
H. Verbeet -
Hartmut Figge -
Neil Skrypuch -
Stefan Dösinger -
Stefan Dösinger -
Tom Wickline