Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

EdTheGreat

macrumors newbie
Original poster
Aug 11, 2010
7
0
Searsport, ME
I got Wine for my MacBook because I was tired of always having to use Windows to play my favorite games, most of which require DirectX. But I can't install DirectX in Wine! Any help will be greatly appreciated.
 
You didn't create a prefix for Wine files to live in first. You need to do that BEFORE installing DirectX. This is easy enough with WineBottler:
  1. Go to the Wine menulet.
  2. Choose Change Prefix...
  3. Click New
  4. Choose where it should go and what to name it
  5. Click OK
  6. Wait while Wine initializes the new prefix to default settings
 
Once that's done, activate your new prefix by clicking its name in the Change Prefix dialog. Then, install the DirectX runtime as usual.
 
Wine has its own directX implementation. Installing MS DirectX is not a good idea ad can actually break things or make things run worse. It can help with some games, but you shouldn't do it unless the game will not work without it... that doesn't mean the game says it wants directx that you should install it... you should only install it if, and only if the directX in Wine is not working right.

Installing d3dx9 is just using a few dll files from DX9, not installing all of directX... do it if you game errors related to those specific dlls. Most games will run better without MS DirectX 9 installed than with it.
 
is installing the directx prefix in wine/winebottler the same as installing a ."msi"prefix?

if so, i am having trouble running a file with a ".msi" (microsoft installer) prefix.
 
is installing the directx prefix in wine/winebottler the same as installing a ."msi"prefix?

if so, i am having trouble running a file with a ".msi" (microsoft installer) prefix.
No. MSI files DO work in the Wine environment, but you normally have to invoke them via the Wine Command Prompt, not by double-clicking.

This is the command to use:
Code:
msiexec /i drive:\path\to\msi\file

For example, if you put the installer file in a folder called Installers inside the prefix's virtual C drive, and it is called setup.msi, then the command to invoke it is:
Code:
msiexec /i C:\Installers\setup.msi
... just like in Windows.
 
No. MSI files DO work in the Wine environment, but you normally have to invoke them via the Wine Command Prompt, not by double-clicking.

This is the command to use:
Code:
msiexec /i drive:\path\to\msi\file

For example, if you put the installer file in a folder called Installers inside the prefix's virtual C drive, and it is called setup.msi, then the command to invoke it is:
Code:
msiexec /i C:\Installers\setup.msi
... just like in Windows.


thanks for this clarification!

in this case would i need to create a new prefix virtual drive? or is there one already created? i noticed in winebottler one can create a new virtual drive depending on the prefix, but i am uncertain if the ".msi" is native.


regardless thank you for your guidance
 
@wrldwzrd89 type the wine commands in the "wine" command prompt or type the "wine" commands in mac os x terminal?
 
thanks for this clarification!

in this case would i need to create a new prefix virtual drive? or is there one already created? i noticed in winebottler one can create a new virtual drive depending on the prefix, but i am uncertain if the ".msi" is native.


regardless thank you for your guidance
Yes, you need to create a prefix first.
@wrldwzrd89 type the wine commands in the "wine" command prompt or type the "wine" commands in mac os x terminal?
Wine Command Prompt, NOT the Terminal.
I think he means the Wine Command Prompt, not the Terminal prompt.
You are correct.
 
Your not supposed to install DX9/10/ because its already in wine. It also clearly states to NOT install DX because it will fu** it up.
 
Your not supposed to install DX9/10/ because its already in wine. It also clearly states to NOT install DX because it will fu** it up.
Yes, DirectX is already in Wine, BUT the Wine implementation is a bit lacking in some areas. This is why winetricks allows installation of various DLLs to make up for the missing functionality.
 
start.exe (part of Wine) will run msi files as well as .bat or any file type that has an associated installed program for (like a .txt will open in notepad).

You can just do like...
wine start /unix "/path/to/my/program/exectuble.msi"

If you use Wineskin, I have a built in option when you select the file to run to use start.exe if you need/want to.
 
start.exe (part of Wine) will run msi files as well as .bat or any file type that has an associated installed program for (like a .txt will open in notepad).

You can just do like...
wine start /unix "/path/to/my/program/exectuble.msi"

If you use Wineskin, I have a built in option when you select the file to run to use start.exe if you need/want to.
Thanks, I did not know about that little program. That will make my Wine experience easier. :D
 
winebottler

you didn't create a prefix for wine files to live in first. You need to do that before installing directx. This is easy enough with winebottler:
  1. go to the wine menulet.
  2. choose change prefix...
  3. click new
  4. choose where it should go and what to name it
  5. click ok
  6. wait while wine initializes the new prefix to default settings

how do i do that?????????
 
Can someone post a guide with pictures because Im trying to play Rivals of aether and Im having the same trouble with Winebottler/Directx as he is ^
 
OMG thats perfect, how do I "select" my directx file? I double clicked it and it just told me it was being changed?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.