(old)Puppy Linux Discussion Forum

BarryK wrote:From 3.0 onwards, if you do have "root=/dev/ram0" it just gets ignored. But, better not to have it as it will confuse people wondering why it is there.

Thanks Barry. I understand the "root=/dev/ram0" option is harmless but better to be removed as for the Puppy-3.x and later.

I just figured out what this was. Wow! Thank you so much!

jemimah wrote:I just figured out what this was. Wow!

Thanks jemimahf for your interest.

Please take a look on 'How to Install Puppy on Windows PC':
http://www.murga-linux.com/puppy/viewtopic.php?t=61796

Also consider the Windows Installer:
http://www.murga-linux.com/puppy/viewtopic.php?t=61404
The Windows Installer does not support Windows Me,
some problem reported with Windows 7(64bit) at this point of time,
Windows 7(32bit) is OK.

Just a word of thanks. I had an issue with my eeepc after fiddling with the partitions grub2 installed by ubuntu decided it would just give me an error message, with no solution. After much googling, it seems there is no working solution for grub2. Never did like it. I have no idea why ubuntu decided grub2 was better. Its a p.o.s. in my opinion anyway.

So back on topic, I had a usb drive with quirkynop on it, that included both a grub installer, and this grub4dos. Having only used grub before, I was happy to install it, but it insisted that my ext4 and ext3 partitions were both not linux partitions. Grrr-ub. So I tried grub4dos with the gui config. Wow. Awesome. Two clicks and it told me that there was puppeee, ubuntu and windows installed on the machine; and also that quirky was running via usb. Quick few name changes, and it installed everything perfectly. Beautiful. I didn't even have to argue with it like I have always had to with grub.

The only issue was that it put in an entry for the quirky usb that I had used to rescue the eeepc. So downloaded and installed grub4dosconfig to the puppeee install, ran the gui again. Absolutely perfect. And, also with a puppeee pfix=ram option. Fantastic. Even shows me my old grub2, which still doesn't work properly, but who cares.

I spent an entire day searching google and fiddling with ubuntu and repartitioning and generally messing around to get grub2 fixed, and in the end, grub4dos fixed it in under ten minutes. Brilliant.

Love puppy.

Love grub4dos.

Love simplicity.

I used Grub4Dos bootloader config to configure a USB Zip drive to boot puppy in a subdirectory on my harddisk.

My pc finds the zip drive and starts to boot from it however I got messages to say that grldr could not be found even though it had been successfully installed on the zip drive.

So I copied both grldr and menu.lst onto my harddisk and now after a few error messages the system boots into puppy as I wanted it to....

So why if I'm booting off the zip drive are the files on the zip drive not being found I wonder.....

Thanks
Peter

peebee wrote:I used Grub4Dos bootloader config to configure a USB Zip drive to boot puppy in a subdirectory on my harddisk.
My pc finds the zip drive and starts to boot from it however I got messages to say that grldr could not be found even though it had been successfully installed on the zip drive.
So I copied both grldr and menu.lst onto my harddisk and now after a few error messages the system boots into puppy as I wanted it to....
So why if I'm booting off the zip drive are the files on the zip drive not being found I wonder.....

Thanks Peter for the report.
I tried BootFlash on a USB flash to emulate ZIP drive.
Used the Grub4DosConfig-1.6.3 on Luci-241 and got success to boot.
It may depend on the hardware and BIOS?

How about copying the grldr and menu.lst to sdb4(assuming your zip appears sdb1 and sdb4)?

shinobar wrote:How about copying the grldr and menu.lst to sdb4(assuming your zip appears sdb1 and sdb4)?

Hi Shinobar

I formatted my zip cartridge with gparted to a single partition so it just appears as sdb1 - there is no sdb4...

grub4dos put the grldr and menu.lst correctly onto sdb1 - I had to copy them to sda1 (my harddisk) to make it work.

It's a pretty bog standard pc with an asus motherboard and an amd-athlon cpu (from memory). The only change I had to make to the boot order was to give the zip drive priority over the floppy disk.

Cheers
Peter

grldr is built to work with ntldr. It must be placed on the root directory of the partition holding Windows.

If you install grub4DOS to a USB drive should it not be using grub.exe somehow, not grldr.

ICPUG wrote:grldr is built to work with ntldr. It must be placed on the root directory of the partition holding Windows.

If you install grub4DOS to a USB drive should it not be using grub.exe somehow, not grldr.

@ICPUG
It is not the problem. I am testing floppies, or USB flash drives, with only two files, grldr and menu.lst.
In this case, grldr is called not from ntldr but from the MBR the bootlace.com made.

Both work:

1. MBR(made by Windows) --> PBR(made by Windows)-->ntldr-->grldr
2. MBR(made by bootlace.com)-->grldr

ZIP drives should contain a single partition with the number 4 -that is what them getrecognized as ZIP drives. there should be no sdb1, sdb2 or sdb3, only sdb4.

amigo wrote:ZIP drives should contain a single partition with the number 4 -that is what them getrecognized as ZIP drives. there should be no sdb1, sdb2 or sdb3, only sdb4.

How strange - no sdb4 here - just the sdb1

How can it be sdb4 if there is no sdb1, 2 or 3????

What generates the sdb4?

Confused of the UK

Cheers
Peter

"What generates the sdb4?" fdisk will do that -when you press 'n' to add a partition it gives you the option of specifying the number.
I've just been reading the bootflash script and noticed that it creates both 1 and 4 partitions, but my understanding has always been that for real ZIP drives to work there should be only the fourth partition, but maybe I am wrong -that happened once before, IIRC. LOL

