Installing app with the PPM how do I get missing libraries?

[Mike3]

So I was installing a webbrowser from the Puppy Package Manager, but there were like 8 to 12 missing shared libraries so it doesn't work.

Where is the best place to find the missing libraries? Github or slackware.pkgs.com ?

Do I need to download these libraries before installing the browser? How do I download and install them? Do I need a compiler and if so for which programming languages, which compilers? Or could I do it after I installed the browser?

I use a slackware based puppy.

And also, why doesn't the PPM install the necessary packages? I thought this was the point of the PPM.

[mistfire]

pkgs.org

Since slackware does not track dependencies. Use Fedora or Debian as reference for dependencies. If the package name starts with "lib" prefix and the package was not available on slackware try to search the package without "lib" prefix.

Second Option
Use salix repo or configure the PPM to get slackware package database from slackel repo (for slackware current, slackware 14.x package database might be available)

If you are using packages other than slackware such as debian or fedora. Watch for glibc version and libicu used by corresponding distro version. Make sure it was compatible with Puppy's glibc and libicu.

For example:
lxpupsc uses glibc 2.33 it means apps compiled against glibc 2.33 or lower will work.

In case of libicu the version was very version specific, not abi backward compatible.

For example lxpupsc uses libicu 69.1 it means any apps will work if there is libicu 69.1installed (not all apps required libicu). If other libicu version was needed, you need to installed it at the cost of disk space

[Mike3]

Ok, so I downloaded a firefox version directly from the .pkgs site, version 24 or something and it seems to work to a degree, it loads and I can access this site but when I try to go into another page on this site I get error messages. UPDATE now I installed a later version, 45 and now it seems that most sites I use are working. But still I can't get my email provider homepage to load properly... It loads but the reslt is a totally BLANK page... Major problem... Same with palemoon version I use now. It used to work fine. Why?

UPDATE 2: Ok, so now I installed the latest version for Slackware 14.2, it is firefox 68, and now it doesn't start, so I guess missing libraries I will do more tests... I think my puppy should be like 14.2 compatible atleast this is what you get in the PPM.

Could this be because of missing libraries?

Also, how do I remove an app I installed downloading from pkgs.org?

[bigpup]

I use a slackware based puppy.

Which exact one???
Yes it matters with Linux software packages.

For Firefox and using it in any Puppy version.
It is best to get a version of Firefox from this forum.
The ones built by mikewalsh, as portable packages, have the best chance of working on a lot of different Puppy versions.
viewtopic.php?t=4083
They have tweaks that are needed for Firefox running in Puppy Linux.

Welcome to Linux software

[JASpup]

The update error of missing packages in Puppy usually means you didn't update the repository database.

You can get an almost current version of Firefox to run in Puppy. I use versions 68 and 88 in Tahr, which is older than Slackware 14.1. The only problem I have is no audio.

Remove Firefox in the ppm. The fourth button up top is Uninstall, or the first after the big space to the left of the search box.

[mistfire]

The update error of missing packages in Puppy usually means you didn't update the repository database.

You can get an almost current version of Firefox to run in Puppy. I use versions 68 and 88 in Tahr, which is older than Slackware 14.1. The only problem I have is no audio.

Remove Firefox in the ppm. The fourth button up top is Uninstall, or the first after the big space to the left of the search box.

You have to option in order to have audio on firefox

1. Install pulseaudio
2. Use apulse

Also check for ffmpeg version.

[JASpup]

You have to option in order to have audio on firefox

1. Install pulseaudio
2. Use apulse

Also check for ffmpeg version.

I noticed this about pulse:

On 8 March 2017 a new version of Firefox, 52.0, arrived through the update process. This version removed ALSA audio support from Firefox in favour of PulseAudio, something initially not mentioned in the Mozilla release notes. Since Lubuntu 16.04 LTS shipped with only ALSA audio, this broke the default Lubuntu audio system in the default Lubuntu browser. In response to a bug filed, Mozilla developers declined to fix the issue.[123]

https://en.wikipedia.org/wiki/Lubuntu

I think the first system I checked had it installed, but maybe the version is too old. Not sure what apulse is or how to use it. Overall this would make a good how-to.

It seems rather ridiculous to me as audio works in Pale Moon with a Firefox 68 user agent. Whatever I do to Firefox has to work standalone.

[bigpup]

