Revision history for UsingPuppy


Revision [28637]

Last edited on 2013-08-26 07:42:32 by darkcity
Additions:
{{redirect target="Steps to Installation"}}
Deletions:
{{include tonguesSteps To Installation}}
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[InstallationIndex Install]]

====Steps to Installation====

==Step 1 - Acquire the container file (either ISO or ZIP) of required Puppy Linux version==
~Typically Puppy comes as a set of three files:
---
~~- //vmlinuz//
~~- //initrd.gz//
~~- //*.sfs// (* is determined by the Puppy version)
---
~N.B. Some Puppy versions make use of an additional file: //z*.sfs//
---
~These files are usually distributed within a single container file in either [[ISO]] or [[ZIP]] file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com download page]], [[http://puppylinuxnews.org/releases/ puppylinuxnews.org release]] or [[http://ftp.cc.uoc.gr/mirrors/linux/quirky/ ftp.cc.uoc.gr archive]]

==Step 2 - Choose how to use Puppy Linux with your machine with ==
~This will depend on the media type. Whether it is to be used without installation 'Live', or as the single or one of many installed operating systems. Also if Puppy is to take a occupy or share a [[partition]]:
---
~~-[[InstallationFrugal]] - typically on USB flash memory, or harddrive, does not takeover a partition
~~-[[InstallationFullHDD]] - typically on a harddrive, takes over a partition
~~-[[LiveDVD]] - typically on an optical disc drive
~~-[[PXELINUX]] - uses network server drive

==Also on the Wiki==
~[[MinimumSystemRequirements]]
~[[InstalltionAppendix]]

----
==Categories==
CategoryInstallation

Revision [28635]

Edited on 2013-08-26 07:41:23 by darkcity [tonguesUpdaye]
Additions:
{{include tonguesSteps To Installation}}
====Steps to Installation====
==Step 1 - Acquire the container file (either ISO or ZIP) of required Puppy Linux version==
~Typically Puppy comes as a set of three files:
---
~~- //vmlinuz//
~~- //initrd.gz//
~~- //*.sfs// (* is determined by the Puppy version)
---
~N.B. Some Puppy versions make use of an additional file: //z*.sfs//
---
~These files are usually distributed within a single container file in either [[ISO]] or [[ZIP]] file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com download page]], [[http://puppylinuxnews.org/releases/ puppylinuxnews.org release]] or [[http://ftp.cc.uoc.gr/mirrors/linux/quirky/ ftp.cc.uoc.gr archive]]
==Step 2 - Choose how to use Puppy Linux with your machine with ==
~This will depend on the media type. Whether it is to be used without installation 'Live', or as the single or one of many installed operating systems. Also if Puppy is to take a occupy or share a [[partition]]:
---
~~-[[InstallationFrugal]] - typically on USB flash memory, or harddrive, does not takeover a partition
~~-[[InstallationFullHDD]] - typically on a harddrive, takes over a partition
~~-[[LiveDVD]] - typically on an optical disc drive
~~-[[PXELINUX]] - uses network server drive
==Also on the Wiki==
~[[MinimumSystemRequirements]]
~[[InstalltionAppendix]]
Deletions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy Linux version===
This operating system essentially consists of three files:
- //vmlinuz//
- //initrd.gz//
- //*.sfs// (where the nature of * is determined by the Puppy version)
N.B. Some Puppy versions make use of an additional file: //z*.sfs//
These files are usually distributed within a single container file in either ISO or ZIP file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]], [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]] or [[http://ftp.cc.uoc.gr/mirrors/linux/quirky/ ftp.cc.uoc.gr]]
===Step 2 - Choose how to use Puppy Linux with your machine with MinimumSystemRequirements===
<<Using Puppy from a **[[InstallationFrugal flash memory drive]]**
Using Puppy from a **[[InstallationFullHDD hard disk drive]]**
Using Puppy from an **[[LiveDVD optical disc drive]]**
Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server drive]]**<<
===Step 3 - [[http://puppylinux.com/ Learn more about Puppy]]===

Revision [25159]

Edited on 2012-11-20 12:44:29 by coolpup [tonguesUpdaye]
Additions:
These files are usually distributed within a single container file in either ISO or ZIP file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]], [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]] or [[http://ftp.cc.uoc.gr/mirrors/linux/quirky/ ftp.cc.uoc.gr]]
Deletions:
These files are usually distributed within a single container file in either ISO or ZIP file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]

Revision [22417]

Edited on 2012-07-19 05:43:52 by coolpup [tonguesUpdaye]
Additions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy Linux version===
Deletions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy Linux release===

Revision [22416]

Edited on 2012-07-19 05:43:24 by coolpup [tonguesUpdaye]
Additions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy Linux release===
This operating system essentially consists of three files:
===Step 2 - Choose how to use Puppy Linux with your machine with MinimumSystemRequirements===
Deletions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy release===
Puppy essentially consists of three files:
===Step 2 - Choose how to use Puppy with your machine with MinimumSystemRequirements===

Revision [20042]

Edited on 2012-01-02 09:36:32 by coolpup [tonguesUpdaye]
Additions:
These files are usually distributed within a single container file in either ISO or ZIP file format. It is this container file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
Deletions:
These files are usually distributed as a single container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]

Revision [20041]

Edited on 2012-01-02 09:35:08 by coolpup [tonguesUpdaye]
Additions:
Puppy essentially consists of three files:
These files are usually distributed as a single container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
Deletions:
From either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
The container file contains three files which essentially make up Puppy:
These files are usually distributed as a single container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system.

Revision [20040]

Edited on 2012-01-02 09:31:45 by coolpup [tonguesUpdaye]
Additions:
===Step 1 - Acquire the container file (either ISO or ZIP) of a recent Puppy release===
From either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
===Step 2 - Choose how to use Puppy with your machine with MinimumSystemRequirements===
===Step 3 - [[http://puppylinux.com/ Learn more about Puppy]]===
Deletions:
1) Acquire the container file (either ISO or ZIP) of a recent Puppy release from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
2) Choose how to use Puppy with your machine with MinimumSystemRequirements:
3) [[http://puppylinux.com/ Learn more about Puppy]]

Revision [20039]

Edited on 2012-01-02 09:28:09 by coolpup [tonguesUpdaye]

No Differences

Revision [20038]

Edited on 2012-01-02 09:26:38 by coolpup [tonguesUpdaye]
Additions:
1) Acquire the container file (either ISO or ZIP) of a recent Puppy release from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
The container file contains three files which essentially make up Puppy:
2) Choose how to use Puppy with your machine with MinimumSystemRequirements:
3) [[http://puppylinux.com/ Learn more about Puppy]]
Deletions:
1) [[http://puppylinux.com/ Learn more about Puppy]]
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
3) Choose how to use Puppy with your machine with MinimumSystemRequirements:
===Appendix 1 - The container file===
Puppy essentially consists of three files:
===Appendix 2 - Co-existing with another operating system===
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 [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 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.
There is an option to install from within Microsoft Windows using the relevant file from here: http://www.mediafire.com/?5ah0d0rzcz5cc
===Appendix 3 - The start-up process===
Upon starting (booting), the computer will access specific boot code located at a special location, the first sector of the drive, called the ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]). Subsequently,control is transferred to a Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
So, if the existing operating system is to be kept, one has to choose which operating system is to be the primary one to initiate the boot process:
- either, the //existing// operating system (e.g. Windows)
- or, the //new// operating system (i.e. Puppy)
If Microsoft Windows is chosen it will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing ""GRUBforDOS"" from within Puppy, which will make Microsoft Windows available as an option from the GRUB boot menu. However, this will only work if Puppy has been installed into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) does not install GRUB to a F.A.T. or N.T.F.S. partition because then it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Microsoft Windows-only setup, run the //fixmbr// command within Microsoft Windows.
===Appendix 4 - Frugal and Full Installations===
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed) and deposited as a Linux file-system onto one's chosen partition. Therefore, a full installation involves __one file-system__. Any subsequent software application installations, or file edits, are appended to this file-system so that the total number of files and folders gradually increases with time.
A frugal installation involves __two distinct file-systems__:
- the Linux file-system, consisting of a compressed, read-only single file
- the "save file" or "pupsave file" consisting of a decompressed, read/write single file
Upon start-up these two file-systems are super-imposed upon each other so that they appear merged. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are those two files. Any additional user files that are written to the operating system are written to within the save file.
The main advantages of a frugal installation is that one always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages can be installed completely outside the save file: [[opera]], [[libreoffice]]
Frugal installations can be made almost anywhere. It may even be placed inside a full installation of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition. When using older machines it is recommended to compare both frugal and full installations to determine which functions better.
Windows Vista may become corrupted if a user tries to shrink the Windows partition using Linux tools. A safer procedure is to use Vista's own Disk Management tool, then create the new partitions using Linux. If one wants to keep Vista as the primary boot-loader, look at Easy BCD [[http://neosmart.net/wiki/display/EBCD/EasyBCD+Documentation+Home;jsessionid=4CDEDEBD199D7577A170EDA271A0B04A
here]].
For computers with low R.A.M. a full installation is preferred since it will run faster.
Puppy can boot from a non-primary partition. Or you can have the PUI write GRUB's stage1 to a floppy boot disk. Or you can do the frugal installation manually and use a [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 boot CD]] to launch it. In that case, one could even put Puppy in a logical FAT partition which would be shared with Windows.

Revision [20019]

