Lines Matching full:bios
582 @dfn{normal working order}, i.e. as initialized by the @sc{bios} (or
584 operating system should be able to make @sc{bios} calls and such after
585 being loaded, as long as it does not overwrite the @sc{bios} data
587 @sc{pic} programmed with the normal @sc{bios}/DOS values, even if it
669 field is valid, and indicates which @sc{bios} disk device the boot
671 @sc{bios} disk, then this field must not be present (bit 3 must be
685 The first byte contains the @sc{bios} drive number as understood by the
686 @sc{bios} INT 0x13 low-level disk interface: e.g. 0x00 for the first
802 memory map of the machine provided by the @sc{bios}. @samp{mmap_addr} is
863 The @samp{drive_number} field contains the BIOS drive number. The
877 @sc{bios}. @samp{drive_cylinders} contains the number of the
883 for the drive in the @sc{bios} code. The array consists of zero or more
890 returned by the @dfn{GET CONFIGURATION} @sc{bios} call. If the @sc{bios}
928 Management (APM) BIOS Interface Specification}, for more information.
964 * BIOS device mapping techniques::
975 @sc{bios} interfaces, or the newest ones are not available (see
982 @sc{bios} drive maps to which device driver in an operating system is
986 this problem, there are 2 @sc{bios} device mapping techniques
987 (@pxref{BIOS device mapping techniques}).
996 @sc{bios} interface, passing along any extra data to be interpreted by
1000 @node BIOS device mapping techniques
1001 @section BIOS device mapping techniques
1014 remaining @sc{bios} devices when not all of them have operating system
1038 The data on some @sc{bios} devices might be identical (so the part
1039 reading the drives from the @sc{bios} should have some mechanism to give
1043 There might be extra drives not accessible from the @sc{bios} which are
1044 identical to some drive used by the @sc{bios} (so it should be capable
1054 original copies for the @dfn{clean @sc{bios} virtual machine} to be
1057 For each device driver brought online, determine which @sc{bios} devices
1062 Create a @dfn{clean @sc{bios} virtual machine}.
1077 For each device driver, given how many of the @sc{bios} devices were
1082 @sc{bios} numbers, but they pretty much always count from the lowest
1187 BIOS drive information, BIOS configuration table, the name of a boot
