As many Puppys are now 64bit operating systems, while most Windows programs which continue to be useful are 32-bit, the objective is to efficiently run the latter under the former. The Windows programs I need, and/or hoped to have available themselves occupy only 20Mbs +/- of 'storage'.
wiak's reported, https://www.forum.puppylinux.com/viewto ... 902#p65902 the possibility of being able to use 32-bit Windows programs if only 64-bit Wine was installed. Essentially, once installed this command could be run from a terminal:
$ WINEPREFIX=~/.new32prefix WINEARCH="win32" winecfg
creating a 32bit wine-prefix thereby avoiding the need to first create a Linux Multi-Arch system: one under which both 32-bit and 64-bit applications can run; or the employment of a Wine.AppImage which creates a 1500 Mb +/- prefix (folder) even before you install any of your desired programs into it.
'Portablizing' Wine has the advantage that it locates almost all its components on Storage (less than 5 Mbs are within your operating system, itself) and installs programs when necessary (use of portable-programs are not) into the wine-prefix on Storage. Wiak's post engendered the idea of using one of Version2013's Wine64 pets as a source in creating a Portable-Wine64. See, https://www.forum.puppylinux.com/viewto ... 915#p65915 for details.
As a first step to trying to see if one of Version2013's Wine64 bit pets could be portablized, it seems sensible to make certain the above mentioned command would, itself, worked using a Wine64.pet. It does; but only after first creating a 64-bit wine prefix -- /root/.wine -- which --prior to Saving to a SaveFile or Folder where it would occupy the same amount on Store-- weighed in at 1500 Mbs. Creating the 'new32prefix' added another 500Mbs initially occupying RAM.
2,000 Mbs of storage to run a 20 Mb program? If it would run. It didn't. Not even wordpad* which the above command itself created within the 'new32prefix' ran. Even after I configured my Puppy to open an 'exe' mime-type with the wine32.
Maybe I didn't configure it correctly. But I'll leave resolution of that to someone with greater expertise.
For me, when available --it's not under VanillaDpup, likely also not VanillaUpup, but as AFAIK, only those-- the process of first loading and configuring a 32bit-Compatibility SFS, then Registering Wine-portable remains the most efficient --least resource demanding-- method to run Windows programs.
-=-=--=-=--=
* winepad was the only program created within the newwine32 prefix. Such programs as winefile, wineconfig and others which you execute under a wine32 implementation as 32bit programs were absent and would be run as 64-bit programs. This suggests that unless assigned to wine32 via set run action you still couldn't run 32-bit programs.