Edited on 2011-12-30 08:43:12 by coolpup [tonguesUpdaye]
Additions:
There is an option to install from within Microsoft Windows using the relevant file from here: http://www.mediafire.com/?5ah0d0rzcz5cc
Deletions:
====Quick Start====
Either [[http://www.mediafire.com/?5ah0d0rzcz5cc Install directly from Windows exe]]
or use a CD-burning program to burn the [[http://distro.ibiblio.org/puppylinux/puppy-5.3.1/slacko-5.3.1-SCSI-MAIN.iso ISO image]] slowly to a CD or DVD disc (4X is recommended for CD and 1X for DVD). A small and excellent CD burning program for Windows is [[http://www.terabyteunlimited.com/downloads/burncdcc.zip BurnCDCC]] Download, unzip to a folder in Windows and click on burncdcc.exe (do not forget to choose low burning speed).
====Complete Installation Guide====

Revision [19986]

Edited on 2011-12-28 00:25:35 by CrustyLobster [Quick Start]
Additions:
====Quick Start====
Either [[http://www.mediafire.com/?5ah0d0rzcz5cc Install directly from Windows exe]]
or use a CD-burning program to burn the [[http://distro.ibiblio.org/puppylinux/puppy-5.3.1/slacko-5.3.1-SCSI-MAIN.iso ISO image]] slowly to a CD or DVD disc (4X is recommended for CD and 1X for DVD). A small and excellent CD burning program for Windows is [[http://www.terabyteunlimited.com/downloads/burncdcc.zip BurnCDCC]] Download, unzip to a folder in Windows and click on burncdcc.exe (do not forget to choose low burning speed).

Revision [19501]

Edited on 2011-11-14 06:50:57 by coolpup [Quick Start]
Additions:
- 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.
Upon start-up these two file-systems are super-imposed upon each other so that they appear merged. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are those two files. Any additional user files that are written to the operating system are written to within the save file.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages can be installed completely outside the save file: [[opera]], [[libreoffice]]
For computers with low R.A.M. a full installation is preferred since it will run faster.
Deletions:
- or, using an //existing partition// for Puppy (recommended) (see Appendix 3)
One can place a frugal installation within a pre-existing Windows installation. The save file, although itself is 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.
Upon start-up these two file-systems are super-imposed upon each other so that they appear merged. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are those two files. Any additional user files that are written to the operating system are written to the save file.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages are installed outside the save file: [[seamonkey]], [[libreoffice]]
A frugal installation may be performed on a Windows FAT or NTFS partition without requiring to re-partition it; operates faster in high-R.A.M. computers; and is easier to upgrade. However, if one has fast, newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition. On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
To be able to dual-boot Puppy alongside Windows without re-partitioning or re-formatting: perform a [[InstallationFrugal frugal Puppy installation]].
For a full installation the conventional Linux file system is directly placed onto the partition. A full installation runs faster on low-RAM computers.
On a full hard disk install, the //vmlinuz// file is usually at /boot, and executables are located at /usr/bin. On a frugal install //vmlinuz// is outside of pup_save.2fs somewhere on the "real" file system. executable files within frugal installations are also are /usr/bin, but /usr/bin itself is not directly on the disk but rather is at /initrd/pup_rw which in reality is pup_save.2fs on the disk's "real" file-system, "union'ed" into the overall Linux / directory tree in pup_xxx.sfs.
Another thing frugal installations do is copy the pup_xxx.sfs file into R.A.M. if there is a sufficient amount, causing applications to start slightly faster. If the computer does not have sufficient R.A.M., it will instead mount the pup_xxx.sfs file from the HDD.
In the case that a frugal installation's save file is on a flash memory drive, Puppy stores its file changes within R.A.M., and only copies them to the save file on the drive periodically (or when one clicks the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).

Revision [19345]

Edited on 2011-11-02 07:17:51 by coolpup [Quick Start]
Additions:
These files are usually distributed as a single container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system.
Deletions:
These files are usually distributed in a container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system.

Revision [19344]

Edited on 2011-11-02 07:14:46 by coolpup [Quick Start]
Additions:
===Appendix 4 - Frugal and Full Installations===
Deletions:
===Appendix 4 - Using an appropriate file-system===
When Puppy is to be installed to its own partition it may be formatted with the file-system of choice. EXT4 is the recommended file-system to use.
===Appendix 5 - Frugal and Full Installations===

Revision [19343]

Edited on 2011-11-02 07:11:04 by coolpup [Quick Start]
Additions:
When Puppy is to be installed to its own partition it may be formatted with the file-system of choice. EXT4 is the recommended file-system to use.
Deletions:
When Puppy is to be installed to its own partition it may be formatted with the file-system of choice.
EXT4 is the recommended file-system.
F.A.T. formatting would enable an external drive, e.g. U.S.B. flash memory drive, for file sharing with the Microsoft Windows operating system. It is not suitable for installing Puppy Linux onto since such a file-system does not permit the use of symbolic links. Also it does not support files with sizes greater than 4GB.
N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB. However, users have reported problems with it and so it is not recommended.
The formatting can only be performed on an unmounted partition, using a LiveDVD or [[installationfrugal LiveUSB]], and going to:
//Menu > System > GParted > Partition > Format to//

Revision [19280]

Edited on 2011-10-30 14:29:39 by coolpup [Quick Start]
Additions:
N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB. However, users have reported problems with it and so it is not recommended.
Deletions:
N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB. However, there are problems with its usage and so it is not recommended.

Revision [19241]

Edited on 2011-10-30 09:01:08 by coolpup [Quick Start]
Additions:
Upon starting (booting), the computer will access specific boot code located at a special location, the first sector of the drive, called the ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]). Subsequently,control is transferred to a Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
Deletions:
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.

Revision [19240]

Edited on 2011-10-30 08:51:48 by coolpup [Quick Start]
Additions:
The formatting can only be performed on an unmounted partition, using a LiveDVD or [[installationfrugal LiveUSB]], and going to:
Deletions:
The formatting can be performed on an unmounted partition using a LiveDVD or [[installationfrugal LiveUSB]] and going to:

Revision [17848]

Edited on 2011-09-05 05:47:47 by coolpup [Quick Start]
Additions:
These files are usually distributed in a container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of the Puppy operating system.
Deletions:
These files are usually distributed in a container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of Puppy.

Revision [17847]

Edited on 2011-09-05 05:46:47 by coolpup [Quick Start]
Additions:
These files are usually distributed in a container file in either ISO or ZIP file format. It is this one file that one has to acquire so as to be able to make use of Puppy.
Deletions:
These files are usually distributed in a container file in either ISO or ZIP format. It is this one file that one has to acquire so as to be able to make use of Puppy.

Revision [17846]

Edited on 2011-09-05 05:45:58 by coolpup [Quick Start]
Additions:
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release from either [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release from [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]

Revision [17845]

Edited on 2011-09-05 05:45:31 by coolpup [Quick Start]
Additions:
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release from [[http://puppylinux.com/download/index.html puppylinux.com]] or [[http://puppylinuxnews.org/releases/ puppylinuxnews.org]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release:
http://puppylinuxnews.org/releases/

Revision [17844]

Edited on 2011-09-05 05:43:26 by coolpup [Quick Start]
Additions:
2) Acquire the container file (either ISO or ZIP) of a recent Puppy release:
http://puppylinuxnews.org/releases/
Puppy essentially consists of three files:
One can place a frugal installation within a pre-existing Windows installation. The save file, although itself is 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.
If Microsoft Windows is chosen it will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing ""GRUBforDOS"" from within Puppy, which will make Microsoft Windows available as an option from the GRUB boot menu. However, this will only work if Puppy has been installed into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) does not install GRUB to a F.A.T. or N.T.F.S. partition because then it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Microsoft Windows-only setup, run the //fixmbr// command within Microsoft Windows.
Deletions:
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
Puppy essentially consists of three compressed files:
One can place a frugal install within a pre-existing Windows installation. The save file, although itself is a Linux file-system, may reside on a FAT or NTFS 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.
If Windows is chosen it will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing ""GRUBforDOS"" from within Puppy, which will make Windows available as an option from the GRUB boot menu. However, this will only work if Puppy has been installed into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) does not install GRUB to a F.A.T. or N.T.F.S. partition because then it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.

Revision [17505]

Edited on 2011-08-17 12:36:41 by darkcity [Quick Start]
Additions:
[[HomePage]] > [[ComponentHowTo Components and HowTos]] > [[InstallationIndex Install]]
Deletions:
[[HomePage]] > [[HowToIndex HowTo]] > [[InstallationIndex Install]]

Revision [16976]

Edited on 2011-07-20 12:43:51 by darkcity [Quick Start]
Additions:
[[HomePage]] > [[HowToIndex HowTo]] > [[InstallationIndex Install]]
====Complete Installation Guide====
Deletions:
[[HomePage]] > [[HowToIndex HowTo]]
===How to Use Puppy Linux===

Revision [16970]

Edited on 2011-07-20 12:27:30 by darkcity [Quick Start]
Additions:
[[HomePage]] > [[HowToIndex HowTo]]

Revision [16268]

Edited on 2011-07-02 04:36:00 by coolpup [Quick Start]
Additions:
EXT4 is the recommended file-system.
Deletions:
EXT4 is the recommended file -system.

Revision [16267]

Edited on 2011-07-02 04:35:34 by coolpup [Quick Start]
Additions:
One can place a frugal install within a pre-existing Windows installation. The save file, although itself is a Linux file-system, may reside on a FAT or NTFS 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.
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed) and deposited as a Linux file-system onto one's chosen partition. Therefore, a full installation involves __one file-system__. Any subsequent software application installations, or file edits, are appended to this file-system so that the total number of files and folders gradually increases with time.
A frugal installation involves __two distinct file-systems__:
- the Linux file-system, consisting of a compressed, read-only single file
- the "save file" or "pupsave file" consisting of a decompressed, read/write single file
Upon start-up these two file-systems are super-imposed upon each other so that they appear merged. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are those two files. Any additional user files that are written to the operating system are written to the save file.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages are installed outside the save file: [[seamonkey]], [[libreoffice]]
A frugal installation may be performed on a Windows FAT or NTFS partition without requiring to re-partition it; operates faster in high-R.A.M. computers; and is easier to upgrade. However, if one has fast, newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition. On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
Deletions:
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed) and deposited as a Linux file-system onto one's chosen partition. Therefore, a full installation involves //one decompressed file-system//. Any subsequent software application installations, or file edits, are appended to this file-system so that the total number of files and folders gradually increases with time.
With a frugal installation, an additional file-system is used known as the "save file" or "pupsave file". Therefore, a frugal installation involves //two compressed file-sytems//.Upon start-up, the file-system stored in the core Puppy files is loaded into memory, and it remains read-only. Any additional user files that are written to the operating system are stored in this save file. These two file-systems are operational simultaneously so that they appear merged; it appears that one is working with a single file-system. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are the core files and the save file.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages are installed outside the save file: [[opera]], [[libreoffice]]
GRUB can be installed [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 manually]]. GRUB has two parts - ""stage1"" and ""stage2"". ""Stage1"" is the small block of boot code that gets written onto the M.B.R. ""Stage2"" is the collection of support files that are stored in the directory ///boot/grub// on the Linux partition. That is also where the GRUB menu file //menu.lst// is located.
Partitioning tools like PartedMagic, or the partitioning programs in some other Linux distributions, can have a major side-effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in EXT partitions]].
For a frugal installation the file system is placed inside a single file, known as the frugal save file, which itself contains a compressed read-only file system - the Linux file system. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the ISO file.
A frugal installation may be performed on a Windows FAT32 or NTFS partition without requiring to re-partition it; operates faster in high-R.A.M. computers; and is easier to upgrade. However, if one has fast, newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition. On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
One can place a frugal install within a pre-existing Windows installation. The frugal save file (although it itself contains an ext file system) may reside on a FAT or NTFS partition; which is why a frugal installation is also called a "co-exist" installation. Not so with a full hard disk drive installation - one cannot make a full installation on a FAT partition because it does not support Linux symbolic links.

Revision [16246]

Edited on 2011-07-01 09:44:41 by coolpup [Quick Start]
Additions:
Frugal installations can be made almost anywhere. It may even be placed inside a full installation of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition. When using older machines it is recommended to compare both frugal and full installations to determine which functions better.
Deletions:
Frugal installations can be made almost anywhere. It may even be placed inside a full installation of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition.

Revision [16244]

Edited on 2011-07-01 09:12:43 by coolpup [Quick Start]
Additions:
----
==Categories==
CategoryInstallation

Revision [16243]

Edited on 2011-07-01 09:11:27 by coolpup [Quick Start]
Additions:
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
If Windows is chosen it will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Deletions:
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (e.g. Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
Is Windows to be used to boot-up the computer? If so Windows will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.

Revision [16242]

Edited on 2011-07-01 09:09:21 by coolpup [Reverting last edit by CrustyLobster [16238] to previous version [16221]]
Additions:
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
===Appendix 1 - The container file===
Puppy essentially consists of three compressed files:
These files are usually distributed in a container file in either ISO or ZIP format. It is this one file that one has to acquire so as to be able to make use of Puppy.
===Appendix 2 - Co-existing with another operating system===
===Appendix 3 - The start-up process===
===Appendix 4 - Using an appropriate file-system===
===Appendix 5 - Frugal and Full Installations===
Deletions:
2) Download the ISO (or occasionally ZIP) of an up to date [[http://puppylinuxnews.org/releases/ release]]
===Puppy essentially consists of three compressed files:===
These files are usually distributed in a container file in either ISO or ZIP format.
===Co-existing with another operating system===
===The start-up process===
===Using an appropriate file-system===
===Frugal and Full Installations===

Revision [16238]

Edited on 2011-06-30 17:31:41 by CrustyLobster [appendix v title - just title simpler?]
Additions:
2) Download the ISO (or occasionally ZIP) of an up to date [[http://puppylinuxnews.org/releases/ release]]
===Puppy essentially consists of three compressed files:===
These files are usually distributed in a container file in either ISO or ZIP format.
===Co-existing with another operating system===
===The start-up process===
===Using an appropriate file-system===
===Frugal and Full Installations===
Deletions:
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
===Appendix 1 - The container file===
Puppy essentially consists of three compressed files:
These files are usually distributed in a container file in either ISO or ZIP format. It is this one file that one has to acquire so as to be able to make use of Puppy.
===Appendix 2 - Co-existing with another operating system===
===Appendix 3 - The start-up process===
===Appendix 4 - Using an appropriate file-system===
===Appendix 5 - Frugal and Full Installations===

Revision [16221]

Edited on 2011-06-30 05:53:24 by coolpup [appendix v title - just title simpler?]

No Differences

Revision [16220]

Edited on 2011-06-30 05:53:03 by coolpup [appendix v title - just title simpler?]

No Differences

Revision [16219]

Edited on 2011-06-30 05:52:49 by coolpup [appendix v title - just title simpler?]

No Differences

Revision [16218]

Edited on 2011-06-30 05:52:28 by coolpup [appendix v title - just title simpler?]
Additions:
<<Using Puppy from a **[[InstallationFrugal flash memory drive]]**
Using Puppy from a **[[InstallationFullHDD hard disk drive]]**
Using Puppy from an **[[LiveDVD optical disc drive]]**
Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server drive]]**<<
Deletions:
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
__Using Puppy from an **[[LiveDVD optical disc drive]]**__
__Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server drive]]**__

Revision [16214]

Edited on 2011-06-30 05:45:14 by coolpup [appendix v title - just title simpler?]
Additions:
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed) and deposited as a Linux file-system onto one's chosen partition. Therefore, a full installation involves //one decompressed file-system//. Any subsequent software application installations, or file edits, are appended to this file-system so that the total number of files and folders gradually increases with time.
With a frugal installation, an additional file-system is used known as the "save file" or "pupsave file". Therefore, a frugal installation involves //two compressed file-sytems//.Upon start-up, the file-system stored in the core Puppy files is loaded into memory, and it remains read-only. Any additional user files that are written to the operating system are stored in this save file. These two file-systems are operational simultaneously so that they appear merged; it appears that one is working with a single file-system. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are the core files and the save file.
The main advantages of a frugal installation is that one always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy.
The save file is of a fixed size but it may be increased if more space is required. However it is simpler to just store or move data outside of the save file, which is recommended. For example these software packages are installed outside the save file: [[opera]], [[libreoffice]]
Deletions:
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed)and deposited as a Linux file-system onto one's chosen partition. Any subsequent software application installations, or file saves, are appended to this file-system so that the total number of files and folders gradually increases with time.
With a frugal installation, Puppy creates an additional file-system known as the "save file" or "pupsave file". Upon boot up, the file-system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to store any additional files that the user wishes. These two file-systems are merged together so that it appears that one is working with a single file-system. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are the core files and the save file.
The main advantage of a frugal installation is that one always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy. If your save file gets filled up Puppy has a utility for increasing its size. Or data can be stored/moved outside of the save file.

Revision [16212]

Edited on 2011-06-30 05:17:24 by darkcity [appendix v title - just title simpler?]
Deletions:
{{nocomments}}

Revision [16206]

Edited on 2011-06-30 04:10:50 by coolpup [appendix v title - just title simpler?]
Additions:
===Appendix 2 - Co-existing with another operating system===
Deletions:
===Appendix 2 - Co-existing with an existing operating system===

Revision [16198]

