I built box86 and box64 and installed them over the previous version, and I replaced my wine components with the ones from the latest (7.0 RC4). Unfortunately, I still got the segfault when I ran winetricks. I even grabbed a new copy of winetricks (in case the other was somehow corrupt), but that didn’t help. I took a closer look at the winetricks script and it mentioned near the top that there were dependencies to install, so I did that manually in case I was missing something, but it didn’t affect the segfault.
sudo apt install aria2 binutils cabextract fuseiso p7zip-full policykit-1 tor unrar unzip wine xdg-utils xz-utils zenity
Not sure I should be installing wine like that, but it and a few other things were missing and got installed.
But I realized I CAN run winetricks if I go to ~/wine and run
I also managed to install the windows components mentioned above by running
BOX86_NOBANNER=1 ./winetricks -q corefonts vcrun2010 dotnet20sp1
Though it did hang several times with a warning, saying it would hang until all wine processes in prefix=/home/cpi/.wine terminated. So to get past that (after waiting a bit), I manually killed the wineserver -w process and the script continued.
Speaking of scripts, I think the segfault problem was caused by the contents of the wineserver script in /usr/local/bin:
env BOX86_NOBANNER=1 box86 $HOME/wine/winetricks “$@”
I’m guessing that was created by the armbian-gaming script, but I think there’s an error there. I don’t think it should have “box86” on that line since it would be trying to run the script through box86, which doesn’t make any sense. If I remove that, it would just function as a wrapper that would include that environment variable, which I think is what we want.
I didn’t really see any differences with the newer box86/64 binaries, with the exception of one game that used to run and now doesn’t. I haven’t done much testing yet though. And I’m curious to see if the winetricks script changed anything for the better. Seems weird to me that I’m having to kill the wineserver every time the script runs it, but that’s moving things along, so hopefully this will work.