There's a wealth of 32-bit applications out there to handle any task other than web-browsing. 32-bit applications --at least to some extent-- do not make the same demands on CPU and RAM as do 64-bit applications. But to a large extent publishers of Web-browsers no longer publish 32-bit versions; while publishers of websites increasingly cater to those whose operating systems have all the RAM needed to display graphic rich web-pages, denying access to any web-browser not reasonably current.
What can you do if your computer was really designed for a time gone by?
peebee may have come up with a solution. Most computers manufacture in the last 20 years, maybe longer, can actually support a 64-bit operating system even if they shipped with only a 32-bit operating system. [What was Microsoft and computer manufacturers going to do with 32-bit operating system disks already in stock? And why not sell 64-bit systems at a premium?].
peebee has developed a 64-bit compatibility SFS which enables some 32-bit operating systems to run 64 bit applications. You can obtain the compatibility SFS from the link here, https://www.forum.puppylinux.com/viewto ... 284#p78284. As reported on that thread it was originally published for use with S15pup32 and LxPupSc32. To use it requires a 64-bit kernel which LxPupSc32 already had. Under S15pup32 you'd have to replace the Kernel. It also works with JammyPup32*, under which, AFAIK, the kernel also has to be replaced. https://www.forum.puppylinux.com/viewto ... 564#p55564
Edit: Use this 64bit Compatibility SFS, instead, https://www.forum.puppylinux.com/viewto ... 523#p79523
Replacing the kernel is easy. Your Puppy may have an application built in to do so. Or you can download it from here, https://www.forum.puppylinux.com/viewto ... 1497#p1497. If not, exclusive of downloading time, it can be done manually in less than 5 minutes. All that's necessary to do it manually is to rename some files (Right-Click>rename): vmlinuz-SPECIFIC-INFORMATION-ABOUT-IT to just vmlinuz; kernel-modules-SPECIFIC-INFORMATION-ABOUT-IT.sfs to zdrv_YOUR-PUPPYS-SPECS.sfs. For example, if your puppy's main/core sfs was named puppy_upupbb_19.03.sfs you'd rename the 'zdrv' to zdrv_upupbb_19.03.sfs. The kernel-modules-SPECIFIC-INFORMATION-ABOUT-IT.sfs will always contain drivers needed to access hardware. But it may or may not contain firmware. You may need a firmware SFS. You can find some here, https://www.forum.puppylinux.com/viewtopic.php?t=5374. These would also have to be renamed to your Puppy's SPECS, e.g. fdrv_upupbb_19.03.sfs.
Caution: You can swap kernels from a running system. That, however, doesn't guarantee you'll be able to boot into it with the changed kernel. [As the Cardiac Surgeon said, "The operation was successful, but the patient died."]. I recommend Right-Clicking your Puppy's folder and selecting 'Duplicate' and giving the duplicate a unique name. Then add the duplicate to your boot-menu/grub.cfg. Delete the SaveFile/Folder from the duplicate. Its contents may conflict and prevent booting. Once you boot into your 'new puppy', you can copy over the SaveFile/Folder and test. Keep your old Puppy until you know the new version is fully functional.
Let us know what works, and what doesn't.
-=-=--=-=-=
* This is interesting and the reason for this post. S15pup32 is woofed from Slackware binaries; jammyPup32 primarily from Ubuntu binaries, but using some debian binaries as Ubuntu has entirely abandoned 32-bit operating systems. So peebee's work may have much further use than has yet been reported.
Wouldn't life be boring if everything you could think of worked the first time OOTB?