apulse is basically some files in Puppy, that trick programs wanting to use Pulse Audio, into using ALSA to produce sound.
Just enough special files, to make it work.

[Mike3]

Ok, so now I got firefox up and running despite some missing libraries so then I also wanted sound and got pulseaudio from the PPM, but no sound.

UPDATE: So now I installed apulse and it works! Thanks for the help here. I removed pulseaudio also cause it didn't seem to work anyways.

[JASpup]

Ok, so now I got firefox up and running despite some missing libraries so then I also wanted sound and got pulseaudio from the PPM, but no sound.

UPDATE: So now I installed apulse and it works! Thanks for the help here. I removed pulseaudio also cause it didn't seem to work anyways.

apulse but no pulseaudio, got it

i had a similar experience with thunar

glad you shared your experience

[mikewalsh]

@Mike3 :-

Yup, bigpup's right on this one. It's always best to obtain browser packages from the 'Additional Software' section here on the forum.....mainly because we build these to work with Puppy's slightly oddball/unique approach to things. Stuff from the PPM is invariably from the 'parent' distro round which your Puppy is built.....and without fail, these are built to function in the 'non-root', 'ordinary user' mode of the average mainstream distro. Like this, they simply won't function under Puppy, and always require modification.

Slacko Puppies have the added liability of being built around a distro whose policy has always been to include just the bare minimum required to get an OS actually functional. From this point, the user is expected to add everything extra they need/want manually, by themselves. They're incredibly stable Puppies, but require a lot more TLC & 'hand-holding' to get the best out of them. Slackware itself still runs very much along the lines of Linux from the early days. You want a new app/software package? No problemo. Compile it and build it yourself, from scratch...

Even today, Slackware has a huge army of faithful users, who truly believe that this is the only way to run an OS. Build everything yourself.

(I'm a bit of a 'freak' when it comes to browser packages. I've long espoused the idea of running Puppy browsers as 'portables', running from outside the save-file/folder, because to me it simply makes more sense.)

------------------------------------------------------

The other aspect to this is that so far as I'm concerned, the browser is the most important tool in the community's arsenal; it's the 'glue' that holds the community together, and makes it possible for us to stay in touch with each other. So, it makes sense to ensure that browser usage/operation is as fuss-free as possible. Wherever necessary, those portable-browsers from me that require PulseAudio invariably have the 'apulse' emulation library included OOTB, and are set-up to use it.

Fredx181 deserves a mention here, because he's the one who really set me off on the 'portable-browser' path.....a long-held ambition of mine dating back to my very early days with Puppy.

Mike.

[bigpup]

The one bad thing, with the idea of PPM getting stuff from non-Puppy repositories.
The program packages were compiled for the other Linux OS and what that Linux OS already has in it.
Thus Puppy may not have all of what is in the other Linux OS.
The program package can sometimes only have what needs to be added to the other Linux OS.
Thus for using in Puppy, needed dependencies are going to be missing, and need to be added to Puppy.
It can turn into a hunting trip in the internet.

[mistfire]

Thus Puppy may not have all of what is in the other Linux OS.
The program package can sometimes only have what needs to be added to the other Linux OS.
Thus for using in Puppy, needed dependencies are going to be missing, and need to be added to Puppy.

The problem here was package maintainability. A volunteer to maintain curation of those packages

It can turn into a hunting trip in the internet.

pkgs.org is the one-stop place to hunt linux packages.

[PFO]

First Post,

I am trying to install Open Office 4.1.12.

So I seem to have installed Open Office 4.1.12 in 'program files'. The "open office" file is there with the 'he' file inside.

/program files/open office/he/DEBS/openoffice-core04_4.1.12-1_i386.deb

Sorry, I'm a defector from the "crapple - gulag - macrosloth sorftware wars, unfamiliar with the language of the linux world. So, any advice gladly followed.

PFO

[OscarTalks]

Hello PFO

You really need to tell us what version of Puppy you are running.
I would not normally expect to see a "program files" directory in the root of the linux filesystem as your post suggests, so that looks a little strange.
The file at the end of that string is a .deb package which you would install by clicking on it, BUT it is just one of a large number which you need for a full installation of Open Office suite.
If you find all of them and click on all of them it will give a complete installation of sorts, but there are still some modifications which you would need to do to make it all work perfectly in Puppy.
That package file is 32bit. Is your Puppy version 32bit or 64bit?
A better approach would be to look in this forum in the Additional Software section to see if you can find a version which has been put together especially for Puppy.
Anyway, give us a bit more information about your setup and I am sure people will try to help you.

