No joy installing Puppy to an ext4 partition.

[kyferez]

The live cd runs great, however installing to the hard drive is not working. It copies the files, but when I get to running grub, it asks for the device, so I enter /dev/hda1 and it says it's not a valid linux partition.

What? Yes it is. It's ext4. So when I reboot, nothing happens and I get grub recovery of course.

Grrr.

[rcrsn51]

Try the automated install procedure here.

[Béèm]

Grrr, you should use the Puppy Universal Installer from the menu.

[kyferez]

I did use the Puppy Universal Installer. It popped up a file to use in the grub menu.lst file but that file didn't exist, and when I created it in the boot/grub folder grub didn't recognize it., so I tried using the grub installer from the live cd menu. That's where it kept saying not a valid linux filesystem.

Anyway, I got it to work using Grub4DOS installer instead.

And Grrr was me growling

[Karl Godt]

/dev/hda1

Would be the wrong entry in 90%+ of all Puppy standard kernels nowerdays .

/dev/sda1

would be the correct entry in that [particular] case [ if installed to first partition of the first (internal) hard drive ] .

There are few IDE kernels around , which would use /dev/hda1 ; but these kernels mainly are extra .pets and are not shipped with the standard Puppy .iso(s) .

[kyferez]

...I should have said I tried both /dev/sda1 and /dev/hda1...

So after getting that pc working, I decided to try it on an old 1ghz Athlon laptop. Works great once I used Hirens bootcd to delete the partitions. Why did I use Hirens? 2 reasons:
1) It didn't want to boot from the ntfs
2) Gparted kept giving me weird errors after I forced puppy to unmount the ntfs filesystem.

I created a swap partition, but puppy said it was creating a swap file at shutdown, so does it not use the swap partition?

Other than those questions, it's working great; recognized the wifi and sound. Going to see how well it works online with some resource intensive websites now...

[Béèm]

I did use the Puppy Universal Installer. It popped up a file to use in the grub menu.lst file but that file didn't exist, and when I created it in the boot/grub folder grub didn't recognize it., so I tried using the grub installer from the live cd menu. That's where it kept saying not a valid linux filesystem.

Anyway, I got it to work using Grub4DOS installer instead.

And Grrr was me growling

Why didn't you tell this in your initial post. Information like this is key to a successful reply.

[Béèm]

kyferez,
I think you do need to do some reading on how puppy works to get the terminology correct.

[kyferez]

Why didn't you tell this in your initial post. Information like this is key to a successful reply.

Sorry, I thought that was the standard method and it would have been understood what I was talking about...

I wanted permanent full-takeover installs to the PC hdd as both the PCs I was playing with are old systems. The install didn't go smoothly using the universal puppy installer where there were pre-existing systems on the hdds. I first had to delete and recreate partitions outside of puppy, then it worked fine every time.

[Béèm]

kyferez,
In order for people to help you correctly, you have to specify all the details you go through when doing things.

Precise description of what you do.
What do you see on the screen.
What did you select in scripts.
If possible and applicable screen shots.

You are the eyes of the people eager to help you.

[kyferez]

I understood from the first post... I was just explaining why I didn't thoroughly explain myself the first time.

And since you brought it up again... I usually make very detailed and long posts when asking for help, but then never get any assistance or get people responding who don't read my whole post or miss stuff within the post or misunderstand stuff and I end up repeating myself, so it has become easier in the long run to be a little vague and let people ask questions... Sad but true.