Bookworm Pup64 10.0.3 booting UEFI PC via ozsouths CD or DVD

[oldaolgeezer]

Thanks to radky, dimkr, rockedge, ozsouth and many others for Puppy Bookworm.

When Booting Puppy Linux on my only UEFI PC, a Dell Inspiron 15 (3552),
I tried to make few changes to Windows (turning off "secure boot"
and setting "hibernate" to "off")
https://oldforum.puppylinux.com/viewtopic.php?t=112224

I copied the same 13 files from ozsouth's CD or DVD iso as I did for my
Bookworm SDcard forum post earlier into C:\Bookworm
viewtopic.php?t=9867

On my three file (plus boot flag) fat32 USB flash drive for booting my UEFI PC,
I added an grub.cfg entry (see below) for booting Bookworm.

After the edited grub.cfg file is on my USB flash drive and the Bookworm folder with the
13 files from ozsouth's Bookworm CD or DVD are on the C: drive,
I try to get the PC to boot from the USB flash drive.
(on my DELL UEFI PC, press F12 key down while turning the power on.
or for an HP UEFI PC, hold ESC key down while powering on, then F9 key)
and choose the USB flash drive.
(After this experiment is done and Puppy is shutdown properly, and the
USB flash drive removed, the UEFI PC will boot Windows as usual.)

When Booting a UEFI PC, Bookworm seems to need a PDRV=sdax parameter for
PCs with Windows already on the disk drive partition: sdax

Without the PDRV= parameter, you get the boot failure error message:
*** sdb1 /Bookworm/puppy_dpup_10.0.3.sfs not found.
*** Error is too critical, dropping out to console ...

(older versions of Puppy, like Fossapup64_9.5, xenial-7.5 or DpupStretch, don't seem
to require this parameter to boot themselves on the same UEFI PC.)

===

my UEFI menu entry in grub.cfg, for just Bookworm looks like this:

menuentry ' '{
true
}

# Bookworm needs a PDRV=sdax parameter for PCs with Windows already on disk drive
# (the iso files folder is on a different device than the UEFI PC grub.cfg file)
#
# Installing ozsouth's BookwormPup64 10.0.3 on a PC with having a
# disk drive with Windows on the sda x partition and booting Puppy
# from a USB flash disk:

# menu.lst needs an additional PDRV=sda3 parameter on my own DELL

menuentry "Bookworm 64-bit " {
search --set -f /Bookworm/vmlinuz
linux /Bookworm/vmlinuz psubdir=/Bookworm PDRV=sda3 pfix=nocopy,fsck i915.modeset=0
initrd /Bookworm/initrd.gz
}
menuentry "Bookworm 64-bit SAFE MODE" {
search --set -f /Bookworm/vmlinuz
linux /Bookworm/vmlinuz psubdir=/Bookworm PDRV=sda3 pfix=ram i915.modeset=0
initrd /Bookworm/initrd.gz
}

menuentry ' '{
true
}

===

Perhaps all this will help someone who has a spare Windows UEFI PC try several
versions of Puppy Linux and the new Bookworm version too.

[bigpup]

Comparing what is needed to boot from one Puppy version to another is a wast of time.

Just understand that the boot process has changed over the years and boot menu entry requirements have also changed.

So what works with one specific Puppy version, may or may not work with a different Puppy version.

Most Puppy versions are setup, to need the least amount of info in the boot menu entry, as long as the install of Puppy is as simple as it can be.

Everything in one single partition.

On a USB that would be one single partition, formatted fat 32, with all the files from the Puppy ISO on that partition.
However, because the ISO boot loader menu entries are setup for booting from a CD/DVD install.
In the boot menu entry it will have pmedia=cd that may need changed to pmedia=usbflash, because it is booting from a USB install not a CD install.
The boot process does do a little changing of how it boots based on the type device it is booting from.
pmedia= tells it what type device.