How to Create a Full Installation on an Internal Device (H.D.D. or S.S.: PuppyLinux

Revision [607]

This is an old revision of InstallationFullHDD made by coolpup on 2009-08-25 00:55:08.

It is assumed that your PC is able to boot from an optical disc drive, and that you are installing to an internal hard disk drive.
 
 
Please note that the partition sizes used are for example only; make yours to the sizes that you want. As to the size of the SWAP partition, it is usually recommended that it is twice the size of your RAM. So if you have 128MB of RAM, create a SWAP partititon of 256MB,
 
 
Before starting, make a note of what screen resolution your graphics card/monitor can handle; you will need this information soon after booting the CD.
 
 
Also note that because this was done using QEMU, i had to use Xvesa therefore i cannot show any screenshots for the Xorg sequences.
 
 
QEMU is a generic and open source machine emulator and virtualizer. For more information, visit the <a class="postlink" target="_blank" href="http://bellard.org/qemu/about.html">QEMU website.</a> 
So for the purpose of this how-to, just ignore the QEMU window, you will not see it yourself, so do not expect to.
 
 
Part 1. Booting to the desktop.
 
 
Place the Puppy LiveCD/DVD into the drive and re-boot the computer.
 
 
The first thing you see will be this:
 
Image-1
 
<a class="postlink" target="_blank" Unknown action; the action name must not contain special characters.><img border="0" Unknown action; the action name must not contain special characters./></a>
 
 
Next you will be asked to select the keyboard layout:
 
Image-2
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=32&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/210.png" /></a>
 
Use the up/down arrows on the keyboard to make your choice then press ENTER/RETURN for OK.
 
 
Next you will be asked to choose either Xorg or Xvesa, make your choice (try Xorg first, if that fails then use Xvesa):
 
Image-3
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=33&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/310.png" /></a>
 
If you need to use Xvesa use the TAB key to make your selection then press ENTER/RETURN for OK.
 
 
If you chose Xorg, you then need to select a screen resolution:
 
Select an appropriate resolution then press ENTER/RETURN for OK.
 
 
Now test it:
 
Again, use the TAB key to select Test, then press ENTER/RETURN for OK
 
 
If it works, thats good, if it did not, then try with Xvesa
 
now do the linux three finger shuffle (Ctrl + Alt + Backspace)
 
 
If you chose Xvesa you will then see this:
 
Image-4
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=34&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/610.png" /></a>
 
Select an appropriate resolution and click Change
 
 
When the desktop comes back up, along with the Xvesa video wizard click OKAY
 
 
You should now be at the desktop like this:
 
Image-5
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=35&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/710.png" /></a>
 
 
 
Part 2. Partitioning and Formatting the drive.
 
 
Now for the main part of this how-to.
 
 
Right click the desktop to get the menu up,
 
now go to System > GParted partition manager
 
Image-6
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=36&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/810.png" /></a>
 
 
Next click to highlight where it says unallocated (where it is blue in the picture below)
 
Then click on New to create a new partition.
 
Image-7
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=37&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/910.png" /></a>
 
 
You will get something similar to this:
 
Image-8
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=38&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1010.png" /></a>
 
 
Make the partition to the size you wish, as you can see below, i left enough space for the SWAP partition.
 
For Filesystem you can choose either ext2 or ext3.
 
 
If you are wondering what the difference is between the Filesystems,
 
and would like to know more, please check out the following links:
 
 
<a class="postlink" target="_blank" href="http://en.wikipedia.org/wiki/Ext2">http://en.wikipedia.org/wiki/Ext2</a>
 
<a class="postlink" target="_blank" href="http://en.wikipedia.org/wiki/Ext3">http://en.wikipedia.org/wiki/Ext3</a>
 
 
Image-9
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=39&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1110.png" /></a>
 
Click on Add
 
 
Once again click to highlight unallocated, then New
 
Image-10
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=40&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1210.png" /></a>
 
 
Now create the SWAP partition (be sure to select linux-swap as Filesystem)
 
Image-11
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=41&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1310.png" /></a>
 
click on Add
 
 
Next click on Apply
 
Image-12
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=42&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1410.png" /></a>
 
 
And again, click on Apply
 
Image-13
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=43&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1510.png" /></a>
 
 
You will now see it Applying pending operations
 
Image-14
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=44&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1610.png" /></a>
 
 
When it has finished, click on Close
 
Image-15
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=45&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1710.png" /></a>
 
 
Now click to highlight /dev/hda1
 
then RIGHT click and select Manage Flags.
 
Image-16
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=46&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1810.png" /></a>
 
 
Now click to select boot.
 
Image-17
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=47&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/1910.png" /></a>
 
when its ready click on Close.
 
 
Things should now look something like this.
 
Image-18
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=48&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2010.png" /></a>
 
If so, you can now close GParted, we are finished with it.
 
 
 
Part 3. Install Time.
 
 
Now we will use the Puppy Universal Installer to make a full installation to hda1, followed by installing GRUB to the MBR.
 
 
So again RIGHT click the desktop and go to Setup > Puppy universal installer
 
Image-19
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=49&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2110.png" /></a>
 
 
Select Internal (IDE or SATA) hard drive
 
Image-20
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=50&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2210.png" /></a>
 
Then click OK
 
 
Next choose which drive to install to (in this case it is hda)
 
Image-21
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=51&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2310.png" /></a>
 
Then click OK
 
 
Next select the partition to install to (in this case it is hda1)
 
Image-22
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=52&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2410.png" /></a>
 
 
Confirm your choice, by clicking on OK
 
Image-23
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=53&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2510.png" /></a>
 
 
Now tell it where the files are, in this case click on CD
 
Image-24
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=54&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2610.png" /></a>
 
 
Click OK again
 
Image-25
 


<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=55&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2710.png" /></a> 
 
Next we will choose FULL
 
Image-26
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=56&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2810.png" /></a>
 
 
Now wait, while it copies files to the hard drive
 
Image-27
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=57&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/2910.png" /></a>
 
Image-28
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=58&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3010.png" /></a>
 
 
Now we will install GRUB
 
Image-29
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=59&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3110.png" /></a>
 
 
Select INSTALL
 
Image-30
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=60&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3210.png" /></a>
 
 
Click OK
 
Image-31
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=61&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3310.png" /></a>
 
 
Choose simple and click OK
 
Image-32
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=62&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3410.png" /></a>
 
 
Select standard and click OK
 
Image-33
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=63&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3510.png" /></a>
 
 
Accept the default entry (in this case /dev/hda1) and click OK
 
Image-34
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=64&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3610.png" /></a>
 
 
Scroll down the list, and select MBR and click OK
 
Image-35
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=65&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3710.png" /></a>
 
 
Hopefully you will get confirmation that GRUB was successfully installed
 
Image-36
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=66&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3810.png" /></a>
 
Click OK
 
 
We are now finished with the Universal Installer, so click on NO
 
Image-37
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=67&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/3910.png" /></a>
 
 
Now REBOOT (REMOVE the CD from the drive first)
 
Image-38
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=68&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/4010.png" /></a>
 
 
Answer NO when asked if you want to save
 
Image-39
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=69&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/4110.png" /></a>
 
 
When it reboots, you should see the GRUB boot screen,
 
(in this case Linux (on /dev/hda1)) is already selected so just hit ENTER/RETURN
 
Image-40
 
<a class="postlink" target="_blank" href="http://www.servimg.com/image_preview.php?i=70&u=12365505"><img border="0" src="http://i46.servimg.com/u/f46/12/36/55/05/4210.png" /></a>
 
 
You will need to make your choice of Keyboard Layout, and Xorg or Xvesa once again.
 
 
When you get to the desktop, that is it done.
 
 
Next time you reboot, after selecting the partition to boot via GRUB you should go straight to the desktop.
 
 
 
CatDude

<h1>Appendix</h1>

[data from previous articles]

<h2> install</h2>
<div class="indent">
1. Use Gparted from the Control Panel menu to create an ext3 and linux swap partition. Maximum size of the swap partition should be 2 x RAM. 
2. Use the Puppy Universal Installer from the Setup menu to perform a NORMAL install. 
3. When prompted, put Grub's boot loader in the MBR of the hard drive. The other Grub files will be placed in a /boot directory on the ext3 partition
</div>
 
A laptop with 128Mb RAM or more would best be served by a FRUGAL install. After Step 1 above: 
 
<div class="indent">
1. Copy vmlinuz, initrd.gz, pup_212.sfs and zdrv_212.sfs to the / directory of the hard drive. 
2. Use the Grub bootloader config program from the Control Panel menu to install. 
3. Edit the /boot/grub/menu.lst file to read 
Quote: 
title <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/PuppyLinux/edit">Puppy Linux</a> 
root (hd0,0) 
kernel (hd0,0)/vmlinuz pmedia=idehd 
initrd (hd0,0)/initrd.gz
</div>
 
Note: the .sfs files have to be in the / directory, but the vmlinuz and initrd.gz files can also be copied to a sub-directory e.g. /puppy212; 
in this case the GRUB entries need to be changed accordingly to show the path to these files like: 
<div class="indent">
kernel /puppy212/vmlinuz pmedia=idehd 
initrd /puppy212/initrd.gz
</div>
This is needed when installing multiple versions of puppy, where for each version the vmlinuz and initrd.gz files have to be copied to their own sub-directory since these names do not change with the version (but all .sfs files for all versions in the / directory). 
<div class="indent">
 
</div>
<h3>Hard Disc Drive Install</h3>
 
<h3>Update for 2.xx Universal Installer Bug</h3>
1) boot <a href="http://puppylinux.org/wikka/LiveCD">LiveCD/DVD</a>; 
2) run GParted and create 2 partitions 
<ol type="2">

