I ran the installer and put Puppy on my "guest" partition. I didn't install grub, as I would be keeping the existing grub.

When I got to making an entry for Puppy, I found that the installer had only installed vmlinux: no initrd. I copied that and tried to boot Puppy: oops, no sfs file. Now I've copied that, all's well. But shouldn't the installer have done it?

I ran the installer and put Puppy on my "guest" partition. I didn't install grub, as I would be keeping the existing grub.

When I got to making an entry for Puppy, I found that the installer had only installed vmlinux: no initrd. I copied that and tried to boot Puppy: oops, no sfs file. Now I've copied that, all's well. But shouldn't the installer have done it?

Nope, not for a full install.

A full install doesn't use the sfs , see the screenie for the filesystem on a full install. The vmlinuz is located in the "boot" directory.
HTH.

Your problem is Grub does not have the proper info for the type of install you have.
I suggest after doing the full install
Before rebooting
Look in menu->system
Run Grub4dos bootloader config program
It will setup everything with no manual input needed.
This info may help.
http://www.murga-linux.com/puppy/viewtopic.php?t=60302

You can also run Grub4dos from the Puppy Live CD
Just make sure to boot the CD with the option Puppy pfix=ram.
When you get done running the CD do not make a save file.

After actually stopping to think, I realised that by copying initrd and the sfs files, I manually created a frugal install! So, I started again.

I re-installed from scratch and followed the instructions on what to put in Fedora's grub.conf. The result on rebooting was
Kernel panic : not synching : VFS : unable to mount root FS on unknown block (0,0)

Then I started a fresh live-CD session and ran the tool to create grub. This invited me to put it in /dev/hda3 when it should have said /dev/sda3, but grub was duely installed. I then altered Fedora's grub.conf to use the chainloader approach. The result this time was
Error 13: Invalid or unsupported executable format

If someone has actually made a full install of Puppy, I'd be delighted to know how they did it; but please don't refer me to the on-line instructions, because they aren't working on this computer.

After actually stopping to think, I realised that by copying initrd and the sfs files, I manually created a frugal install! So, I started again.

I re-installed from scratch and followed the instructions on what to put in Fedora's grub.conf. The result on rebooting was
Kernel panic : not synching : VFS : unable to mount root FS on unknown block (0,0)

Then I started a fresh live-CD session and ran the tool to create grub. This invited me to put it in /dev/hda3 when it should have said /dev/sda3, but grub was duely installed. I then altered Fedora's grub.conf to use the chainloader approach. The result this time was
Error 13: Invalid or unsupported executable format

If someone has actually made a full install of Puppy, I'd be delighted to know how they did it; but please don't refer me to the on-line instructions, because they aren't working on this computer.

Full install of Puppy Linux Lucid 5.2
Boot with the Puppy Live CD.
If you do not already have a Linux formatted partition or hard drive.
Run the program Gparted.
Format a partition or hard drive to a Linux format ext2, ext3, ext4
For full install need partition of at least 1GB ( I would make it much bigger, room to add stuff)
Run the Puppy Universal Installer.
Chose to install to partition or Hard drive you formatted.
Choose full install.Do not install grub if asked by installer.
After installer is finished.
Before rebooting.
Look in menu->system
Run Grub4dos bootloader config program.
Use default settings.
It will find everything, setup the boot loader, with no manual input needed.
Remove the CD.
Reboot.
Because you where running with the CD it will ask if you want to make save file. Say no.
On reboot.
Should see boot menu with everything on computer listed.

Why grub4dos? I've never heard of that, but the name suggests a Microsoft partition, which I do not have.

Although I've been experimenting on my desktop, my real interest was using Puppy on my old notebook (Thinkpad X31). Last night I tried running the live CD on that, and got an immediate kernel panic. Under the circumstances, I think there are too many bugs here for me. Thank you all for your help.

I installed AntiX Grub to / in Antix. When install was done, I ran smxi script to install Latest Liqourix Kernel which was kernel 2.6.37-0.dmz.5-liquorix-686 at the time. I also let smxi do a apt-get update and at-get dist-upgrade also. Grub in Antix was automatically upgraded via smxi aslo.

I then went into Bruno Pup (my first installed Puppy which has grub4dos installed)

Let it do automatic upgrade. Closed it and opened it up again. Then changed Strategy.

Ran it again and I opened grub4dos and told it to NOT automatically update and to not make any changes. In other words. Don't change or touch anything.

Next Window I hit the edit button for menu.lst for grub4dos.

I opened /boot/grub/menu.lst in Antix in Bruno with text editor. I copy and pasted what entries I wanted from /boot/grub menu.lst because now I had UUIDs which found my Antix file system better than grub4dos could. I edited out the grub4dos entries that were simplified Antix entries without the UUIDs. Saved and exited. All my Distro boot and run fine. Hope that makes sense.

I installed AntiX Grub to / in Antix. When install was done, I ran smxi script to install Latest Liqourix Kernel which was kernel 2.6.37-0.dmz.5-liquorix-686 at the time. I also let smxi do a apt-get update and at-get dist-upgrade also. Grub in Antix was automatically upgraded via smxi aslo.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum