J
Jamie Hunter [MS]
Hey Holiday, not directly my area, but I can give you some quick answers...
Vista uses a new database called "BCD" to contain boot configuration data
and a whole new architecture for booting using a brand new boot component
called "BOOTMGR". It never tries to understand "boot.ini" or how to boot an
earlier version of windows. When you select the "Earlier Version" option, it
runs NTLDR, and uses that to boot the earlier version of Windows.
Regards BCDEDIT, it's a command line editor. You should use this in an
"elevated" command prompt (right-click on the "Command" icon and click "Run
as Administrator"). If you type "BCDEDIT /?" it lists all the options, and
how to get more information on it's use.
Regards drive letters, there have been lots of problems in the past where
applications expect "C:" to be the volume that contains the OS. Vista
shuffles drive letters around to help such older programs work. It's bit me
on occasion, until I got used to it. One thing that helps is to utilize the
ability to label volumes.
Vista uses a new database called "BCD" to contain boot configuration data
and a whole new architecture for booting using a brand new boot component
called "BOOTMGR". It never tries to understand "boot.ini" or how to boot an
earlier version of windows. When you select the "Earlier Version" option, it
runs NTLDR, and uses that to boot the earlier version of Windows.
Regards BCDEDIT, it's a command line editor. You should use this in an
"elevated" command prompt (right-click on the "Command" icon and click "Run
as Administrator"). If you type "BCDEDIT /?" it lists all the options, and
how to get more information on it's use.
Regards drive letters, there have been lots of problems in the past where
applications expect "C:" to be the volume that contains the OS. Vista
shuffles drive letters around to help such older programs work. It's bit me
on occasion, until I got used to it. One thing that helps is to utilize the
ability to label volumes.