<li> One(1) 0.5GB plus Primary ext3 (1.5Gb to 2.5Gb should be plenty for most users);

</li>

<li> One(1) 2 x RAM (max 0.5Gb) Primary linux-swap;</li>

</ol>
3) run Puppy Universal Installer, pick IDE (ATA) internal Drive installation 
4) install onto the ext3 partition you created 
5) follow the on-screen direction from this point 
6) when prompted, install the GRUB bootloader to MBR of the drive. 
 
2 partitions to choose from straightens out the script, and you'll want a swap area of some type anyway. 
 
<a href="http://puppylinux.org/wikka/HardDiskInstall">See also Installing Puppy Linux to Your Hard Drive</a> 
 
<h2>How to make a bootable hard drive that is dedicated to Puppy Linux.</h2>
<div class="indent">
For Linux Newbies.
</div>
 
<div class="indent">
Why would you want to do this? 
Because you want to experiment with reconfiguring Puppy. (And maybe all the other wonderful Puppy features for saving configuration info are not quite working for you yet.)
</div>
 
Is this easy? 
<div class="indent">
NO. If you have a hard drive that you are prepared to dedicate completely to Puppy, it should be easy, but if you are new to Linux it is not. Yet. You cannot just press a button and have Puppy take over the hard drive.
</div>
 
