Grub4DosConfig

Miscellaneous tools
Message
Author
User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: Where should grldr be?

#201 Post by shinobar »

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)?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Where should grldr be?

#202 Post by peebee »

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

ICPUG
Posts: 1308
Joined: Mon 25 Jul 2005, 00:09
Location: UK

#203 Post by ICPUG »

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.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

grldr with ntldr

#204 Post by shinobar »

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
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#205 Post by amigo »

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.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#206 Post by peebee »

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

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#207 Post by amigo »

"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

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#208 Post by peebee »

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

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#209 Post by nooby »

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?
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Sda1 or Sda3

#210 Post by shinobar »

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.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#211 Post by nooby »

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 :)
I use Google Search on Puppy Forum
not an ideal solution though

gcmartin

fdisk come with ALL Linux distros

#212 Post by gcmartin »

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

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#213 Post by bigpup »

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

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Chainload PBR

#214 Post by shinobar »

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
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

mave
Posts: 129
Joined: Thu 02 Apr 2009, 13:42
Location: Germany

german localization for Grub4DosConfig 0.4.4

#215 Post by mave »

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

Regards,
Markus
Attachments
Grub4Dos_0.4.4_locale_de.tar.gz
(6.3 KiB) Downloaded 453 times

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#216 Post by James C »

Continuation of our discussion in the Lucid thread.

Perfectly working box with 3 full installs..... Vector 6 (sda1),Puppy 4.20 (sda6) and Puppy 4.31 (sda7).Legacy Grub in the mbr.
Did a frugal install of Lupu-515 and installed Grub4dos in the mbr as bootloader.The only 2 installs that would boot were the 2 full Puppy installs....no go on Vector and the Lupu frugal.Both had a kernel panic.I've since edited the menu.lst and have Vector booting.


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

# Frugal installed Puppy

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

title Lupu 515 (sda7/puppy515) RAM mode\nBoot up Puppy withot pupsave
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=ram,fsck
initrd /puppy515/initrd.gz

# Full installed Linux

title Vector6.0 (sda1/boot)
uuid 5b0174b6-0b72-11e0-9cae-a5a52175c61b
kernel /boot/vmlinuz root=0301 ro

title Puppy 420 (sda6/boot)
uuid 4777244e-4b25-4819-84b1-5020579e4bd4
kernel /boot/vmlinuz root=/dev/sda6 ro

title Puppy 431 (sda7/boot)
uuid 35132a1e-f6b8-4e35-9f9e-f4a593818cf1
kernel /boot/vmlinuz root=/dev/sda7 ro

# 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

# 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


I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.
Now to get the Lupu frugal booting. :)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#217 Post by bigpup »

This is my munu.lst entry for luci 246 made by Grub4dos config and it works. Looks like yours for Lupu 515.
Why yours does not work?????

title Luci 246 (sda2/puppy246)
find --set-root --ignore-floppies /puppy246/initrd.gz
kernel /puppy246/vmlinuz pmedia=atahd psubdir=puppy246 pfix=fsck
initrd /puppy246/initrd.gz

Yours;

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

Where did you install Grub4dos?
Are all the files in /puppy515?

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#218 Post by James C »

bigpup wrote:This is my munu.lst entry for luci 246 made by Grub4dos config and it works. Looks like yours for Lupu 515.
Why yours does not work?????

title Luci 246 (sda2/puppy246)
find --set-root --ignore-floppies /puppy246/initrd.gz
kernel /puppy246/vmlinuz pmedia=atahd psubdir=puppy246 pfix=fsck
initrd /puppy246/initrd.gz

Yours;

title Lupu 515 (sda7/puppy515)
find --set-root --ignore-floppies /puppy515/initrd.gz
kernel /puppy515/vmlinuz pmedia=atahd psubdir=puppy515 pfix=fsck
initrd /puppy515/initrd.gz

Where did you install Grub4dos?
Are all the files in /puppy515?
Grub4dos in the MBR.

I saw that the entries were basically the same,so it should boot. I suspect an installer error....I primarily do manual installs so I'm manually copying the files right now.
Back in a few.

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#219 Post by James C »

After manually copying the files, it's booting.So,installer error. :)

Three out of four booting without editing is not too bad I guess.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#220 Post by bigpup »

I had to change the kernel line for the Vector install from "root=/dev/sda1" to "root=0301" boots fine again now.
I had to do something similar for an install of Mint. Mint has its own way of doing stuff. It puts files in strange places. Simple adjustment of the menu.lst entry.

Post Reply