Page 9 of 13

Posted: Wed 16 Sep 2009, 14:42
by rjbrewer
This doesn't necessarily slow it down.

In many cases the full will run as fast or faster than frugal
or live cd..

How to Fully install Puppy to empty HD

Posted: Mon 21 Dec 2009, 13:23
by georgecorkland
Catdude, thanks for this very concise and easy to follow tutorial. I have struggled for a couple of weeks trying to install on a very old Toshiba Satellite 4100XCDT laptop having nuked Win 95 with DBAN HD Wiper. Followed your advice and Puppy is running fast and well. I hope this tutorial stays on this forum and remains easy to find. Top Notch!!

Re: How to Fully install Puppy to empty HD

Posted: Mon 21 Dec 2009, 21:27
by CatDude
Hello georgecorkland

Welcome to the kennels.

Thank you for your kind words, and i am glad you found this howto useful.

CatDude
.

Show Stopper.....

Posted: Mon 28 Dec 2009, 03:40
by Bronco Billy
Hi There....
Works a Charm Until Hard Plug Pull then No Boot..... Any Ideas for a Fix? Have a Great day.....

Thanks!

Posted: Fri 29 Jan 2010, 05:15
by sunnypies
I'm a firstimer and good to go now thanks to all the pics and good instructions! Puppy rocks on my Dell GX 260

Posted: Mon 19 Apr 2010, 21:28
by Nehemoth
First I wanna thank you for the awesome guide and thank you for Puppy.

I am trying to convert Puppy as a brute terminal for some old PC's, for that I am using this instructions
hxxp://pctsc.ponderworthy.org/downloads/instructions.txt

from the project pc tsc and I can tell you is working like a charm.

My problem is that now I want to do some other things on Puppy and for that I need GCC, I understood that you need an sfs file and also you need to follow the instructions for full HD installation as per the link below
hxxp://www.puppylinux.com/hard-puppy.htm

Sadly after some multiples intents I could not get GCC installed, so I would like to know if someone can help me.

I had done this exactly

Code: Select all

2. Click on the devx_xxx.sfs in a ROX-Filer window to mount it.
3. Open a terminal in the mounted directory.
6. # cp -a --remove-destination ./* /mnt/sda1/
7. # sync
8. Close the terminal.
9. Click on the devx_xxx.sfs file to unmount it
or

Code: Select all

2. Click on the devx_xxx.sfs in a ROX-Filer window to mount it.
3. Open a terminal in the mounted directory.
6. # cp -a --remove-destination ./* /mnt/home/
7. # sync
8. Close the terminal.
9. Click on the devx_xxx.sfs file to unmount it
But the result is the same, nothing when I try gcc [command] on the terminal.

Best regards

Thanks!

Posted: Tue 27 Apr 2010, 18:32
by Bud
CatDude, just wanted to thank you for the install tutotial.
Having run Puppy for a while off disk I decided to take the plunge and install to hard disk on an old but function fine Sony Vaio F-480.
Was having trouble getting Puppy to boot until I slowly followed your guide step by step.
Worked first time and I'm blown away with the speed and new life breathed into a box that had virtually slowed to a crawl with Win98.
Can't think of a better way to learn the new world of Linux...... :)

Posted: Wed 12 May 2010, 13:12
by phouse512
Thanks for this helpful guide. I just wiped one of my hard drives with DBAN and I wanted to make sure that I installed it correctly. Puppy Linux runs like a charm now

:D

Posted: Fri 13 Aug 2010, 05:37
by mrreality13
this is always use full -could it be stickied please?

Posted: Sat 14 Aug 2010, 04:24
by scsijon
Nehemoth wrote: My problem is that now I want to do some other things on Puppy and for that I need GCC, I understood that you need an sfs file and also you need to follow the instructions for full HD installation as per the link below
hxxp://www.puppylinux.com/hard-puppy.htm

Sadly after some multiples intents I could not get GCC installed, so I would like to know if someone can help me.

Best regards
I take it you have already done a full install and rebooted.

Download and install the sfs installer pet (link below), run it, it's easier than playing around and off you go (make sure your installing dev EXACTLY matches the version of puppy your running). gcc works!

http://www.murga-linux.com/puppy/viewto ... search_id=

woops wrong link, will fix when found, you want the file "SFS_installer-0.1.pet", it's one of trio's pets.

regards
scsijon

Posted: Tue 07 Dec 2010, 04:34
by Insomniacno1
This is a great guide and is rightfully under sticky, but could someone modify it to show how to install newer version 5.xx.

In my case it would be extrememely good if someone could explain how to install 5.xx onto IBM Thinkpad 570 with 192mb ram and 20GB hdd.

You see 5.xx don\t detect the hdd on startup. 4.xx has no probleme at all.

Thanx in advance

With regards

JBJ

Posted: Mon 16 May 2011, 19:44
by Sky Aisling
@CatDude

Hello and good day to you,

Well, I am attempting to do a full install of Lupu 520 onto a Toshiba Satellite 1415-S115 - RAM 512MB - Processor Intel Celeron 2.00GHz - 30 Gigs HDD.

Your excellent tutorial has helped me so much in the past. All was going swell until Image Step 29. Then Lupu 520 deviated.

Here is screen shot of message box I see at Step 29. (Install1.png)
Here is a screen shot of a search for *grub* - It appears that both *grub* and *grub4dos* are installed.
Here is a screen shot of a search for *menu.lst*. - Is this the *menu.lst* to change?
Here is a screen shot of /mnt/sda1/boot - There is no *menu.lst* inside the *grub* folder.

Question: How and Where do I find the appropriate *grub* menu.lst in order to change it according to the message box directions?

