Jump to content

Recommended Posts

Posted

PKHeX on Mac
A User Friendly Guide for WINE
pkmac.png.8ac9f26b5e2a2e95721f46af8e0765eb.png

Intro
This guide will hopefully clarify a few things regarding WINE and PKHeX running on MacOS as well as help anyone start from scratch with WINE [in order to run PKHeX].  WINE is a fickle thing; it's not guaranteed to work (at all) but the success rate these days is impressive!  So, don't get discouraged if things do not work the first time around.  Nothing we do in this guide is permanent, although I encourage you to make a Time Machine backup of your system or at least backup your important data.


With that being said, I have been using WINE for quite some time. Regarding PKHeX, It's going on almost a year and I have yet to experience any depressive issues using WINE to run it.  I have done several clean installs of macOS Sierra and macOS High Sierra in order to give you the most accurate information possible.  If I have missed something or you know any tips or tricks, I would appreciate the feedback!  Also, you'll find only the bare minimum information in this guide of what you will need to get PKHeX up and running.  I say this because without any theming, the app will look like an old school Windows program.  NOTE:  Aesthetics may not be the most important thing to consider (especially if you're in a hurry or maybe don't care) however there are some dependencies (winetricks) that are absolutely necessary for some programs to run.  Fortunately PKHeX isn't too picky.

Choices

  • Download the PKHeX app in the PKHeX for Mac thread
  • Use Winebottler to make a PKHeX.app for yourself
  • Use Wineskin Winery to make a PKHeX.app for yourself (no support here)
  • Use WINE to run the PKHeX executable via Terminal
  • Use a Virtual Machine (VM) or something along those lines (no support here)

 

