Tlarhices wrote: > > vitamin wrote: > > BACK to where we started. > > > > WHY and WHO asking people to install native DirectX? > > > > All posts NOT RELATED to answering those _TWO_ questions will be removed. > > > I think for many of them the 'who' doesn't exist. If you install a game under windows at the end it will ask you if you want to install it, it is a standard question where (nearly) everybody answer yes because it can only make the thing work better. > And under windows if you are using a game and have error messages about directX, you just take the last version and update without even thinking about it. > > The main point is installing directX under windows is something normal and people expect it to solve their game problems just like it has always done under windows. So if a windows program has problem using directX under wine, they just think it is the best way to solve their own problem without bothering everybody. > > Maybe it ends up being a bad thing for their wine installation but it is just 'the normal way' under windows. > > One way to solve this problem may be to detect when a user is about to install directX and show a popup explaining clearly than going further may result in more problem than they had before and that it is not a way to solve problems. I'm not talking about blocking directX installation but just showing a warning message people have never seen when trying to install directX before (maybe showing a wine logo and a big "danger" sign) That's a valid point. However point-click installation won't do much damage to Wine. Or should I say should not. If it does - Wine needs to be fixed. But I was more referring to elaborate instructions to override nearly all dlls that can be overridden. That is harmful and should be avoided for the same reasons winetools and ies4linux are bad - they slow down Wine development and lock users to having valid windows license.