[mikeslr]

@ PFO. Using a 'deb' to Install OpenOffice you are going to run into the same problem szept ran into trying to install LibreOffice. See this thread for solutions: https://www.forum.puppylinux.com/viewto ... 594#p80594

I suggest after uninstalling the deb*, and --per OscarTalks, checking that you have the right architecture for your Puppy, i.e. 32-verses-64-- you do the following:

(1) Install PaDS from here, https://www.forum.puppylinux.com/viewto ... 6355#p6355
(2) Download the OpenOffice deb. DO NOT install it. Right-Click it and from the pop-up menu select UExtract. In the extraction folder you'll find many debs and one folder as shown in this screenshot:

OpenOffice-deb-extracted.png (72.5 KiB) Viewed 1189 times

(3) Right-Click an empty space [anywhere, EXCEPT, the extraction folder or /root] and select New>Directory. Name the new folder OpenOffice-4.1x: you got 4.12, but the latest 32 bit is 4.13. Replace the 'x' with whatever version you're using.
(4) Copy/move all the files into the OpenOffice-4.1x. [Tip: Left-Click an empty space in the extraction folder to focus Rox on it. Hold down the Ctrl-Key and press the 'a' key. Everything in the folder will be high-lighted. Put your mouse-cursor on any highlighted file, Left-Press, Hold, then drag that file into your OpenOffice-4.1x folder and select copy/move. All will be copied/moved. Right-Click the desktop-integration folder now in the OpenOffice-4.1x folder and select delete].
(5) Right-Click the OpenOffice-4.1x folder and from the pop-up menu select Combine to SFS which your installation of PaDS enabled. PaDS will create an SFS named OpenOffice-4.1x.sfs in /root. Don't move it until the md5.txt file shows up indicating the process is complete. Then move it out of /root. If you SFS-load it from there, when you unload it it will be deleted. Eventually, the best place for it is on the same partition as your Puppy's folder.
(6) Install the attached pet to create menu entries.

OpenOffice-menus.pet

(85.4 KiB) Downloaded 46 times

. I created it for use with 4.10. So it will lie about which version you have. Feel free to edit all the Desktop files you'll find in /opt/OpenOffice4/share/xdg. [It can be used with either 32 or 64bit OpenOffice].

-=-=--=
* Actually, now that I see how many debs will show up under Puppy Package Manager>Uninstall, it may be easier to start from scratch by creating a new Savefile/Folder.

[mikewalsh]

@mikeslr :-

I tried using PaDS for the very first time this morning, Mike. I, too, was attempting to build a package from all those tiny debs you obtain from OpenOffice - a very strange way of providing an install, I must say!

Does PaDS have a limit to the number of files it can work with at once? There's 43 .debs in total, and after a few minutes it had gone unresponsive; 5 minutes later, the entire system had frozen solid. Not sure if I did summat wrong, or if I'd overstepped its capabilities.....

(*shrug*)

T'other Mike.

[rockedge]

@PFO to the kennels......

Which Puppy Linux version are we dealing with? Once I know that I can do a run through to install OpenOffice and share what steps I took to do it.

We'll get this going once we know the details !!

[mikeslr]

Mike, I've created SFS using as many as 82 or 83. Obviously, the more source packages the longer it takes. PaDS decompress each package in RAM, copies its content to a work folder in RAM, then proceeds to the next package.

PaDS has limitations. None of the source packages can have the identical name as the SFS being build. Don't use /root as the location for the folder into which the source packages will be placed. That folder can be on a Fat32/ntfs partition as PaDS does all its work in RAM. The source packages can't have any mistakes. For example, sometimes in rebuilding a pet the old pet-specs file created by a prior build will have the wrong name. PaDS can't decompress it, copies it to /root and then creates a SFS which contains the entire /root folder and, obviously, doesn't work. But mounting the SFS will reveal the problem pet. You can decompress that pet, rebuild it and try again.

Were you trying to build the openoffice sfs? I did before posting rather than relying on my flaky memory as to what problems were encountered. Did you include the desktop-integration folder in folder containing the debs? I edited my post when --after Uextraction-- I realized it was there. PaDS can only work with compressed packages.

