You can install either 32bit wine, 64bit wine or both. Many windows applications are 32bit in which case you will need the 32bit version of wine. The easiest way to do this on puppy will be within a 32bit system. However, for 64bit systems you may find on this form (or in the package repo) versions built for 64bit system, that can also run 32bit versions of wine if you either install the necessary 32bit libs or load an sfs that contains these libs (e.g. 32bit_compatibility_libs_tahr64.sfs -- see post). The sfs approach to getting the 32bit libs is safer because if you try to install the 32bit libs onto your system there could be name conflicts with the 64 bit libs.
Rather than worrying about such name conflicts one could just install the 32bit wine in a 32bit puppy.
How to Install Wine using "pkg", an example tested in Bionic32-light (19.03+2) - 27 April, 2019
Download (or clone), the following branch of pkg: "add-keep-epoch-env_var_no_global_rtn&fix_issue_74&81"
(part of merge request #22)
If you downloaded an archive (e.g. Pkg-add-keep-epoch-env_var_no_global_rtn&fix_issue_74&81.tar.gz)
then extract it and run the install script that was extracted from the archive.
**Note: you should do the command "uname -a" first and if you see "x86_64" then it means that you are using a 64 bit kernal, either because the puppy has a 64bit kernal or it is running a chroot with a 64bit host. If you have a 32bit puppy running with a 64bit kernal you need to apply the following fix, "Issue #97. wrong arch in ppa2pup_gawk when run as 32bit chroot system in a 64bit host". I'll create an update soon that has this fix. You can probably do this fix after doing the install script but I recommend doing it before hand.
Now set, the default repo. For instance in "upup bionic beaver" (versions 64bit, 32bit and 32bit light), do the following command:
Code: Select all
pkg --repo bionic-main
Now let's add the official wine repos using pkg.
**On older versions of pkg do "pkg add-repo" instead of "pkg --add-repo"
Code: Select all
sandbox# pkg --add-repo https://dl.winehq.org/wine-builds/ubuntu/ bionic main
Enter a repo name, such as 'bionic-DISTRO_SUB_VERSION-main':
bionic-DISTRO_SUB_VERSION-main
"bionic-wine-main"
and then press enter. The latest version of wine in the repo is 5.2.
** We are going to try 5.1. I tried running studiotax on dpupbuster32 with wine 5.2 and while it sort of worked it crached too often. To run studiotax on wine the big thing is that you need a version of wine that is new enough to have windows installer 2.0.
To see what is available for version 5.1 do the command:
Code: Select all
sandbox# pkg --names-all wine | grep 5.1
wine-devel_5.1~bionic
wine-devel-dbg_5.1~bionic
wine-devel-dev_5.1~bionic
wine-devel-i386_5.1~bionic
winehq-devel_5.1~bionic
winehq-staging_5.1~bionic
wine-staging_5.1~bionic
wine-staging-dbg_5.1~bionic
wine-staging-dev_5.1~bionic
wine-staging-i386_5.1~bionic
Code: Select all
pkg --get wine-staging-i386_5.1~bionic
Now install the following package,
Code: Select all
pkg --get wine-staging_5.1~bionic
Finnaly install the package
Code: Select all
pkg -get winehq-staging_5.1~bionic
If one moves the opt folder then they will have to readjust these symlinks. Also in a 64 bit system one might want to create a second folder containing these symlinks but not have the symlink to wine in this folder but instead the symlink to wine64 in this folder. If this is done then any scripts that are symlinked in this directory (e.g. regedit) will be called with respect to the 64bit version of wine rather than the 32bit version of wine.
In either case the wine script will be called with the default wine prefix for either wine (which has a default wine prefix ~/.wine) or wine64 (which has a default wine prefix of ~/.wine64). Since a prefix can only be for either wine or wine64 then presumably specifying the prefix is another way to determine which wine to use.
If one is running wine32 as an underdog (see thread) one might want to consider moving he files in wine-staging-i386_5.1~bionic from /opt/wine-staging to somewhere else like /opt32/wine-staging. If one does this then they will have to copy the scripts from wine-staging_5.1~bionic to this folder, and also should edit the scripts to change the default folder. This move isn't necessary because the path names don't conflict between the 64bit and 32 bit versions. However, it could reduce the risk of a files being blocked. If one does such a move they will also have to adjust the symlinks in winehq-staging_5.1~bionic.
Configure WIne
Configure wine with the command:
Code: Select all
winecfg
Note that this will only configure the 32bit wine prefixe (i.e. ~/.wine) unless you specify the architechre.
Code: Select all
WINEARCH="Winearch=win64 winecfg
No say we want to install StudioTax and we coppied the installer to "~/.wine/drive_c". THen we can do this:
Code: Select all
cd ~/.wine/drive_c
wine ./StudioTax2019Install.exe
Code: Select all
cd /root/.wine/drive_c/Program Files/BHOK IT Consulting/StudioTax 2019
wine ./StudioTax.exe
Notes
-----------------
1 - Installation, works using psandbox (see thread) to create a chroot system. For installation purposes this sandbox can be used as the chroot folder of an ssh server (see thread). Configuring and running wine over ssh might be more problematic because there might be issues with X11 forwarding and wine. If you install wine using a sandbox, you might want to convert the save folder of the sandbox to a sfs file (see thread)
Further Reading
-----------------------------
https://wiki.winehq.org/Wine_User%27s_G ... wine_start