Hi peebeepeebee wrote:+ now a uefi bootable iso (? not tested)
I love that you took the effort to make your iso this way!!
It would be nice if this behaviour were standard for Puppy builds (woof CE builds).
Imo it makes Puppy more easily portable and more usable for new users.
(Regulars probably do a frugal install with grub4dos manually and switch the machine to legacy boot in the bios.
Or they put it on the HD directly and use one of many ways to boot it from there, legacy or uefi.)
So I've tested it.
I put the iso on a pendrive with the dd command and tried to boot it on my uefi laptop.
The pendrive was recognised as uefi bootable in the bios as well as legacy bootable. (The laptop supports legacy boot as well.)
Booting succeeded for both! YES!
I went one step further and created pupsave.
First I used the fix-usb.sh to make a third partition on the pendrive, ext3.
I had to disable the exit after the sanity check for 3rd partition empty. I do not know why it says there is something on the 3rd partition.
Then I saved a pupsavefolder to this partition. But on reboot it was not found.
I put another pupsavefolder on the root of an ext3 partition on the ssd/HD. There the pupsave was found and loaded.
If one could put the pupsave on the same stick as the Puppy and have it used, one would have a even more portable Puppy.
So I tried to add puppy boot param.
That should be possible with F2 when the boot screen comes up in legacy boot, but on that moment there is an error in red displaying "DESKTOP FAIL: Black-screen/hangs... " and it is not possible to add anything.
Instead I tried by editing (e) the kernel line, both in eufi (grub2?) and legacy (syslinux?). There I added psave=sdb3 and booted. And that worked!
Would there be a way to avoid this workaround and to have Puppy looking for fitting pupsaves everywhere?