Levi Bard wrote:
> I thought Linux saw the drives on its own, without input from the BIOS.
> I had an old packard bell machine that had to have some seagate
> utility installed over the bootloader because the BIOS wouldn't deal
> with anything over 2G (when I had win 3.1 or some such on it).
That utility was a real-mode int13 hook driver that patched around your
faulty BIOS.
> At some point, the disk utility got corrupted, but Linux never cared
> about it one way or the other.
Your existing BIOS does int13 calls to read the bootsector off the drive
and execute the stage 0 bootstrap of your lilo/grub.
As long as your stage1/2 bootstraps and boot kernel are located below
that 2G limit (on the first partition on the disk, for example), there
should be no problems.
-- - Ian C. Blenke <icblenke@nks.net> (This message bound by the following: http://www.nks.net/email_disclaimer.html)----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:12:10 EDT