since I'm already quoted here and have a new feature for this famous forum, I decided to register .
I'm not quite sure, where my ideas fit (Grub4dos ->Grub4dos,.iso images ... or new topic under Grub4dos?) .
I managed to get Grub4dos (0.4.4-2009-11-14) "isohybrided" (comparable to isolinux), i.e. using ONE image for both creating a bootable CD and a bootable USB pendrive. Well, isolinux can do that stuff already ... and it 's faster ! But it can only do it with ONE ISO image on ONE storage device. Grub4dos can potentially do it with MULTIPLE different ISO images on ONE medium. And Grub4dos is able to boot virtually ANY ISO image, no matter if it loads additional files, when running initial ramdisk, since ISO Image works like booted from a CD. At the moment, I have to create such images manually ( of course, I will upload a sample file for your tests and mention my tools), so I search for co-workers to create (Windows and Linux) scripts/programs for process automation, if this forum finds, that it's a useful feature.
The principle structure is as follows :
[ Master Boot Record; Code derived from isolinux, isohybrid]*
[ (fake)1st primary partition; boot, ID 0x83 (Linux; all ISO Image(s))]
[ 2nd partition : primary (FAT) or extended, for GRLDR, menu.lst and else ]
*) grldr.mbr didn't work !
When BIOS boots a USB pendrive as USB-HDD, it gets device (hd0). The Master Boot Record searches for GRLDR, but only on MS filesystems, first primary partition is skipped. So we need GRLDR on another partition, which eases BTW editing menu.lst.
How do we boot first ISO Image ?
menu.lst :
title Boot ISO image 1
map --unhook
# +100024 : size of 1st ISO image in sectors (512B) = 48.84 MiB
map --heads=0 --sectors-per-track=0 (hd0)0+100024 (hd32)
map --hook
root (hd32)
chainloader
Regards
COD11