Before defaulting to what I know is possible, I'm exploring two potential new ways to boot Puppy.
One is booting an internal hd Puppy via a USB bootloader. The USB uses SYSLINUX which I've read from one source requires boot files to be on the same partition as configuration files. There are vague instructions for a way around it by installing the builtin extlinux utility on the internal hd partition.
Code: Select all
root# extlinux --help
Usage: extlinux [options] directory
--install -i Install over the current bootsector
--update -U Update a previous installation
--zip -z Force zipdrive geometry (-H 64 -S 32)
--sectors=# -S Force the number of sectors per track
--heads=# -H Force number of heads
--stupid -s Slow, safe and stupid mode
--raid -r Fall back to the next device on boot failure
--once=... -o Execute a command once upon boot
--clear-once -O Clear the boot-once command
--reset-adv Reset auxilliary data
--menu-save= -M Set the label to select as default on the next boot
root# I would use any open source utility on the USB, but the 1st goal is to avoid overwriting or significantly altering the internal hd bootloader.
For that, the other possibility is using the Windows boot loader: https://www.lifewire.com/windows-boot-m ... gr-2625813, but I have no idea if it can boot a Linux partition after searching on it. It looks like everyone dual-booting Windows, most often with Ubuntu, is using Ubuntu's GRUB 2 bootloader.
If none of this works I am probably going to make every Puppy a live boot kindred with the other recent discussions, and how I began using Puppy until I starting believing there was something wrong with it, starting with the idea the ample ramdisk we're presented with is using half our ram, when that's only the case if we've written that much data to it.
