On 14/03/2016 21:09, Dale R. Worley wrote:
bilsch writes:
How can an OS partition and format a drive if it doesn't know the
number of sectors?
I have a vague memory that in the earliest days of hard disks on PC's
that you had to enter that number from documentation that came with the
drive.
O
bilsch writes:
> How can an OS partition and format a drive if it doesn't know the
> number of sectors?
I have a vague memory that in the earliest days of hard disks on PC's
that you had to enter that number from documentation that came with the
drive.
Dale
On 03/11/2016 08:56 AM, Dale R. Worley wrote:
bilsch writes:
I'm a low energy QEMU user. I use it for running a 'hobby' OS that is
little more than a boot sector. It has a program that calls int 0x13
ah=0x48 to get the number of sectors on the hard drive. If the call
returns CF=1 it means
The QEMU site says it emulates PC BIOS from the Seabios project. I
looked at the Seabios site and it references many sources. I'm not sure
how to interpret the info on the Seabios site but they do reference Ralf
Brown Interrupt List. RBIL info implies Seabios does not support int
0x13/ah=0x4
bilsch writes:
> I'm a low energy QEMU user. I use it for running a 'hobby' OS that is
> little more than a boot sector. It has a program that calls int 0x13
> ah=0x48 to get the number of sectors on the hard drive. If the call
> returns CF=1 it means the call was unsuccessful (and presumabl
I'm a low energy QEMU user. I use it for running a 'hobby' OS that is
little more than a boot sector. It has a program that calls int 0x13
ah=0x48 to get the number of sectors on the hard drive. If the call
returns CF=1 it means the call was unsuccessful (and presumably the # of
sectors info
I'm a low energy QEMU user. I use it for running a 'hobby' OS that is
little more than a boot sector. It has a program that calls int 0x13
ah=0x48 to get the number of sectors on the hard drive. If the call
returns CF=1 it means the call was unsuccessful (and presumably the # of
sectors info
