A frugal Puppy installation is performed by extracting the contents of the container file (either ISO or ZIP) to normally one, i.e. the same, directory. Let that desired partition be known as the target partition since one is aiming to install to it. That partition may be located on:

either an external device, e.g. a flash memory drive (often erroneously referred to as a memory stick)

or, an internal device, usually a hard disk drive (H.D.D.)

Therefore, the target device is the device which contains the partition that one aims to install to, such as an external flash memory drive or an internal hard disk drive. The minimum, nominal storage capacity for a flash memory drive is 256MB.

WARNING: If the target partition contains any important files make a minimum of two copies of important files, where each copy is located on a separate partition on a separate device, because they will be destroyed whenever the target partition is formatted.

IMPORTANT: determine the correct device name (sdX) of the target device to work on, via the command-line interface:

lsblk

The following procedure assumes that one is running Puppy Linux. However, the same procedure can be followed within any Linux distribution. If one wishes to use Microsoft Windows go to Appendix 1 below.

install, to one's actual operating system in use, a recent version of the boot-loader SYSLINUX

N.B. installing this package merely makes available the SYSLINUX files for one's use; it does not replace any of the existing boot-loader files which one's actual operating system makes use of for booting (starting-up) itself

install the boot configuration file syslinux.cfg (sample file for flash memory drives only) on the target device by copying it to /boot/syslinux (this file will need editing if more than one Puppy version has been installed; the pkeys parameter will need to be configured for one's geographical location)

install the boot system file ldlinux.sys to the target partition directory sdXY/boot:

the ldlinux.sys file has the immutable attribute set, which prevents it from being deleted or overwritten; this is because the sector location of the file must not change or else Syslinux has to be reinstalled; to remove it, run:

copy from the ISO (or ZIP) directory to the target device either all the files, or, just these essential ones: vmlinuz, initrd.gz, and all those with the extension .sfs (if more than one Puppy version is to be installed ensure that they are each contained within their own directory)

When making an installation to an internal H.D.D. with an existing operating system, one has the option to either allow that operating system to remain or be removed. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide new B.I.O.S. versions after that time. If the intention is to remove the existing operating system, regardless of computer age, then ensure to check for and install any B.I.O.S. updates first.

If the Puppy files are to be appended, by making a frugal installation only of Puppy, then this would involve one of the following:

either making a new partition for Puppy (not recommended)

or, using an existing partition for Puppy (recommended)

One can place a frugal installation within a pre-existing Windows installation. The save file, although itself is comprised of a Linux file-system, may reside on a F.A.T. or N.T.F.S. partition; which is why a frugal installation is also called a "co-exist" installation. A full hard disk drive installation on a F.A.T. partition is not possible because F.A.T. partitions do not support Linux symbolic links.

older Puppy versions will not boot from an external flash memory drive if the internal H.D.D. has been removed:

Posted on 23 Apr 2011, 22:54 by perthie
USB Install Issue?
I notice that you still haven't commented on this issue. A machine
missing an internal hard drive can no longer be booted from a flash
drive. The new search procedure fails to find the sfs file on the flash
drive.
Posted on 24 Apr 2011, 8:20 by BarryK
Re no boot usb
I have written it down in my to-do list.