C
Colonel Blip
Hello, All!
I am having a problem that is either a result of a major "senior moment" or
is definitely a new one for me. My boot.ini (which I rebuilt from recovery
console using bootcfg /rebuild after a 'can't find hal.dll' problem) is, for
lack of a better phrase - out of sync - with the disk manager data. Here is
my boot.ini:
[boot loader]
timeout=7
default=multi(0)disk(0)rdisk(1)partition(4)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(4)\WINDOWS="n boot" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="D boot" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="C Boot" /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Colonel Blip Raid XP (E
"
/noexecute=optin /fastdetect /noguiboot
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional (C
" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(2)partition(4)\WINDOWS="Microsoft Windows XP Beta (Q
"
/noexecute=optin /fastdetect
Under [operating system], the first 3 items were added to my boot.ini when I
perfromed the bootcfg. I have verified that the 'n boot' corresponds to the
"Microsoft Windows XP Beta (Q
" line pre-bootcfg rebuild, the 'D boot'
corresponds to the "Colonel Blip Raid XP (E
" boot and the 'C boot' with
"Microsoft Windows XP Professional (C
". I have booted into each of the 1st
three successfully and verified they were the same as the previously working
ok last three. The strange thing is, I have not changed my hardware AND when
I open Disk Manager the last three items correspond to the actual rdisk,
partition data that shows.
Any idea why this has happened and what I might do about it?
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
I am having a problem that is either a result of a major "senior moment" or
is definitely a new one for me. My boot.ini (which I rebuilt from recovery
console using bootcfg /rebuild after a 'can't find hal.dll' problem) is, for
lack of a better phrase - out of sync - with the disk manager data. Here is
my boot.ini:
[boot loader]
timeout=7
default=multi(0)disk(0)rdisk(1)partition(4)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(4)\WINDOWS="n boot" /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="D boot" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="C Boot" /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Colonel Blip Raid XP (E

/noexecute=optin /fastdetect /noguiboot
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional (C

multi(0)disk(0)rdisk(2)partition(4)\WINDOWS="Microsoft Windows XP Beta (Q

/noexecute=optin /fastdetect
Under [operating system], the first 3 items were added to my boot.ini when I
perfromed the bootcfg. I have verified that the 'n boot' corresponds to the
"Microsoft Windows XP Beta (Q

corresponds to the "Colonel Blip Raid XP (E

"Microsoft Windows XP Professional (C

three successfully and verified they were the same as the previously working
ok last three. The strange thing is, I have not changed my hardware AND when
I open Disk Manager the last three items correspond to the actual rdisk,
partition data that shows.
Any idea why this has happened and what I might do about it?
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)