Why isn't it easy? 
<div class="indent">
Mostly, because no one has done the work yet to make it easy. (Maybe you will fix this? Someday.) 
The available Puppy hard disk install process is too timid. It wants to coexist with other uses of the hard disk. This means in most cases using a boot floppy to get Puppy started from the hard disk. Maybe that is what you want. But if you want to take over the hard drive and have Puppy be bootable and self contained, read on.
</div>
 
What size HDD do I need? 
<div class="indent">
A minimal hard drive install seems to use about 100MB. So 200MB might be a minimum. 500MB to 1GB should be plenty for most experimental purposes. You might need more for heavy-duty re-compiling re-mastering etc. So, most any old scavenged hard drive that is not defective should be plenty big. And you might want to avoid drives over 8GB if you want to experiment with transplants into older computers, which can have problems with larger drives.
</div>
 
The rest of this assumes that you will be choosing OPTION-2 in the install procedure. 
 
In order to have a bootable hard drive, four steps have to succeed: 
1) PARTITION (Pdisk, fdisk, cfdisk) 
2) FORMAT (mkfs, mke2fs?) 
3) LOAD PUPPY SOFTWARE (Option-2) 
4) MAKE BOOTABLE (Grub, MBR) 
 
The OPTION-2 script handles most of this OK -- except unfortunately for Step 1 - Partition. Partitioning and Formatting are actually somewhat separate and potentially rather complex matters. The script is likely to need you to take care of Step 1 manually. 
Steps 2-4 the script should be able to walk you through and it should do most of the hard work. (Even if your goal is a bootable hard drive, it will encourage you to make a boot floppy, too. Not much harm in having one for back-up, but it does add another tedious step to the process, and you can choose to skip it.) 
<div class="indent">
 
IF you are trying this with Puppy 1.0.5, there is a bug in the process; you may end up with a hard drive that partially runs, but cannot start X (the windows-graphics interface) up. You may be able to cure this by booting from a CD and copying /usr to the hard drive. Or by patching 1.0.5. Or by researching more about the bug, in the forums. But the easiest cure is to use 1.0.6. 
 
IF you have an existing FAT (<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Fat12/edit">Fat12</a>/<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Fat16/edit">Fat16</a>) MS-DOS type partition, OPTION-2 will try to convert it, but will probably fail. You might as well delete the partition. You can do this by fiddling with PDISK, or use other tools if you are more familiar/comfortable with them. 
 
IF you have an existing partition of just the type that Puppy wants (perhaps you are updating Puppy) you will probably be in trouble! Because Puppy probably already mounted the partition during your last boot, in order to use it. Because it is mounted, the update process will refuse to change it! You will have to find a trick to boot from the CD without using/mounting that partition. One way to do this is use PDISK to delete the partition. Fortunately, PDISK is too dumb to realize that it should not allow you to delete a partition that you are using! So you can just delete the partition (this just removes the MBR partition entry), then reboot. 
 
IF you have no partitions on the hard drive, OPTION-2 will fail. You will need to use PDISK or some other method to create a partition. Then at long last you may actually be able to successfully run OPTION-2 and make a hard drive that can boot itself with GRUB. 
 
(What we really need is a new OPTION-3: NUKE THE HARD DRIVE, IGNORE ANY EXISTING CONTENTS, WRITE ZEROES TO SECTOR 0, AND MAKE A BOOTABLE PUPPY HARD DRIVE.)
</div>
 
-k 18nov05 
 
<a href="http://puppylinux.org/wikka/PdisK">Pdisk</a> 
 
 
What if this isn't working for me? 
<div class="indent">
First, make sure that you can actually boot from that hard drive in that computer. Do this by using some tool to wipe the hard drive clean and installing a bootable test system on it, like a simple minimal MS-DOS 6.22.
</div>
If that works, be aware that left over data on the hard drive could be confusing things. Changing partitioning and formatting are actually separate and quite confusing matters. The better you wipe the drive to all zeroes, the less potential for confusion. In most cases just zeroing the first sector (the MBR) should give you a fresh start, but if things aren't working try zeroing out the whole volume. Look into making sure the drive is not only properly partitioned, but also FORMATTED if necessary. 
You could try avoiding fdisk and using cfdisk instead, since it has a better reputation. 
 
<a href="http://puppylinux.org/wikka/HardDriveInstallBruce">HardDriveInstallBruce</a> 
<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/BruceB/edit">BruceB</a> excerpts from the Forum 
 
See Also: 
<a class="ext" href="http://www.murga.org/~puppy/viewtopic.php?t=3665∞">http://www.murga.org/~puppy/viewtopic.php?t=3665∞</a>∞; 
Post subject: HD install routine 
Apologies if someone has already sussed this, but installing Puppy to HD can be very problematic... 
 
 
Posted: Sat Nov 12, 2005 8:50 pm 
The purpose of my post is to explain some of the obstacles could encounter in an Option 2, and techniques a person could use. And ramble on some. 
 
Puppy's default creates a pupxxx user file on a filesystem it deems the best one to use. This might not be the filesystem you would have liked it to create the pupxxx file. There are many ways to control where the pupxxx file is created and how large it is. But the default is to let Puppy make this decision. 
 
One problem people have when attempting to do an Option 2 install is that they want to install on the same partition that the 'mounted' pupxxx file is on. 
 
The install routine will not install on a 'mounted' partition. 
 
One work around is: at boot time don't let Puppy mount the pupxxx file at all. This way the partitions will be unmounted and likely available for an Option 2 install. 
 
At install time, Puppy will give a you a list of available partitions to install to. 
 
<hr />
 
