Today I tried using winetricks to install the Windows directplay libraries but received the error "Wineserver not found!" From research I did elsewhere, this should not be appearing for me if I built Wine from MacPorts as outlined here: https://wiki.winehq.org/MacOSX
Wine itself seems to work well enough for me, as the .exe I downloaded (Voobly) opens as it should using Wine. Right now the wine directory appears to have been built in my user folder: /Users/mike/.wine
However, from the research I did it seems like I should have a file called "wineserver" somewhere, such as in my /usr/local/bin folder, but it is not there or anywhere else on my computer. When MacPorts builds the /.wine directory where does it put the wineserver?
Winetricks error - Wineserver not found
-
- Level 2
- Posts: 14
- Joined: Wed Mar 16, 2016 3:22 pm
-
- Level 2
- Posts: 14
- Joined: Wed Mar 16, 2016 3:22 pm
Re: Winetricks error - Wineserver not found
I've got some additional information that I am finding odd. I ran "wine regedit" in the Terminal (my intent is to switch the DirectDraw Renderer to GDI to attempt to fix a game video flicker) and got this error:
-bash: wine: command not found
I did some more research and everything I'm reading seems to indicate I should have an executable file "wine" in my /usr/local/bin folder (or in one of the other bin folders in my $PATH), but I checked there and in the others and there is no wine executable. The closest I have is wget, which I installed separately. I did a system-wide search for "wine" and found no executable files with that name -- the closest I got was a wine.in that was located deep within the macports directory (opt/local/var/macports/etc etc etc/x11/wine-crossover/files/wine.in), but the macports website did not seem to indicate this was what I was looking for.
I also added the /.wine directory into my $PATH, with no luck. Again, everything I see people saying elsewhere is that the lack of a wine command in those directories (+ the lack of the wineserver mentioned in the post above) means wine wasn't installed properly. I don't understand how this is possible though, since I have gotten two different applications to run successfully in Wine (Voobly and Uru). I used the WineHQ packages and Macports as recommended, did I miss something?
-bash: wine: command not found
I did some more research and everything I'm reading seems to indicate I should have an executable file "wine" in my /usr/local/bin folder (or in one of the other bin folders in my $PATH), but I checked there and in the others and there is no wine executable. The closest I have is wget, which I installed separately. I did a system-wide search for "wine" and found no executable files with that name -- the closest I got was a wine.in that was located deep within the macports directory (opt/local/var/macports/etc etc etc/x11/wine-crossover/files/wine.in), but the macports website did not seem to indicate this was what I was looking for.
I also added the /.wine directory into my $PATH, with no luck. Again, everything I see people saying elsewhere is that the lack of a wine command in those directories (+ the lack of the wineserver mentioned in the post above) means wine wasn't installed properly. I don't understand how this is possible though, since I have gotten two different applications to run successfully in Wine (Voobly and Uru). I used the WineHQ packages and Macports as recommended, did I miss something?
Re: Winetricks error - Wineserver not found
Nobody here ever recommended installing both the WineHQ packages and Wine from Macports, as well as, it seems, Crossover.
Wine from the WineHQ packages has to be started from the launcher. https://www.winehq.org/pipermail/wine-d ... 11010.html
As for Macports, ask for help on their support channels.
Wine from the WineHQ packages has to be started from the launcher. https://www.winehq.org/pipermail/wine-d ... 11010.html
As for Macports, ask for help on their support channels.
-
- Level 2
- Posts: 14
- Joined: Wed Mar 16, 2016 3:22 pm
Re: Winetricks error - Wineserver not found
I'm referring to this page: https://wiki.winehq.org/MacOSX
First it describes installing the packages, then it says "It is strongly recommended that one use either Homebrew, MacPorts, or Fink to build WINE on OSX. All support the current releases of OSX."
So you're saying if I do the first step (installation of the packages), I do not need to do the second step (building Wine)?
And if that's the case, since I did both of those things, why did neither of them apparently give me the files I need?
(I'm not 100% sure why Crossover is nested in MacPorts since I only just downloaded MacPorts and I tried Crossover a long time ago and thought I deleted it.)
First it describes installing the packages, then it says "It is strongly recommended that one use either Homebrew, MacPorts, or Fink to build WINE on OSX. All support the current releases of OSX."
So you're saying if I do the first step (installation of the packages), I do not need to do the second step (building Wine)?
And if that's the case, since I did both of those things, why did neither of them apparently give me the files I need?
(I'm not 100% sure why Crossover is nested in MacPorts since I only just downloaded MacPorts and I tried Crossover a long time ago and thought I deleted it.)
Re: Winetricks error - Wineserver not found
Correct. Those aren't steps, those are completely separate sections.iPenguin67 wrote: So you're saying if I do the first step (installation of the packages), I do not need to do the second step (building Wine)?
Are you able to run Wine from the launcher, as explained in the email I linked you to above? If not, then something is wrong with your install of the WineHQ packages.And if that's the case, since I did both of those things, why did neither of them apparently give me the files I need?
As for Macports, you have to ask them about any problems. It is a separate project.
-
- Level 2
- Posts: 14
- Joined: Wed Mar 16, 2016 3:22 pm
Re: Winetricks error - Wineserver not found
Thanks, I think I got it and it appears to be working now. I'd recommend updating the documentation to indicate that "Building Wine" is an alternative to "Installing Wine" because this is not intuitive to the layman.