What determines hard disk number?

I don't think that XP necessarily follows the BIOS enumeration order. At least
across different classes of device. My %boot%/%system% SATA drive is disk0,
until I plug in a PATA HDD, in which case the boot drive becomes disk1, and
the PATA becomes disk0.

However, I think the BIOS is still enumerating the boot SATA as 0.

If I boot to a floppy and run BootitNG the SATAs are enumerated before the PATA.
I'm pretty sure that BING uses int 0x13 to communicate with HDDs.



"JS" <@> wrote in message news:%23xHKfdM9IHA.4820@TK2MSFTNGP06.phx.gbl...
> Just to add to this, on one PC which I use, I installed a PCI Promise card that provides two extra IDE channels. The PC sees the
> card as SCSI. As soon as I connected an IDE hard drive to that card and rebooted, my boot drive (which is an IDE drive connected
> to the motherboard) changed from disk 0 to disk 1 and the drive connected to the Promise card is seen by Disk Manager as disk 0.
>
> It's still boots OK with the Disk 0 entry in the boot.ini file as the Promise card I would guess is not detected by Windows until
> after the drivers for this card are loaded.
>
> JS
>
> "Ian D" <taurus.TakeThisOut@nowhere.com> wrote in message news:O93%23ozE9IHA.4140@TK2MSFTNGP02.phx.gbl...
>>
>> "Walter R." <wer25.TakeThisOut@example.com> wrote in message news:%238KH$mE9IHA.1200@TK2MSFTNGP04.phx.gbl...
>>> Thank you, Ian.
>>>
>>> --
>>> Walter
>>
>> You're welcome. Another interesting thing I have found is
>> that if you have SATA and eSATA connectors with only
>> a SATA disk connected, it will be disk 0, but if you then
>> connect an eSATA disk, it will become disk 0, even if you
>> are still booting to the SATA disk. A disk connected to the
>> IDE master will always be disk 0, and the rest will re-rank.
>>
>
>

What's the boot order, regarding hard drives, in the bios settings?

--
Dave

"Bill Blanton" <bblanton DeleteThis @REMOVEmagicnet.net> wrote in message
news:%23VPFRSY9IHA.356@TK2MSFTNGP02.phx.gbl...
>I don't think that XP necessarily follows the BIOS enumeration order. At
>least
> across different classes of device. My %boot%/%system% SATA drive is
> disk0,
> until I plug in a PATA HDD, in which case the boot drive becomes disk1,
> and
> the PATA becomes disk0.
>
> However, I think the BIOS is still enumerating the boot SATA as 0.
>
> If I boot to a floppy and run BootitNG the SATAs are enumerated before the
> PATA.
> I'm pretty sure that BING uses int 0x13 to communicate with HDDs.
>
>
>
> "JS" <@> wrote in message news:%23xHKfdM9IHA.4820@TK2MSFTNGP06.phx.gbl...
>> Just to add to this, on one PC which I use, I installed a PCI Promise
>> card that provides two extra IDE channels. The PC sees the
>> card as SCSI. As soon as I connected an IDE hard drive to that card and
>> rebooted, my boot drive (which is an IDE drive connected
>> to the motherboard) changed from disk 0 to disk 1 and the drive connected
>> to the Promise card is seen by Disk Manager as disk 0.
>>
>> It's still boots OK with the Disk 0 entry in the boot.ini file as the
>> Promise card I would guess is not detected by Windows until
>> after the drivers for this card are loaded.
>>
>> JS
>>
>> "Ian D" <taurus DeleteThis @nowhere.com> wrote in message
>> news:O93%23ozE9IHA.4140@TK2MSFTNGP02.phx.gbl...
>>>
>>> "Walter R." <wer25 DeleteThis @example.com> wrote in message
>>> news:%238KH$mE9IHA.1200@TK2MSFTNGP04.phx.gbl...
>>>> Thank you, Ian.
>>>>
>>>> --
>>>> Walter
>>>
>>> You're welcome. Another interesting thing I have found is
>>> that if you have SATA and eSATA connectors with only
>>> a SATA disk connected, it will be disk 0, but if you then
>>> connect an eSATA disk, it will become disk 0, even if you
>>> are still booting to the SATA disk. A disk connected to the
>>> IDE master will always be disk 0, and the rest will re-rank.
>>>
>>
>>
>
>
>