Changing subject a little. I think a lot of people conceptualize Linux as mounting drives and / or partitions, which it does do. I'd like to sell the idea of conceptualizing Linux as an operating system that mounts filesystems. For an example, the way the Puppy uses the pupxxx file is: 
 
1) it mounts the filesystem where the pupxxx file is on 
2) it mounts the pupxxx file as a filesystem 
 
The result is: One partition mounted with two separate mounted filesystems. 
 
 
<hr />
 
More change of subject. 
 
Marking a FAT filesystem as hidden doesn't hinder Linux' ability to mount and use the filesystem. Although, it could be that the Puppy install scripts deal with hidden FAT partitions in different ways, according to the scripting. 
 
<hr />
 
About DOS Fdisk programs: 
 
The DR DOS fdisk only recognizes about 8 GB, it's a good FDISK otherwise. If you format a partition with DR DOS format, it will be a good format. If MS-DOS / Windows accesses that filesystem it will damage it. 
 
The PC DOS (IBM) fdisk won't access large drives either. 
 
<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> fdisk, sys and format utilities had the same problem with MS-DOS behaving destructively against their work. The <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> community was informed about the cause of puzzling behavior MS-DOS on their filesystem. They corrected the problems in July 2004. 
 
DR DOS version 8.0 corrected the problem, the 7.03 version still leaves itself wide open to the MS-DOS bad behavior. 
 
Simply stated the Microsoft Operating system thru virtually all DOS and Windows versions through ME do this: It reads a text field in the boot sector of each FAT partition and adjusts behavior according to the text string it finds. This eight text string is called the OEM ID field. 
 
It is officially denied that Microsoft uses this field in its specifications and other places. Programmers naive enough to believe the official documentation fall into a trap sometimes of writing an OEM text string that triggers MS bad beahvior and don't know what is going on because they did everything right (or so they think). 
 
As far as FDISK programs go, if you are working with big drives, MS Fdisk and <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> Fdisk are viable options. Generally, I use the MS fdisk on big drives, (any drive for that matter). 
 
It is however helpful to understand its personality as well as some Puppy limits. 
 
Puppy's compilation will only recognize up to 9 partitions per hard drive. Considering that the extended partition is not mountable, this means with Puppy you can have up to 8 working partitions per hard disk. 
 
Typically, people set up a primary, then extended, then logical partitions. Doing it that way, they might end up with something like this: 
 
hda1 primary 
hda4 extended (and unmountable) 
hda5 logical 
hda6 logical 
hda7 logical 
hda8 logical 
hda9 logical 
 
If your scheme does look like this you've reached the Puppy limit of 6 as there is no device driver for hda10 and you don't have an hda2 and hda3 
 
In order that I can have 8 usable partitions I do it like this: 
 
hda1 primary 
hda2 primary 
hda3 primary 
hda4 extended (and unmountable) 
hda5 logical 
hda6 logical 
hda7 logical 
hda8 logical 
hda9 logical 
 
 
MS-DOS Fdisk will not create hda2 primary or hda3 primary. Linux cfdisk would create these partitions, but if you used MS-DOS Fdisk to make the extended partition AND you marked hda2 and hda3 as Linux partitions, MS-DOS Fdisk would write the partition inside the Linux partition and make things unusable. If you marked hda2 and hda3 as FAT with Cfdisk, then MS-DOS Fdisk will put the extended partition where it belongs. This is probably very unintentional on MS' part. 
 
There are also other DOS based fdisk utilities that will make hda2 and hda3. Aefdisk will do it and I'm pretty sure the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> fdisk will do it. 
 
One point I wish to make is that using DOS based fdisk utilities, I can create complex Linux partitioning schemes. In the example above, after I setup the partitions, I'd use the DOS aefdisk to mark each partition according to the filesystem I wish it to contain. 
 
If for example I wanted hda9 to be a Linux swap filesytem, I'd mark it as type 82, then when I boot Linux I'd format it accordingly. 
 
<hr />
 
As far as PQmagic is concerned. It is a very powerful tool. But if you use it, you may get stuck with it as your partitioning tool. 
 
Suppose I wanted to delete logical partitions hda8 and hda9. If I do it with Linux fdisk or MS fdisk, I still have free space in the extended partition. I can then make other partitions in the extended partition. 
 
If I delete hda8 and hda9 with PQmagic, it resizes the extended partition to contain hda5 thru hda7. You still have free space on the hard drive, but it is not in the extended partition. What to do? Use PQmagic to handle the free space, as other utilities might not be able to, or give you results you don't want. 
 
I'm not trying to knock PQmagic, I think enough of it that I purchased three version over the course of years. But it does do what it does. 
 
 
<hr />
 
In conclusion: I think the easiest why to prepare for an Option 2 install, is mark the partition you want to install it on as type 83, don't format it. Boot Puppy and it won't mount that partition because there is no filesystem on it to work with. It will therefore be available as a useable, properly marked, and unmounted partition for Puppy to install on. 
 
 
= = = = = = = = = = = = = 
 
Posted: Tue Nov 15, 2005 5:00 am 
 
OPTION 1 HARD INSTALL VS. BOOTING FROM CD DISC 
 
The Option 1 install will boot a lot faster than the CD disc. The reason why is, the computer can read the hard disk faster than a CD disc. There are about 60 MB worth of data that has to be located and read. 
 
Once the computer has been booted the actual operation theoretically should be identical. The three key files necessary to boot Puppy only get read one time, and they are not used or needed again. 
 
An exception would be on a low memory system. The file usr_cram.fs normally gets copied to RAM then mounted as a file system. If Puppy calculates that the computer doesn't have enough RAM to copy usr_cram.fs into RAM, it will mount it and read it as needed from where it is. 
 
 
OPTION 2 INSTALL VS. OPTION 1 HD INSTALL 
 
