I tested shinobar's 1.4 & 1.9 and reported results on Shinobar's thread, but had to go out before providing link here to them. See http://www.murga-linux.com/puppy/viewtopic.php?p=618028#618028. Checking in here, I've discovered jemimah's new sfs-load pet and pemasu's apparent success using it.
I'll test the same.
pemasu, try testing sfses not specifically built for Saluki. Noobs and those running more than one puplet are likely to try to load-unload them. Being able to unload a non-functional sfs is almost as important as being able to load a functional one.

Edit: Tested sfs_load-1.3-saluki.pet with the following: All could be loaded and unloaded without a problem:
gimp-2.6.11.sfs (not from Saluki repo)
google-chrome-stable_12.742.112.sfs
picasa3.sfs
Streamtuner2-2.03.sfs (not from Saluki repo)
LibreOffice-3.5.1-en_us-2.sfs (not from Saluki repo), and
xnviewp-xnconverter.sfs (not from Saluki repo).

With the exception of Streamtuner2-2.03.sfs, all not only loaded and unloaded, but also ran.

This may be the wrong thread to post this, i know. But, I could not think of where else to post this.

Pemasu has done fabulous work for the total PUP community. In SALUKI he has been instrumental with his kernels.

I run a Live media system.

Questions

Is there a way that the Live media (cd/dvd) could have a boot-time

Code:

puppy pfix= ....

method where the user booting the system could direct the process to boot the non-PAE or the PAE versions for, say, SALUKI18+?

Or could Shinobar's method of GRUB4DOS on the booting Live media allow a selection of either PAE or non-PAE?I think its obvious how this would be of benefit to the developers and users alike.

Thoughts for the future distros where the distro developers offer both version of a 32bit kernel.

Here to help

_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engineor use DogPileEdited_time_total

Installed pemasu's aufs3-util-saluki-0.0.1.pet and the sfs_load-1.3-saluki.pet, this seems to be a lot better but I still get the occasional lockup when loading a sfs, I'm only able to load 6 sometimes 7 sfs files running on a usb install, I receive an error message like below, but it sometimes will load on a second attempt.

Installed pemasu's aufs3-util-saluki-0.0.1.pet and the sfs_load-1.3-saluki.pet, this seems to be a lot better but I still get the occasional lockup when loading a sfs, I'm only able to load 6 sometimes 7 sfs files running on a usb install, I receive an error message like below, but it sometimes will load on a second attempt.

This is my fault. I created some loop devices with the wrong permissions. If you go into /dev and delete loop11-loop20 everything should work as expected. I will fix it for the next release.

No floppy is a very bad idea - I said that before. Without it, there is no simple way to manipulate the BIOS, inter alia. Most good boards still have the pin headers and a BIOS entry. Apart from which, 1.44Mb is still a very large text file. This entire episode was a subterfuge initiated by Dell in league with the devil - the DWIntel cartel to save $5. Besides, every review I've read of Puppy and it's derivatives mention it's prime function for resurrecting old kit. It seems rather pointless using what started out as a liveCD and a Mr-fixit tool on SOTA HW which would be more suited to running RH and guiding probes around Saturn's moons. Dan Dare and Sondar must be turning in their graves, if Treens die, that is.