This article describes how to view and manually configure Boot.ini files in http://www.aliyun.com/zixun/aggregation/11208.html ">microsoft Windows Server 2003."
In Windows Server 2003, you can quickly and easily locate the Boot.ini file to verify or edit the Microsoft Windows startup configuration and change the advanced RISC calculation (ARC) path as needed. Alternatively, you can add a switch to the Boot.ini file.
I. Edit Boot.ini file
To view and edit Boot.ini files, follow these steps:
1, click Start, point to Settings, and then click Control Panel.
2, in the Control Panel, double-click System.
3, click the Advanced tab, and then click Settings under Startup and recovery.
4. Under System startup, click Edit.
Note: In a multiple-boot operating system configuration, start by selecting the default operating system by clicking the operating system that you want in the default operating system list.
Ii. Typical situation
The following list describes typical scenarios in which users must manually update the ARC path in the Boot.ini file after the storage configuration changes.
1. If you add a new controller that disables the BIOS, you may have to check in the Boot.ini file and manually correct the ARC path.
Note: This additional controller may also affect the controller portion of the ARC path.
2. Whenever you add or remove a disk from your computer, you may be able to cause a situation in which you must update the ARC path.
3, although the operating system may sometimes update Boot.ini files, you must still manually update the ARC path. Whether you must update the ARC path manually depends on the degree and nature of the changes to the Boot.ini file.
If this change to the ARC path causes problems when you start your computer, use the following procedure:
1. Start the Recovery Console and run the Map ARC command. From the results of the Map Arc command, you can determine the correct ARC path.
2. Create a new Boot.ini file on another computer.
Copy the new Boot.ini file. Use one of the following methods:
1 Copy the new Boot.ini file to the floppy disk, and then use the Recovery Console to copy the new Boot.ini file to the system.
2 Copy the new Boot.ini file to the NT boot floppy disk. If you need the following files, copy them to the same floppy disk: Ntldr, Ntdetect.com, and the mass storage device driver renamed to Bootdd.sys.
3 You can also use the Recovery Console and the/BOOTCFG switch to repair the ARC path in Microsoft Windows XP or Microsoft Windows Server 2003.
Do not automatically update the ARC path
The following explains why the operating system does not automatically update the ARC path when a storage configuration change is detected.
Changing the storage configuration may prevent the operating system from determining whether problems in existing ARC paths in the Boot.ini file can cause problems at the next startup. Because the ARC path is only updated during startup (that is, when you insert a removable hard disk), the operating system cannot determine the ARC path of the removable hard disk. The operating system is also unsure whether the presence of the drive affects the existing ARC path in the Boot.ini file. Similarly, if changes to the storage configuration are made offline, the operating system will not be able to learn about the changes.
For example, if you shut down your computer, the operating system will not discover the following issues until the next time it starts:
Added controller;
Added storage;
Changed the controller BIOS;
Add storage to an existing controller.
The next attempt to start the computer may fail because the startup process does not contain any code to change the ARC path in the Boot.ini file.
Automatic update of ARC path
A lot of doors. Lists the conditions in which the operating system automatically updates the APC path in the Boot.ini file.
1. Change partitions-When you create or delete partitions using Logical Disk Manager or the Diskpart tool.
2. Change dynamic disk-When you change a dynamic disk that has a reserved partition, you may be prompted to update the ARC path. This means that even if this is a dynamic disk, information about the partition still exists in the 0 sectors of the partitioned table. This occurs when either of the following conditions is true:
1 if the partition already exists before the disk is converted to a dynamic disk.
2 If the/retain command runs under the Diskpart tool to ensure that information about the partition is added to the partition table.