Puppy will boot markedly faster with Option 2 than with Option 1. The principle reasons are that it doesn't need to copy usr_cram.fs to RAM, and it doesn't need to setup and configure a file system, as the file system is already in place and ready to go. 
 
Read operations will be slower from hard disk than RAM, simply because the hard disk is slower. On the other hand the files read don't go through the same decompression process. In actual practice the computer should be able to locate and read a small file off the hard disk so fast you wouldn't notice the read time. 
 
If you were to launch a large program like Mozilla, it should take 'noticably' longer time to read it from the hard disc as it would from RAM. 
 
Once Mozilla's working components are loaded in memory, they should run about the same speed. 
 
Except for the very fast boot, an Option 2 is slower in some areas of operation than an Option 1. 
 
There is an exception to this rule and that is with low memory systems. An Option 1 uses up considerably more RAM space than an Option 2, because all the filesystem is in RAM and taking up space, except for /root and whatever you have mounted yourself. 
 
If your computer doesn't have sufficient RAM and is actively using a swap file system for its normal operations on an Option 1, it is very likely that it would run faster with an Option 2 because there is more RAM to work with before it needs to swap. 
 
<hr size="2" width="100%" />
 
For Quick hard disk installs of Puppy 1.03 to 1.05 (in separate partition or in <a href="http://puppylinux.org/wikka/WinXP">WinXP</a>) 
<a class="ext" href="http://ph-islands.net/pupinstall/">TRY THIS Tutorial FIRST</a>∞ 
 
<a href="http://puppylinux.org/wikka/HardDriveInstall">See also Hard Drive Install / Hard Disk Install BOOTABLE</a> 
 
<h3>Step by Step: Installing Puppy Linux to Your Hard Drive</h3>
<h5>A Linux Newbie Guide</h5>
 
This tutorial shows you how to install Puppy Linux to a DOS formatted HD. To install Puppy 
onto a HD with a pre-existing OS present (i.e. Windows) to achieve a dual boot setup, is 
<div class="indent">
not covered in this how-to (you should check <a href="http://puppylinux.org/wikka/Installing">Installing</a> and look for frugal install). If you follow this sequence, you'll end up with a HD with only
</div>
Puppy Linux and MS-DOS installed. 
 
<h5>Software You Need:</h5>
1. A bootable copy of Puppy Linux 1.0.4
on a CD. Make sure it is Checksumed before burning the ISO (link), make
sure it is burned properly (link), and check to make sure that it is
actually bootable by actually booting it. 
2. Darik's Boot and Nuke
(DBN) on a Floppy or another disc-wiping program. (This is necessary
for disc 'wiping' or erasing which is an optional process.) 
3. MS-DOS 6.22 - usually on 3 floppy discs. 
 
To format your Hard Drive, you could install MS-DOS onto your HD, then run 'format c:' 
I prefer totally wiping out the HD using DBN, then installing MS-DOS. 
 
Let's begin. 
 
Important: 
Before Beginning Install 
If your computer has more than one CD/DVD device, then before 
installing Puppy, DISABLE the non-install media device. 
 
This means, if you have both a CD-ROM and a DVD device, and 
you will install Puppy from the CD-ROM, then disable the DVD 
device by unplugging the power supply to the DVD. Open the 
computer case to do this, and then pull out the power plug to 
the DVD. 
 
The reason, is that during install, if more than one CD/DVD device 
is present on your computer, Puppy Linux is unable to Mount & 
Unmount the install device - so you can't install Puppy. 
 
 
<h4>1. DBN How:</h4>
1. Put the DBN floppy in the drive and restart the computer (the BIOS might have to be 
adjusted to boot from floppy). 
 
2. DBN will load. At the first prompt ("boot:") type quick then press Enter. DBN will now 
start to erase the HD. This will take between 15 and 60 minutes - or longer - depending 
on the capacity of your HD. Remove the DBN floppy as soon as the wipe sequence starts. 
 
DBN will go through 1 wipe cycle. You can see the % completed in the large bottom window, 
far left. (I now turn off the monitor, and go and do something for an hour). If you get bored, 
you can abort the wipe at any stage and still have a wiped HD - although not fully wiped. 
When finished, partition HD & install MS DOS. 
 
 
<h4>2. Partition HD using fdisk, then install MS-DOS: Boot with MS-DOS Start Up disk. At A:\> prompt, type fdisk. you will now create 
a Primary Dos Partition of at least 256 Mb (to install pup001 at Puppy boot). 
 
1. Enter choice 1 > 1 > N ("Do you wish to use maximum...") > type 256 (partition size) 
> 2 (set active partition) > 1 (number of partition). 
 
2. Restart, insert MS-DOS Disk 1, and at A:\> type setup > choose Format this drive. 
This will format the 256 Mb partition you've just created - not the entire HD. 
 
3. Follow standard, 3 disk, Dos install. 
 
 
<h4>3. Puppy Linux Install:</h4>
"Use <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Wakepup2/edit">Wakepup2</a>" for older machines that cant boot from CD <a class="ext" href="http://www.murga-linux.com/puppy/viewtopic.php?t=7979">http://www.murga-linux.com/puppy/viewtopic.php?t=7979</a>∞ 
1. Boot from Puppy CD. At Puppy splash-screen "boot:" press 3. 
2. At Red Text, type hda1 then Enter (for pup001 default). 
3. Choose br-latin1-us keyboard, select mouse, etc. 
In Puppy desktop, choose a resolution (800 X 600 is good). 
4. In Puppy desktop, rvxt > type cfdisk. 
5. In cfdisk > Pri/Log > New > Primary > Size = at least 500 Mb > 
Beginning > Write > Yes > Quit. 
 
