Following instructions here (http://www.myscienceisbetter.info/how-to-create-a-new-wine-prefix-or-bottle.html), I entered this from a terminal:

> WINEARCH=win32 WINEPREFIX=”/home/<your username>/.local/share/wineprefixes/wine-pa” winecfg

Case is important, and the webpage didn’t take this into account. His first “winearch” was lower case. This also appears to be a default place that winetricks looks for wine prefixes. You might be able to put it somewhere else, but then you might have problems getting winetricks to find it.

Then, this to install Phonology Assistant, if you’re in the same folder as the PA Windows installer you’ve downloaded:

WINEARCH=win32 WINEPREFIX=”/home/<your username>/.local/share/wineprefixes/wine-pa” wine start ./Pa-Setup-3.6.2.msi

This installed fine, but when I tried to run it, it complained that I needed to install .Net 4.6.2. Winetricks doesn’t have that — they only have up to .Net 4.0 or something which I didn’t write down — but this webpage (https://appdb.winehq.org/objectManager.php?sClass=version&iId=34702) says it’s possible with a repackaged installer from here (http://repacks.net/forum/viewtopic.php?t=7). This gets installed with:

WINEARCH=win32 WINEPREFIX=”/home/emj/.local/share/wineprefixes/wine-pa” wine ./dotNetFx462_Full_x86_x64_Slim.exe

Then it runs fine — or at least, it can run and access things like exported Toolbox databases — but I had font problems, as described in the other email thread. I tried to install MS core fonts, MS tahoma, and Chinese fonts using winetricks, and tried to manually install a lot of other phonetic fonts into that bottle (located in /home/<my username>/.local/share/wineprefixes/wine-pa/drive_c/windows/Fonts), and tell PA to use one of those fonts, but the problem didn’t seem to be resolved.

Anyway, hopefully this will be helpful if anyone else is trying to run PA without a virtual machine. I’ve also submitted this information to the WineHQ app database for PA.