Edited on 2011-06-30 03:29:36 by coolpup [appendix v title - just title simpler?]
Additions:
When one performs a full installation, all of the data from the core Puppy files are extracted (decompressed)and deposited as a Linux file-system onto one's chosen partition. Any subsequent software application installations, or file saves, are appended to this file-system so that the total number of files and folders gradually increases with time.
With a frugal installation, Puppy creates an additional file-system known as the "save file" or "pupsave file". Upon boot up, the file-system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to store any additional files that the user wishes. These two file-systems are merged together so that it appears that one is working with a single file-system. One has, in effect, a full installation whilst Puppy is running, but all that one actually sees on the physical partition are the core files and the save file.
The main advantage of a frugal installation is that one always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy. If your save file gets filled up Puppy has a utility for increasing its size. Or data can be stored/moved outside of the save file.
Frugal installations can be made almost anywhere. It may even be placed inside a full installation of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition.
For a frugal installation the file system is placed inside a single file, known as the frugal save file, which itself contains a compressed read-only file system - the Linux file system. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the ISO file.
A frugal installation may be performed on a Windows FAT32 or NTFS partition without requiring to re-partition it; operates faster in high-R.A.M. computers; and is easier to upgrade. However, if one has fast, newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition. On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
To be able to dual-boot Puppy alongside Windows without re-partitioning or re-formatting: perform a [[InstallationFrugal frugal Puppy installation]].
Deletions:
When one performs a full installation, all of the data from the core Puppy files are extracted and deposited as a Linux file system on one's chosen partition. Any software one installs or files one saves are added to the file system, so the total number of files and folders gradually increases with time.
In a frugal install, Puppy creates an additional, a save file. When booting up, the file system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to hold all the new stuff you add. These two are merged together so it appears that you are working with a single file system. You get the effect of a full install while Puppy is running, but all you actually see on your hard drive are the core files and the save file.
The main advantage of a frugal install is that you always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy. If your save file gets filled up Puppy has a utility for increasing its size. Or data can be stored/moved outside of the save file.
Frugal installations can be made almost anywhere. It may even be placed inside a full install of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition.
For a frugal installation the file system is placed inside a single file, known as the frugal save file, which itself contains a compressed read-only file system - the Linux file system. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the .ISO file.
A frugal installation runs faster in high-RAM computers; install is easy to upgrade; and it can be placed on a Windows FAT32 or NTFS hard drive/partition without re-partitioning it.
However, if you have fast newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition.
On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
To be able to dual-boot Puppy alongside Windows without re-partitioning or re-formatting: perform a frugal Puppy installation.

Revision [16197]

Edited on 2011-06-30 03:06:34 by coolpup [appendix v title - just title simpler?]
Additions:
===Appendix 1 - The container file===
===Appendix 2 - Co-existing with an existing operating system===
===Appendix 3 - The start-up process===
===Appendix 4 - Using an appropriate file-system===
===Appendix 5 - Frugal and Full Installations===
Deletions:
===Appendix 1 - Can Puppy coexist with an existing Operating System?===
===Appendix 2 - The start-up process===
===Appendix 3 - Using an appropriate file-system===
===Appendix 4 - Frugal and Full Installations===

Revision [16196]

Edited on 2011-06-30 03:04:03 by coolpup [appendix v title - just title simpler?]
Additions:
===Appendix 2 - The start-up process===
===Appendix 3 - Using an appropriate file-system===
When Puppy is to be installed to its own partition it may be formatted with the file-system of choice.
EXT4 is the recommended file -system.
===Appendix 4 - Frugal and Full Installations===
Deletions:
===Appendix 2 - What happens when Puppy boots?===
===Appendix 3 - Which File System suits me?===
When Puppy is to be installed to its own partition it may be formatted with the file system of choice.
EXT4 is the recommended file system.
===Appendix 4 - Frugal or Full Install?===

Revision [16195]

Edited on 2011-06-30 02:46:46 by coolpup [appendix v title - just title simpler?]
Additions:
Partitioning tools like PartedMagic, or the partitioning programs in some other Linux distributions, can have a major side-effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in EXT partitions]].
Deletions:
Partitioning tools like Parted Magic, or the partitioning programs in some other Linux distributions, can have a major side-effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in EXT partitions]].

Revision [16194]

Edited on 2011-06-30 02:45:16 by coolpup [appendix v title - just title simpler?]
Additions:
===Appendix 1 - Can Puppy coexist with an existing Operating System?===
===Appendix 2 - What happens when Puppy boots?===
===Appendix 3 - Which File System suits me?===
===Appendix 4 - Frugal or Full Install?===
Deletions:
===What files make up Puppy?===
===Can Puppy coexist with an existing Operating System?===
===What happens when Puppy boots?===
===Which File System suits me?===
===Frugal or Full Install?===

Revision [16141]

Edited on 2011-06-28 20:07:01 by CrustyLobster [What files make up Puppy? renamed appendix headers]
Additions:
===What files make up Puppy?===
===Can Puppy coexist with an existing Operating System?===
===What happens when Puppy boots?===
===Which File System suits me?===
===Frugal or Full Install?===
Deletions:
===Appendix 1===
===Appendix 2===
===Appendix 3===
===Appendix 4===
===Appendix 5===

Revision [16042]

Edited on 2011-06-27 04:51:37 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
For a full installation the conventional Linux file system is directly placed onto the partition. A full installation runs faster on low-RAM computers.
On a full hard disk install, the //vmlinuz// file is usually at /boot, and executables are located at /usr/bin. On a frugal install //vmlinuz// is outside of pup_save.2fs somewhere on the "real" file system. executable files within frugal installations are also are /usr/bin, but /usr/bin itself is not directly on the disk but rather is at /initrd/pup_rw which in reality is pup_save.2fs on the disk's "real" file-system, "union'ed" into the overall Linux / directory tree in pup_xxx.sfs.
Deletions:
For a full installation the conventional Linux file system [/, /boot, /bin, /etc, /lib, /mnt, /root, /sys, /usr, /var, etc.] is placed straight onto the partition. A full installation runs faster on low-RAM computers.
On a full hard disk install, vmlinuz is (usually) in /boot, Firefox is in /usr/bin and so forth. On a frugal install vmlinuz is outside of pup_save.2fs somewhere on the "real" file system. Firefox in frugal is also in /usr/bin, but /usr/bin itself is not directly on the disk but rather is in /initrd/pup_rw which in reality is pup_save.2fs on the disk's "real" file-system, "union'ed" into the overall Linux / directory tree in pup_xxx.sfs using special Puppy magic.

Revision [16041]

Edited on 2011-06-27 04:46:09 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
===How to Use Puppy Linux===
F.A.T. formatting would enable an external drive, e.g. U.S.B. flash memory drive, for file sharing with the Microsoft Windows operating system. It is not suitable for installing Puppy Linux onto since such a file-system does not permit the use of symbolic links. Also it does not support files with sizes greater than 4GB.
The formatting can be performed on an unmounted partition using a LiveDVD or [[installationfrugal LiveUSB]] and going to:
//Menu > System > GParted > Partition > Format to//
Deletions:
===How to Use Puppy===
F.A.T. formatting would be required for when using an external drive, e.g. U.S.B. flash memory drive, that would possibly be needed for file sharing with the Microsoft Windows operating system. permits the use of symbolic links and file sizes greater than 4GB
The formatting can be performed on an unmounted partition using a LiveDVD or [[installationfrugal LiveUSB]] and going to //Menu > System > GParted > Partition > Format to//.

Revision [15193]

Edited on 2011-06-10 04:56:02 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
__Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server drive]]**__
These files are usually distributed in a container file in either ISO or ZIP format. It is this one file that one has to acquire so as to be able to make use of Puppy.
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 [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 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.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (e.g. Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file, e.g. //ldlinux.sys// or //grldr//.
Is Windows to be used to boot-up the computer? If so Windows will need to be modified so that it presents a start-up menu that includes Puppy as one of the available options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the ""Lin'N'Win"" Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing ""GRUBforDOS"" from within Puppy, which will make Windows available as an option from the GRUB boot menu. However, this will only work if Puppy has been installed into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) does not install GRUB to a F.A.T. or N.T.F.S. partition because then it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice.
EXT4 is the recommended file system.
F.A.T. formatting would be required for when using an external drive, e.g. U.S.B. flash memory drive, that would possibly be needed for file sharing with the Microsoft Windows operating system. permits the use of symbolic links and file sizes greater than 4GB
N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB. However, there are problems with its usage and so it is not recommended.
Deletions:
__Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server]]**__
These files are usually distributed in a container file such as an ISO image (or a ZIP file). It is this one file that one has to acquire so as to be able to make use of Puppy.
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 new B.I.O.S. versions]] after that time. If the intention is to remove the existing operating system regardless of age then ensure to check for any B.I.O.S. updates first.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file //ldlinux.sys// or //grldr//.
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 fixmbr]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is not an issue if the existing operating system is to be replaced by Puppy.
Is Windows to be used to boot-up the computer? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing GRUB which Puppy can do. Windows will now run as an option from the GRUB boot menu. However, these will only work if you have installed Puppy into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
This should explain what can go wrong with a dual-boot system. Suppose that your Linux install gets damaged or you decide to delete it completely. If your ///boot/grub// folder has disappeared, the stage 1 code in the M.B.R. won't be able to find its stage 2 files. The computer will refuse to boot, even to Windows. But now you know how to fix this by restoring the M.B.R.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is the recommended file system for first choice, with F.A.T. formatting second.
F.A.T. formatting would be required for when using an external drive, e.g. U.S.B. flash memory drive, that would possibly be needed to be accessed by the Microsoft Windows operating system. Whereas N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB, F.A.T. does not. However, N.T.F.S. formatting has problems and so it is strongly recommended that F.A.T. formatting be used instead of N.T.F.S. formatting.

Revision [14398]

Edited on 2011-04-26 08:31:14 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
__Using Puppy from a **[[http://puppylinux.org/wikka/PXELINUX network server]]**__

Revision [14397]

Edited on 2011-04-26 08:29:09 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
1) [[http://puppylinux.com/ Learn more about Puppy]]
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
3) Choose how to use Puppy with your machine with MinimumSystemRequirements:
Deletions:
1) "Puppy runs as root. It's by design. It's in the attitude. Get used to it." [[http://www.murga-linux.com/puppy/viewtopic.php?p=517104#517104 Luluc]]
2) [[http://puppylinux.com/ Learn more about Puppy]]
3) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
4) Choose how to use Puppy with your machine with MinimumSystemRequirements:

Revision [14390]

Edited on 2011-04-26 08:05:32 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
3) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]]
Deletions:
3) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]

Revision [14389]

Edited on 2011-04-26 07:58:35 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
1) "Puppy runs as root. It's by design. It's in the attitude. Get used to it." [[http://www.murga-linux.com/puppy/viewtopic.php?p=517104#517104 Luluc]]
2) [[http://puppylinux.com/ Learn more about Puppy]]
3) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]
4) Choose how to use Puppy with your machine with MinimumSystemRequirements:
Deletions:
1) [[http://puppylinux.com/ Learn about Puppy]]
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]
3) Choose how to use Puppy with your machine with MinimumSystemRequirements:

Revision [14376]

Edited on 2011-04-26 04:24:42 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
3) Choose how to use Puppy with your machine with MinimumSystemRequirements:
Deletions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]:

Revision [14316]

Edited on 2011-04-24 07:03:15 by coolpup [What files make up Puppy? renamed appendix headers]

No Differences

Revision [14315]

Edited on 2011-04-24 07:02:58 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]:
Deletions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]:

Revision [14314]

Edited on 2011-04-24 07:02:19 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
__Using Puppy from an **[[LiveDVD optical disc drive]]**__
Deletions:
- __Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
- __Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
- __Using Puppy from an **[[LiveDVD optical disc drive]]**__

Revision [14313]

Edited on 2011-04-24 07:01:50 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]:
- __Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
- __Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
- __Using Puppy from an **[[LiveDVD optical disc drive]]**__
Deletions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
__Using Puppy from an **[[LiveDVD optical disc drive]]**__

Revision [14312]

Edited on 2011-04-24 07:00:35 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
2) Acquire the container file (either ISO or ZIP) of a [[http://puppylinuxnews.org/releases/ recent Puppy release]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Fluppy]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]

Revision [14187]

Edited on 2011-04-19 08:50:39 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
3) Choose how to use Puppy with your machine which would need to have a set of minimum [[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]]
Deletions:
3) Choose how to use Puppy with your machine ([[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]])

Revision [14185]

Edited on 2011-04-19 08:47:24 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Fluppy]] or [[http://puppylinux.org/wikka/CategoryPuppies some other]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Fluppy]], [[http://puppylinux.org/wikka/CategoryPuppies others]]

Revision [14184]

Edited on 2011-04-19 08:46:26 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Fluppy]], [[http://puppylinux.org/wikka/CategoryPuppies others]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Wary]] or [[Fluppy]]

Revision [14182]

Edited on 2011-04-19 08:39:25 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
2) Acquire the container file (either ISO or ZIP) of a Puppy version, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Wary]] or [[Fluppy]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Wary]] or [[Fluppy]]

Revision [14170]

Edited on 2011-04-19 08:20:12 by coolpup [What files make up Puppy? renamed appendix headers]
Deletions:
[[http://www.murga-linux.com/puppy/viewtopic.php?p=454016#454016 Various ways to install Puppy Linux]]
[[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.3.0 tutorial file]]
http://puppylinux.org/main/Manual-English.htm

Revision [14166]

Edited on 2011-04-19 08:12:00 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
2) Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[http://puppylinuxnews.org/releases/ latest official release]], [[Wary]] or [[Fluppy]]
Deletions:
2) Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]

Revision [14165]