Now in cfdisk, you should see something like this: 
 
<tt>hda1. . . .Boot. . .Primary. . . .FAT16. . . .[MS-DOS 6]. . . .271.44 
hda2. . . . . . . ..Primary. . . .Linux. . . . . . . . . . . 501.75 
hda3. . . . . . . .. Pri/Log. . . .Free Space. . . . . . . .3536.88</tt> 
 
6. Now, quit rxvt, and -- REBOOT (with Puppy CD still inside).
IMPORTANT STEP! REBOOT! Many online sources never state this step which
can then cause failed installations. When exiting Puppy, select 'DON'T
save changes' when asked. 
 
7. At Puppy splash-screen "boot:" press 3 > press Enter (for pup001). 
You should now go directly to Puppy desktop. 
8. Start > Setup > Install Puppy hard drive. 
9. "Make your choice": type 2. 
10. STEP 1: press Enter. 
11. STEP 2: type /dev/hda2 then press y. 
12. STEP 3: press Enter (to get "vmlinuz" off live-CD). CD-ROM will then eject. 
13. Remove CD-ROM. 
14. STEP 4: press m (or any key) then Enter (for no boot floppy). 
15. STEP 5: Computer will now write tables (inode etc.) and copy files and directories. 
16. STEP 7: GRUB install; press m then Enter (to install GRUB). 
 
GRUBCONFIG V 1.24 
Choose the following: 
1. simple - (Try to install GRUB automatically) = OK. 
2. standard - (Use the standard Linux console - the safe choice) = OK. 
3. SELECT GRUB PARTITION - /dev/hda2 = OK. 
4. SELECT GRUB DESTINATION - select MBR = OK. 
5. Continue clicking on OK boxes until - GRUB INSTALL SUCCESS. 
 
<h4>Final Steps:</h4>
1. Now, REBOOT, and at GNU GRUB 0.96, choose: INSTALL GRUB TO LINUX PARTITION. 
 
2. Post Installation Tweak to Grub Boot File: 
When you reboot your computer, you'll be presented with a GRUB boot option 
of either booting into MS DOS or Linux. If you want to configure the start 
sequence to automatically boot into Linux, you must edit the menu.lst file: 
 
NOTE: 
3. How to edit the menu.lst file: 
A. In Puppy Desktop > rox > parent directory > boot > grub > menu.lst. 
B. Open the menu.lst file. 
C. Cut these 3 lines... 
 
title Linux (on /dev/hda2) 
root (hd0,1) 
kernel /boot/vmlinuz root=/dev/hda2 ro vga=normal 
 
and paste them below this line... 
 
# Other bootable partition config begins 
 
 
D. Now, you can set the timeout value: 
 
In the line 
 
#timeout 30 
 
CHANGE the 30 into 10, and REMOVE the # at the beginning 
of the line (you can specify the timeout value to whatever 
you like). Save & exit. 
 
Now, when you start computer, it will auto-boot into 
Puppy in 10 seconds. 
 
Ends. 
 
<hr />
 
<h3>Puppy 1.0.3 Option 2 install</h3>
 
This is a fresh Hard disk install 
 
<ul>

<li> Boot up with Puppy but select Option 2 when the splash screen comes up

</li>

<li> Go to Hard disk Install and choose option 2

</li>

<li> Type in /dev/hda1 (or the number of your hard disk)

</li>

<li> Hit j and enter (that is an example any key)

</li>

<li> Hit j and enter again

</li>

<li> Choose MBR as area for GRUB to boot (I chose dev/hda1 as I was using a non Linux partition)</li>

</ul>
<hr />
 
<h5> Clearing the master Boot Record </h5>
One way you might could wipe the MBR is to boot up your machine using a
Windows 98 boot-up diskette, which contains among other things, FDISK. 
At the A:> prompt, type fdisk /mbr, press Enter, and see what happens. 
 
<h5> Installing to a hard drive </h5>
' Warning' this sections only goes up to section 6 (as that is as far as I know) 
 
It is not possible with version 0.9.9 to install automatically to a hard disk. 
Best bet is booting from a CD allowing Puppy to store its configuration details on any available HD 
 
 
# Creating live-CD Puppy by download the latest "puppy-xxxx.iso" file,
which is a complete CD image, and burn it to CD or order from Barry -
only $10 
# Change your bios setting to boot from CD 
# Prepare your hard disk 
<div class="indent">
If the hard disk is vfat (FAT16
and FAT32) - (not NTFS) - that is older versions of Windows this is OK
and Puppy will create a file on these disks. Vfat and NTFS are the way
your hard disk stores data - known as formatting. Linux users should be
using ext2 ext3 or Resier(?) 
If you are using a new or unformatted disk - which
I am just about to try then you must use fdisk (or similar) to create a
partition and format it - this requires some DOS knowledge 
The install script is very cautious. It does not
alter any partitions on your hard drive, nor does it touch the MBR
(Master Boot Record). It creates a boot floppy disk. It does copy
image.gz (Puppy himself) (and also file usr_cram.fs if it exists) onto
a partition, but they are just files, so the partitions are not messed
around with at all. 
* To prepare the hard disk I used Knoppix to boot up and qtparted to partition
</div>
remember to commit (create) and format the partitions 
 
 
# Boot from puppy 
# Go to Start / Set up / Install to Hard Drive 
# You will be given two options - we will be using option 2 
 
