Re: Boot.ini question

"Rod Speed" wrote: 
You cant do it that way either. You should be leaving the 80G drive
with the only boot.ini at the top of the hard drive boot order list, so
you can be sure that that drive is being booted by the bios.



   That is clearly being done.  First, with the 80GB HD at
the head of the HD boot order, each of the 3 HDs were booted.
Then with the 80GB HD remaining at the head of the HD boot
order and the order of the other 2 HDs reversed, all 3 HDs
were again booted.

   Next, with the 40GB HD at the head of the HD boot order,
each of the 3 HDs were booted.  Then with the 40GB HD
remaining at the head of the HD boot order and the order
of the other 2 HDs reversed, all 3 HDs were again booted.

   Next, with the 120GB HD at the head of the HD boot order,
each of the 3 HDs were booted.  Then with the 120GB HD
remaining at the head of the HD boot order and the order
of the other 2 HDs reversed, all 3 HDs were again booted.

    You can see, if you study the results, that the HD that
contained the OS that got booted was always the one
corresponding to the value of rdisk(n), where "n" was the
displacement from the head of the HD boot order.

*TimDaniels*








THEN you should swap JUST the 40G and the 120G
drives in the boot order list, while keeping them at
lower priority in the boot order list than the 80G drive
and see what drive gets booted when you select each
of the boot.ini entrys with rdisk values of 1 and 2.

Each of the three entries in the boot.ini-derived boot menu was selected and the OS that loaded was recorded. A file with a name identifying the HD it was on was put on the desktop of each OS in partition #1 of each HD to aid in
identifying the HD. Since the boot.ini files contained entries
only for the partition #1 on each HD, the experiment was a specific test for the meaning of the "rdisk()" parameter.

Then the order of the 2nd and 3rd HD in the hard drive boot order was reversed, and the above experiment was repeated.

RESULTS 

   HD boot order: 80GB, 40GB, 120GB
   menu option selected:                                 booted:
       (80GB part 1 boot.ini) rdisk 0, part 1      80GB,  part 1
       (80GB part 1 boot.ini) rdisk 1, part 1      40GB,  part 1
       (80GB part 1 boot.ini) rdisk 2, part 1      120GB, part 1


   HD boot order: 80GB, 120GB, 40GB
   menu option selected:                                 booted:
       (80GB part 1 boot.ini) rdisk 0, part 1      80GB,  part 1
       (80GB part 1 boot.ini) rdisk 1, part 1      120GB, part 1
       (80GB part 1 boot.ini) rdisk 2, part 1      40GB,  part 1


   HD boot order: 40GB, 80GB, 120GB
   menu option selected:                                 booted:
       (40GB part 1 boot.ini) rdisk 0, part 1      40GB,  part 1
       (40GB part 1 boot.ini) rdisk 1, part 1      80GB,  part 1
       (40GB part 1 boot.ini) rdisk 2, part 1      120GB, part 1


   HD boot order: 40GB, 120GB, 80GB
   menue option selected:                                booted:
       (40GB part 1 boot.ini) rdisk 0, part 1      40GB,  part 1
       (40GB part 1 boot.ini) rdisk 1, part 1      120GB, part 1
       (40GB part 1 boot.ini) rdisk 2, part 1      80GB,  part 1


   HD boot order: 120GB, 40GB, 80GB
   menue option selected:                                booted:
       (120GB part 1 boot.ini) rdisk 0, part 1     120GB, part 1
       (120GB part 1 boot.ini) rdisk 1, part 1     40GB,  part 1
       (120GB part 1 boot.ini) rdisk 2, part 1     80GB,  part 1


   HD boot order: 120GB, 80GB, 40GB
   menue option selected:                                booted:
       (120GB part 1 boot.ini) rdisk 0, part 1     120GB, part 1
       (120GB part 1 boot.ini) rdisk 1, part 1     80GB,  part 1
       (120GB part 1 boot.ini) rdisk 2, part 1     40GB,  part 1


DISCUSSION

   The "rdisk()" parameter was seen to always correspond to the
position of the hard drive in the Phoenix Tech BIOS's hard drive
boot order through all permutations of the hard drive boot order.


No it wasnt, you confused the issue with the SIIG IDE PCI controller card.

Whether this correspondence is found in other BIOSes is unknown by this investigator, but since the Phoenix Tech's BIOSes are used by several large manufacturers of PCs, it is probably a very common meaning for "rdisk()" among modern PCs running a Microsoft Windows operating system. 

Fraid not, and phoenix bios are the least commonly used of the 3
majors. And most dont have their drives on a PCI controller either.

*TimDaniels*, Investigator

Wanker, actually. 


.

Relevant Pages

  • Re: "rdisk()" in boot.ini file
    ... has been a failure of one of the drives in that list. ... drives on the controllers, not the HD boot order list. ... Irrelevant to the FACT that if the bios uses the HD ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: How do I uninstall one of two OS installed on separate hard dr
    ... hard drives - that's why you're calling the HD with the C: ... the BIOS's HD boot order, and "rdisk" will refer to that HD, ... Master/Slave jumpering of the 2 HDs puts the HD containing the ... partition at the head of the BIOS's HD boot order. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Boot.ini question
    ... Irrelevant to the whole point of the rdisk() parameter. ... out there as well, do have such drives; ... which allow to boot easily from any drive recognized by the BIOS ... drives below the entry at the top of the hard drive boot order ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Silicon Image Ultra ATA Ide Controller Card
    ... I connect my drives to the card and restart, Windows sees the drives as Secondary and hangs. ... It will go to the HD at the head of the ... HD boot order and look for its MBR. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Boot.ini question
    ... This experiment shows that the Phoenix Technologies BIOS ... > boot order, where "x" is a positive integer starting with 0. ... > Maxtor DiamondMaxPlus 9 hard drives connected to ... are claiming with drives on the motherboard IDE ports. ...
    (comp.sys.ibm.pc.hardware.storage)
Loading