I understand that I 'might' find the *menu.lst* at what is called the *top* '/' or /boot/menu.lst
I've looked into *sda1* and into *home* files but cannot locate the grub boot menu.lst. And, as the search indicates, there is only one *menu.lst* found.

I took the *ok* option without correcting the *menu.lst* so currently there is no OS installed but the partitioning is done.
The Live CD of Lupu 520 booted up again with no issues. The bios boot order is set to check the CD drive first for an OS.

(And, yes, I understand there is an issue with what drive name is sighted by the grub and that is why the change needs to happen. I just can't find the menu.lst in order to change it.)

Posted: Mon 16 May 2011, 20:01
by rjbrewer
On the earlier versions of Puppy, the Grub install was included
when running the installer. (step 29 +)
For some obscure reason that is no longer the case.

When the puppy is installed now, it is necessary to click Grub in
the menu and install it.

I always use Legacy Grub.

You would type "/dev/sda1" (no quotes) in the box for where the
grub files go, (I use /dev/sda2 if I have Windows on sda1) and then MBR for where grub goes.

Posted: Mon 16 May 2011, 20:16
by Sky Aisling
Thank you, rjbrewer

Is this the box to work with?

Also, I was careful *not* to *save* the pup file on each exit while I was experimenting with various Puppys. Should I check to see if by accident a *save* file was made? or does that make any difference in this situation?

Posted: Mon 16 May 2011, 20:40
by rjbrewer
Sky Aisling wrote:Thank you, rjbrewer

Is this the box to work with?

Also, I was careful *not* to *save* the pup file on each exit while I was experimenting with various Puppys. Should I check to see if by accident a *save* file was made? or does that make any difference in this situation?
That box is right.
If you had made a save file you would remember it; I'm not even
sure if it's possible with the full install.

When you reboot after installing grub, you can find the menu.lst by
either clicking sda1 or clicking rox and going to /boot/grub/menu.lst.

That's where you would change the title for the boot screen or
the amount of pause time when booting.

Posted: Mon 16 May 2011, 21:09
by Sky Aisling
@rjbrewer,

What is the sequence that I do the *simple* grub install?

Do I open the Universal Installer and somewhere in that sequence I do the *grub* install, and, the text correction to *menu.lst*?
or
Do I do the grub install by just selecting it from the menu without opening the Universal Installer? Then go on to install Lupu 520 with Universal Installer, and, somewhere in there I make the text correction?

Sorry, for the stupid question. This is probably self-evident when I open the Universal Installer.

Posted: Mon 16 May 2011, 21:25
by rjbrewer
Sky Aisling wrote:@rjbrewer,

What is the sequence that I do the *simple* grub install?

Do I open the Universal Installer and somewhere in that sequence I do the *grub* install, and, the text correction to *menu.lst*?
or
Do I do the grub install by just selecting it from the menu without opening the Universal Installer? Then go on to install Lupu 520 with Universal Installer, and, somewhere in there I make the text correction?

Sorry, for the stupid question. This is probably self-evident when I open the Universal Installer.
Just to be safe I would run the install of 5.2 again.
At the end when the grub window comes up, close the window and
run grub from the menu.
You don't actually need a text correction; it's something you can do anytime if you want to make a change to the menu.lst.
I mentioned a few before and sometimes a boot parameter
can be added to the kernel line if necessary to help with booting
or shutting down.

Posted: Mon 16 May 2011, 21:55
by Sky Aisling
OK, I've got it installed. I have the desktop up and it appears to be functioning normally.
However, in the boot up process:

Image 40 (from CatDude's tutorial) appears on the screen
*enter*
Message - Undefined video mode #316 - enter to see video modes available - space to continue - wait 30 sec

Seems like these shouldn't be there. Would this have anything to do with my choice of the *grub* frame buffer. errr, I didn't take the 'standard' Linux console (the 'safe' one) but instead chose the one that would show TUX on the boot up screen. Well,... I think TUX is cute.

How do I get rid of this? This system is for someone else who is brand new to using a computer and I'd like it to look as slick as possible and not confuse him. Thanks....I feel a bit silly at this point.

Posted: Mon 16 May 2011, 22:10
by rjbrewer
Sky Aisling wrote:OK, I've got it installed. I have the desktop up and it appears to be functioning normally.
However, in the boot up process:

Image 40 (from CatDude's tutorial) appears on the screen
*enter*
Message - Undefined video mode #316 - enter to see video modes available - space to continue - wait 30 sec

Seems like these shouldn't be there. Would this have anything to do with my choice of the *grub* frame buffer. errr, I didn't take the 'standard' Linux console (the 'safe' one) but instead chose the one that would show TUX on the boot up screen. Well,... I think TUX is cute.

How do I get rid of this? This system is for someone else who is brand new to using a computer and I'd like it to look as slick as possible and not confuse him. Thanks....I feel a bit silly at this point.
I'm sure it has to do with choosing framebuffer mode.
I've never done that before.
Maybe that message will go away after another reboot?

Catdude also has tutorials on making fancy boot screens.

In any case, now you can take a look at /boot/grub/menu.lst.
You can change the title line to say anything you want, it doesn't
affect booting.

Be sure to click save after making any changes.

Posted: Mon 16 May 2011, 22:45
by Sky Aisling
Nope, oh sigh! the *grub* blue and black boot screen (image 40 from CatDude's tutorial) doesn't go away on reboot. I guess I have figure out how to configure *grub* to use the *frame buffer console*. Surely there is a way to change that choice?

Any clues on how I get rid of the Image 40 *grub* boot screen?

The good news is Lupu 520 in combo with Firefox 3.6.13 on Toshiba Satellite 1415-S115 is looking good! Running well.