(old)Puppy Linux Discussion Forum

Hi,

can anyone tell how the menu.lst should look for grub4dos to boot an ISO from the hard drive?

Several Isos are on the HD in the / ISOS /

Greetings

Wolfgang

Read here at the end of the first post. But note the issue with contiguous space and using a FAT32 partition.

For more info on how to boot from HDD, steve over at rmprepusb.com do great projects on booting.

If you can settle on an easy way to boot multiple ISO's from USB, the Easy2Boot solution is the way to go.

Check out USB version and let me now what you think?
HOWTO create easy multi-boot USB Puppy from Linux
HOWTO create easy multi-boot USB Puppy from Windows

Scoobs- does a corresponding mnu need to accompany a given ISO in _ISO/Linux/AUTO?

Semme wrote:Scoobs- does a corresponding mnu need to accompany a given ISO in _ISO/Linux/AUTO?

No!

The mnu file is auto-generated as you boot, just drop iso in AUTO dir and it will work.

Several ISO's in AUTO dir will also work, You'll get a list to choose from at boot.

Also other Linux Live CD's will work. I tested Ubuntu, Mint and more

Oh great! Sounds like it's reading their boot catalog? Does it work if the loader's Lilo?

Sorry, I haven't read into it too deep. I'll need some time, though it sounds terrific!

Hi,

thanks for the feedback but if I really understand it can Puppy Linux isos only boot from USB.
This approach is not possible in my application because it comes to PCs for students and because the sticks could be removed!
It's not about an external hard drive!

Greetings

Wolfgang

Although the instructions here are for USB drives, they should also work with a hard drive partition, provided that it is contiguous. So you would need a clean FAT32 partition, then copy the ISO's into it.

However, this method will not work with Puppy ISO's.

rcrsn51 wrote:Although the instructions here are for USB drives, they should also work with a hard drive partition, provided that it is contiguous. So you would need a clean FAT32 partition, then copy the ISO's into it.

However, this method will not work with Puppy ISO's.

But here it's all about Puppy isos!

Semme wrote:Oh great! Sounds like it's reading their boot catalog? Does it work if the loader's Lilo?

Sorry, I haven't read into it too deep. I'll need some time, though it sounds terrific!

Easy2boot is essentially Grub4dos

from homepage

GRUB4DOS is an universal boot loader based on GNU GRUB. It can boot off
DOS/LINUX, or via Windows boot manager/syslinux/lilo, or from MBR/CD. It also has
builtin BIOS disk emulation, ATAPI CDROM driver, etc.

also

you can add any number of Linux ISO Files to the \_Iso\Linux\Auto folder - this will work
for 99% of linux ISOs and most DOS ISOs too

der-schutzhund wrote: can anyone tell how the menu.lst should look for grub4dos to boot an ISO from the hard drive?

Several Isos are on the HD in the / ISOS /

You have grub4dos setup and it loads menu.lst at boot?

Scooby wrote:

der-schutzhund wrote: can anyone tell how the menu.lst should look for grub4dos to boot an ISO from the hard drive?

Several Isos are on the HD in the / ISOS /

You have grub4dos setup and it loads menu.lst at boot?

Yes!

I used this on USB, maybe you could try something like that on HD?
Never tried it on HD though

Its very easy to boot puppy from HD with Grub4dos!
you have to extract all the files from the ISO file first by mounting it, then copying the files to a folder

below i copied all the files to a folder called arch


title Arch Puppy
root (hd0,3)/arch
kernel /vmlinuz
initrd /initrd.gz


you just have to figure out which partition you have the files on
sda1 is (hd0,0)
sda2 is (hd0,1)
etc.

Perhaps the problem is still not clear!
The point is not to unpack the ISO but the iso as it is, to boot!
Lazy has 4 different user groups. Each group, for example, child, beginner, can be associated with any program. Now I want to create an iso for each group. All roms and all come sfs in the same directory. The 4 Isos should then be started from the boot menu and secured by a password. If I were to save every Lazy in a separate partition, then I would also copy the sfs in each partition. If the sfs are 4 times available it will cost not only space but it is a lot more work when the sfs changes anything!
Meanwhile, I have also tried with rmbrepusb / Easyboot. Does not work!
During the installation directories are not generated! No idea how to do that!

Greetings

Wolfgang

Have a hard drive on a laptop partitioned from scratch:
1. partition fat32
2. part. ntfs
3. swap

An iso is in the first Partition (fat32) in / ISOS /
Lazy is a frugal inst. in / PhyTechL-202

three menu.lst - entries have been tested with grub4dos:

title PhyTechL-202-005 iso
map /ISOS/LazYPuppy-202-DE-005.iso (0xff)
map --hook
root (0xff)
kernel /vmlinuz iso-scan/filename=/ISOS/LazYPuppy-202-DE-005.iso quiet splash
initrd /initrd.gz
boot

title PhytechL-202-005-hd32
map (hd32)/ISOS/LazYPuppy-202-DE-005.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)
boot

title Dieser Titel erscheint im Bootmen
fallback 2
find --set-root /ISOS/LazYPuppy-202-DE-005.iso
map /ISOS/LazYPuppy-202-DE-005.iso (0xff)
map --hook
chainloader (0xff)
savedefault --wait=2

the iso is found and loaded the drivers, but if the files are searched, there is the message that will continue to search subdirectories and then starts the frugal Lazy.

It is as if the start.sfs the iso can not be opened.

In any case things do not go!

der-schutzhund wrote:It is as if the start.sfs the iso can not be opened.

Exactly. Puppy has three core files. Grub4dos is smart enough to find vmlinuz and initrd.gz inside the ISO. This gets Puppy started.

But then Puppy needs to find its SFS file. But it's not smart enough to look inside the ISO. So it looks elsewhere on the hard drive and finds it in your frugal install.

Other Linuxes have a boot option like "isoscan" to handle this situation, but Puppy does not.

rcrsn51 wrote:

der-schutzhund wrote:It is as if the start.sfs the iso can not be opened.

Exactly. Puppy has three core files. Grub4dos is smart enough to find vmlinuz and initrd.gz inside the ISO. This gets Puppy started.

But then Puppy needs to find its SFS file. But it's not smart enough to look inside the ISO. So it looks elsewhere on the hard drive and finds it in your frugal install.

Other Linuxes have a boot option like "isoscan" to handle this situation, but Puppy does not.

Is there a Bootmanager wich can handle this?

with the zip on this side it will run but the sfs will not be found by Lazy-Puppy!
http://www.murga-linux.com/puppy/viewtopic.php?t=83583

der-schutzhund wrote:with the zip on this side it will run but the sfs will not be found by Lazy-Puppy!
http://www.murga-linux.com/puppy/viewtopic.php?t=83583

I downloaded Lazy and tried it with boot from USB, unpacked and still in ISO.
It works fine.

You tried the zipfile on HD? did you use the AUTO folder or did you use .mnu approach?

what was the error you receive during boot?

You may have to fiddle with root pointers
hd(0,1) in the files in /grub folder?

please if you find solution post it back here?

If I can find some time I will run a few tests