Winebottler
Pretty straight forward process.  Tick all of the items with arrows next to them, like in the screenshot below.  Also necessary winetricks for PKHeX: dotnet461; corefonts; cjkfonts; tahoma.
589ba9b52b4b0_ScreenShot2017-02-08at6_21_33PM.png.27f251b65775b94bb7ee2e38ce5da643.png
May need to change security preferences to run the app:
System-Preferances-Security-and-Privacy-open-anyway.png.5a5ae3885ed68fb81cc328ef0eadbaf9.png
NOTE:  Winebottler is the fastest, easiest "DIY" option for a beginner. (Some argue that Wineskin Winery is the fastest and most easy way to whip up an app.  I'll say it just depends on your skill level, though I agree.)  Another thing, apps may be less stable than if they were launched using other methods basically because of the lack of options Winebottler has to fine tune things (e.g.; adding a string in the Registry Editor to enable Retina compatibility.)

 

Install WINE on your Mac [Run PKHeX Using Terminal]
Installing WINE on your system using Homebrew is the most noob-friendly way [to install WINE on Mac] that I have found, so let us just use that.  To start, I'll tell you that you will be installing 4-5 minuscule things on your Mac; Xcode CLT, Homebrew Package Manager, XQuartz, WINE, and  some Winetricks depending on the executable your are attempting to run.  In this instance, our target is PKHeX.  

So onto the first thing, Homebrew.  Before you can use "brew commands" in Terminal, you must have Xcode Command Line Tools installed.  If you already have Xcode installed on your Mac, you should be peachy.  If not, no problem!  Open Terminal to get started!

Xcode CLT:

xcode-select --install

If you're asked to agree to Xcode's ToS, next type:

sudo xcodebuild -license

Homebrew Package Manager:

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

When that finishes up, you'll want to make sure everything is in order:

brew doctor

For future reference, you can update Homebrew using:

brew upgrade

XQuartz:

brew cask install xquartz

WINE:

brew install wine
brew upgrade wine # For future reference

That will create a 64-bit WINEPREFIX which will be located at:

~/.wine

NOTE:  If you would rather use the developer version of WINE, use these instead:

brew install wine --devel
brew upgrade wine --devel # For future reference

Winetricks:

brew install cabextract
brew install winetricks
brew upgrade winetricks # For future reference

NOTE:  You DO NOT need to install every winetrick available, just the ones your programs depend on to function.  For PKHeX, you will need to install these; dotnet461, corefonts, cjkfonts, and tahoma (why not).

Install the "tricks":

winetricks "trick"
# (e.g.; winetricks dontnet461)

Complete list of Winetricks

  Reveal hidden contents

For some, the winetricks process will be easier with a GUI.  I suggest installing Zenity if you want one:

brew install zenity

# After installation finishes, you will have a neat GUI for winetricks. Use:

winetricks --gui

 

Attention
Okay, this is important, so listen up.  It's a known issue that .NET Framework 4.5 and up, (dotnet45 and up) does not install properly on a 64-bit WINEPREFIX, which was installed by default earlier (brew install wine). That is okay because a 64-bit WINEPREFIX may come in handy in the future.  To get around this issue, you will create a 32-bit WINEPREFIX.  

Creating the 32-bit prefix:

WINEPREFIX=~/.wine32 WINEARCH=win32 wine wineboot

You will now have a 32-bit prefix located at:

~/.wine32

Next, install the aforementioned winetricks in your new prefix.  It is important that you use these next commands any time you want to run or install ANYTHING inside of that 32-bit WINEPREFIX.  Remember, we need at least .NET Framework 4.6 to run PKHeX and we must install .NET Framework 4.6 in the 32-bit prefix, therefore we will be running PKHeX from inside of the 32-bit prefix. (I know, don't ask, lol)

WINEPREFIX=~/.wine32 WINEARCH=win32 wine "Program.exe"
WINEPREFIX=~/.wine32 WINEARCH=win32 winetricks "trick"

Senario:
You have done all of the above and you're ready to run "PKHeX.exe".  Download PKHeX and remember its location.  It's usually in the Downloads folder.  Open Terminal and change directories to the PKHeX (version) folder. For example:

cd ~/Downloads/PKHeX\ \(171205\)

TerminalCDtoPKHeX.png

Then, run the executable:

WINEPREFIX=~/.wine32 WINEARCH=win32 wine PKHeX.exe

Screen Shot 2017-12-09 at 2.39.31 AM.png

  • 3 weeks later...
  • 1 month later...
Posted (edited)

This is what happens when i try to download dotnet461, pls help

Screen Shot 2018-02-01 at 4.57.26 PM.png

That happens with the other winetricks too, it wont let me download any, it just gives me that same message.

Edited by Rowlet17
  • 3 weeks later...
  • 1 month later...
Posted

cabextract installed correctly for me. However, I cannot get any of the winetricks installed. I've tried "winetricks dotnet461" and "brew install winetricks dotnet461" among other permutations. I'm running OSX Sierra. All other steps went fine until I tried doing any winetrick.

 

Thank you for any assistance.

  • 2 weeks later...
Posted

whenever i make it and i try to open it it just jumps and closes. im nor sure if it is because im using the wrong winetrick or something else. i am using pkhex.7z.  should i use 7zip or dotnet 46 or both.

 

 

thank you for your assistance.                

 

  • 4 weeks later...
Posted

i don't know how to run it on my mac after installing it, this is too complicated for me, someone help, i can't use the winebottler method, and i don't want to use terminal and install so many unnecessary programs just to get one thing to work, just seems to complex just to be able to run a simple application, is there any other way or a video in english explaining how to do this process?

 

  • 2 weeks later...
Posted

OK so I ran "brew install cabextract" and i got the "warning: taskset/cpuset not available on your platform!" error. Could you possibly tell me what it is I did wrong?

Posted

I am trying to install dotnet461 however it says that it cannot be installed because it "conflicts with fotnet40, which is already intalled"

Solutions?

 

 

There is a lot of minor things that could use clarification. For example, do I tick each of boxes that have arrows on them or are some intentionally left unticked even though there is an arrow next to them?

  • 2 weeks later...
Posted

Is there DMG version for the recently updated version of PkHex? I remember downloading a version a few months ago that I could just open with Keka. Thanks. 

  • 2 weeks later...
  • 3 months later...
Posted

I tried the app and the Winebottler method but they both don’t work AT ALL! I’m afraid to try the other methods because I don’t know coding whatsoever... Someone please help me!

The downloadable app won’t even open and Wine won’t open the original .exe version. Using Winebottler to convert it myself didn’t started to work at first but then gets stuck on “installing PkHex.exe”. 

  • 3 weeks later...
  • 4 months later...
Posted (edited)
  On 7/2/2018 at 8:17 PM, ADMH said:

I am trying to install dotnet461 however it says that it cannot be installed because it "conflicts with dotnet40, which is already installed"

Solutions?

Expand  

I recently obtained a new Mac computer. My old one does not run OS X Mojave, but my current one does. On Yosemite, I don't have this issue, and I've just run PKHeX, and it went fine. This did not. I followed the OP instructions to the letter, including paying close attention to the prefix differences, as I did with my previous installations that were successful.

The hell do I do now? 

EDIT 4/14/2019:

Alright, this is a little bit, erm...roundabout so I'll see what I can explain.

1) You have your 32-bit prefix, I'll assume. You'll now need "wget". Type into Terminal the following code exactly: brew install wget.

2) Next, in order to get the winetrick for dotnet461 in the first place, type in: 

  Quote

