thanks Icecube!
Can you post the menu.lst file?
Not my project - just pic I saw on the internet...
If you boot from CD (ISOLINUX), all entries with 'on first hard drive' will boot your internal HDD (in normal cases at least).
When you boot from an USB stick (SYSLINUX), all entries with 'on first hard drive' refer to your USB stick (if it is detected as HDD in BIOS, not if is detected as a floppy). So you need the 'on second hard drive' options to boot your internal HDD.
I will only be using the first HDD portion to chainload other partitions on the USB-HDDs. I will use this to work around the single INSTALL.WIM limitation of setup.exe in Win7/Vista/Win2k8. First partition would have my custom UBCD build with a BOOTMGR with all the recovery WIMs and a single INSTALL.WIM (say Win7 32bit). Second partition would be likely just a NTFS partition with say Win7 64bit ISO extracted into it.
I wouldnt see any good reason for supporting hdd loading in UBCD ISO so I dont have to worry about drive 2.
I will likely only add code for partition 2 and 3 on the first hdd using following code:
Code: Select all
LABEL -
MENU LABEL Boot primary partition #2 on first hard drive
COM32 /boot/syslinux/chain.c32
APPEND hd0 2
LABEL -
MENU LABEL Boot primary partition #3 on first hard drive
COM32 /boot/syslinux/chain.c32
APPEND hd0 3
As an "aside" thought.... If my whole goal was to chainload a second partition with BOOTMGR to kick off a different installation version/bootmgr instance (and it is) then a more sensible way would be to add an entry(s) into the BCD file of the first partition that would have an option of loading the second/third partitions. Does that make sense?