Commit Graph

6 Commits

Author SHA1 Message Date
fvdl 6a2c64449b Sanity check the drive number in %dl and use it instead of blindly
assuming disk 0.
1999-05-02 13:48:30 +00:00
christos 8eeaf82ae4 - Use the proper multiply instructions so that we don't get truncated.
- Fix comparison, which did not work before.
1999-04-30 15:29:44 +00:00
fvdl a6f7895b92 Only use int13 extensions if the sectors can not be read through the
older CHS interface. This works around stupid BIOSs who report that
int13 extensions are present and functional, but fail when you actually
use them. Like Adaptec SCSI BIOSs.

For the bootselector, there was no space to get the CHS info from
the BIOS. Instead, use a flag that can be set by fdisk. fdisk will
set it if one of the partitions on the disk is out of CHS reach
for this disk/BIOS, so that the bootselector will use int13 extensions.
This isn't so bad, because it needs to be configured via fdisk anyway.

Change the mbr manualpage to reflect some shorter error messages.
1999-04-28 23:27:01 +00:00
ws f0a4bb6818 Use the drive parameter from the partition table
to support booting from the second disk.
1999-02-08 21:52:43 +00:00
ws faf59c0aba Initialize drive number in DL (not done by some BIOSs).
If you want to use 32-bit addresses, be sure to init the high bits, too.
Some additional register saves around BIOS calls (just in case).
1999-01-28 14:14:04 +00:00
ws 3cdac6d69c Separate master bootcode from fdisk.
Add int13 extension support to master bootcode.
1998-10-15 15:22:13 +00:00