Difference between revisions of "Boot an Iso image"

From Syslinux Wiki
Jump to: navigation, search
(Add specific links to the MEMDISK page about the restrictions and workaround for booting ISO images)
Line 8: Line 8:
 
Note: just like floppy emulation ([[MEMDISK]] or grub4dos) this will only work as long the operating system is accessing the virtual disk using the BIOS. After the operating system loads its own drivers for accessing the controller it's very likely that this virtual disk can be no longer accessed.
 
Note: just like floppy emulation ([[MEMDISK]] or grub4dos) this will only work as long the operating system is accessing the virtual disk using the BIOS. After the operating system loads its own drivers for accessing the controller it's very likely that this virtual disk can be no longer accessed.
  
For examples, restrictions and workaround for booting ISO and floppy images with MEMDISK, see [[MEMDISK#ISO_images]].
+
For examples, restrictions and workaround for booting ISO and floppy images with MEMDISK, see [[MEMDISK#ISO_images]] and [[MEMDISK#INT_13h_access:_Not_all_images_will_boot_completely.21]].

Revision as of 14:40, 23 April 2011

You can boot install a bootmanager on CD. That`s called ISOLINUX.

However, you can chainload a CD using Smart Boot Manager, see here.

An even better method can be done with grub4dos. Grub4dos can act as an CD-ROM emulator. This is also possible if the BIOS has no native support for booting from CD-ROM.

Note: just like floppy emulation (MEMDISK or grub4dos) this will only work as long the operating system is accessing the virtual disk using the BIOS. After the operating system loads its own drivers for accessing the controller it's very likely that this virtual disk can be no longer accessed.

For examples, restrictions and workaround for booting ISO and floppy images with MEMDISK, see MEMDISK#ISO_images and MEMDISK#INT_13h_access:_Not_all_images_will_boot_completely.21.