amigo wrote: fdisk will do that -when you press 'n' to add a partition it gives you the option of specifying the number.

I used gparted to format the zip drive - was this incorrect?
Where do I find fdisk? - I can find pdisk in the menu but not fdisk....

Thanks
Peter

Shinobar,

the older version of your program placed the menu.lst on Sda1 instead of Sda3 where mnt/home is and all the pup folders and other programs.

How can I move them from Sda1 to Sda3? Drag and drop or do I need to do something more involved? The sda_mbr.bak should that one still be in Sda1 then?

What about bootmgr and grldr where should they be?

nooby wrote:the older version of your program placed the menu.lst on Sda1 instead of Sda3 where mnt/home is and all the pup folders and other programs.
How can I move them from Sda1 to Sda3? Drag and drop or do I need to do something more involved? The sda_mbr.bak should that one still be in Sda1 then?
What about bootmgr and grldr where should they be?

The bootmgr is of Windows, you cannot move it.

The grldr and menu.lst can be on any partition.
But notice that they are searched from the first partition and then next.

There is a trap. If there is a ext4 partition in the grldr search process, it hungs up.
One of the reason the grub4dosconfig put grldr on the first partition is escaping this trap.

The MBR which grub4dosconfig made should be on the drive that is selected as the boot device by the BIOS.

Thanks indeed for your answer.


it worked as expected and I should have asked you this a long time ago.
This is so much more practical

peebee wrote:

amigo wrote: fdisk will do that -when you press 'n' to add a partition it gives you the option of specifying the number.

I used gparted to format the zip drive - was this incorrect?
Where do I find fdisk? - I can find pdisk in the menu but not fdisk....
Thanks
Peter

@PeeBee ... fdisk is a command that is BUILT-IN to all Linux systems (that I am aware of). To use it, open a terminal window and type fdisk ... and if I were you, when fdisk starts up, type m
"m" <=== will give you a list of options for using fdisk and "q" will quit.

There are all sorts of help on the Internet for fdisk.

I like fdisk because it will change tables on my drive(s) without changing data. So, if after making some changes, I want to change it back, I can and my may be able to get back to the original data (assuming I didn't do anything stupid). Luck to you

shinobar,
I have grub4dos installed to the MBR of the hard drive.
Grub4dos config found all installed operating systems and they have working entries in the menu.lst.
However, there are some extra entries that do nothing. Not sure why they are there.
Lucid Puppy 243 is a full install to a partition.
Luci 237 is a frugal install, with a save to full partition option, on a usb flash drive.

Here is what they are:

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

The entire menu.lst


# menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0

# Frugal installed Puppy

title Luci 242 (sda1/puppy242)
find --set-root --ignore-floppies /puppy242/initrd.gz
kernel /puppy242/vmlinuz pmedia=atahd psubdir=puppy242 pfix=fsck
initrd /puppy242/initrd.gz

title Luci 242 (sda1/puppy242) RAM mode\nBoot up Puppy withot pupsave
find --set-root --ignore-floppies /puppy242/initrd.gz
kernel /puppy242/vmlinuz pmedia=atahd psubdir=puppy242 pfix=ram,fsck
initrd /puppy242/initrd.gz

title Lupu 511 (sda2/puppy511)
find --set-root --ignore-floppies /puppy511/initrd.gz
kernel /puppy511/vmlinuz pmedia=atahd psubdir=puppy511 pfix=fsck
initrd /puppy511/initrd.gz

title Luci 236 (sda5/puppy236)
find --set-root --ignore-floppies /puppy236/initrd.gz
kernel /puppy236/vmlinuz pmedia=atahd psubdir=puppy236 pfix=fsck
initrd /puppy236/initrd.gz

title Luci 237 (sdb1)
find --set-root --ignore-floppies /luci_237.sfs
kernel /vmlinuz pmedia=usbflash pfix=fsck
initrd /initrd.gz

# Full installed Linux

title Lucid Puppy 243 (sda3/boot)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
kernel /boot/vmlinuz root=/dev/sda3 ro

title Linux Mint 8 Helena - Main Edition (sda7)
uuid 2a7dc791-ef27-4a70-ae9e-f59d14bdfa18
kernel /vmlinuz root=/dev/sda7 ro
initrd /initrd.img

# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Linux Mint 8 Helena - Main Edition (sda7:PBR)
uuid 2a7dc791-ef27-4a70-ae9e-f59d14bdfa18
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

# additionals

title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img

title Grub4Dos commandline\n(for experts only)
commandline

title Reboot computer
reboot

title Halt computer
halt

bigpup wrote:Grub4dos config found all installed operating systems and they have working entries in the menu.lst.
However, there are some extra entries that do nothing. Not sure why they are there.
Lucid Puppy 243 is a full install to a partition.
Luci 237 is a frugal install, with a save to full partition option, on a usb flash drive.

Here is what they are:

# Boot from Partition Boot Record

title Lucid Puppy 243 (sda3/boot:PBR)
uuid b3722aa6-7a19-4c72-a387-3a83fb1b030b
chainloader +1

title Luci 237 (sdb1:PBR)
uuid 75f04685-1ccc-44aa-8ad8-0e556405ebd7
chainloader +1

Good question.
Yes, the new version of grub4dosconfig makes these extra entries.
They do not always work and in many case they are redundant.
You can remove them from the menu.lst after you confirm that the corresponding OS can boot up with other entries.

See the document:
http://shino.pos.to/linux/puppy/grub4do ... html#chain

mo- and po- and .desktop-file ...attached.

Regards,
Markus