Edited on 2011-04-19 08:10:06 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
1) [[http://puppylinux.com/ Learn about Puppy]]
2) Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]
3) Choose how to use Puppy with your machine ([[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]])
Deletions:
- [[http://puppylinux.com/ Learn about Puppy]]
- Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]
- Then choose how to use Puppy with your machine ([[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]])

Revision [14158]

Edited on 2011-04-19 08:00:53 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
===How to Use Puppy===
Deletions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===How to Use Puppy===

Revision [14157]

Edited on 2011-04-19 08:00:38 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
- [[http://puppylinux.com/ Learn about Puppy]]
- Acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]
Deletions:
- First acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]

Revision [14068]

Edited on 2011-04-18 09:07:12 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
- First acquire the container file (either ISO or ZIP) of a PuppyVersion, e.g. [[Wary]] or [[Fluppy]]
Deletions:
- First acquire the container file (either ISO or ZIP) of one of the PuppyVersions, e.g. [[Wary]] or [[Fluppy]]

Revision [14024]

Edited on 2011-04-18 03:51:05 by coolpup [What files make up Puppy? renamed appendix headers]
Additions:
- First acquire the container file (either ISO or ZIP) of one of the PuppyVersions, e.g. [[Wary]] or [[Fluppy]]
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g. [[Wary]] or [[Fluppy]]

Revision [13466]

Edited on 2011-03-16 00:31:47 by CrustyLobster [Various ways to install Puppy Linux]
Additions:
[[http://www.murga-linux.com/puppy/viewtopic.php?p=454016#454016 Various ways to install Puppy Linux]]

Revision [13364]

Edited on 2011-03-10 14:28:13 by coolpup [Various ways to install Puppy Linux]
Additions:
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 fixmbr]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is not an issue if the existing operating system is to be replaced by Puppy.
Deletions:
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is not an issue if the existing operating system is to be replaced by Puppy.

Revision [13363]

Edited on 2011-03-10 14:27:17 by coolpup [Various ways to install Puppy Linux]
Additions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is the recommended file system for first choice, with F.A.T. formatting second.
F.A.T. formatting would be required for when using an external drive, e.g. U.S.B. flash memory drive, that would possibly be needed to be accessed by the Microsoft Windows operating system. Whereas N.T.F.S. formatting permits the use of symbolic links and file sizes greater than 4GB, F.A.T. does not. However, N.T.F.S. formatting has problems and so it is strongly recommended that F.A.T. formatting be used instead of N.T.F.S. formatting.
The formatting can be performed on an unmounted partition using a LiveDVD or [[installationfrugal LiveUSB]] and going to //Menu > System > GParted > Partition > Format to//.
Deletions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is the recommended file system.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be required to be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite these advantages of N.T.F.S. formatting, it is strongly recommended that F.A.T. formatting be used instead.
The formatting can be performed using a LiveDVD or [[installationfrugal LiveUSB]] and going to //Menu > System > GParted > Partition > Format to//.

Revision [13362]

Edited on 2011-03-10 14:13:54 by coolpup [Various ways to install Puppy Linux]
Additions:
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot-loader system file //ldlinux.sys// or //grldr//.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may be installed to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be required to be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite these advantages of N.T.F.S. formatting, it is strongly recommended that F.A.T. formatting be used instead.
Deletions:
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot file //ldlinux.sys// or //grldr//, another part of the boot-loading process.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be required to be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., it is strongly recommended that F.A.T. be used instead.

Revision [13361]

Edited on 2011-03-10 14:09:13 by coolpup [Various ways to install Puppy Linux]
Additions:
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 new B.I.O.S. versions]] after that time. If the intention is to remove the existing operating system regardless of age then ensure to check for any B.I.O.S. updates first.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the Linux boot file //ldlinux.sys// or //grldr//, another part of the boot-loading process.
Deletions:
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 new B.I.O.S. versions]] after that time.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the boot program (e.g. //ldlinux.sys//, //grldr//) that is commonly stored on whichever partition is used for booting the PC.

Revision [13360]

Edited on 2011-03-10 14:00:19 by coolpup [Various ways to install Puppy Linux]
Additions:
Is Windows to be used to boot-up the computer? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project, that will achieve this.
Is Puppy to be used to boot-up the computer? This will involve installing GRUB which Puppy can do. Windows will now run as an option from the GRUB boot menu. However, these will only work if you have installed Puppy into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT4.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows (error message "This partition is not Linux"). Instead, the boot-loader may to the M.B.R.. To return to a Windows-only setup in the future simply run the //fixmbr// command.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be required to be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., it is strongly recommended that F.A.T. be used instead.
Deletions:
Do you want to continue using Windows as the primary boot-loader? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project that will do this.
Do you want Puppy to be the primary boot loader? This will involve installing GRUB which Puppy can do. Windows will now run as an option from the GRUB boot menu. However, these will only work if you have installed Puppy into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT3.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows. Watch for the cryptic error message "This partition is not Linux". Now we get to the M.B.R. issue. The quickest out-of-the-box solution is to install GRUB to the M.B.R. of the H.D.D. The P.U.I. will warn you about the dangers. But this is only an issue if you want to return your machine to a Windows-only setup in the future. In which case, you would simply run the //fixmbr// procedure.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., the recommended file system to use is N.T.F.S..

Revision [13205]

Edited on 2011-03-03 01:34:33 by coolpup [Various ways to install Puppy Linux]
Additions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is the recommended file system.
When one performs a full installation, all of the data from the core Puppy files are extracted and deposited as a Linux file system on one's chosen partition. Any software one installs or files one saves are added to the file system, so the total number of files and folders gradually increases with time.
Deletions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended.
When you do a full install, all of the data in the core Puppy files is extracted from the CD into a file system on your hard drive. Any software you install or files you save are added to the file system, so the total number of files and folders gradually increases.

Revision [13204]

Edited on 2011-03-03 01:31:24 by coolpup [Various ways to install Puppy Linux]
Additions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended.
N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., the recommended file system to use is N.T.F.S..
The formatting can be performed using a LiveDVD or [[installationfrugal LiveUSB]] and going to //Menu > System > GParted > Partition > Format to//.
Deletions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., the recommended file system to use is N.T.F.S..
The formatting can be performed using a LiveDVD and going to //Menu > System > GParted > Partition > Format to//.

Revision [13203]

Edited on 2011-03-03 01:28:14 by coolpup [Various ways to install Puppy Linux]
Additions:
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since most computer manufacturers cease to provide [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 new B.I.O.S. versions]] after that time.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be accessed by the Microsoft Windows operating system. N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, whereas F.A.T. does not. Despite the advantages of N.T.F.S., the recommended file system to use is N.T.F.S..
Deletions:
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since Microsoft ceases to provide new B.I.O.S. versions after a period of time. Therefore the only main benefit to temporarily keep an existing operating system is for any future [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 B.I.O.S. updates]].
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader. Compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.

Revision [13154]

Edited on 2011-02-26 15:07:21 by coolpup [Various ways to install Puppy Linux]
Additions:
When making an installation to an internal H.D.D. with an existing operating system, one has the option to either keep it or remove it. Only remove the existing operating system if the computer is more than 3 years old since Microsoft ceases to provide new B.I.O.S. versions after a period of time. Therefore the only main benefit to temporarily keep an existing operating system is for any future [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 B.I.O.S. updates]].
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is not an issue if the existing operating system is to be replaced by Puppy.
Do you want to continue using Windows as the primary boot-loader? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project that will do this.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. or F.A.T. formatting is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader. Compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.
Frugal installations can be made almost anywhere. It may even be placed inside a full install of Puppy or another Linux distribution. Or one may have multiple frugal installations in the same partition.
GRUB can be installed [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 manually]]. GRUB has two parts - ""stage1"" and ""stage2"". ""Stage1"" is the small block of boot code that gets written onto the M.B.R. ""Stage2"" is the collection of support files that are stored in the directory ///boot/grub// on the Linux partition. That is also where the GRUB menu file //menu.lst// is located.
Partitioning tools like Parted Magic, or the partitioning programs in some other Linux distributions, can have a major side-effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in EXT partitions]].
Windows Vista may become corrupted if a user tries to shrink the Windows partition using Linux tools. A safer procedure is to use Vista's own Disk Management tool, then create the new partitions using Linux. If one wants to keep Vista as the primary boot-loader, look at Easy BCD [[http://neosmart.net/wiki/display/EBCD/EasyBCD+Documentation+Home;jsessionid=4CDEDEBD199D7577A170EDA271A0B04A
For a frugal installation the file system is placed inside a single file, known as the frugal save file, which itself contains a compressed read-only file system - the Linux file system. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the .ISO file.
Another thing frugal installations do is copy the pup_xxx.sfs file into R.A.M. if there is a sufficient amount, causing applications to start slightly faster. If the computer does not have sufficient R.A.M., it will instead mount the pup_xxx.sfs file from the HDD.
In the case that a frugal installation's save file is on a flash memory drive, Puppy stores its file changes within R.A.M., and only copies them to the save file on the drive periodically (or when one clicks the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
One can place a frugal install within a pre-existing Windows installation. The frugal save file (although it itself contains an ext file system) may reside on a FAT or NTFS partition; which is why a frugal installation is also called a "co-exist" installation. Not so with a full hard disk drive installation - one cannot make a full installation on a FAT partition because it does not support Linux symbolic links.
Puppy can boot from a non-primary partition. Or you can have the PUI write GRUB's stage1 to a floppy boot disk. Or you can do the frugal installation manually and use a [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 boot CD]] to launch it. In that case, one could even put Puppy in a logical FAT partition which would be shared with Windows.
Deletions:
When making an installation to an internal H.D.D. with an existing operating system:
- either, //append// the Puppy files to an existing file system of some other operating system
- or, //replace// the existing file system with Puppy's (not recommended)
To replace the existing operating system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing a Puppy installation.
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is a crucial issue because Puppy can use its own boot loader. This is not an issue if the existing operating system is to be replaced by Puppy.
Do you want to continue using Windows as the primary boot loader? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project that will do this.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.
Frugal installations can be made almost anywhere. You can even stick it inside a full install of Puppy or another Linux. Or you can have multiple frugal installs in the same partition.
GRUB can be installed [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 manually]]. GRUB has two parts - stage1 and stage2. Stage1 is the small block of boot code that gets written onto the M.B.R. Stage2 is the collection of support files that are stored in the folder /boot/grub on the Linux partition. That is also where the GRUB menu file //menu.lst// is located.
Partitioning tools like Parted Magic, or the partitioning programs in some other Linux distributions, can have a major side effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in ext partitions]].
There have been reports that Vista can be corrupted if a user tries to shrink the Windows partition using Linux tools. A safer procedure is to use Vista's own Disk Management tool, then create the new partitions using Linux. If you want to keep Vista as the primary bootloader, look at Easy BCD [[http://neosmart.net/wiki/display/EBCD/EasyBCD+Documentation+Home;jsessionid=4CDEDEBD199D7577A170EDA271A0B04A
For a frugal installation the file system is placed inside a single file, pup_xxx.sfs, which itself contains a compressed read-only ext2 file system into which the Linux "/" dir is placed, with its sub-directories inside it. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the .ISO file.
Another thing frugal installs do is copy the pup_xxx.sfs file into ram if there is enough memory, causing applications to start slightly faster. If the computer does not have sufficient RAM, it will instead mount the pup_xxx.sfs file from the HDD.
In the case that a frugal install's pup_save.2fs file is on a flash-based drive, Puppy stores its file changes within R.A.M., and only copies them to the save file on the drive periodically (or when one clicks the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
One can place a frugal install within a pre-existing [[http://puppylinux.org/wikka/Win98 Win98]] installation; the save file (although it itself contains an ext2 file system) may reside on a FAT32 or NTFS partition. Which is why a frugal install is also called a "co-exist" install. Not so with a full hard disk drive install: one cannot make a full installation on a FAT partition because it does not support Linux symbolic links.
Puppy can be booted off a non-primary partition. Or you can have the PUI write GRUB's stage1 to a floppy boot disk. Or you can do the frugal install manually and use a [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 boot CD]] to launch it. In that case, you could even put Puppy in a logical FAT partition which would be sharable with Windows.

Revision [13020]

Edited on 2011-02-23 06:42:54 by coolpup [Various ways to install Puppy Linux]
Additions:
[[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.3.0 tutorial file]]
http://puppylinux.org/main/Manual-English.htm
Deletions:
[[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.3.0 tutorial file]]

Revision [12732]

Edited on 2011-02-13 07:32:18 by coolpup [Various ways to install Puppy Linux]
Additions:
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__
Deletions:
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__ (read //Appendices 1, 2, 3// and //4//)
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__ (read //Appendix 1//)

Revision [12320]

Edited on 2011-01-26 10:03:21 by coolpup [Various ways to install Puppy Linux]
Additions:
__Using Puppy from a **[[InstallationFullHDD hard disk drive]]**__ (read //Appendices 1, 2, 3// and //4//)
__Using Puppy from a **[[InstallationFrugal flash memory drive]]**__ (read //Appendix 1//)
Deletions:
__Using Puppy from an //internal// **[[InstallationFullHDD hard disk drive]]**__ (read //Appendices 1, 2, 3// and //4//)
__Using Puppy from an //external// **[[InstallationFrugal flash memory drive]]**__ (read //Appendix 1//)

Revision [12310]

Edited on 2011-01-25 07:38:37 by coolpup [Various ways to install Puppy Linux]
Additions:
__Using Puppy from an **[[LiveDVD optical disc drive]]**__
__Using Puppy from an //internal// **[[InstallationFullHDD hard disk drive]]**__ (read //Appendices 1, 2, 3// and //4//)
__Using Puppy from an //external// **[[InstallationFrugal flash memory drive]]**__ (read //Appendix 1//)
Deletions:
__Using Puppy from an **optical disc drive**__
- via a LiveDVD
__Using Puppy from an //internal// **hard disk drive**__ (read //Appendices 1, 2, 3// and //4//)
- via either a //[[InstallationFrugal frugal]]// or //[[InstallationFullHDD full]]// Puppy installation
__Using Puppy from a **flash memory drive**__ (read //Appendix 1//)
-via a //[[InstallationFrugal frugal]]// Puppy installation only

Revision [12308]

Edited on 2011-01-25 07:25:30 by coolpup [Various ways to install Puppy Linux]
Additions:
- via either a //[[InstallationFrugal frugal]]// or //[[InstallationFullHDD full]]// Puppy installation
Deletions:
- via a //[[InstallationFrugal frugal]]// or //[[InstallationFullHDD full]]// Puppy installation

Revision [12307]

Edited on 2011-01-25 07:24:42 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFrugal frugal]]// or //[[InstallationFullHDD full]]// Puppy installation
Deletions:
- via a //[[InstallationFrugal frugal]]// Puppy installation
- via a //[[InstallationFullHDD full]]// Puppy installation

Revision [12306]

Edited on 2011-01-25 07:24:06 by coolpup [Various ways to install Puppy Linux]
Additions:
-via a //[[InstallationFrugal frugal]]// Puppy installation only
Deletions:
-via a //[[InstallationFrugal frugal]]// Puppy installation

Revision [12305]

Edited on 2011-01-25 07:23:49 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a LiveDVD
- via a //[[InstallationFrugal frugal]]// Puppy installation
- via a //[[InstallationFullHDD full]]// Puppy installation
-via a //[[InstallationFrugal frugal]]// Puppy installation
Deletions:
- via a LiveDVD (>=256MB R.A.M. or swap partition recommended)
- via a //[[InstallationFrugal frugal]]// Puppy installation (>=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- via a //[[InstallationFullHDD full]]// Puppy installation (>=350MB partition space {{color text="required" c="red"}})
-via a //[[InstallationFrugal frugal]]// Puppy installation (>=256MB R.A.M. or swap partition {{color text="required" c="red"}})

Revision [12303]

Edited on 2011-01-25 07:05:23 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFrugal frugal]]// Puppy installation (>=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- via a //[[InstallationFullHDD full]]// Puppy installation (>=350MB partition space {{color text="required" c="red"}})
-via a //[[InstallationFrugal frugal]]// Puppy installation (>=256MB R.A.M. or swap partition {{color text="required" c="red"}})
Deletions:
- via a //[[InstallationFrugal frugal]]// Puppy installation (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- via a //[[InstallationFullHDD full]]// Puppy installation (LiveDVD or LiveUSB {{color text="required" c="red"}}; >=350MB partition space {{color text="required" c="red"}})
-via a //[[InstallationFrugal frugal]]// Puppy installation (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})

Revision [12302]

Edited on 2011-01-25 07:03:18 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFullHDD full]]// Puppy installation (LiveDVD or LiveUSB {{color text="required" c="red"}}; >=350MB partition space {{color text="required" c="red"}})
Deletions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=350MB partition space {{color text="required" c="red"}})

Revision [12301]

Edited on 2011-01-25 07:01:27 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a LiveDVD (>=256MB R.A.M. or swap partition recommended)
Deletions:
- via a LiveDVD

Revision [12300]

Edited on 2011-01-25 05:30:37 by coolpup [Various ways to install Puppy Linux]
Additions:
__Using Puppy from a **flash memory drive**__ (read //Appendix 1//)
Deletions:
__Using Puppy from **any other type of drive**__ (read //Appendix 1//)

Revision [12057]

Edited on 2011-01-14 04:38:36 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=350MB partition space {{color text="required" c="red"}})
Deletions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=400MB partition space {{color text="required" c="red"}})

Revision [12055]

Edited on 2011-01-14 03:11:19 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=400MB partition space {{color text="required" c="red"}})
Deletions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=400MB partition space {{color text="required" c="red"}}))

Revision [12054]

Edited on 2011-01-14 03:10:54 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=400MB partition space {{color text="required" c="red"}}))
Deletions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=500MB space {{color text="required" c="red"}}))

Revision [12053]

Edited on 2011-01-14 03:09:16 by coolpup [Various ways to install Puppy Linux]
Additions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}}; >=500MB space {{color text="required" c="red"}}))
Deletions:
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}})

Revision [12008]

Edited on 2011-01-13 04:50:46 by coolpup [Various ways to install Puppy Linux]
Additions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. is needed for when using an external drive, e.g. U.S.B. flash memory drive, that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.
Deletions:
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. is needed for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.

Revision [12007]

Edited on 2011-01-13 04:49:26 by coolpup [Various ways to install Puppy Linux]
Additions:
- either making a //new partition// for Puppy (not recommended)
- or, using an //existing partition// for Puppy (recommended) (see Appendix 3)
To replace the existing operating system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing a Puppy installation.
Deletions:
- making a //new partition// for Puppy (not recommended)
- using an //existing partition// for Puppy (recommended) (see Appendix 3)
To replace the existing operating system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.

Revision [12006]

