If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
meaning of "rdisk()" in boot.ini file
ABSTRACT
This investigation shows that the "rdisk()" parameter in the C:\boot.ini file represents a hard drive in terms of its displacement from the head of the hard drive boot order in the BIOS. The value of n in "rdisk(n)" expresses this displacement, where n is an integer value starting with 0, and where "rdisk(0)" represents the hard drive which is at the head of the hard drive boot order, i.e. the hard drive at zero displacement from the head of the hard drive boot order. The BIOS used in the investigation was the Phoenix Technologies BIOS as supplied in Dell Dimension desktop PCs. HARDWARE Dell Dimension XPS-R450 with a Phoenix Tech BIOS, (3) Maxtor DiamondMaxPlus 9 hard drives connected to (1) SIIG IDE PCI controller card used in the 1st half of the investigation, and connected to (1) motherboard IDE controller used in the 2nd half of the investigation. HARD DRIVE CONFIGURATION IDE channel 0, Master - 80GB hard drive IDE channel 0, Slave - 40GB hard drive IDE channel 1, Master - 120GB hard drive Each HD had a Master Boot Record (MBR), each HD had as its partition #1 a Primary partition that 1) had a Boot Sector, 2) was marked "Active", and which 3) contained the boot files ntldr, boot.ini, and ntdetect.com . SOFTWARE CONFIGURATION Microsoft WindowsXP Pro installed in partition #1 of each HD. boot.ini file in the 80GB HD: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="(80GB part 1 boot.ini) rdisk 0, part 1" /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="(80GB part 1 boot.ini) rdisk 1, part 1" /fastdetect multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="(80GB part 1 boot.ini) rdisk 2, part 1" /fastdetect boot.ini file in the 40GB HD: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="(40GB part 1 boot.ini) rdisk 0, part 1" /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="(40GB part 1 boot.ini) rdisk 1, part 1" /fastdetect multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="(40GB part 1 boot.ini) rdisk 2, part 1" /fastdetect boot.ini file in the 120GB HD: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="(120G B part 1 boot.ini) rdisk 0, part 1" /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="(120G B part 1 boot.ini) rdisk 1, part 1" /fastdetect multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="(120G B part 1 boot.ini) rdisk 2, part 1" /fastdetect Each of the above boot.ini file entries under the line "[operating systems]" specified an OS in partition #1 of one of the HDs, i.e. from "rdisk(0)", "rdisk(1)", or "rdisk(2)". The character string between the quotes in each OS entry became a line in the on-screen menu displayed by ntldr at boot time, and it was to aid in identifying which HD got control from the BIOS (i.e 80GB, 40GB, or 120GB) and which "rdisk()" value each line corresponded to. A file with a name identifying the HD which contained it was put on the Desktop of each OS. This was to aid in identi- fying the HD of the OS that was loaded. EXPERIMENT Each HD was in turn put at the head of the BIOS's hard drive boot order and the PC was started. Each of the three entries in the on-screen boot menu was selected in turn, and the OS that loaded was recorded. 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 in the BIOS, and the above experiment was repeated. Then, the hard drives were disconnected from the IDE PCI controller card and connected to the IDE controller on the motherboard, and the entire experimental sequence detailed above was repeated. A total of 36 boot-ups were executed. RESULTS The following results were identical for both the PCI IDE controller case and for the motherboard IDE controller case: HD boot order: 80GB, 40GB, 120GB boot menu entry selected: HD the OS booted from: (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 boot menu entry selected: HD the OS booted from: (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 boot menu entry selected: HD the OS booted from: (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 boot menu entry selected: HD the OS booted from: (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 boot menu entry selected: HD the OS booted from: (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 boot menu entry selected: HD the OS booted from: (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 OS always booted from the hard drive having a position in the hard drive boot order expressed as the n in "rdisk(n)" parameter of the boot.ini file entry. This correspondence persisted throughout all all permutations of the hard drive boot order and despite which IDE controller the HDs were connected to. Whether this is the case in other less common BIOSes is unknown by this investigator. But since the Phoenix Technologies' BIOSes are used by many large PC manufacturers, it is probably a very common meaning of "rdisk()" among modern PCs running a Microsoft Windows operating system. *TimDaniels* |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
errors using retrospect express s-ware --- too many?? | MB_ | Dell Computers | 5 | October 14th 05 08:50 PM |
BenQ Dw1620 Dvd burner problem | oops | Cdr | 2 | May 20th 05 04:40 AM |
Fixing HDD errors | perrin | Storage (alternative) | 3 | March 27th 05 02:17 AM |
PartitionMagic Question | Harvey Gratt | Storage (alternative) | 43 | February 5th 05 08:20 PM |
Help! - The dreaded buffer underrun | XPG | Cdr | 5 | August 31st 03 06:27 PM |