2. Give Puppy his own partition. There are a few ways this can be 
done, but this script requires that you have a spare partition 
that Puppy can take over entirely. This option is recommended for 
anyone interested in developing applications for Puppy, as it 
gives the most flexibility. With this option, Puppy does NOT run 
in a ramdisk, and /usr folder is read-write. 
Option 2 requires a pre-existing spare partition. Puppy will 
convert it to ext2 filesystem. PARTITION WILL BE ERASED! 
 
Got as far as Step 6 of the script 
 
This message came up: 
 
"Now creating ext2 filesystem on /dev/hda1/ etc . . . 
 
mkfs:ext2:bad blocks count - <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/ExtFs/edit">ExtFs</a>" 
 
 
<h5> Alternative HD Install Method </h5>
'Configure LILO for hard-Puppy' 
WMCreate contributed this to the old forum: 
 
I'd had some difficulty getting Puppy Linux to work happily 
with Lilo on a hard drive. And, from searching the 'net and 
this forum, I see that I'm not alone. 
 
So, what follows is the solution that I came up with. 
YMMV. 
 
Using Partition Magic 8.0, I created a 600MB primary FAT32 
partition. (I tried using a logical/extended partition but 
things wouldn't work right). In my case, it became 
partition#4 (hdd). 
 
If you don't have Partition Magic, you can use QTparted on 
the bootable <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/SystemRescueCD/edit">SystemRescueCD</a> ( <a class="ext" href="http://www.sysresccd.org">http://www.sysresccd.org</a>∞ ). 
And, if you can't boot CD's, you can use the Smart Boot 
Manager floppy disk ( <a class="ext" href="http://btmgr.sourceforge.net/">http://btmgr.sourceforge.net/</a>∞ ) to 
change that. 
 
Note: If you use <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/QtParted/edit">QtParted</a> to make a FAT32 partition, you 
should use a <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Win98SE/edit">Win98SE</a> boot floppy to format the partition (no 
system files). I couldn't get QTparted to format a 
partition for me - something that Partition Magic does with 
ease. Also, I've had problems using the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> (more on 
that to come, <a class="ext" href="http://www.freedos.org">http://www.freedos.org</a>∞ ) format command, so I 
recommend using the format command from a Windoze or DOS 
boot diskette (or using Partition Magic to format). 
 
I now had: 
hda=<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Win98SE/edit">Win98SE</a> FAT32 10GB 
hbb=Linux EXT3 8GB 
hdc=Linux SWAP 1.4GB 
hdd=<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> FAT32 0.6GB 
 
I then booted from a <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> boot diskette and did 'sys D:' 
- you might have to replace the 'D:' with some other drive 
letter. 
 
I copied vmlinuzℑ.gz(from the Puppy Linux CD), and 
tiny.exe&autoexec.bat (from the Puppy Linux startup 
diskette) to the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> drive. 
 
I then modified the autoexec.bat to show PHOME=hda4. 
 
And, I modified my lilo.conf to include the new <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> 
partition. To get <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> booting correctly, I have to hide 
the Windoze partition and unhide the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> partition (OK, 
honestly, I never have to un/hide the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> partition, but 
why bother Windoze with its existence?). 
 
other=/dev/hda1 
label=<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/Win98SE/edit">Win98SE</a> 
table=/dev/hda 
change 
partition=/dev/hda1 
activate 
set=dos16_big_normal 
partition=/dev/hda4 
deactivate 
set=dos16_big_hidden 
other=/dev/hda4 
label=Puppy 
table=/dev/hda 
change 
partition=/dev/hda1 
deactivate 
set=dos16_big_hidden 
partition=/dev/hda4 
activate 
set=dos16_big_normal 
 
If you don't have any FAT partitions except for <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a>, you 
can probably do this: 
 
other=/dev/hda4 # location of non-Linux OS, in this case 
<a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> 
label=Puppy # prompt label 
table=/dev/hda # partition table pass-through to the OS 
(might not need this). 
 
When all was said and done, I had a Puppy Linux hard disk 
install that only messed around inside of its own partition 
(that is, it creates its 500MB pup1 file inside the <a title="Create this page" class="missingpage" href="http://puppylinux.org/wikka/FreeDOS/edit">FreeDOS</a> 
partition), and was bootable by LILO and ran itself inside 
RAM. Nice. 
 
 
 
Reply #1 
From: WMCreator (wmcreator AT collegeclub.com) 
Date: 07/26/2004 
 
Oops, I just noticed that some of the above comments spilled 
over. Read it as: 
 
other=/dev/hda4 # location of non-Linux... 
label=Puppy # prompt label... 
table=/dev/hda # partition table... 
 
<h5> Other Desktops </h5>
 
[<a class="ext" href="http://www.goosee.com/puppy/sforum/simpleforum_pro.cgi?fid=02&topic_id=1109374653">http://www.goosee.com/puppy/sforum/simpleforum_pro.cgi?fid=02&topic_id=1109374653</a>∞ Using Fluxbox] 
<hr />
 
temp . . . 
 
more to follow as I av a go 
 
1. Install vmlinuz and image.gz 
 
When you boot up live-Puppy from a CD, mount the CD using "Puppy driver
mounter" (see the menu, under Start > File managers), and copy
vmlinuz and image.gz to the hard drive (and also usr_cram.fs if it
exists). let's use the Windows partition, the C: drive -- it will
probably already be mounted, at /mnt/cdrive, so use ROX to copy those
two files across. Place them in the top level "C:\" directory. 
2. Edit the boot manager 
 
So far I have only had experience with the Grub bootloader. Mount the
partition that has the /boot/grub directory. Right-click over the file
grub.conf and open it in a text editor. It will look something like as
follows, and you need to add the lines that I have shown in bold: 
 
<tt>default=1 
timeout=10 
splashimage=(hd0,4)/boot/grub/splash.xpm.gz 
title Red Hat Linux (2.4.18-14) 
</tt>
<div class="indent">
<tt> root (hd0,4) 
kernel /boot/vmlinuz-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi 
initrd /boot/initrd-2.4.18-14.img</tt>
</div>
<tt>title DOS 
</tt>
<div class="indent">
<tt> rootnoverify (hd0,0) 
chainloader +1</tt>
</div>
<tt>title Puppy Linux 
</tt>
<div class="indent">
<tt> rootnoverify (hd0,0) 
kernel /vmlinuz root=/dev/ram0 PFILE=pup1-none-524288 PHOME=hda1 
initrd /image.gz</tt>
</div>
 
An important thing to understand here is that "(hd0,0)" refers to hda1, "(hd0,4)" is hda5 and "(hd0,2)" is hda3. 
 
Apart from editing grub.conf, nothing else is required, as the
bootloader will automatically look at that file during booting. Some
other bootloaders may need an extra step to install the changes. 
3. Reboot 
 
That's it, Puppy should start 
 
When you get Puppy installed in this very cautious way, you might like
to read further down this page to the "take two" instructions, to see
how to configure a boot manager. 
 
Puppy v0.9.0 added an extra option to the install-to-hard-drive script.
"Option 2" is to install Puppy such that no ramdisk is used. This
requires that Puppy take over an entire partition. It is up to you to
have such a spare partition. The script will convert it into an ext2
filesystem, if it wasn't before. 
Option 2 is good for developers, as the /usr folder is not compressed and is read/write. 
 
Puppy v0.9.8 added an "upgrade" option to the install script, if you
are upgrading from a previous installation. All you do is download the
latest live-CD ISO file, burn it to CD, boot up on it, then run the
install-to-hard-drive script and when it asks whether you are doing a
new installation or upgrade, you answer appropriately. 
 
 
<hr />
 
Simple Grub: 
<div class="indent">
 
This is a simple intro to Grub for people who have Puppy installed as the only operating system on a hard drive in a ext2fs. 
If other filesystems are used I can post the stage1_5 files required. 
If you dont like this or find it confusing please post a reply as this is a tentative attempt to supply some information. 
 
 
<a class="ext" href="http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/pup-grub.tar.gz">http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/pup-grub.tar.gz</a>∞
</div>
 
<hr />
 
Simple HD install with Grub bootmanager 
<div class="indent">
 
Requirements: 
* Puppy live CD 
* grub executable and files /boot/grub/* - get: <a class="ext" href="http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/Grub.zip">http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/Grub.zip</a>∞
</div>
 
<div class="indent">
Steps: 
1. boot off puppy live cd 
2. cfdisk hda - create hda1 bootable partition of type linux (min. 400MB). save your work! 
3. mkfs.ext2 /dev/hda1 - create ext2 file system on hda1. 
4. get access to grub executable. Use my grub.zip file. unzip. you should see grub (elf exe) and 
directory boot/grub/* with file menu.lst. menu.lst is already setup for Puppy on hd(0,0) (hda1) only! 
5. copy required file to hda1: 
5.1 mount puppy live cd via drive mounter wizard (mount /dev/hdc /mnt/cdrom). 
5.2 mount /dev/hda1 /mnt/data 
5.3 cp /mnt/cdrom/vmlinuz /mnt/data 
5.4 cp /mnt/cdrom/image.gz /mnt/data 
5.5 cp /mnt/cdrom/usr_cram.fs /mnt/data 
5.6 mkdir -p /mnt/data/boot/grub 
5.7 cp boot/grub/* /mnt/data/boot/grub 
6. setup grub on hda 
6.1 grub 
grub> root hd(0,0) 
... 
grub> setup hd(0) 
... 
Done. 
grub> quit
</div>
 
<div class="indent">
Thats it!
</div>
 
<div class="indent">
If one created a different partition for hd install, menu.lst and some statements above MUST be changed 
accordingly: 
primary ide channel 
1st ide hd; 1st primary part. hda1 hd0,0 
1st ide hd; 2nd primary part. hda2 hd0,1 
1st ide hd; 3rd primary part. hda3 hd0,2 
1st ide hd; 4th primary part. hda4 hd0,3 
 
2nd ide hd; 1st primary part. hdb1 hd1,0 
2nd ide hd; 2nd primary part. hdb2 hd1,1 
...
</div>
 
<div class="indent">
Peter.Sieg@gmx.de 
<div class="indent">
 
</div>
<a class="ext" href="http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/Grub.zip">http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/Grub.zip</a>∞
</div>
 
 
<hr />
 
Simple Grub Win/Puppy Boot CD: 
<div class="indent">
This is a simple <a href="http://puppylinux.org/wikka/HowTo">HowTo</a> on creating a Grub boot CD to boot Puppy if you have it installed in a Win fat32 partition. 
Just download the file to my-applications, open rxvt, cd to my-applications and type in : 
 
 
tar zxvf simplegrub_cdboot.tar.gz 
 
This will open the file and you can take it from there. 
 
If you don't understand or find the instructions confusing please post a reply. 
 
<a class="ext" href="http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/simplegrub_cdboot.tar.gz">http://www.goosee.com/puppy/sforum/simpleforum_files/attachments/simplegrub_cdboot.tar.gz</a>∞
</div>

PuppyLinux : InstallationFullHDD

Revision [607]