text mode boot phase is run from a hard disk image
boot device is changed to real hard disk
gui mode boot phase is run from a hard disk
At text mode boot phase windows remember a hard disk like device by MBR signature and a internal checksum.
At gui mode boot phase these infomation are used to detect boot device again.
Behaviour can be used to change boot device on the fly.
boot from USB/Firewire HD without BIOS support
boot from Compact Flash card at PC Card adapter without BIOS support
boot from SD card at laptop without BIOS support
boot from USB stick with half broken BIOS (image and PE at the same device)
Text mode boot image has to load appropiate drivers for external devices.
Gui mode boot phase switch boot hardware next.
A more general boot description: Troubleshooting the Startup Process
To accomplish chain boot real hardware has to contain a MBR:
USB hard disk, USB stick, CF card, SD card. Actually there is no limitation.
This approach is possible at setupldr.bin PE too.
Txtsetup.sif desribe early boot environment.
Of course loaded image has to contain required drivers.
E.g. use USB drivers, if you like to chain boot a USB device. That's enable USBSupport.Script at this example.
Thanks to jaclaz, default image was created with mkimg.cmd. http://www.boot-land...?showtopic=3191
This script prepare a hard disk image. Boot files are read from a PE %TargetDir%.
Hence use this hard disk image with this PE %TargetDir%.
Select a physical drive containing a MBR. Disk Management list drive number.
Select the same format for hard disk image and physical drive partition.
Integrate hard disk image, grub4dos grldr and menu.lst to a boot media.
I've difficulties to include this to LiveXP at boot CD.
A addional grub4dos boot option would be nice.
Multiprocessor files are not copied at multiprocessor.script runtime.
CreateISO.script create a new menu.lst and Run,%multiprocessor_script%,CreateISO-%multiprocessor_section%.
Different approaches are possible:
multiprocessor.script copy files at multiprocessor runtime. And menu.lst is appended at CreateISO.script.
Or CreateISO.script build a new menu.lst. And run chainboot.script [Create_Add_menu_lst] and [multiprocessor].
Not tested, remember that's my first script.
What's your opinion? Do you adjust multiprocessor.script or CreateISO.script?
Atttachment updated 2008-Sep-02: