are the boot.ini settings related to disk # in Disk Management WS2

[ki1r]

I have a 2003 Server with a SATA RAID controller (ID 0) Onboard SCSI unused
(ID 1) and Adaptec SCSI (ID 2). System boots from the SATA RAID. Added a SCSI
drive to the Adaptec controller for pagefile and SQL Transaction logs. The
Adaptec also is hosting my tape drive. I noticed when I went into the Disk
Management after I booted the RAID array was now listed as Drive 1 from Drive
0, and the new SCSI drive was now Drive 0. Nothing else has changed. Just
wanted to make sure I didn't need to change the boot.ini file. I spoke with
the server manufacturer and they told me to change the boot.ini disk setting
from 0 to 1 based on the change in disk management. After doing some research
on the boot.ini I am not sure that what is showing in the Disk Management
Console is related to the boot.ini settings. The server is up and running,
just wanted to avoid any problems on reboot. I made a copy of the file and
added the changes the manufacturer reccommended as a second boot item to the
original but left the default section alone for now until I can see if
someone can confirm or deny my assumptions. I have two other servers exactly
like this one that are original and have confirmed the controller ID's are
the same on those machines. I suspect that the Disk Management disk number
has changed doesn't reflect what the boot disk number should be. Any help
would be appreciated.
Current Boot.ini multi(0)disk(0)rdisk(0)partition(2) (Partition # is
correct due to utility partition on array).
--
Ed