Edited on 2011-01-13 04:27:34 by coolpup [Various ways to install Puppy Linux]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g. [[Wary]] or [[Fluppy]]
__Using Puppy from **any other type of drive**__ (read //Appendix 1//)
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g. Puppy 5 {[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=479987#479987 Lucid edition]]} or [[Fluppy]]
__Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)__ (read //Appendix 1//)

Revision [11896]

Edited on 2011-01-07 07:17:20 by coolpup [Various ways to install Puppy Linux]
Additions:
Puppy essentially consists of three compressed files:
N.B. Some Puppy versions make use of an additional file: //z*.sfs//
These files are usually distributed in a container file such as an ISO image (or a ZIP file). It is this one file that one has to acquire so as to be able to make use of Puppy.
Deletions:
Puppy essentially consists of either three or four compressed files:
- //z*.sfs// (optional)
These files are usually distributed in a container file such as an ISO image or a ZIP file. It is this one file that one has to acquire so as to be able to make use of Puppy.

Revision [11895]

Edited on 2011-01-07 07:15:01 by coolpup [Various ways to install Puppy Linux]
Additions:
To replace the existing operating system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.
Deletions:
To replace the existing file system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.

Revision [11894]

Edited on 2011-01-07 07:14:00 by coolpup [Various ways to install Puppy Linux]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g. Puppy 5 {[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=479987#479987 Lucid edition]]} or [[Fluppy]]
To replace the existing file system with Puppy's is __not recommended__ unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: Puppy 5{[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=479987#479987 Lucid edition]]}, or [[Fluppy]]
To replace the existing file system with Puppy's is not recommended unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.

Revision [11893]

Edited on 2011-01-07 07:02:09 by coolpup [Various ways to install Puppy Linux]
Additions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===How to Use Puppy===
Deletions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===

Revision [11881]

Edited on 2011-01-06 01:52:10 by CrustyLobster [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: Puppy 5{[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=479987#479987 Lucid edition]]}, or [[Fluppy]]
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: Puppy 5{[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=457202#457202 Lucid edition]]}, or [[Fluppy]]

Revision [11865]

Edited on 2011-01-04 06:08:05 by coolpup [Lucid edition]
Additions:
- Then choose how to use Puppy with your machine ([[http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements]])
In a frugal install, Puppy creates an additional, a save file. When booting up, the file system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to hold all the new stuff you add. These two are merged together so it appears that you are working with a single file system. You get the effect of a full install while Puppy is running, but all you actually see on your hard drive are the core files and the save file.
In the case that a frugal install's pup_save.2fs file is on a flash-based drive, Puppy stores its file changes within R.A.M., and only copies them to the save file on the drive periodically (or when one clicks the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
One can place a frugal install within a pre-existing [[http://puppylinux.org/wikka/Win98 Win98]] installation; the save file (although it itself contains an ext2 file system) may reside on a FAT32 or NTFS partition. Which is why a frugal install is also called a "co-exist" install. Not so with a full hard disk drive install: one cannot make a full installation on a FAT partition because it does not support Linux symbolic links.
Deletions:
- Then choose how to use Puppy with your machine (http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements)
In a frugal install, Puppy creates another file named pup_save.2fs. When you boot up, the file system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to hold all the new stuff you add. These two are merged together so it appears that you are working with a single file system. You get the effect of a full install while Puppy is running, but all you actually see on your hard drive are the core files and the save file.
In the case that a frugal install's pup_save.2fs file is on a flash-based drive, Puppy will actually store any changes and new files you make in RAM, and only copy them to the pup_save.2fs file on the drive periodically (or when you click the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
You can place a frugal install on a pre-existing [[http://puppylinux.org/wikka/Win98 Win98]] install; the pup_save.2fs (though it itself contains an ext2 filesystem) may reside on a FAT32 or NTFS partition. Which is why a frugal install is also called a "co-exist" install. Not so with a full hard disk drive install: you cannot place a full install on a pre-existing FAT partition because it does not support Linux symlinks.

Revision [11864]

Edited on 2011-01-04 05:56:16 by coolpup [Lucid edition]
Additions:
- or, //replace// the existing file system with Puppy's (not recommended)
To replace the existing file system with Puppy's is not recommended unless one never intends to possibly [[http://murga-linux.com/puppy/viewtopic.php?p=483349#483349 update the B.I.O.S.]]. Replacing the existing file system involves performing either a full Puppy installation or a frugal Puppy installation.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the boot program (e.g. //ldlinux.sys//, //grldr//) that is commonly stored on whichever partition is used for booting the PC.
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the ""WinXP"" Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is a crucial issue because Puppy can use its own boot loader. This is not an issue if the existing operating system is to be replaced by Puppy.
Deletions:
- or, //replace// the existing file system with Puppy's
To replace the existing file system with Puppy's perform either a full Puppy installation or a frugal Puppy installation.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the boot program (e.g. //ldlinux.sys//, //grldr//) stored on whichever partition is used for booting the PC.
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the WinXP Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is a crucial issue because Puppy can use its own boot loader. This is not an issue if the existing operating system is to be replaced by Puppy.

Revision [11862]

Edited on 2011-01-04 05:39:49 by coolpup [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: Puppy 5{[[Wary Wary edition]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=457202#457202 Lucid edition]]}, or [[Fluppy]]
- Then choose how to use Puppy with your machine (http://murga-linux.com/puppy/viewtopic.php?t=63547 system requirements)
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. EXT4 is recommended. N.T.F.S. is needed for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation.
The formatting can be performed using a LiveDVD and going to //Menu > System > GParted > Partition > Format to//.
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: [[Fluppy]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=457202#457202 Puppy 5.2]]
- Then choose how to use Puppy.
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. Use either of the following common types:
- EXT3
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation, and the ""GRUBforDOS"" boot loader is faster than the Syslinux boot loader.
The formatting can be performed using a LiveDVD and going to //Menu > System > GParted//.

Revision [11437]

Edited on 2010-12-13 14:39:11 by coolpup [Lucid edition]
Additions:
- via a LiveDVD
Deletions:
- This is the simplest way to use Puppy: LiveDVD

Revision [11436]

Edited on 2010-12-13 14:21:22 by coolpup [Lucid edition]
Additions:
- using an //existing partition// for Puppy (recommended) (see Appendix 3)
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires specific boot code (Master Boot Code) to be located at a special location ([[http://www.pcguide.com/ref/hdd/file/structMBR-c.html Master Boot Record]]) on the boot drive. This program eventually transfers control to the boot program (e.g. //ldlinux.sys//, //grldr//) stored on whichever partition is used for booting the PC.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB to a F.A.T. or N.T.F.S. partition because it assumes that the partition contains Windows. Watch for the cryptic error message "This partition is not Linux". Now we get to the M.B.R. issue. The quickest out-of-the-box solution is to install GRUB to the M.B.R. of the H.D.D. The P.U.I. will warn you about the dangers. But this is only an issue if you want to return your machine to a Windows-only setup in the future. In which case, you would simply run the //fixmbr// procedure.
This should explain what can go wrong with a dual-boot system. Suppose that your Linux install gets damaged or you decide to delete it completely. If your ///boot/grub// folder has disappeared, the stage 1 code in the M.B.R. won't be able to find its stage 2 files. The computer will refuse to boot, even to Windows. But now you know how to fix this by restoring the M.B.R.
Deletions:
- using an //existing partition// for Puppy (recommended) (see Appendix 3
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires a bit of code called a boot loader located at the root of the boot partition, specifically the Master Boot Record.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB in a FAT or NTFS partition, because it assumes that the partition contains Windows. Watch for the cryptic error message "This partition is not Linux". Now we get to the M.B.R. issue. The quickest out-of-the-box solution is to install GRUB on the M.B.R. of the H.D.D. The P.U.I. will warn you about the dangers. But this is only an issue if you want to return your machine to a Windows-only setup in the future. In which case, you would simply run the "fixmbr" procedure.
This should explain what can go wrong with a dual-boot system. Suppose that your Linux install gets damaged or you decide to delete it completely. If your ///boot/grub// folder has disappeared, the stage1 code in the MBR won't be able to find its stage2 files. The computer will refuse to boot, even to Windows. But now you know how to fix this by restoring the M.B.R.

Revision [11251]

Edited on 2010-12-01 06:32:42 by coolpup [Lucid edition]
Additions:
__Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)__ (read //Appendix 1//)
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; compared to F.A.T., N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation, and the ""GRUBforDOS"" boot loader is faster than the Syslinux boot loader.
Deletions:
__Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)__
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation, and the ""GRUBforDOS"" boot loader is faster than the Syslinux boot loader)

Revision [11250]

Edited on 2010-12-01 06:24:30 by coolpup [Lucid edition]
Additions:
[[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.3.0 tutorial file]]
Deletions:
===References===
- [[http://puppylinux.ca/tpp/smokey/The%20Puppy%20Linux%20Book%201.0.pdf ebook by Grant Wilson]]
- [[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.30 tutorial PDF ]]
- Video Tutorials: TutorialYouTube http://rhinoweb.us/
- [[http://puppylinux.com/download/index.html Donate]] to the creator of Puppy Linux

Revision [10365]

Edited on 2010-10-31 09:48:40 by coolpup [Lucid edition]
Additions:
__Using Puppy from an **optical disc drive**__
__Using Puppy from an //internal// **hard disk drive**__ (read //Appendices 1, 2, 3// and //4//)
__Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)__
Deletions:
===Using Puppy from an **optical disc drive**===
===Using Puppy from an //internal// **hard disk drive**=== (read //Appendices 1, 2, 3// and //4//)
===Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)===
----
==Categories==
CategoryDocumentation

Revision [10364]

Edited on 2010-10-31 09:46:26 by coolpup [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: [[Fluppy]] or [[http://www.murga-linux.com/puppy/viewtopic.php?p=457202#457202 Puppy 5.2]]
- [[http://puppylinux.com/download/index.html Donate]] to the creator of Puppy Linux
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: [[Fluppy]] or LupQ.
- http://puppylinux.org/main/index.php?file=Overview%20and%20Getting%20Started.htm
- Donate to the creator of Puppy Linux [[http://puppylinux.com/download/index.html here]]

Revision [10096]

Edited on 2010-10-24 04:55:37 by coolpup [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy [[Versions version]], e.g.: [[Fluppy]] or LupQ.
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy version, e.g.: [[Fluppy]] or LupQ.

Revision [9965]

Edited on 2010-10-20 02:15:28 by coolpup [Lucid edition]
Additions:
===Using Puppy from an **U.S.B. flash memory drive** (or any other type of //external// drive)===
Deletions:
===Using Puppy from an **U.S.B. flash memory drive**=== (or any other type of //external// drive)

Revision [9857]

Edited on 2010-10-14 08:24:27 by coolpup [Lucid edition]
Additions:
- [[http://puppylinux.ca/tpp/smokey/The%20Puppy%20Linux%20Book%201.0.pdf ebook by Grant Wilson]]
- making a //new partition// for Puppy (not recommended)
Deletions:
- [[http://www.lulu.com/product/download/the-puppy-linux-book-v10/4204807 ebook by Grant Wilson]]
- making a //new partition// for Puppy (not recommended)

Revision [9838]

Edited on 2010-10-12 16:10:01 by coolpup [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy version, e.g.: [[Fluppy]] or LupQ.
Deletions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.

Revision [9837]

Edited on 2010-10-12 16:09:03 by coolpup [Lucid edition]
Additions:
- First acquire the container file (either ISO or ZIP) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.
- Then choose how to use Puppy.
===Using Puppy from an **optical disc drive**===
===Using Puppy from an //internal// **hard disk drive**=== (read //Appendices 1, 2, 3// and //4//)
===Using Puppy from an **U.S.B. flash memory drive**=== (or any other type of //external// drive)
Deletions:
First acquire the container file (either ISO or ZIP) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.
Then choose how to use Puppy.
Using Puppy from an **optical disc drive**
Using Puppy from an //internal// **hard disk drive** (read //Appendices 1, 2, 3// and //4//)
Using Puppy from an **U.S.B. flash memory drive** or any other type of //external// drive

Revision [9836]

Edited on 2010-10-12 16:07:25 by coolpup [Lucid edition]
Additions:
-via a //[[InstallationFrugal frugal]]// Puppy installation (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
Deletions:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})

Revision [9835]

Edited on 2010-10-12 16:06:10 by coolpup [Lucid edition]
Additions:
- via a //[[InstallationFrugal frugal]]// Puppy installation (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- via a //[[InstallationFullHDD full]]// Puppy installation (optical disc drive {{color text="required" c="red"}})
Deletions:
- [[InstallationFrugal via a //frugal// Puppy installation]] (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- [[InstallationFullHDD via a //full// Puppy installation]] (optical disc drive {{color text="required" c="red"}})

Revision [9834]

Edited on 2010-10-12 16:04:11 by coolpup [Lucid edition]
Additions:
Using Puppy from an //internal// **hard disk drive** (read //Appendices 1, 2, 3// and //4//)
- [[InstallationFullHDD via a //full// Puppy installation]] (optical disc drive {{color text="required" c="red"}})
Deletions:
Using Puppy from an //internal// **hard disk drive** (also read //Appendices 1, 2, 3// and //4//)
Choose either a full or frugal installation :
- ]]InstallationFullHDD via a //full// Puppy installation]] (optical disc drive {{color text="required" c="red"}})

Revision [9833]

Edited on 2010-10-12 16:03:31 by coolpup [Lucid edition]
Additions:
Using Puppy from an //internal// **hard disk drive** (also read //Appendices 1, 2, 3// and //4//)
Choose either a full or frugal installation :
- [[InstallationFrugal via a //frugal// Puppy installation]] (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- ]]InstallationFullHDD via a //full// Puppy installation]] (optical disc drive {{color text="required" c="red"}})
Deletions:
Using Puppy from an //internal// **hard disk drive**
Choose either a full or frugal installation (also read //Appendices 1, 2, 3// and //4//):
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}})

Revision [9832]

Edited on 2010-10-12 16:00:14 by coolpup [Lucid edition]
Additions:
Then choose how to use Puppy.
Using Puppy from an **optical disc drive**
Using Puppy from an //internal// **hard disk drive**
Using Puppy from an **U.S.B. flash memory drive** or any other type of //external// drive
Deletions:
Then choose how to use Puppy:
- using Puppy from an **optical disc drive**
- using Puppy from an //internal// **hard disk drive** (H.D.D.)
- using Puppy from an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive
**optical disc drive**
**hard disk drive**
**U.S.B. flash drive**

Revision [9831]

Edited on 2010-10-12 15:55:13 by coolpup [Lucid edition]
Additions:
{{nocomments}}
Deletions:
{{no comments}}

Revision [9830]

Edited on 2010-10-12 15:54:27 by coolpup [Lucid edition]
Additions:
{{no comments}}

Revision [9829]

Edited on 2010-10-12 15:53:29 by coolpup [Lucid edition]
Additions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===
Deletions:
{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===

Revision [9828]

Edited on 2010-10-12 15:53:05 by coolpup [Lucid edition]
Additions:
{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===
First acquire the container file (either ISO or ZIP) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.
Deletions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===
First acquire the container file (either ISO or ZIPO) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.

Revision [9826]

Edited on 2010-10-12 15:50:16 by coolpup [Lucid edition]
Deletions:

Revision [9825]

Edited on 2010-10-12 15:49:53 by coolpup [Lucid edition]
Additions:
- Donate to the creator of Puppy Linux [[http://puppylinux.com/download/index.html here]]
Deletions:
- boot from CD
There is no need to install!
On shutdown you will be asked to save (or not to save) your personal settings and data,
you will be guided where to save to
and you can continue starting from cd and using your saved data
If you like to install (later)
it is easy:
Menu > Setup > Puppy Universal Installer
will guide you and explain everything
- Donations to the creator of Puppy Linux via this [[http://puppylinux.com/download/index.html page]]

Revision [9824]

Edited on 2010-10-12 15:06:05 by CrustyLobster [no need to install]
Additions:
- boot from CD

There is no need to install!
On shutdown you will be asked to save (or not to save) your personal settings and data,
you will be guided where to save to
and you can continue starting from cd and using your saved data

If you like to install (later)
it is easy:
Menu > Setup > Puppy Universal Installer
will guide you and explain everything

Revision [9809]

Edited on 2010-10-12 02:25:26 by coolpup [no need to install]
Additions:
First acquire the container file (either ISO or ZIPO) of the desired Puppy Linux version, e.g.: [[Fluppy]] or LupQ.
Deletions:
First acquire the container file (either ISO or ZIPO) of the desired Puppy Linux version, e.g.: [[Wary]], [[Fluppy]], or LupQ

Revision [9808]

Edited on 2010-10-12 02:24:26 by coolpup [no need to install]
Additions:
- using Puppy from an **optical disc drive**
- using Puppy from an //internal// **hard disk drive** (H.D.D.)
- using Puppy from an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive
**optical disc drive**
- This is the simplest way to use Puppy: LiveDVD
**U.S.B. flash drive**
Deletions:
- using Puppy on an **optical disc**
- using Puppy on an //internal// **hard disk drive** (H.D.D.)
- using Puppy on an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive
**optical disc**
- This is the simplest option if an optical disc drive is available: LiveDVD
**U.S.B.**

Revision [9807]

Edited on 2010-10-12 02:21:04 by coolpup [no need to install]
Additions:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap partition {{color text="required" c="red"}})
Deletions:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [9806]

Edited on 2010-10-12 02:10:46 by coolpup [no need to install]
Additions:
First acquire the container file (either ISO or ZIPO) of the desired Puppy Linux version, e.g.: [[Wary]], [[Fluppy]], or LupQ
Deletions:
First acquire the container file (either iso or zip) of the desired Puppy Linux version, e.g.: [[Wary]], [[Fluppy]], or LupQ

Revision [9805]

Edited on 2010-10-12 01:49:25 by coolpup [no need to install]
Additions:
- This is the simplest option if an optical disc drive is available: LiveDVD
Choose either a full or frugal installation (also read //Appendices 1, 2, 3// and //4//):
Deletions:
Simplest option if an optical disc drive is available: LiveDVD
Choose between either a full or frugal installation (also read //Appendices 1, 2, 3// and //4//):
[[http://www.pendrivelinux.com/put-lucid-puppy-on-usb-flash-drive-from-windows/#more-4392 install to USB]]

Revision [9803]

Edited on 2010-10-12 01:05:56 by CrustyLobster [install to USB]
Additions:
Simplest option if an optical disc drive is available: LiveDVD
[[http://www.pendrivelinux.com/put-lucid-puppy-on-usb-flash-drive-from-windows/#more-4392 install to USB]]
Deletions:
This is the simplest option if an optical disc drive is available: LiveDVD

Revision [9795]

Edited on 2010-10-11 07:32:12 by coolpup [install to USB]
Additions:
Then choose how to use Puppy:
- using Puppy on an **optical disc**
- using Puppy on an //internal// **hard disk drive** (H.D.D.)
- using Puppy on an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive
Deletions:
Then choose either:
Puppy on an **optical disc**
Puppy on an //internal// **hard disk drive** (H.D.D.)
Puppy on an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive

Revision [9786]

Edited on 2010-10-11 06:01:48 by CrustyLobster [choose either:]
Additions:
Then choose either:
Puppy on an **optical disc**
Puppy on an //internal// **hard disk drive** (H.D.D.)
Puppy on an **U.S.B.** flash memory drive (U.F.D.) or any other type of //external// drive
**optical disc**
**hard disk drive**
**U.S.B.**
Deletions:
Then choose either option A, B or C:
- (A) using Puppy on an optical disc
- (B) using Puppy on an //internal// hard disk drive (H.D.D.)
- (C) using Puppy on an U.S.B. flash memory drive (U.F.D.) or any other type of //external// drive
__Option A__
__Option B__
__Option C__

Revision [9641]

Edited on 2010-10-01 01:43:53 by coolpup [choose either:]
Additions:
Puppy essentially consists of either three or four compressed files:
- //z*.sfs// (optional)
Deletions:
Puppy essentially consists of three compressed files:
Some Puppy versions contain an additional file: //z*.sfs//

Revision [9640]

Edited on 2010-10-01 01:41:49 by coolpup [choose either:]
Additions:
Choose between either a full or frugal installation (also read //Appendices 1, 2, 3// and //4//):
Deletions:
Please read //Appendices 1, 2, 3// and //4//.
Choose between either a full or frugal installation:

Revision [9639]

Edited on 2010-10-01 01:39:57 by coolpup [choose either:]
Additions:
{{image class="right" url="http://tinypic.com/2anwo6"}}===Using Puppy===
Choose between either a full or frugal installation:
Deletions:
{{image url="http://tinypic.com/2anwo6" }}
===Using Puppy===

Revision [9634]

Edited on 2010-09-30 22:54:37 by CrustyLobster [image added]
Additions:
{{image url="http://tinypic.com/2anwo6" }}

Revision [9546]

Edited on 2010-09-27 04:28:53 by coolpup [image added]
Additions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation, and the ""GRUBforDOS"" boot loader is faster than the Syslinux boot loader)
Deletions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation)

Revision [9545]

Edited on 2010-09-27 04:18:08 by coolpup [image added]
Additions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will possibly also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation)
Deletions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation)

Revision [9544]

Edited on 2010-09-27 04:16:32 by coolpup [image added]
Additions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system because N.T.F.S. permits the use of symbolic links and file sizes greater than 4GB, and there is less/no defragmentation)
Deletions:
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system)

Revision [9543]

Edited on 2010-09-27 04:13:22 by coolpup [image added]
Additions:
This is the simplest option if an optical disc drive is available: LiveDVD
- N.T.F.S. (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader; using this file system is superior to the F.A.T. file system)
Deletions:
With an optical disc drive available option A is the simplest: LiveDVD
- NTFS (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader)

Revision [9542]

Edited on 2010-09-27 04:09:50 by coolpup [image added]
Additions:
First acquire the container file (either iso or zip) of the desired Puppy Linux version, e.g.: [[Wary]], [[Fluppy]], or LupQ
Deletions:
First acquire the container file (either iso or zip) of the desired Puppy Linux, e.g.: [[Wary]], [[Fluppy]], or LupQ

Revision [9505]

Edited on 2010-09-26 14:15:50 by coolpup [image added]
Additions:
First acquire the container file (either iso or zip) of the desired Puppy Linux, e.g.: [[Wary]], [[Fluppy]], or LupQ
Deletions:
First acquire the container file (either iso or zip) of the desired Puppy Linux, e.g.:
- [[http://distro.ibiblio.org/pub/linux/distributions/quirky/ Quirky]]
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]]
- [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]]
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]]
- [[http://murga-linux.com/puppy/viewtopic.php?t=58654 LupQ]]

Revision [9478]

Edited on 2010-09-25 16:17:12 by coolpup [image added]
Additions:
Please read //Appendices 1, 2, 3// and //4//.
Deletions:
Please read //Appendices 1, 2, 3 and 4//.

Revision [9477]

Edited on 2010-09-25 16:16:26 by coolpup [image added]
Additions:
Please read //Appendices 1, 2, 3 and 4//.
Deletions:
Please read //Appendices 1, 2, 3, 4 and 5//.

Revision [9476]

Edited on 2010-09-25 16:15:52 by coolpup [image added]
Additions:
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}})
Deletions:
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}}); <256MB R.A.M.

Revision [9475]

Edited on 2010-09-25 16:13:34 by coolpup [image added]
Additions:
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}}); <256MB R.A.M.
Deletions:
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}})
When performing a Puppy installation choose one of two types:
- [[InstallationFullHDD full installation to an internal drive only]] - recommended for when there is <256MB R.A.M.
- [[InstallationFrugal frugal installation to any type of drive]] - highly recommended for its versatility
===Appendix 6===

Revision [9474]

Edited on 2010-09-25 16:07:17 by coolpup [image added]
Additions:
Please read //Appendices 1, 2, 3, 4 and 5//.
When making an installation to an internal H.D.D. with an existing operating system:
- using an //existing partition// for Puppy (recommended) (see Appendix 3
===Appendix 5===
===Appendix 6===
Deletions:
Please read //Appendices 1, 2, 3 and 4//.
==={{color fg="black" bg="yellow" text="Keeping the existing operating system or not"}}===
- using an //existing partition// for Puppy (recommended)
==={{color fg="black" bg="yellow" text="How to start/boot the computer"}}===

Revision [9473]

Edited on 2010-09-25 15:55:31 by coolpup [image added]
Additions:
- NTFS (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions; it will be necessary to use the GRUBforDOS boot loader)
Deletions:
- NTFS (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions)

Revision [9472]

Edited on 2010-09-25 15:51:30 by coolpup [image added]
Additions:
- (B) using Puppy on an //internal// hard disk drive (H.D.D.)
- (C) using Puppy on an U.S.B. flash memory drive (U.F.D.) or any other type of //external// drive
Deletions:
- (B) using Puppy on a hard disk drive (H.D.D.)
- (C) using Puppy on an U.S.B. flash memory drive (U.F.D.)

Revision [9471]

Edited on 2010-09-25 15:45:22 by coolpup [image added]
Additions:
Please read //Appendices 1, 2, 3 and 4//.
These files are usually distributed in a container file such as an ISO image or a ZIP file. It is this one file that one has to acquire so as to be able to make use of Puppy.
Deletions:
Please read //Appendices 1, 2 and 3//.
These files are usually distributed in a container file such as an iso image or a zip file. It is this one file that one has to acquire so as to be able to make use of Puppy.

Revision [9470]

Edited on 2010-09-25 15:43:40 by coolpup [image added]
Additions:
These files are usually distributed in a container file such as an iso image or a zip file. It is this one file that one has to acquire so as to be able to make use of Puppy.
Deletions:
These files are usually distributed in a container file such as an iso image or a zip file. It is this one file that one has to acquire so as to be able to make use of Puppy. Some good choices are: [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]], [[http://www.murga-linux.com/puppy/viewtopic.php?t=42553 Classic Pup]] and [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]].

Revision [9469]

Edited on 2010-09-25 15:39:12 by coolpup [image added]
Additions:
Please read //Appendices 1, 2 and 3//.
- NTFS (only recommended for when using an external drive, e.g. U.F.D., that will also be used for accessing Microsoft Windows partitions)
Deletions:
Please read //Appendix 1// below first.
- NTFS

Revision [9468]

Edited on 2010-09-25 15:34:08 by coolpup [image added]
Additions:
- making a //new partition// for Puppy (not recommended)
- using an //existing partition// for Puppy (recommended)
- [[InstallationFullHDD full installation to an internal drive only]] - recommended for when there is <256MB R.A.M.
- [[InstallationFrugal frugal installation to any type of drive]] - highly recommended for its versatility
Deletions:
- //making a new partition// for Puppy (not recommended)
- //using an existing partition// for Puppy (recommended)
- [[http://puppylinux.org/wikka/HowToUsePuppy full installation]] - recommended for when there is <256MB R.A.M.
- [[http://puppylinux.org/wikka/HowToUsePuppy frugal installation]] - highly recommended for its versatility

Revision [9467]

Edited on 2010-09-25 15:25:56 by coolpup [image added]
Additions:
- (C) using Puppy on an U.S.B. flash memory drive (U.F.D.)
Some Puppy versions contain an additional file: //z*.sfs//
- either, //append// the Puppy files to an existing file system of some other operating system
- or, //replace// the existing file system with Puppy's
If the Puppy files are to be appended, by making a //frugal installation only// of Puppy, then this would involve one of the following:
- //making a new partition// for Puppy (not recommended)
- //using an existing partition// for Puppy (recommended)
To replace the existing file system with Puppy's perform either a full Puppy installation or a frugal Puppy installation.
Upon starting, the computer needs to select one of its partitions from which to load an operating system. This requires a bit of code called a boot loader located at the root of the boot partition, specifically the Master Boot Record.
When performing a Puppy installation choose one of two types:
- [[http://puppylinux.org/wikka/HowToUsePuppy frugal installation]] - highly recommended for its versatility
===Appendix 3===
When Puppy is to be installed to its own partition it may be formatted with the file system of choice. Use either of the following common types:
- NTFS
The formatting can be performed using a LiveDVD and going to //Menu > System > GParted//.
===Appendix 4===
Deletions:
- (C) using Puppy on an U.S.B. flash drive (U.F.D.)
Some Puppy versions contain an additional file //z*.sfs//.
- either, **append** the Puppy files to an existing file system of some other operating system, e.g. Microsoft Windows
- or, **replace** the existing file system with Puppy's
If the Puppy files are to be appended then this would involve either:
- shrinking the Windows partition to provide the necessary space
Tools like the [[http://partedmagic.com/wiki/PartedMagic.php Parted Magic Live CD]] can reliably repartition the H.D.D. Or use the GParted program on the Puppy LiveDVD. But there are risks, especially if your Windows installation has some underlying corruption. And because there is a learning curve to using a partitioning program, you might not want to practice on your best Windows machine.
- or, stay with one partition, do a frugal install and put the Puppy files inside Windows. For example, the first core file would then become c:\vmlinuz. This is known as a "co-exist" install. Since NTFS became the standard file system format for Windows, there are some reports that if Puppy crashes it can also damage the Windows file system. But many users are running Puppy this way without incident. So one needs to choose between two small risks - corrupting Windows during a drive repartition or corrupting it as a side effect of Puppy failing.
To replace the existing file system with Puppy's perform either a full installation or a frugal installation.
==={{color fg="black" bg="yellow" text=" Which type of Puppy installation to perform"}}===
Choose one of two types:
- [[http://puppylinux.org/wikka/HowToUsePuppy frugal installation]] - recommended for its versatility
==={{color fg="black" bg="yellow" text=" Which type of formatting to perform"}}===
Choose one of two common types:
- FAT
The formatting can be performed using a LiveDVD.
Upon starting the computer needs to select one of its partitions from which to load an operating system. This requires a bit of code called a boot loader located at the root of the boot partition, specifically the Master Boot Record.

Revision [9456]

Edited on 2010-09-25 04:19:42 by coolpup [image added]
Additions:
- Donations to the creator of Puppy Linux via this [[http://puppylinux.com/download/index.html page]]

Revision [9452]

Edited on 2010-09-25 03:56:52 by coolpup [image added]
Additions:
- [[http://distro.ibiblio.org/pub/linux/distributions/quirky/ Quirky]]

Revision [9353]

Edited on 2010-09-18 04:05:39 by coolpup [image added]
Additions:
- http://puppylinux.org/main/index.php?file=Overview%20and%20Getting%20Started.htm

Revision [9258]

Edited on 2010-09-11 03:58:14 by coolpup [image added]
Additions:
- (A) using Puppy on an optical disc
- (B) using Puppy on a hard disk drive (H.D.D.)
- (C) using Puppy on an U.S.B. flash drive (U.F.D.)
Deletions:
- (A) using Puppy with an optical disc
- (B) using Puppy with a hard disk drive (H.D.D.)
- (C) using Puppy with an U.S.B. flash drive (U.F.D.)

Revision [9236]

Edited on 2010-09-10 00:51:57 by coolpup [image added]
Additions:
===References===
Deletions:
===Tutorials===

Revision [9235]

Edited on 2010-09-10 00:50:51 by coolpup [image added]
Additions:
Please read //Appendix 1// below first.
Deletions:
Prior to installing one should read this first: InstallationChoices

Revision [9234]

Edited on 2010-09-10 00:49:19 by coolpup [image added]
Additions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]]
- [[http://murga-linux.com/puppy/viewtopic.php?t=58654 LupQ]]
Then choose either option A, B or C:
- (A) using Puppy with an optical disc
- (B) using Puppy with a hard disk drive (H.D.D.)
- (C) using Puppy with an U.S.B. flash drive (U.F.D.)
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
__Option C__
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
===Appendix 1===
Puppy essentially consists of three compressed files:
- //vmlinuz//
- //initrd.gz//
- //*.sfs// (where the nature of * is determined by the Puppy version)
Some Puppy versions contain an additional file //z*.sfs//.
These files are usually distributed in a container file such as an iso image or a zip file. It is this one file that one has to acquire so as to be able to make use of Puppy. Some good choices are: [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]], [[http://www.murga-linux.com/puppy/viewtopic.php?t=42553 Classic Pup]] and [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]].
==={{color fg="black" bg="yellow" text="Keeping the existing operating system or not"}}===
- either, **append** the Puppy files to an existing file system of some other operating system, e.g. Microsoft Windows
- or, **replace** the existing file system with Puppy's
If the Puppy files are to be appended then this would involve either:
- shrinking the Windows partition to provide the necessary space
Tools like the [[http://partedmagic.com/wiki/PartedMagic.php Parted Magic Live CD]] can reliably repartition the H.D.D. Or use the GParted program on the Puppy LiveDVD. But there are risks, especially if your Windows installation has some underlying corruption. And because there is a learning curve to using a partitioning program, you might not want to practice on your best Windows machine.
- or, stay with one partition, do a frugal install and put the Puppy files inside Windows. For example, the first core file would then become c:\vmlinuz. This is known as a "co-exist" install. Since NTFS became the standard file system format for Windows, there are some reports that if Puppy crashes it can also damage the Windows file system. But many users are running Puppy this way without incident. So one needs to choose between two small risks - corrupting Windows during a drive repartition or corrupting it as a side effect of Puppy failing.
To replace the existing file system with Puppy's perform either a full installation or a frugal installation.
==={{color fg="black" bg="yellow" text=" Which type of Puppy installation to perform"}}===
Choose one of two types:
- [[http://puppylinux.org/wikka/HowToUsePuppy full installation]] - recommended for when there is <256MB R.A.M.
- [[http://puppylinux.org/wikka/HowToUsePuppy frugal installation]] - recommended for its versatility
==={{color fg="black" bg="yellow" text=" Which type of formatting to perform"}}===
Choose one of two common types:
- FAT
- EXT3
The formatting can be performed using a LiveDVD.
==={{color fg="black" bg="yellow" text="How to start/boot the computer"}}===
Upon starting the computer needs to select one of its partitions from which to load an operating system. This requires a bit of code called a boot loader located at the root of the boot partition, specifically the Master Boot Record.
All hard drives that have Windows installed contain a standard block of code in their M.B.R. If this code gets altered Windows will refuse to boot. It is easy to repair with the WinXP Recovery Console and its [[http://www.murga-linux.com/puppy/viewtopic.php?search_id=1691645923&t=16950 //fixmbr//]] command. Vista users should read [[http://neosmart.net/blog/2008/windows-vista-recovery-disc-download/ here]]. This is a crucial issue because Puppy can use its own boot loader. This is not an issue if the existing operating system is to be replaced by Puppy.
So, if the existing operating system is to be kept, one has to choose which operating system is to be the primary one to initiate the boot process:
- either, the //existing// operating system (e.g. Windows)
- or, the //new// operating system (i.e. Puppy)
Do you want to continue using Windows as the primary boot loader? If so, you will need to modify Windows so it presents a start-up menu that includes Puppy as one of the options. These changes have to be made from inside Windows and not from within Puppy. There is an on-line [[http://www.icpug.org.uk/national/linnwin/step00-linnwin.htm tutorial]] called the Lin'N'Win Project that will do this.
Do you want Puppy to be the primary boot loader? This will involve installing GRUB which Puppy can do. Windows will now run as an option from the GRUB boot menu. However, these will only work if you have installed Puppy into its own partition. And the partition must be formatted using a Linux-compatible file system such as EXT3.
The Puppy Universal Installer (P.U.I.) will refuse to install GRUB in a FAT or NTFS partition, because it assumes that the partition contains Windows. Watch for the cryptic error message "This partition is not Linux". Now we get to the M.B.R. issue. The quickest out-of-the-box solution is to install GRUB on the M.B.R. of the H.D.D. The P.U.I. will warn you about the dangers. But this is only an issue if you want to return your machine to a Windows-only setup in the future. In which case, you would simply run the "fixmbr" procedure.
This should explain what can go wrong with a dual-boot system. Suppose that your Linux install gets damaged or you decide to delete it completely. If your ///boot/grub// folder has disappeared, the stage1 code in the MBR won't be able to find its stage2 files. The computer will refuse to boot, even to Windows. But now you know how to fix this by restoring the M.B.R.
===Tutorials===
- [[http://www.lulu.com/product/download/the-puppy-linux-book-v10/4204807 ebook by Grant Wilson]]
- [[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.30 tutorial PDF ]]
- Video Tutorials: TutorialYouTube http://rhinoweb.us/
===Appendix 2===
When you do a full install, all of the data in the core Puppy files is extracted from the CD into a file system on your hard drive. Any software you install or files you save are added to the file system, so the total number of files and folders gradually increases.
In a frugal install, Puppy creates another file named pup_save.2fs. When you boot up, the file system stored in the core Puppy files is loaded into memory, but remains read-only. The save file is used to hold all the new stuff you add. These two are merged together so it appears that you are working with a single file system. You get the effect of a full install while Puppy is running, but all you actually see on your hard drive are the core files and the save file.
The main advantage of a frugal install is that you always boot with pristine copies of the core Puppy files. If the install gets corrupted it is just a matter of restoring the single save file from a backup copy. If your save file gets filled up Puppy has a utility for increasing its size. Or data can be stored/moved outside of the save file.
Frugal installations can be made almost anywhere. You can even stick it inside a full install of Puppy or another Linux. Or you can have multiple frugal installs in the same partition.
GRUB can be installed [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 manually]]. GRUB has two parts - stage1 and stage2. Stage1 is the small block of boot code that gets written onto the M.B.R. Stage2 is the collection of support files that are stored in the folder /boot/grub on the Linux partition. That is also where the GRUB menu file //menu.lst// is located.
Partitioning tools like Parted Magic, or the partitioning programs in some other Linux distributions, can have a major side effect on Puppy: [[http://www.murga-linux.com/puppy/viewtopic.php?p=262324#262324 inode sizes in ext partitions]].
There have been reports that Vista can be corrupted if a user tries to shrink the Windows partition using Linux tools. A safer procedure is to use Vista's own Disk Management tool, then create the new partitions using Linux. If you want to keep Vista as the primary bootloader, look at Easy BCD [[http://neosmart.net/wiki/display/EBCD/EasyBCD+Documentation+Home;jsessionid=4CDEDEBD199D7577A170EDA271A0B04A
here]].
For a frugal installation the file system is placed inside a single file, pup_xxx.sfs, which itself contains a compressed read-only ext2 file system into which the Linux "/" dir is placed, with its sub-directories inside it. There is also a pup_save.2fs file which contains an uncompressed ext2 file system. This one, called the "save file", stores any changes or additions you make to the normal file system. Upon booting, pup_save.2fs is super-imposed over pup_xxx.sfs so that one sees a complete file system. There are only two other small files: initrd.gz and vmlinuz (the kernel). Prior to Puppy Linux 4.00, zdrv_xxx.sfs was also used. Thus you can conveniently back up everything to, for example, a USB flash drive by simply copying /mnt/home/pup_save.2fs (plus vmlinuz, initrd.gz, pup_xxx.sfs) and your GRUB boot loader marker and config files to the drive. Technically though, you only need to back up the pup_save.2fs file, because the rest are all the original files from the .ISO file.
A frugal installation runs faster in high-RAM computers; install is easy to upgrade; and it can be placed on a Windows FAT32 or NTFS hard drive/partition without re-partitioning it.
However, if you have fast newer disks and plenty of R.A.M., frugal loses its speed advantage. On a P3-1GHz machine with 1GB of RAM and UDMA5 hard disks, there is no material performance difference between a frugal install and a full H.D.D install, provided the full install is on a reiserfs partition.
On a P3-800 laptop with only a UDMA2 hard disk, there is a great deal of difference. If you have enough RAM to hold Puppy, e.g. 256MB, then the frugal install is the only way to go.
To be able to dual-boot Puppy alongside Windows without re-partitioning or re-formatting: perform a frugal Puppy installation.
For a full installation the conventional Linux file system [/, /boot, /bin, /etc, /lib, /mnt, /root, /sys, /usr, /var, etc.] is placed straight onto the partition. A full installation runs faster on low-RAM computers.
On a full hard disk install, vmlinuz is (usually) in /boot, Firefox is in /usr/bin and so forth. On a frugal install vmlinuz is outside of pup_save.2fs somewhere on the "real" file system. Firefox in frugal is also in /usr/bin, but /usr/bin itself is not directly on the disk but rather is in /initrd/pup_rw which in reality is pup_save.2fs on the disk's "real" file-system, "union'ed" into the overall Linux / directory tree in pup_xxx.sfs using special Puppy magic.
Another thing frugal installs do is copy the pup_xxx.sfs file into ram if there is enough memory, causing applications to start slightly faster. If the computer does not have sufficient RAM, it will instead mount the pup_xxx.sfs file from the HDD.
In the case that a frugal install's pup_save.2fs file is on a flash-based drive, Puppy will actually store any changes and new files you make in RAM, and only copy them to the pup_save.2fs file on the drive periodically (or when you click the "save" icon or shut down). This is to cut down on writes to the drive to extend it's life. This behavior does not happen on non-flash media (if it does you probably forgot to set the pmedia=satahd parameter when using a SATA drive).
You can place a frugal install on a pre-existing [[http://puppylinux.org/wikka/Win98 Win98]] install; the pup_save.2fs (though it itself contains an ext2 filesystem) may reside on a FAT32 or NTFS partition. Which is why a frugal install is also called a "co-exist" install. Not so with a full hard disk drive install: you cannot place a full install on a pre-existing FAT partition because it does not support Linux symlinks.
Puppy can be booted off a non-primary partition. Or you can have the PUI write GRUB's stage1 to a floppy boot disk. Or you can do the frugal install manually and use a [[http://www.murga-linux.com/puppy/viewtopic.php?t=16950 boot CD]] to launch it. In that case, you could even put Puppy in a logical FAT partition which would be sharable with Windows.
Deletions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition]] with extra multi-lingual support)
Then choose either option A or option B:
- (A) create a ""LiveDVD""
- (B) create an installation
- InstallationFrugal (H.D.D. & U.S.B.) (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [9231]

Edited on 2010-09-09 10:32:00 by coolpup [image added]
Additions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]]
Deletions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (extra support for older hardware with Xorg 7.3+ and Kernel 2.6.32.16)

Revision [9127]

Edited on 2010-09-01 04:57:00 by coolpup [image added]
Additions:
- InstallationFrugal (H.D.D. & U.S.B.) (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
Deletions:
Hard disk drive (H.D.D.) installations:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
U.S.B. flash drive installations:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [9126]

Edited on 2010-09-01 04:53:59 by coolpup [image added]
Additions:
Hard disk drive (H.D.D.) installations:
Deletions:
H.D.D. installations :

Revision [9125]

Edited on 2010-09-01 04:53:07 by coolpup [image added]
Additions:
H.D.D. installations :
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
U.S.B. flash drive installations:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
Deletions:
Frugal installations (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}}):
- H.D.D.: InstallationFrugal
- U.S.B. flash drive: InstallationFrugal
Full installations:

Revision [9124]

Edited on 2010-09-01 04:50:14 by coolpup [image added]
Deletions:
- InstallationFullUSB

Revision [9118]

Edited on 2010-08-30 14:37:44 by coolpup [image added]
Additions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition]] with extra multi-lingual support)
Deletions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition]] with extra multi-lingual keyboard support)

Revision [9117]

Edited on 2010-08-30 14:37:04 by coolpup [image added]
Additions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (extra support for older hardware with Xorg 7.3+ and Kernel 2.6.32.16)
Deletions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (support for older hardware with Xorg 7.3+ and Kernel 2.6.32.16)

Revision [9116]

Edited on 2010-08-30 14:36:28 by coolpup [image added]
Additions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (support for older hardware with Xorg 7.3+ and Kernel 2.6.32.16)
Deletions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (support for older hardware)

Revision [9115]

Edited on 2010-08-30 14:24:38 by coolpup [image added]
Additions:
- InstallationFullHDD (optical disc drive {{color text="required" c="red"}})
Deletions:
- InstallationFullHDD

Revision [9114]

Edited on 2010-08-30 14:22:59 by coolpup [image added]
Additions:
Frugal installations (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}}):
- H.D.D.: InstallationFrugal
- U.S.B. flash drive: InstallationFrugal
Full installations:
Deletions:
- InstallationFrugal (both to H.D.D. & U.S.B. flash drive) (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [9111]

Edited on 2010-08-30 14:11:56 by coolpup [image added]
Additions:
- InstallationFrugal (both to H.D.D. & U.S.B. flash drive) (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
Deletions:
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [9109]

Edited on 2010-08-30 14:06:37 by coolpup [image added]
Additions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition]] with extra multi-lingual keyboard support)
Deletions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition with extra multi-lingual keyboard support]]

Revision [9108]

Edited on 2010-08-30 14:05:41 by coolpup [image added]
Additions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (support for older hardware)
- [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]]
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition with extra multi-lingual keyboard support]]
Deletions:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (suitable for older hardware)
- [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]] (suitable for older hardware)
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] (suitable for newer hardware) ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition with extra multi-lingual keyboard support]]

Revision [9107]

Edited on 2010-08-30 14:03:58 by coolpup [image added]
Additions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] (suitable for newer hardware) ([[http://murga-linux.com/puppy/viewtopic.php?t=58654 Quickset edition with extra multi-lingual keyboard support]]
Deletions:
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] (suitable for newer hardware)
- Puppy 5 Quickset edition with extra [[http://murga-linux.com/puppy/viewtopic.php?t=58654 multi-lingual keyboard]] support

Revision [9106]

Edited on 2010-08-30 14:02:33 by coolpup [image added]
Additions:
===Using Puppy===
First acquire the container file (either iso or zip) of the desired Puppy Linux, e.g.:
- [[http://bkhome.org/blog/?viewDetailed=01771 Wary]] (suitable for older hardware)
- [[http://murga-linux.com/puppy/viewtopic.php?p=422444#422444 Fluppy]] (suitable for older hardware)
- [[http://puppylinux.org/main/index.php?file=Download%20Latest%20Release.htm Puppy 5]] (suitable for newer hardware)
- Puppy 5 Quickset edition with extra [[http://murga-linux.com/puppy/viewtopic.php?t=58654 multi-lingual keyboard]] support
Then choose either option A or option B:
Deletions:
===Using Puppy:===
Choose either option A or option B:

Revision [9015]

Edited on 2010-08-25 03:57:30 by coolpup [image added]
Additions:
Prior to installing one should read this first: InstallationChoices
Deletions:
- InstallationChoices

Revision [9013]

Edited on 2010-08-25 03:22:10 by coolpup [image added]
Additions:
- (A) create a ""LiveDVD""
With an optical disc drive available option A is the simplest: LiveDVD
Deletions:
- (A) create a LiveDVD
If you have an optical disc drive option A is the simplest.

Revision [9012]

Edited on 2010-08-25 03:19:23 by coolpup [image added]
Deletions:
[[http://www.murga-linux.com/puppy/ Free Technical Support]]

Revision [8914]

Edited on 2010-08-22 05:15:39 by coolpup [image added]
Additions:
- InstallationChoices
Deletions:
- InstallationNotes

Revision [8876]

Edited on 2010-08-20 13:35:22 by coolpup [image added]
Additions:
Choose either option A or option B:
Deletions:
Choose either option A or B:

Revision [8875]

Edited on 2010-08-20 11:58:06 by coolpup [image added]
Additions:
__Option A__
Deletions:
_Option A__

Revision [8874]

Edited on 2010-08-20 11:57:43 by coolpup [image added]
Additions:
_Option A__
__Option B__
Deletions:
===Option A===
===Option B===

Revision [8873]

Edited on 2010-08-20 11:57:20 by coolpup [image added]
Additions:
===Option A===
===Option B===
Deletions:
===Installation===

Revision [8860]

Edited on 2010-08-20 11:29:25 by coolpup [image added]
Additions:
Choose either option A or B:
- (A) create a LiveDVD
- (B) create an installation
If you have an optical disc drive option A is the simplest.
Deletions:
- either, create a LiveDVD
- or, create an installation

Revision [8845]

Edited on 2010-08-20 08:38:05 by coolpup [image added]
Additions:
===Using Puppy:===
- either, create a LiveDVD
- or, create an installation
Deletions:
Using Puppy perform one of the following options:
- create a LiveDVD
- create an installation

Revision [8844]

Edited on 2010-08-20 08:37:01 by coolpup [image added]
Additions:
Using Puppy perform one of the following options:
Deletions:
To be able to use Puppy perform one of the following options:

Revision [8841]

Edited on 2010-08-20 07:51:34 by coolpup [image added]
Additions:
To be able to use Puppy perform one of the following options:
[[http://www.murga-linux.com/puppy/ Free Technical Support]]
Deletions:
To be able to use Puppy perform one of the following:
===[[http://www.murga-linux.com/puppy/ Free Technical Support]]===

Revision [8787]

Edited on 2010-08-18 05:09:58 by coolpup [image added]
Additions:
- create a LiveDVD
Deletions:
- create a [[http://puppylinux.org/wikka/CreateLiveCDorDVD LiveDVD]]

Revision [8785]

Edited on 2010-08-18 05:05:41 by coolpup [image added]
Deletions:
===Tutorials===
- [[http://www.lulu.com/product/download/the-puppy-linux-book-v10/4204807 ebook by Grant Wilson]]
- [[http://puppylinux.org/main/Puppy430-tutorial-English.pdf Puppy Linux 4.30 tutorial PDF ]]
- Video Tutorials: TutorialYouTube http://rhinoweb.us/
===[[PuppyLinuxSearchEngine Puppy Linux Search Engine]]===

Revision [8783]

Edited on 2010-08-18 05:03:41 by coolpup [image added]
Additions:
To be able to use Puppy perform one of the following:
- create a [[http://puppylinux.org/wikka/CreateLiveCDorDVD LiveDVD]]
- create an installation
Deletions:
To be able to use Puppy either:
- use a [[http://puppylinux.org/wikka/CreateLiveCDorDVD LiveDVD]]
- or, perform an installation

Revision [8781]

Edited on 2010-08-18 04:58:43 by coolpup [image added]
Additions:
To be able to use Puppy either:
- use a [[http://puppylinux.org/wikka/CreateLiveCDorDVD LiveDVD]]
- or, perform an installation
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}; >=256MB R.A.M. or swap space {{color text="required" c="red"}})
Deletions:
To be able to use Puppy either run a [[http://puppylinux.org/wikka/CreateLiveCDorDVD LiveDVD]] or perform an installation.
- InstallationFrugal (optical disc drive {{color text="optional" c="green"}}) (>=256MB R.A.M. or swap space {{color text="required" c="red"}})

Revision [8767]

The oldest known version of this page was created on 2010-08-18 03:23:03 by coolpup [image added]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki