Hi rek769
64bit Pups based on Ubuntu, with 32-bit compatibility installed/loaded, have problems with some 32-bit applications; sometimes its necessary to move or symlink libs from one place to another. I don't run Slacko64s often enough to tell you whether they have similar problems. Sometimes resolvable; sometimes not.
Regardless, wondering whether XP's version (or portable version) might be of use, I googled and discovered there was a "sort-of" 64bit Linux version. You'll find it here:
http://www.peazip.org/peazip-linux-64.html. I chose the portable version, which bears this description:
"does not require installation, simply de-compress and start the application clicking on peazip binary natively compiled for x86-64, ia-32 libs required only for some additional backend binaries"
It's at the top of the webpage, the first of three, and bears the name "Portable x86-64 GTK2".
I downloaded it and right-clicked the file which ends with tar.gz, selecting UExtract from the popup menu. That produced a folder named "peazip_portable
+plus other defining symbols too boring to type+Extracted". See below. Within that folder was another folder, same name, but without the "extracted" ending. And within the later folder was an executable appropriately named "peazip". Left-clicking "peazip" started the application without incident. As I'm currently running Xenialpup64, it should provide you the application you need.
Originally In order to keep my SaveFile small, and as I try-out different Puppies and debiandogs --the same application will often be used by more than one*-- I've gotten into the practice of running portable applications from /mnt/home whenever I can. They usually don't care what name is used for their folder.
With peazip, I changed the
interior folder's name to just peazip64 --to distinguish it from a possible 32-bit portable-- and moved it to a folder on /mnt/home I had named Pup-Apps. The Pup-Apps folder is just to maintain a semblance of order on /mnt/home.
As a portable, peazip's folder can be placed anywhere. If you're using a SaveFolder, a frequently used location is /opt. That's where LibreOffice, Chrome and its clones place their folders.
For ease of access, I create menu entry via a pet consisting of three files, a bash script "on the path", an icon in /usr/share/pixmaps, and a desktop file in /usr/share/application which uses the other two and is used to create a menu entry. I've attached the pet. Peazip appears on the Utilities submenu. If you place your peazip folder somewhere else, after installing the pet, browse to its script at /usr/bin and edit this line:
exec /mnt/home/Pup-Apps/peazip64/peazip "$@"
to wherever you've placed the folder. For example,
exec /opt/peazip64/peazip "$@"
being careful with case and spelling.
I'm not certain to what extent you'll still need the 32-bit compatibility SFS. The text from the webpage I quoted can be interpreted a couple of ways. Or, it may depend on the structure of the file you are trying to unzip.
mikesLr
* portables and AppImages, are designed to be "self-contained" and self-referential. The latter may be why it doesn't throw a "wrong ELF" error. Sometimes, however, they may expect a lib to have been included in the base system; or the presence of a framework such as Qt.
Opening a terminal to the executable's location and entering the code "ldd NAME OF EXECUTABLE" can show what is missing.