[PFO]

OK Guys,

Thanx for the suggestions, but here is the box specs:

▶—— BASE SYSTEM ——◀

PC Manufacturer: Hewlett-Packard
Product Name: HP Compaq nx6110 (EK048ES#AKN)

Motherboard Vendor: Hewlett-Packard
Product Name: 3088

BIOS Vendor: Hewlett-Packard
Version: 68DTD Ver. F.0A
Release Date: 07/25/2005

Intel(R) Celeron(R) M processor 1.50GHz
Min/Max Speed: 187/1500 MHz
Current Speed of Core 0:1500 MHz
Core Count: 1

Frequency governor : performance
Freq. scaling driver : p4-clockmod

l1tf:Mitigation: PTE Inversion
meltdown:Vulnerable
spec_store_bypass:Vulnerable
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Mitigation: Full generic retpoline

Sensor status is not available, or required kernel drivers are not loaded.

Memory Allocation:
Total RAM: 485 MB
Used RAM: 460 MB
Free RAM: 25 MB
Buffers: 8 MB
Cached: 259 MB
Total Swap: 1499 MB
Free Swap: 1320 MB

Actual Used RAM: 193 MB Used - (buffers + cached)
Actual Free RAM: 292 MB Free + (buffers + cached)

Linux Kernel: 4.9.163-lxpup-32-pae (i686)
Kernel Version: #1 SMP Thu Mar 14 15:41:19 GMT 2019
Build GCC: 8.3.0
PAE Enabled: Yes

Kernel Command Line:
root=UUID=9b278b90-547b-4323-b372-ccaa6eccfd84 ro fullinstall

Distro: BionicPup32 19.03
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
Bash: 4.4.20
Geany: 1.29
Gtkdialog: 0.8.4
Perl: 5.26.1
Python: 2.7.17
Yad: 0.40.3 (GTK+ 2.24.32)
--
busybox: 1.30.1
dhcpcd: 6.7.1
Glibc: 2.27
OpenSSL: 1.1.1 11 Sep 2018, built on: Wed Nov 24 13:50:16 2021 UTC
wpa_supplicant: 2.6

UNFORTUNATELY, I cannot make sense of the OS without instructions that look like:

SYSTEM
Click on PuPSys Info.
Do this or do that.

OTHERWISE, I cannot decipher instructions like:

viewtopic.php?p=80951#p80951

I suggest after uninstalling the deb*, and --per OscarTalks, checking that you have the right architecture for your Puppy, i.e. 32-verses-64-- you do the following . . .

CURRENT STATUS

DOWNLOADED Open Office 4.1.12

Seem to have installed Open Office 4.1.12 in 'program files'. The "open office" file is there with the 'he' file inside:

mmt/sda1/Program Files/Open Office/he/DEBS/openoffice-core04_4.1.12-1_i386.deb

Somehow I found the "missing libraries" program and it listed the following missing libraries:

MISSING LIBRARIES
File /opt/openoffice4/program/libdbp.so has these missing library files:
libsvt.so libvcl.so libtl.so libsvl.so libsfx.so libdbtools.so libutl.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libuno_sal.so.3
File /opt/openoffice4/program/libadabasui.so has these missing library files:
libuno_cppu.so.3 libuno_cppuhelpergcc3.so.3 libuno_sal.so.3 libdbtools.so libutl.so libsvt.so libtl.so libsvl.so libvcl.so libucbhelper4gcc3.so libsfx.so libootk.so libcomphelpgcc3.so
File /opt/openoffice4/program/libabp.so has these missing library files:
libvcl.so libuno_sal.so.3 libtl.so libuno_cppu.so.3 libsvt.so libsvl.so libsfx.so libuno_cppuhelpergcc3.so.3 libcomphelpgcc3.so libootk.so libutl.so libsvxcore.so libsvx.so
File /opt/openoffice4/program/librptxml.so has these missing library files:
libediteng.so libsvxcore.so libxo.so libvcl.so libutl.so libtl.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libucbhelper4gcc3.so libsfx.so libsvl.so libsot.so libuno_sal.so.3 libediteng.so libsvxcore.so libsvx.so libfwe.so libsfx.so libtl.so libi18nisolang1gcc3.so libsvl.so libsvt.so libutl.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvcl.so libootk.so libvos3gcc3.so libuno_sal.so.3 libsvxcore.so libsvx.so libsfx.so libsvt.so libfwe.so libootk.so libvcl.so libsvl.so libsot.so libutl.so libtl.so libucbhelper4gcc3.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvos3gcc3.so libuno_sal.so.3 libdba.so
File /opt/openoffice4/program/libdbu.so has these missing library files:
libsvxcore.so libsvx.so libsfx.so libsvt.so libfwe.so libootk.so libvcl.so libsvl.so libsot.so libutl.so libtl.so libucbhelper4gcc3.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvos3gcc3.so libuno_sal.so.3 libdba.so
File /opt/openoffice4/program/librpt.so has these missing library files:
libediteng.so libsvxcore.so libsvx.so libfwe.so libsfx.so libtl.so libi18nisolang1gcc3.so libsvl.so libsvt.so libutl.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvcl.so libootk.so libvos3gcc3.so libuno_sal.so.3 libsvxcore.so libsvx.so libsfx.so libsvt.so libfwe.so libootk.so libvcl.so libsvl.so libsot.so libutl.so libtl.so libucbhelper4gcc3.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvos3gcc3.so libuno_sal.so.3 libdba.so
File /opt/openoffice4/program/librptui.so has these missing library files:
libediteng.so libsvxcore.so libsvx.so libsfx.so libsvt.so libootk.so libvcl.so libsvl.so libsot.so libutl.so libtl.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libfwe.so libi18nisolang1gcc3.so libuno_sal.so.3 libfor.so libforui.so libsvxcore.so libsvx.so libsfx.so libsvt.so libfwe.so libootk.so libvcl.so libsvl.so libsot.so libutl.so libtl.so libucbhelper4gcc3.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvos3gcc3.so libuno_sal.so.3 libdba.so libediteng.so libsvxcore.so libsvx.so libfwe.so libsfx.so libtl.so libi18nisolang1gcc3.so libsvl.so libsvt.so libutl.so libdbtools.so libcomphelpgcc3.so libuno_cppuhelpergcc3.so.3 libuno_cppu.so.3 libvcl.so libootk.so libvos3gcc3.so libuno_sal.so.3

Sorry I've not looked at this for several weeks, but I only have WEB access several hours each week and that time gets taken-up with Emails, etc.

Meanwhile, I suspect there is only a few commands to get Open Office operating, so please post simple commands that a "crapple - gulag - macrosloth" defector can easily understand.

Thanx again for your help . . .

Regards,
PFO

[mikewalsh]

@PFO :-

Not being "funny", but I think you're just asking too much of such an elderly, low-spec machine, with the current state of software as-is. Yes, it's exactly the kind of machine that Puppy was originally created for, it's true.....but all those years ago, office suites were one hell of a lot smaller. EVERYTHING was a lot smaller.

You're now labouring under the additional problem that, over the last 19 years, office suites have grown in size to such an extent that OpenOffice itself requires more RAM that your machine possesses! Don't forget, you also have to run the OS itself out of that - what is it.....485 MB?? - and THEN you want to run OpenOffice as well..?

As the years have passed, RAM as supplied with new machines has increased proportionately. 2 GB became 4 GB, then 8 GB, and now many machines come with 16 GB as standard. Many even have a purchase-time optional extra of 32 GB nowadays, as it comes OOTB. The industry itself is seriously talking about 64-128 GB RAM as standard within the next couple of years!

Unfortunately, this - along with a whole new generation of "easy" programming languages - has encouraged a new generation of young, 'lazy' coders.....who see all this RAM, take it for granted that everyone must have the same amounts, and make no attempts to keep their code neat, tidy & 'tight' any more. Apps that perhaps took up 20 MB in years gone by are now using 10-15 times that amount.....for no good reason that I can see. So far as the current generation of devs are concerned, YOUR RAM is their 'playground'. Tough titty if you're running elderly, low-resource hardware; you're expected to be a good little drone & dutifully buy a new, more powerful machine every other year. And if you can't, well.....it's not THEIR problem. It's yours, for dragging your heels & not "moving with the times".

Way of the world, my friend. We're the "spanner in the works", here in Puppyland. The "fly in the ointment", y'know? Trying to keep elderly hardware alive is simply not 'playing the game' & 'toeing the line', so far as the industry is concerned.....

---------------------------------------------

I can't see how you can do it, even with a large swap partition.

Others may have different ideas, but to me, it's a case of seriously "wishful thinking"..... I wish you luck, but I honestly think you're going to be banging your head against a brick wall here.

You either need more RAM, or a newer machine. A Core2Duo machine, from just a handful of years later than your current one (2007-2010) is an ideal Linux machine (and perfect for Puppy!); dual-core, 64-bit capable, and most come with at least 4 GB RAM. The late 2000s/early 2010s was a golden era for hardware development, when things really got into high gear. The market's awash with the afore-mentioned Core2Duo machines, and they're still quite reasonably-priced. No longer really capable of keeping up with modern Windows, yet they were produced in vast numbers around the time of Win 7.....and most are still fully-functional. Their loss; OUR gain!

Mike.

[PFO]

Hello Mike,

Yes the machine is older like many thousands here in Central Europe. BUT, Open Office is installed and works well on the XP side of this box and the current status suggest that I just need to install missing libraries and it wil work fine on the Puppy side.

mmt/sda1/Program Files/Open Office/he/DEBS/openoffice-core04_4.1.12-1_i386.deb

Can you direct me to the Puppy Libraries WEBsites and give me the command lines necessary to accomplish same?

Thanx,
PFO

[OscarTalks]

Hello PFO,
Your previous post suggests you are running BionicPup 32bit
If you are happy to run a slightly earlier version of OpenOffice I do have a package which I believe all works OK including all the menu entries. Otherwise unless someone has made a more recent package you would have to quite a lot of work to get everything installed and configured for Puppy.

Download from here:-
https://yadi.sk/d/JNgvahmT3P8hB8?force_show=1
It is version 4.1.7 in 32bit with British English language pack
Packaged as .sfs
Download, right click and use sfs-load program (Uninstall any other versions first).
If you want to remove it, use sfs-load from the Setup section of the main menu.
At least you can give it a try, see if it performs all the tasks you want and go from there.

[PFO]

Hello Mike,

OK, first I've been installing Open Office in sda1, which of course is the Macrosloth wside of the hard drive.

I've also downloaded:

1. Apache_OpenOffice_4.1.7_Linux_x86_install-deb_en-US.tar
2. OpenOffice-menus.pet
3. menumaker-1.1.9.pet
4. PaDS-1.1.7.pet
5. Xdotool32.pet

I have installed #1, in - root/Open Office 4.1.7/en-US/DEBS/Licenses/readmes

and #2 to #5 and now have all kinds of menu icons - NONE of which work.

I'm sorry, but I have no idea how to delete/uninstall programs in Puppy. So, could you please give me dummy instructions for same, and I'll try to uninstall everything and then follow your INSTALL commands.

Please make it very simple like:

right-click here
open command window
cut & paste
XXXXXXXXXXX

Thanx again,
PFO

[PFO]

Hey Guys,

Here is probably more Puppy Version data than you need:

▶—— Distro Specifications ——◀

Distro: BionicPup32 19.03
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
Bash: 4.4.20
Geany: 1.29
Gtkdialog: 0.8.4
Perl: 5.26.1
Python: 2.7.17
Yad: 0.40.3 (GTK+ 2.24.32)
--
busybox: 1.30.1
dhcpcd: 6.7.1
Glibc: 2.27
OpenSSL: 1.1.1 11 Sep 2018, built on: Wed Nov 24 13:50:16 2021 UTC
wpa_supplicant: 2.6

▶—— /etc/DISTRO_SPECS ——◀

One or more words that identify this distribution:
• DISTRO_NAME='BionicPup32'

Version number of this distribution:
• DISTRO_VERSION=19.03

The distro whose binary packages were used to build this distribution:
• DISTRO_BINARY_COMPAT='ubuntu'

Prefix for some filenames: exs: upupbbsave.2fs, puppy_upupbb-19.03.sfs
• DISTRO_FILE_PREFIX='upupbb'

The version of the distro whose binary packages were used to build this distro:
• DISTRO_COMPAT_VERSION='bionic'

Read by /usr/bin/xwin to bypass Xorg Wizard at first boot:
• DISTRO_XORG_AUTO='yes'
• DISTRO_KERNEL_PET='Huge_Kernel'
• DISTRO_DB_SUBNAME='upupbb'
• DISTRO_ARCHDIR='i386-linux-gnu'
• WOOF_VERSION=8
• DISTRO_TARGETARCH='x86'
• BUILD_FROM_WOOF='testing;c1a16e15;2019-03-22 12:34:12 +0800'

Puppy default filenames...
Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
For the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
• DISTRO_PUPPYSFS='puppy_upupbb_19.03.sfs'
• DISTRO_ZDRVSFS='zdrv_upupbb_19.03.sfs'
• DISTRO_FDRVSFS='fdrv_upupbb_19.03.sfs'
• DISTRO_ADRVSFS='adrv_upupbb_19.03.sfs'
• DISTRO_YDRVSFS='ydrv_upupbb_19.03.sfs'
• DISTRO_PUPPYDATE='Dec 2021'

Multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
• DISTRO_ARCHDIR='i386-linux-gnu'

▶—— /etc/os-release ——◀

NAME=Puppy
VERSION="19.03"
ID=puppy_upupbb
VERSION_ID=19.03
PRETTY_NAME="BionicPup32 19.03"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:puppy:puppy_linux:19.03"
HOME_URL="http://puppylinux.com/"
SUPPORT_URL="http://www.murga-linux.com/puppy/index.php"
BUG_REPORT_URL="https://github.com/puppylinux-woof-CE/woof-CE"

[PFO]

Meanwhile,

My month of trying to install Open Office has left me completely confused. So, just a few questions:

1. On the WIN XP side of the my ancient "BionicPup32 19.03" HP - Compaq nx6110 box, Open Office works great. What 32 bit version can be installed on the Puppy side?

A. Apache_OpenOffice_4.1.7_Linux_x86_install-deb_en-US.tar.gz
B. Apache_OpenOffice_4.1.7_Linux_x86_install-rpm_en-US.tar.gz

YES, older versions, but they work better on this iron. I tried both, but can't get them to install. Clicking on the individual icons in the unpacked "he" file opens XArchive 0.2.8.6 and I simply cannot determine what to do next.

2. In what directory should I INSTALL Open Office?

3. Right-clicking on the icon in the download directory - what terminal commands can I cut & paste to INSTALL the 30 plus files?

4. What are the terminal commands I can cut & paste to INSTALL menu items in the Document Menu?

Again, I'm sorry to be so dense, but have never had a mentor to walk me through Linux usage, I couldn't even get DOS to open in the 1980s, but fortunately, someone invented point & clik with a mouse, so I carried-on til I became mental carrion.

Thanx for your help.
PFO

[OscarTalks]

Hello again PFO,

In the post I made above I gave you a complete package of OpenOffice which has been set up for everything including the Puppy menu entries. All you have to do is download the one file (package) and use the SFS-Load program to "Install" it.

This will confirm whether or not OpenOffice will run in Puppy on your hardware and if it does it may satisfy all your needs. There are concerns especially about the low amount of RAM according to the specifications you posted.

The problem with asking someone to help you install OpenOffice by the other method is that it is long and involved and you have made it clear that you are not experienced with such things.

[janugsa]

@PFO
I tried @mikeslr and @OscarTalks' offer on a very old and weak laptop.
They work. Your laptop is more powerful, so openoffice should work.

You have installed programs. You can use PPM (Puppy Packet Manager) to uninstall them. It is in all puppy.
viewtopic.php?p=52257#p52257

Did you full install the puppy??
I would recommend the frugal installation. Almost everyone frugal installs puppy.
So you can recommended by Oscar easily load or unload SFS program package.
viewtopic.php?t=6953
viewtopic.php?p=2006#p2006
viewtopic.php?p=52188#p52188

I thought full install because that's what you wrote:
"Kernel command line:
root=UUID=9b278b90-547b-4323-b372-ccaa6eccfd84 ro fullinstall"

You can also use the full install puppy.

I made a video on how to use openoffice-4.1.7.sfs.
I then unload it and made it into a pet file. I also tried this.
I also show how to use Sfs.load and Puppy package manager.
I did not use terminal commands, but ROX file manager and the right or left mouse button.
You don't have the memory for that kind of processing. I hope you have a swap file or partition. If not , you can create a swap file. Type in terminal: pupswap

Video 8MB 8 minutes

xxxxxxxxxxhttps://drive.google.com/file/d/1eLxbJ6nok1-Nj7v51AUtm3TxDMhwDynv/view?usp=share_link
It says something else, but you can download the video.

Translated with DeepL Translator