Re: El-Torito and HD partitions

From: KM (konstmor_at_nospam_yahoo.com)
Date: 09/15/04 

Date: Wed, 15 Sep 2004 13:44:20 -0700

Slobodan,

Well... You are absolutely right about the disk.sys but (there is always some but's :-) ) according to the
http://support.microsoft.com/default.aspx?scid=kb;en-us;93373:
    This process is repeated for all hard drives in the system. Please note that if you have multiple controllers in your system,
the drive letter ordering is based on the order in which the device drivers are loaded by Windows NT.

I assume CD-ROM could sit on a different controller (it is often the case). Would it be primary controller? or secondary? I don't
know. But if it is the secondary one and there is a HDD on primary - HDD would probably take C:\.

Again.. it is up to an experiment. 

-- 
 Regards,
        KM, BSquare Corp.
> Konstantin,
>
> > > Even if you remove all entries including C:. It should work since during the boot C: and other letters will be autoassigned.
> > I never tried this. But I guess it would only work if you don't have a HDD in the target device when you boot from El-Torito CD,
> > right?
> > Otherwise, HDD (active partition) will probably take precedence and would be assigned with C:\.
>
> I have not tried it either, but. To higher level drivers el-torito and HDD are same thing, they are both handled trough disk.sys
> driver.
> ntldr pass along with ARC names disk id and MBR CRC. Then kernel match this signature with same disk signature calculated trough
> disk.sys driver.
>
> From that point forward (this is time before volume letters are assigned) OS knows what partition belong to the OS itself.
> So OS partition should take precedence to all other partitions in volume letter assignment algorithm.
>
> This mean that it should be C:, right?
>
> Best regards,
> Slobodan
>
>
>
>
>

Relevant Pages

  • Re: hibernation file location
    ... If a disk controller driver was copied to the system partition (where NTLDR, BOOT.INI, and NTDETECT.COM reside), and renamed as NTBOOTDD.SYS, then NTLDR would be able to read a kernel and drivers from the boot partition on a drive connected to that controller, even if the controller didn't have a BIOS. ... Thinking about the generalities of the BOOT.INI file, specifying a number of controllers and drives and partitions, I'm still trying to figure out how NTLDR could load drivers for all of those controllers when all of the drivers had to be given the same filename NTBOOTDD.SYS. ...
    (microsoft.public.development.device.drivers)
  • Re: XP wont install on SATA HDD
    ... 131MB of this drive to partition... ... install Raid or Mass Storage Device drivers. ... the problem is not recognition of your SATA HDD. ... 128 GB binary) of hard drive disk space. ...
    (microsoft.public.windowsxp.general)
  • Re: El-Torito and HD partitions
    ... And XPe partition will be given volume letter C: ... Drivers load order is independed of BIOS settings, so this probably mean that link you provided is not accurate for Win XP. ... Regards, ... > I assume CD-ROM could sit on a different controller. ...
    (microsoft.public.windowsxp.embedded)
  • Upgrading Win XP Home Edition to Pro.
    ... HDD, a recovery partition. ... along with the drivers for the ... to the MB) and video display. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Upgrading Win XP Home Edition to Pro.
    ... > HDD, a recovery partition. ... along with the drivers for the ... I would like to upgrade ...
    (microsoft.public.windowsxp.help_and_support)