In that command, ~/.wine32 is where in the past I have asked wine to put my 32-bit wine prefix. (But don't paste this into Terminal before knowing the right location of your wine Prefix and making sure that 32-bit not 64-bit is desired) $ WINEARCH=win32 WINEPREFIX=~/.wine32 wine SteamSetup.exe On my PC this would look like downloading SteamSetup.exe to some folder, then opening a terminal there and running the command:. I think that reducing the complexity is still virtuous when we are doing something non-recommended. Given how complex Steam is, Windows_Steam works incredibly well in Wine, so the OP might want to try creating a 32-bit Wine instance and installing SteamSetup.exe there - which takes out PlayOnLinux. I personally can't get my PlayOnLinux to install SteamSetup.exe on a virtual drive at the moment, but the following solution might be helpful to others in the OP's position, given it was already adopting a non-recommended approach. I suspect these differences -could- be overcome by working harder to configure things correctly inside Linux_Steam, and that this is largely about the convenience of which default settings end up being automatically applied. This question has been solved for the OP in the comments by a better way.Īnecdotally, there are sometimes differences between the (recommended) approach of Linux_Steam>Wine>Game and the (non-recommended) approach of Wine>Windows_Steam>Game.
0 Comments
Leave a Reply. |