add-circle-bold add-circle add-square add alarm-bell-1 alert-diamond analytics-pie-2 archive archive arrow-down-1 arrow-down-2 arrow-left-1 arrow-right-1 arrow-up-1 attachment-1 bin-paper-1 book-star button-record check-1 check-circle-1 close close-quote close cog-1 cog common-file-stack copy-paste credit-card-1 diagram-fall-down disable time-clock-midnight download-thick-bottom drawer-send envelope-letter envelope-letter expand-6 expand-6 file-code filter-1 floppy-disk flying-insect-honey folder-file-1 headphones-customer-support hierarchy-9 hyperlink-2 information-circle keyboard-arrow-down keyboard-arrow-up layout-module-1 list-bullets lock-2 lock-unlock-1 love-it messages-bubble-square move-to-top multiple-circle multiple-neutral-1 multiple-users-1 navigation-menu-horizontal navigation-menu network-browser open-quote pencil-1 pencil-write pencil-1 print-text rating-star rating-star remove-circle remove-square-1 search send-email-1 shield-warning single-neutral-actions single-neutral smiley-sad-1 smiley-unhappy smiley-indifferent smiley-smile-1_1 smiley-happy smiley-sad-1 smiley-unhappy smiley-indifferent smiley-happy smiley-thrilled social-media-twitter synchronize-arrows-1 tags-double ticket-1 ticket-1 time-clock-circle undo view-1 view-off view wench

How to edit the boot.ini file in Windows Server 2003

“Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware.”

The ARC path in the boot.ini file incorrectly identifies the location of the system boot files on the recovered machine. This may occur when a DATASTOR Computer System type plan protects a Windows Server 2003 system that contains multiple partitions, for example an OEM recovery partition in addition to the system partition, but during recovery the same number and mapping of partitions is not recreated. The recovered system then contains a different disk configuration with a different number of partitions. When the system attempts to boot, it reads the ARC path in the boot.ini file for the location of system boot files, which references the original disk layout, not the current disk layout.

After the system is recovered using the System Recovery Environment (SRE) and the desired system image, but before exiting the SRE, edit the boot.ini file to reflect the correct boot partition. If you exit the SRE and find that the system will not boot, you can boot into the SRE again to edit the boot.ini file. 


1. Recover a Windows Server 2003 system following the steps outlined in the document, “Computer System Recovery”, available for download. 

2. Reboot the system. Upon reboot, the system does not boot, in this case. See figure A.

3. Boot into the System Recovery Environment. On the menu, select Open command prompt (Advanced).

4. At the command prompt, type C:\boot.ini and hit enter. The boot.ini file opens in notepad. In this example, the partition parameter is 3 because the system had a 100 MB OEM partition, an OEM Recovery partition, and a third system partition (C:) that contained the boot files. See figure B.

5. In notepad, edit the partition parameter in both the [boot loader] and [operating systems] ARC paths so the partition number corresponds to the partition number on the recovered system that contains the boot system files. ARC partition numbering begins with 1, not 0. If you restored onto the first partition of a disk, edit the partition(n) entries so they read partition(1), for example. See figure C. 

6. In notepad, click the File menu, then Save. 
Note: If the file is marked read-only, the Save As dialog box will open. The file will then save with a .txt extension, which will not resolve the problem. Instead, cancel the Save As dialog box, then remove the read-only attribute of boot.ini at the command line:  attrib -R -S -H C:\boot.ini, hit enter, then save the file in notepad again. 

7. In the command prompt window, type exit and hit enter. 

8. In the SRE menu, select Restart Computer.

9. The system restarts and boots into Windows Server 2003. See figure D.

For more detail on ARC path naming conventions, see