Afternoon, gang.
Got a wee poser for y'all. I've been meaning to ask this for ages, but just never quite seem to actually get around to it...
Out of all the Puppies I used to run on the old Compaq rig, Slacko 5.6.0 was my absolute fave. Ran absolutely everything, rock-solid in use, and was a marvellous "daily driver". Unfortunately - like so many of the older 5-series or earlier Puppies, in standard trim it will not boot on this new HP rig.....because of the UEFI stuff.
Older Puppies appear to search for something called "VESA BIOS extensions" during the boot sequence; at any rate, this is the point at which they always quit on me.....
--------------------------------------------
I did a mild remaster on Slacko 560. Upgraded from k3.10.5 to DPup 'Stretch's k4.1.48 - necessary, because at the time k3.10.5 was compiled, my present audio chip didn't even exist in some engineer's imagination, much less in actual silicon. No kernel can be expected to know about stuff that doesn't exist when it's built..! Also, I upgraded from glibc 2.15 to 2.20 while I was in there, so it would handle newer software.
Now; don't ask me how it's working, because I don't have a clue.....but I have a functional version of this Frankenpuppy, installed to a 2GB SD card, running in a USB card reader, and booting off its own bootloader installed to the root of the card; I always start this from the 'Advanced' boot menu. Some of its software is installed; some is portable apps from the big data partition on the new SSD, some of it runs from the 32-bit Xenial 'chroot' on sdb2. It's a right old mish-mash, but somehow it works. Only in Puppy, eh?
------------------------------------------
My query is this; quite simple, really. Somehow, I've managed to "lose" the JWM 'tray'.....and I don't know how to retrieve it; get it to show, like. The .jwmrc-tray config is there in /root, exactly as it should be, with everything that ought to be there.....only it refuses to display. It's not a huge problem; I still have the right-click desktop Menu, and plenty of my usual desktop launchers, but it wasn't till this happened that I suddenly realised just how many items I have that are designed to run from executable icons in the tray. Some have menu entries, but those are only to place the executable into the tray in the first place.
Anybody able to help Uncle Mike sort this one out, please? Any takers?
Mike.