Lines Matching full:boot
36 // $e6f2 ; INT 19h Boot Load Service Entry Point
70 // NOTES for El-Torito Boot (cbbochs@free.fr)
72 // - Current code is only able to boot mono-session cds
73 // - Current code can not boot and emulate a hard-disk
76 // - I used cmos byte 0x3D to store extended information on boot-device
78 // - Here are the cdrom boot failure codes:
85 // 7 : can not read cd - boot catalog
86 // 8 : boot catalog : bad header
87 // 9 : boot catalog : bad platform
88 // 10 : boot catalog : bad signature
89 // 11 : boot catalog : bootable flag not set
90 // 12 : can not read cd - boot image
121 // - should be able to boot any cdrom instead of the first one
172 /* 256 bytes at 0x9ff00 -- 0x9ffff is used for the IPL boot table. */
177 #define IPL_SEQUENCE_OFFSET 0x0082 /* u16: next boot device */
193 # error El-Torito Boot can only be use if ATA/ATAPI Driver is available
717 // EBDA must be at most 768 bytes; it lives at EBDA_SEG, and the boot
1951 // BIOS Boot Specification 1.0.1 compatibility
1953 // Very basic support for the BIOS Boot Specification, which allows expansion
1954 // ROMs to register themselves as boot devices, instead of just stealing the
1955 // INT 19h boot vector.
2009 /* Get the count of boot devices, and refuse to overrun the array */
2032 printf("Press F12 for boot menu.\n\n");
2043 printf("Select boot device:\n\n");
2093 // displays the boot device
2121 // displays the reason why boot failed
2129 printf("Boot failed");
2135 printf(": could not read the boot disk");
2142 // displays the reason why boot failed
2148 bios_printf(BIOS_PRINTF_SCREEN | BIOS_PRINTF_INFO, "CDROM boot failure code : %04x\n",code);
2162 BX_PANIC("INT18: BOOT FAILURE\n");
3557 // Start of El-Torito boot functions
3610 // Read the Boot Record Volume Descriptor
3630 // ok, now we calculate the Boot catalog address
3633 // And we read the Boot Catalog
3657 // Win2000 cd boot needs to know it booted from cd
3730 // return the boot drive + no error
3735 // End of El-Torito boot functions
5987 case 0x4c: // ElTorito - Initiate disk emu and boot
5988 case 0x4d: // ElTorito - Return Boot catalog
7993 // 0: system boot sequence, first drive C: then A:
7994 // 1: system boot sequence, first drive A: then C:
7996 // CMOS regs 0x3D and 0x38 contain the boot sequence:
7997 // CMOS reg 0x3D & 0x0f : 1st boot device
7998 // CMOS reg 0x3D & 0xf0 : 2nd boot device
7999 // CMOS reg 0x38 & 0xf0 : 3rd boot device
8000 // boot device codes:
8006 // else : boot failure
8008 // Get the boot sequence
8021 /* Reset boot sequence */
8028 if (seq_nr ==2) BX_PANIC("No more boot devices.");
8030 /* Boot from floppy if the bit is set or it's the second boot */
8036 /* Read the boot device from the IPL table */
8038 BX_INFO("Invalid boot device (0x%x)\n", bootdev);
8042 /* Do the loading, and set up vector as a far pointer to the boot
8043 * address, and bootdrv as the boot drive */
8089 /* Always check the signature on a HDD boot sector; on FDD, only do
8131 /* Jump to the boot vector */
8136 ;; Build an iret stack frame that will take us to the boot vector.
8143 ;; Set the magic number in ax and the boot drive in dl.
8588 // ebx is modified: BSD 5.2.1 boot loader problem
8622 int18_handler: ;; Boot Failure recovery: try the next device.
8630 ;; Get the boot sequence number out of the IPL memory
8646 int19_relocated: ;; Boot function, relocated
8660 ;; Start from the first boot device (0, in AX)
8670 ;; Call the C code for the next boot device
8673 ;; Boot failed: invoke the boot recovery function
10257 mov ax, 0x16[bx] ;; 0x16 is the offset of Boot Connection Vector
10284 ;; Found a device that thinks it can boot the system. Record its BEV and product name string.
10479 ;; Warm Boot Flag 0040:0072
10695 .org 0xe6f2 ; INT 19h Boot Load Service Entry Point