wget 'https://download.microsoft.com/download/E/4/1/E4173890-A24A-4936-9FC9-AF930FE3FA40/NDP461-KB3102436-x86-x64-AllOS-ENU.exe'

Expand  

3) Next, type in: 

  Quote
env WINEPREFIX=~/.wine32 WINEARCH=win32 wine ~/NDP461-KB3102436-x86-x64-AllOS-ENU.exe
Expand  

 4) Follow installation instructions, then grab the other winetricks as instructed.

Hope this helps!

Edited by BiggestGuyUUUU
Posted

I installed dotnet461 on, I think, both 32- as well as 64-prefix, and it still tells me I have to install .NET 4.6 to run PKHeX.exe. Help?

Posted (edited)
  On 4/14/2019 at 10:26 AM, BiggestGuyUUUU said:

I recently obtained a new Mac computer. My old one does not run OS X Mojave, but my current one does. On Yosemite, I don't have this issue, and I've just run PKHeX, and it went fine. This did not. I followed the OP instructions to the letter, including paying close attention to the prefix differences, as I did with my previous installations that were successful.

The hell do I do now? 

EDIT 4/14/2019:

Alright, this is a little bit, erm...roundabout so I'll see what I can explain.

1) You have your 32-bit prefix, I'll assume. You'll now need "wget". Type into Terminal the following code exactly: brew install wget.

2) Next, in order to get the winetrick for dotnet461 in the first place, type in: 

3) Next, type in: 

 4) Follow installation instructions, then grab the other winetricks as instructed.

Hope this helps!

Expand  

I tried this but Terminal tells me "env: wine : No such file or directory". Help? :(

 

Edit: managed to open it, now it says my operating system is not supported to install the file above. Jeez, how am I going to ever fix this? I tried both Windows 7 as well as W10 by changing settings "winecfg".

 

Edited by Cavier
  • 7 months later...
Posted

Don't know if anyone still pays attention to this thread, but when I try using Winebottler I get the error:

###BOTTLING### Create .app...
###BOTTLING### Enabling CoreAudio, Colors, Antialiasing  and flat menus...
/Applications/WineBottler.app/Contents/Frameworks/WBottler.framework/Resources/bottler.sh: line 134: /Applications/Wine.app/Contents/Resources/bin/wine: Bad CPU type in executable
### LOG ### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.

###ERROR### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.
Task returned with status 1.

If someone knows whats up please help!

Posted (edited)
  On 11/19/2019 at 11:39 AM, killer_memestarr said:

Don't know if anyone still pays attention to this thread, but when I try using Winebottler I get the error:

###BOTTLING### Create .app...
###BOTTLING### Enabling CoreAudio, Colors, Antialiasing  and flat menus...
/Applications/WineBottler.app/Contents/Frameworks/WBottler.framework/Resources/bottler.sh: line 134: /Applications/Wine.app/Contents/Resources/bin/wine: Bad CPU type in executable
### LOG ### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.

###ERROR### Command '/Applications/Wine.app/Contents/Resources/bin/wine regedit /tmp/reg.reg' returned status 126.
Task returned with status 1.

If someone knows whats up please help!

Expand  

Im pretty sure you have to install the stable version of wine found here, https://dl.winehq.org/wine-builds/macosx/download.html,  downgrade to high sierra, or install winetricks.

 

Edited by CoolPerson69420
I had to add something
Posted (edited)

I haven't used pkhex in a year since 3ds days and now I can't open anything.

 

I use wine and I can open the Pkhex_19_09.19.7z file no problem... The PkHex_19_11.15.7z doesn't work just gives me the error. "The application “PKHeX” can’t be opened." Its just an upgrade why won't the new one open? Someone help me. Its just Lets go Eevee on the last update. I need sword and shield!!!!

Update: Fixed!

 

Edited by umleydie
  • 5 weeks later...
Posted
  On 12/9/2017 at 8:35 AM, jasenyoface said:

PKHeX on Mac
A User Friendly Guide for WINE
pkmac.png.8ac9f26b5e2a2e95721f46af8e0765eb.png

Intro
This guide will hopefully clarify a few things regarding WINE and PKHeX running on MacOS as well as help anyone start from scratch with WINE [in order to run PKHeX].  WINE is a fickle thing; it's not guaranteed to work (at all) but the success rate these days is impressive!  So, don't get discouraged if things do not work the first time around.  Nothing we do in this guide is permanent, although I encourage you to make a Time Machine backup of your system or at least backup your important data.


With that being said, I have been using WINE for quite some time. Regarding PKHeX, It's going on almost a year and I have yet to experience any depressive issues using WINE to run it.  I have done several clean installs of macOS Sierra and macOS High Sierra in order to give you the most accurate information possible.  If I have missed something or you know any tips or tricks, I would appreciate the feedback!  Also, you'll find only the bare minimum information in this guide of what you will need to get PKHeX up and running.  I say this because without any theming, the app will look like an old school Windows program.  NOTE:  Aesthetics may not be the most important thing to consider (especially if you're in a hurry or maybe don't care) however there are some dependencies (winetricks) that are absolutely necessary for some programs to run.  Fortunately PKHeX isn't too picky.

Choices

  • Download the PKHeX app in the PKHeX for Mac thread
  • Use Winebottler to make a PKHeX.app for yourself
  • Use Wineskin Winery to make a PKHeX.app for yourself (no support here)
  • Use WINE to run the PKHeX executable via Terminal
  • Use a Virtual Machine (VM) or something along those lines (no support here)

 

Winebottler
Pretty straight forward process.  Tick all of the items with arrows next to them, like in the screenshot below.  Also necessary winetricks for PKHeX: dotnet461; corefonts; cjkfonts; tahoma.
589ba9b52b4b0_ScreenShot2017-02-08at6_21_33PM.png.27f251b65775b94bb7ee2e38ce5da643.png
May need to change security preferences to run the app:
System-Preferances-Security-and-Privacy-open-anyway.png.5a5ae3885ed68fb81cc328ef0eadbaf9.png
NOTE:  Winebottler is the fastest, easiest "DIY" option for a beginner. (Some argue that Wineskin Winery is the fastest and most easy way to whip up an app.  I'll say it just depends on your skill level, though I agree.)  Another thing, apps may be less stable than if they were launched using other methods basically because of the lack of options Winebottler has to fine tune things (e.g.; adding a string in the Registry Editor to enable Retina compatibility.)

 

Install WINE on your Mac [Run PKHeX Using Terminal]
Installing WINE on your system using Homebrew is the most noob-friendly way [to install WINE on Mac] that I have found, so let us just use that.  To start, I'll tell you that you will be installing 4-5 minuscule things on your Mac; Xcode CLT, Homebrew Package Manager, XQuartz, WINE, and  some Winetricks depending on the executable your are attempting to run.  In this instance, our target is PKHeX.  

So onto the first thing, Homebrew.  Before you can use "brew commands" in Terminal, you must have Xcode Command Line Tools installed.  If you already have Xcode installed on your Mac, you should be peachy.  If not, no problem!  Open Terminal to get started!

Xcode CLT:

xcode-select --install

If you're asked to agree to Xcode's ToS, next type:

sudo xcodebuild -license

Homebrew Package Manager:

/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

When that finishes up, you'll want to make sure everything is in order:

brew doctor

For future reference, you can update Homebrew using:

brew upgrade

XQuartz:

brew cask install xquartz

WINE:

brew install wine
brew upgrade wine # For future reference

That will create a 64-bit WINEPREFIX which will be located at:

~/.wine

NOTE:  If you would rather use the developer version of WINE, use these instead:

brew install wine --devel
brew upgrade wine --devel # For future reference

Winetricks:

brew install cabextract
brew install winetricks
brew upgrade winetricks # For future reference

NOTE:  You DO NOT need to install every winetrick available, just the ones your programs depend on to function.  For PKHeX, you will need to install these; dotnet461, corefonts, cjkfonts, and tahoma (why not).

Install the "tricks":

winetricks "trick"
# (e.g.; winetricks dontnet461)

Complete list of Winetricks

  Reveal hidden contents

For some, the winetricks process will be easier with a GUI.  I suggest installing Zenity if you want one:

brew install zenity

# After installation finishes, you will have a neat GUI for winetricks. Use:

winetricks --gui

 

Attention
Okay, this is important, so listen up.  It's a known issue that .NET Framework 4.5 and up, (dotnet45 and up) does not install properly on a 64-bit WINEPREFIX, which was installed by default earlier (brew install wine). That is okay because a 64-bit WINEPREFIX may come in handy in the future.  To get around this issue, you will create a 32-bit WINEPREFIX.  

Creating the 32-bit prefix:

WINEPREFIX=~/.wine32 WINEARCH=win32 wine wineboot

You will now have a 32-bit prefix located at:

~/.wine32

Next, install the aforementioned winetricks in your new prefix.  It is important that you use these next commands any time you want to run or install ANYTHING inside of that 32-bit WINEPREFIX.  Remember, we need at least .NET Framework 4.6 to run PKHeX and we must install .NET Framework 4.6 in the 32-bit prefix, therefore we will be running PKHeX from inside of the 32-bit prefix. (I know, don't ask, lol)

WINEPREFIX=~/.wine32 WINEARCH=win32 wine "Program.exe"
WINEPREFIX=~/.wine32 WINEARCH=win32 winetricks "trick"

Senario:
You have done all of the above and you're ready to run "PKHeX.exe".  Download PKHeX and remember its location.  It's usually in the Downloads folder.  Open Terminal and change directories to the PKHeX (version) folder. For example:

cd ~/Downloads/PKHeX\ \(171205\)

TerminalCDtoPKHeX.png

Then, run the executable:

WINEPREFIX=~/.wine32 WINEARCH=win32 wine PKHeX.exe

Screen Shot 2017-12-09 at 2.39.31 AM.png

Expand  

dont let me download wine, i put  brew install wine and say me no formulae fount it tape

 

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...