Boot.ini album

xiaoxiao2021-03-06 77

Windows may use Signature () syntax in the boot.ini file

summary

After installing Windows, you may notice that the advanced RISC calculation (ARC) path item in the boot.ini file is started with the "Signature ()" syntax. E.g:

Signature (8B467C12) Disk (1) Rdisk (0) Partition (2) / Winnt = "Description"

Use Signature () syntax only when there is one of the following conditions:

• Bearing the system BIOS or controller installed with Windows start partitioning, INT-13 Extensions or disabled "INT-13 extension" option is disabled, and the partition with Windows is larger than ~ 7.8 Ji-byte (GB) or the partition The end cylindrical number is greater than 1024. • Installed with Windows drives to connect to their BIOS-disabled SCSI controller, so INT13 BIOS calls cannot be used during startup. For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

242518 Long Pause During Windows 2000 Startup Process (Suspension during the Windows 2000 boot process)

More information

Signature () syntax is equivalent to the SCSI () syntax, but the former is changed to support the plug-in structure in Windows. Since Windows is a plug-and-play operating system, SCSI controller number instances may be different each time you started Windows, especially when adding a new SCSI controller hardware after installation.

Using the Signature () syntax indicates that NTLDR locates the drive of its disk signature and the value of the value in parentheses, regardless of the number of the SCSI controller connected to the drive.

The Signature () value is extracted from the primary start record (MBR) of the physical disk. This unique hexadecimal number is either written in the MBR in the installed text mode section or writes when installing the Microsoft Windows NT 4.0 or earlier.

Note: If the disk signature in the MBR is rewritten (for example, by viral rewrite) or change (corrupted), it is no longer to match the Signature () value in the boot.ini file, it may be charged when you start your computer. To the following error message:

Windows 2000 could not start because of a computer disk hardware configuration problem.Could not read from selected boot disk.Check boot path and disk hardware.Please check the Windows documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals for additional Information.

- or -

Windows could not start because of the following ARC firmware boot configuration problem:. Did not properly generate ARC name for HAL and system paths.Please check the Windows documentation about ARC configuration options and your hardware reference manuals for additional information if you receive them For an error message, see the following article in the Microsoft Knowledge Base to help solve the problem:

119467 CREANG A BOOT Disk for An NTFS or FAT Partition (Create a launch disk for NTFS or FAT partition)

Since the SIGNATURE () syntax is replaced with the SCSI () syntax, the following requirements are also applicable: requires files named ntbootdd.sys in the root folder of the system partition so that the SCSI controller is addressed in the startup. This file is a specific SCSI port device driver for the SCSI adapter that you launched, it is renamed NTBootdd.sys and placed in the root folder of the system drive.

For additional information about the ARC name in the boot.ini file, see the following article in the Microsoft Knowledge Base:

102873 Boot.ini and arc path naming conventions and usage (boot.ini and ARC path naming rules and usage)

The information in this article applies to:

• Microsoft Windows 2000 Server • Microsoft Windows 2000 Advanced Server • Microsoft Windows 2000 Professional Edition • Microsoft Windows 2000 Datacenter Server

The role of Boot.ini file in Windows XP

summary

This article describes the role of the Boot.ini file and typical content.

More information

Windows uses the boot.ini file to determine which of the operating system options to display during the startup (boot) process. By default, Boot.ini is marked as read-only system files and usually do not require any manual modifications.

If you need to change this file, use the System tool in Control Panel:

1. Click the Start button, click the Control Panel, and then double-click the system. 2. Click the Advanced tab and click Settings under Startup and Fault Recovery. Typically, the Boot.ini file contains the following data:

[boot loader]

TIMEOUT = 30

DEFAULT = SCSI (0) Disk (0) RDisk (0) Partition (1) / WinNT

[Operating Systems]

SCSI (0) DISK (0) RDisk (0) Partition (1) / Winnt = "Windows NT" / Nodebug C: / = "Previous Operating System On C: /"

The following list describes the meaning of data in the Boot.ini file:

• "Timeout" Specifies the time of Windows waits until you select the default operating system • Specify the default operating system. • "SCSI (0) indicates the main controller (usually also a unique controller) responsible for this device. If there are two SCSI controllers and the disk is associated with the second controller, the second controller is called "SCSI (1)". If the system uses IDE, enhanced IDE (EIDE) or enhanced small device interface (ESDI) drive, or if the system does not have a SCSI adapter that does not have a built-in BIOS, "SCSI" is replaced with "Multi". • "Disk" refers to the SCSI logic unit (LUN) to use. It can be a stand-alone disk, but most SCSI settings have only one LUN for each SCSI ID. • "RDisk (0) refers to" Partition (1) "in this example is a unique partition on the first drive in the computer. If there are two partitions (C and D), the partition C is partition (1), the partition D is Partition (2). • Parameters containing multiple boot mode (if any) requires checking the Winnt folder to boot from the specified SCSI controller's disk and partition. • "/ nodebug" Specifies that no debugging information is not monitored. The debugging information is only useful to program developers. • You can add / sos option to display the driver name when loading the driver. By default, the OS Loader screen only shows the progress point. • "Previous Operating System On C: /" means "Previous Operating System" is MS-DOS because "C: /" is the MS-DOS path. The information in this article applies to:

• Microsoft Windows XP Home Edition • Microsoft Windows XP Professional Edition

Windows XP and Windows Server 2003's Boot.ini file available switch options

summary

You can add different switches to the boot.ini file to modify the startup method of Microsoft Windows XP or Microsoft Windows Server 2003.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

102873 Boot.ini and ARC path naming agreement and usage

More information

The following switches can be added to the Boot.ini file.

Note: These switches apply to Microsoft Windows XP and Microsoft Windows Server 2003 unless otherwise specified.

/ Basevideo

/ basevideo switches enforce the system into standard 640x480 16-color VGA mode by using a video driver compatible with all video adapters. This switch allows you to load the system when you select an error or refresh frequency. Please put the switch with

The / SOS switch is used together. If a new video driver is installed, the driver is not working properly, and this parameter can be used to start the operating system. Then you can delete, update, or roll back to a problematic video driver.

/ Baudrate = Number This switch sets the baud rate for debug ports for kernel debugging. For example, you can enter

/ baudrate = 9600. When a modem is connected, the default baud rate is 9,600 kilobits per second (Kbps). When using a non-modulated demodulator cable, the default baud rate is 115,200 kbps. 9,600 is the normal rate of remote debugging through the modem. If the switch exists in the boot.ini file, automatically enable

/ Debug switch.

For additional information about the modem configuration, click the article number below to see the article in the Microsoft Knowledge Base:

148954 How to use a modem to set a remote debugging session

For additional information about non-modem connection configuration, click the article number below to see the article in the Microsoft Knowledge Base: 151981 How to use a non-modulated demodulator cable to establish a remote debugging session

/ CrashDebug This switch loads the kernel debugger when the operating system is started. The switch will remain inactive until a STOP message error occurs.

/ CrashdeBug Switch is very useful for processing random core errors. Use this switch to use a COM port as usual in Windows. When Windows fails, the switch will convert the port to the debug port. (This action will start remote debugging.)

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

151981 How to establish a remote debugging session using a non-modulated demodulator cable

/ debug This switch opens the kernel debugger when Windows is started. If you want to open a Windows system real-time remote debugging function via the COM port, the switch can be activated at any time by the host debugger connected to the computer. versus

/ Crashdebug switches are different,

/ debug will use a COM port regardless of whether it is debugging. This switch can be used when you debug regularly.

For additional information about remote debugging, click the following article number to see the article in the Microsoft Knowledge Base:

121543 Setting Remote Debugging

/ debugport = COMNUMBER This switch specifies the communication port used as the debug port, of which

Number is a communication port that wants to use, such as COM1. By default, such as the COM2 port exists,

/ Debugport will use the COM2 port. Otherwise, the switch will use COM1. If the switch is included in the boot.ini file,

The / debug switch will be activated.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

151981 How to establish a remote debugging session using a non-modulated demodulator cable

/ maxmem = Number This switch specifies the maximum RAM that Windows can use. Do not set this parameter below 12. This parameter can be used to verify that the memory chip has failed. For example, you have a 128 MB system with two 64 MB RAM modules. If you appear related to the STOP message, you can enter

/ MAXMEM = 64. If the computer is able to start Windows and operate normally, you can replace the first module to see if this problem can be solved.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

108393 MAXMEM option in Windows NT Boot.ini file

/ NOGUIBOOT This switch displays a bitmap of the progress bar when Windows starts. (The progress bar appears before the login prompt.)

/ Nodebug This switch off debug function. If there is a hardware debug break point in a program code, the program may cause a STOP error.

/ NumProc = Number This switch sets the number of processors used when Windows starts. With this switch, you can force a multiprocessor system to use only the specified quantity (

Number's processor. This switch can help you solve performance issues and problems with defective CPUs.

/ PCILock For X86-based systems, the switch prevents the operating system from dynamically assigning hardware input, hardware output, and interrupt request resources for the Peripheral Connect Interface (PCI) device. These devices will be configured by BIOS after using this switch.

/ FASTDETECT: COMNUMBER This switch will turn off the NTDetect.com file to the detection function of serial mouse and bus mouse on the specified port. This switch can be used if you connect components other than the mouse on the serial port during the startup process. For example, input / fastdetect: COMNUMBER, where

Number is a serial port number. A comma can be separated by multiple port numbers to close more than one port. If used

/ FASTDETECT but does not specify a communication port, the serial mouse detection function on all communication port will be turned off.

Note: In the early versions of Windows NT 4.0, the switch is named

/ NOSERIALMICE.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

131976 How to disable device detection on serial port

/ SOS

The / SOS switch displays its name when the device driver is loaded. By default, the Windows Loader screen shows only the progress point. You can use the switch to

The / basevideo switch is used with a driver that causes a fault.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

99743 Function of Boot.ini files in Windows 2000 or Windows NT

/ PAE Use the / PAE switch in Boot.ini and the corresponding entry to allow the computer that supports the physical address extension (PAE) mode to start normally. Under "Security Mode", even if the / PAE switch is specified, the computer is also started using the normal kernel.

/ HAL = filename uses this switch to define the hardware abstraction layer (HAL) actually loaded during the startup process. For example, enter

/Hal=halmps.dll Loads the halmps.dll in the System32 folder. This switch can be used to test a different HAL before renameting the file as HAL.DLL. In addition, the switch is also useful when you try to switch between multiproof mode starts and single processor mode startup. To this end, please turn the switch with

The / kernel switch is used together.

/ kernel = filename Using this switch, you can define the kernel actually loaded during the startup process. For example, enter

/kernel=ntkrnlmp.exe loads NTKRNLMP.EXE in the System32 folder. With this switch, you can switch between the kernel of the full load debug code that has enabled the debug function and the normal kernel.

/ bootLog This switch opens the launch logging function, start the log being recorded

SystemRoot / ntbtlog.txt file. For more information on starting logs, see Windows Help.

/ BurnMemory = Number This switch specifies the number of memory (in megabytes) that Windows cannot be used. This parameter can be used to determine performance issues or other issues related to RAM consumption. For example, enter

/ BurnMemory = 128 Reduces the physical memory available for Windows by 128 MB.

/ 3GB In the X86-based system, the switch enforces the user program to assign 3 GB of virtual address space to assign 1 GB virtual address space for the kernel and executable components. The user program must be able to take advantage of additional memory address spaces. With this switch, the user mode program can access 3 GB of memory instead of usually the 2 GB of memory that is typically allocated to the user mode program. The switch moves the lax position of the kernel to 3 GB. Some Microsoft Exchange Server 2003 and Microsoft Windows Server 2003 configuration may require the switch.

For additional information, click the article number below to see the article in the Microsoft Knowledge Base: 823440 You must use / 3GB parameters when installing Exchange Server 2003 in a Windows Server 2003-based system

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

171793 Information about 4GT RAM Tuning

/ SafeBoot: Parameter This switch enables Windows to start under "safe mode". This switch uses the following parameters:

• Minimal • Network • Safeboot: minimal (Alternateshell)

/ SafeBoot: Parameter parameter can be used in conjunction with other Boot.ini parameters. The following example gives the parameters actually used when selecting a different "Security Mode" option from the startup recovery menu.

• Safety mode with network connections / SafeBoot: Minimal / Sos / BootLog / NOGUIBOOT • Safety mode with network connections / Safeboot: Network / Sos / bootlog / NOGUIBOOT • Safety mode with command line prompts / SafeBoot: minimal (alternateshell) / SOS / Bootlog / NOGUIBOOT

note:

/ SOS,

/ bootlog and

The / NOGUIBOOT switch is not required in these settings, but plus these switches will help to troubleshoot. These switches will be adopted when you press the F8 key and select a mode.

/ Userva can use this switch to customize the amount of memory assigned to the process when using the / 3GB switch. This switch allows more page table entries (PTE) kernel memory while still retaining nearly 3 GB of process memory space.

For additional information on how to use the / userva switch, click the article number below to see the article in the Microsoft Knowledge Base:

316739 How to use the / userva switch in the Boot.ini file / 3GB configuration

For additional information, click the article number below to see the article in the Microsoft Knowledge Base:

810371 XADM: Used / Userva parameters on Exchange Servers based on Windows 2003 Server

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

317526 How to edit boot.ini files in Windows Server 2003

317521 bootcfg command and its usage

289022 How to edit boot.ini files in Windows XP

291980 bootcfg command and its use discussion

/ Redirect can use this switch to start emergency management services (EMS) on a computer based on Windows Server 2003 Enterprise Edition. For additional information about EMS, search for "Emergency Management Services" in Windows Help and Support.

To enable EMS by editing Boot.ini in x86-based computers, you need to edit the "[Boot Loader]" and "[Operating Systems]" section of the Boot.ini file. To do this, configure the following entry:

• In the [Boot Loader] section, add one of the following statements: redirect = COMX In this statement, use one of the following COM port numbers to replace x:

Redirect = UsebiSsettings This statement allows the BIOS of the computer to determine the COM port used by the EMS. • In the [Boot Loader] section, add the following optional statement: redirectbaudrate = baudRate replaces the BAUDRATE: 9600 with one of the following values: 9600

19200

57600

115200

By default, EMS uses 9600 kbps baud rate settings. • In the [Operating Systems] section, add / redirect options in the operating system entry you want to configure using the EMS. The following example demonstrates the use of these switches: [Boot Loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (1) / Windows

Redirect = COM1

RedirectBaudrate = 19200

[Operating Systems]

Multi (0) Disk (0) Rdisk (0) Partition (1) / Windows = "Windows Server 2003, Enterprise" / FastDetect

Multi (0) Disk (0) RDisk (0) Partition (1) / Windows = "Windows Server 2003, EMS" / FastDetect / Redirect

/ channel with

/ Debug switch and

The / debugport switch uses this switch to configure Windows to send debug information through Institute of Electrical and Electronics Engineers, Inc. (IEEE) 1394 port. To support debugging through 1394, the participating computers must run Microsoft Windows XP or higher. The 1394 port has a maximum of 63 independent communication channel numbers from 0 to 62. Different hardware implementation supports different number channels in a bus. There is still up to 4 target computers on Windows XP. But this limit has been canceled in Windows Server 2003. To perform a debugging, select a common channel number to use on a computer (ie, a host) that runs the debugger and the computer you need to debug (ie, the target computer). Any number from 1 to 62 can be used.

Configuring target computers

1. Edit the boot.ini file, add / channel = x option to the operating system entry of the configured debug function. Replace X with the channel number you want to use. For example, configure the "[Operating Systems]" section of the Boot.ini file into the following settings: [boot loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (1) / Windows

[Operating Systems]

Multi (0) DISK (0) PARTIN (1) / Windows = "Windows Server 2003, Enterprise" / FastDetect / Debug / debugport = 1394 / channel = 32. Insert 1394 cable into any 1394 port. 3. Disable 1394 main controllers on the target computer. To do this, open "Device Manager" and right-click the device and click Disable. 4. Restart your computer.

Configure the host

1. Insert the 1394 cable into any 1394 port. 2. Install the kernel debugger binary file. 3. Open a command prompt window. Enter each of the following command to press Enter.

SET_NT_DEBUG_BUS = 1394

SET_NT_DEBUG_1394_Channel = Xkd -k

4. Move to a folder installed with a kernel debugger, enter the following command:

Kd.exe

A 1394 virtual driver will be installed when the debugger is started for the first time. The driver allows the debugger to communicate with the target computer. To successfully install this driver, you must log in with administrator privileges.

The information in this article applies to:

• Microsoft Windows XP 64-Bit Edition • Microsoft Windows Server 2003 Enterprise Edition • Microsoft Windows Server 2003 Standard Edition • Microsoft Windows Server 2003 Web Edition • Microsoft Windows XP Professional Edition • Microsoft Windows XP Home Edition

Modify the boot.ini file

Riann Ba? EZ from Los Angeles City, California

Windows XP mainly depends primarily on the Boot.ini file to determine the computer category that the computer is displayed during the restart (boot) process. Boot.ini is set to implicit and system file properties in the default state, and is identified as read-only files.

Do you have continuously modified Boot.ini files? To ensure that the Folder Options (Folder Item) is enabled in Windows Explorer and selects the cost of the show hidden files and folders on the View menu. Do you feel tired? What's more, have you forgotten the read-only properties that you have before you edit the document?

You can perform editing operations with the command line tool bootcfg.exe for the Boot.ini file. You can modify the system waiting time (Windows waiting for the time waiting for the default operating system) and add a new option on the existing basis.

To start the bootcfg.exe tool, do the following steps:

Click Start and Run and enter the CMD in the RUN dialog. Enter bootcfg.exe in the command line state. Execute the bootcfg.exe / "command to view the relevant parameters.

Safety mode launch switch for Windows Boot.ini files

summary

Windows has a safe mode startup feature. To use this feature, press the F8 key during startup, then select the security mode startup method you want to use. You can also use some switches to provide any of the modes in the boot.ini file. This may be required when you often use some startup mode or need to make a process automatically.

More information

Safety mode startup methods and corresponding switches include:

• Mode: Security Mode Switch: / SafeBoot: Minimal / Sos / BootLog / NOGUIBOOT • Mode: Security Mode Switch with Network Connection: / SafeBoot: Network / Sos / BootLog / NOGUIBOOT • Mode: Security Mode Switch with Command Row Tips: / saveboot: minimal (alternateshell) / SOS / BootLog / NOGUIBOOT • Mode: Enable startup log switch: / bootLog • Mode: Enable VGA mode switch: / basevideo • Mode: Directory Service Recovery mode (for domain controller) Switch: / saFeboot: DSREPAIR / SOS • Mode: Debug mode switch: / debug Sets an example boot.ini file for the "Safety Mode" switch for network connection

[boot loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (1) / Winnt

[Operating Systems]

Multi (0) disc (0) RDisk (0) Partition (1) / Winnt = "Microsoft Windows 2000 Advanced Server" / FastDetect / Safeboot: Minimal (Alternateshell)

Remarks: / SOS / BootLog / NOGUIBOOT switch is not required for any settings, but they can be used to troubleshoot. If you press the F8 key and select one of the modes, these switches are included.

The information in this article applies to:

• Microsoft Windows 2000 Enterprise Edition • Microsoft Windows 2000 Enterprise Edition • Microsoft Windows 2000 PROFESSIONAL Edition • Microsoft Windows 2000 Enterprise Edition

How to use the / userva switch Optimization / 3GB configuration in the boot.ini file

This article discusses a test version of Microsoft products. The information in this article is provided as it is provided, if there is any change, no notice.

Microsoft does not provide formal product support for this beta product. For information on how to get the beta support, see the document included in the beta product file, or view the Web location downloaded this version.

This page

Summary More Information

summary

In the Windows Server 2003 series, you can use

/ Userva = xxxx switch more accurately optimizes user and kernel virtual memory space. In the boot.ini file, this new switch is

/ 3GB switch is used together, you can optimize the size of the user mode space to 2 GB (Gigabit) to 3 GB, difference (3,072 minus)

XXXX) Restores as kernel mode. note,

XXXX is in a megabyte (MB).

The following example boot.ini file explains how to use this new switch to optimize your computer, assign 2,900 MB space for user mode virtual memory, assign 1,196 MB space for kernel mode virtual memory. This increases the available kernel space by 172 MB:

[Boot loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (2) / WinNT

[Operating Systems]

Multi (0) Disk (0) RDisk (0) Partition (2) / Winnt = "Microsoft Windows.net Server" / FastDetect / 3GB / Userva = 2900 More information

/ userva = xxxx switch aims to make user mode space required for 2 GB but not

The program manufacturer of all space provided by the / 3GB switch can more accurately optimize the user mode address space. (Note that only use

The / 3GB switch will assign 1 GB to the kernel mode space to assign 3 GB to the user mode space. ) By reducing usually

/ 3GB switch allocated user mode space, Windows adds the available core memory address space. This additional kernel mode address space will be retained and used as the additional address space of the PTE when the system's page table item (PTE) is insufficient. This address space is assigned to the PTE until the system's PTE space is insufficient.

In order to ensure the stability of the program and the stability of Windows, the program manufacturer must use the above optimization method to fully test the program and must provide programs.

/ Userva = xxxx number. To facilitate testing, manufacturers can use the System Monitor tool to monitor the use of virtual addresses. To do this, "Virtual Ball" counters should be added to enable the program's process to get accurate virtual space reading.

Remarks: Microsoft Product Support Services (PSS) does not support any

/ Userva settings; customers can only add this setting to the boot.ini file according to the manufacturer's recommendation.

For additional information about / 3GB switches, click the article number below to see the article in the Microsoft Knowledge Base:

171793 Information ON Application Use of 4gt Ram Tuning (information about the actual 4GT RAM optimization)

189293 Enabling 4GT Ram Tuning When You Use Windows NT Server Enterprise Edition (Enable 4GT RAM Optimization when using Windows NT Server Enterprise Edition)

On a computer with a large amount of memory, Windows Server 2003 no longer limits the system pane pool to 160 MB. Because the paging pool is not limited, when the computer

The / 3GB switch runs, you may be able to release the additional kernel mode address space by limiting the size of the system paging pool to use as the PTE space.

The information in this article applies to:

• Microsoft Windows Server 2003 Enterprise Edition • Microsoft Windows Server 2003 Datacenter Edition • Microsoft Windows Server 2003, Standard Edition

Boot.ini and ARC path naming agreement and usage

summary

This article explains the Advanced RISC Calculation (ARC) specification for defining an agreement based on the Intel X86 processor and the Windows NT installation path on a RISC-based computer. This article includes the following sections:

• Comparison of X86-based ARC paths and RISC-based ARC paths • Multi (x) and SCSI (X) syntax and applications • X86-based ARC path and RISC-based ARC path example

Based on X86's ARC path and RISC-based ARC path comparison for X86-based computers, use a line in the Boot.ini file to explain the path to each Windows NT installation; however, for RISC-based computers, you need to firmware The start options use four rows to point to a single Windows NT installation. If there are multiple Windows NT installations on the X86-based computer, there is an ARC path for each installation, Boot.ini. In the startup process, a startup menu prompt will be displayed for you to select the installation you want to start. The ARC path is displayed in two basic forms: a form is to begin with a MULTI (), and the other is to start with SCSI (). On the X86-based computer, use these two forms; but on the RISC computer, only SCSI () forms are used:

The X86-based computer is below two ordinary examples, which represent the possible boot.ini ARC path, respectively:

Multi (x) disk (y) rdisk (z) partition (w) /

- or -

SCSI (X) Disk (Y) RDisk (z) Partition (W) /

Where, x, y, z, and w are numbers identifying their left items.

Using the above two Arc path examples, Windows NT can find% systemroot% directory to complete the startup process by loading files residing in this directory. For additional information, see the "Difference between Multi (X) and SCSI (X) syntax and application" section below.

Based on RISC-based computers require firmware to point to different regions of the system based on RISC, the ARC path installed by a single Windows NT installation consists of four definitions containing ARC paths (with this, on the X86-based computer, ARC Path definitions only contain one line). Each ARC path behind each of these four definitions is started with SCSI () followed by the definition name:

SystemPartition SCSI (X) Disk (Y) RDisk (z) partition (w)

Osloader SCSI (X) Disk (Y) RDisk (z) Partition (w) / OS / / OSLOADER.EXE

OsloadPartition SCSI (X) Disk (Y) RDisk (z) partition (w)

OsloadFileName /

The following will explain the various rows in the above four-line definition groups.

Definition 1 (SystemPartition):

Define SystemPartition (it is the path to the small file allocation table (FAT) partition stored by Osloader.exe and Hal.exe:

SCSI (X) Disk (Y) Rdisk (z) partition (w)

Definition 2 (Oslineer):

Define the path to the OSLoader file. It is the same as systemPartition, but it contains a path descriptor:

SCSI (X) Disk (Y) RDisk (z) Partition (W) / OS / / OSLOADER.EXE

Where indicates the directory where Osloader.exe is located.

Definition 3 (OsloadPartition):

Define the startup partition containing the rest of the Windows NT system file:

SCSI (X) Disk (Y) Rdisk (z) partition (w)

Definition 4: Defines the name of the Windows NT installation directory (WinNT_Dir) (without your belt):

The difference between MULTI (X) and SCSI (X) syntax and applications

MULTI (X) Syntax Multi (X) syntax forms of ARC paths are only used on X86-based computers. In Windows NT 3.1, this path is only valid for IDE and ESDI drives; in Windows NT versions 3.5, 3.51, and 4.0, it is valid for the SCSI drive.

Multi () syntax indicates to Windows NT It should rely on computer BIOS to load system files. This means that the operating system will use the Interrupt (int) 13 BIOS call to find and load NToskrnl.exe and to start any other files required to start Windows NT.

Parameters X, Y, Z and W have the following meaning:

• x is the serial number of the adapter and should always be 0 (for reasons, see below). • If the ARC path begins with a MULTI (), Y always is 0 (zero) because MULTI () requests INT 13 call as described above, and thus does not require Disk () parameter information. • Z is the serial number of the disk on the adapter and is usually between 0 and 3. • W is the partition number. All partitions have a number except the type 5 (MS-DOS Extension Partition) and Type 0 (unused) partition, and first is the main partition number, and then the logical drive number. Note: The first valid number of W is 1; with this, X, Y, and Z start with 0 (zero). In theory, you can use this syntax to start Windows NT on any drive in the system. However, this needs to be correctly identified all drives through standard INT 13 interface; because the support of this is different from the disk controller, most system BIOS only identifies a single disk controller through int 13, so only the following How to use is safe: Start Windows NT from the first two drives connected to the main drive controller, or, if the primary disk controller is a dual channel EIDE controller, then from the connected to the main drive controller. Windows NT is started in the first four drives.

In the pure IDE system, the MULTI () syntax will work with up to four drives on the main channel of the dual-channel controller and the auxiliary channel.

In the pure SCSI system, the MULTI () syntax will work on the first SCSI controller (that is, the controller of the BIOS first loaded).

In the SCSI and IDE hybrid systems, the MULTI () syntax will only work on the IDE drive on the first controller.

SCSI (X) Syntax SCSI () syntax applies to RISC-based computers and X86-based computers, and applies to all versions of Windows NT. Using the SCSI () symbol indicates that Windows NT will load a boot device driver and use the driver to access the startup partition.

On the x86-based computer, the device driver used is NTBootdd.sys, which is located in the root directory of the system drive (typically drive C), and is a copy of the device driver of the drive controller used.

On the RISC computer, in accordance with the RISC specification, place the driver in the firmware, so no files are required.

When using the SCSI () syntax, parameters x, y, z, and w have the following meanings: • X is the adapter serial number identified by the NTBootdd.sys driver. • Y is the SCSI ID of the target disk. • Z is the SCSI logic unit number (LUN) of the target disk. This number is almost 0 (zero). • W is the partition number. All partitions have a number except the type 5 (MS-DOS Extension Partition) and Type 0 (unused) partition, and first is the main partition number, and then the logical drive number. Note: The first effective number of W is 1; with this, X, Y and Z start from 0. When using the SCSI () symbol, the value of X depends on NTBootdd.sys. Each SCSI driver under Windows NT has its own controller number, although they generally follow the BIOS's loading order on the controller (provided BIOS loaded).

Also, if you have multiple controllers that use different device drivers, you should only consider those controllers controlled by ntbootdd.sys when they determine the value of the X parameter. For example, if you have an Adaptec 2940 controller (which uses driver AIC78XX.sys) and an Adaptec 1542 controller (it uses AHA154X.sys), X will always be 0. The ntbootdd.sys file will be changed:

• If you load Windows NT from the drive on the ADAPTEC 2940, ntbootdd.sys will be a copy of AIC78xx.sys. • If you load Windows NT from the drive on the ADAPTEC 1542, ntbootdd.sys will be a copy of AHA154X.SYS.

An example of a valid ARC path based on the ARC path based on X86 and RISC. The first two examples are the ARC path based on the x86. Example 3 A single start-up entry is taken from the computer based on DEC ALPHA AXP 150 RISC, but it should be correct for all RISC-based computers with similar drive configurations.

Note: If you have multiple ARC paths in the boot.ini file as shown below, you have multiple different SCSI adapters in your computer, you must first put the corresponding SCSI driver first. Copy the ntbootdd.sys file in the root directory of the system partition (typically drive C), and then shut down to start from the Windows NT installation that resides on the drive connected to other SCSI controllers. This is because NTBootdd.sys always resides on the system partitions no matter which drive remains in another Windows NT installation.

Example 1: Multiple SCSI controllers This is an example of X86-based computers installed with the following drives and controllers:

• Two Adaptec 2940 SCSI controllers, each with two 1 GB hard drive, located in ID 0 and 1, respectively. • A Adaptec 1542 SCSI disk controller with two 1 GB hard drive, located in ID 0 and 4, respectively. Each hard drive has a primary partition that is 1 GB. To better explain the example, these partitions are numbered from 1 to 6, wherein the partitions 1 and 2 identify the disk 1 and 2 connected to the Adaptec 2940 controller, the partitions 3, and 4 identifiers are connected to the second Adaptec 2940 controller. Disks, partitions 5 and 6 are located on disk connected to Adaptec 1542. A path in the following ARC path will appear in Boot.ini according to the partition you use to install Windows NT. This example assumes that Windows NT is installed in a directory called Winnt35: WINDOWS NT installed in the corresponding ARC path.

Partition 1 (located on the first Adaptec 2940) Multi (0) Disk (0) Rdisk (0) Partition (1) / WinNT35

Partition 2 (on the first Adaptec 2940) Multi (0) Disk (0) RDisk (1) Partition (1) / WinNT35

Partition 3 (located on the second Adaptec 2940) SCSI (1) Disk (0) RDisk (0) Partition (1) / WinNT35

Partition 4 (located on the second Adaptec 2940) SCSI (1) Disk (1) Rdisk (0) Partition (1) / WinNT35

Partition 5 (on Adaptec 1542) SCSI (0) Disk (0) RDisk (0) Partition (1) / WinNT35

Partition 6 (on Adaptec 1542) SCSI (0) Disk (4) Rdisk (0) Partition (1) / WinNT35

Remarks: For partitions 3 and 4, ntbootdd.sys is a copy of AIC78xx.sys; for partitions 5 and 6, ntbootdd.sys is a copy of AHA154X.sys. If your NTBootdd.sys file is a copy of the AIC78xx.sys driver, you can use the following paths to replace the Arc paths of the partitions 1 and 2:

WINDOWS NT installed in the corresponding ARC path

Partition 1 (on the first Adaptec 294) SCSI (0) Disk (0) RDisk (0) Partition (1) / Winnt35

Partition 2 (located on the first Adaptec 294) SCSI (0) Disk (1) RDisk (0) Partition (1) / WinNT35

However, the Windows NT installer always uses the multi () syntax for this one drive.

Example 2: Mixed IDE and SCSI Environment This is an example in which the following drives and controllers are installed, and X86-based computers:

• A dual channel EIDE controller with three sizes of 1 GB of drivers, where two drives are located on the main channel and another drive is located on the auxiliary channel. • An Adaptec 2940 SCSI controller, only a hard drive having a size of 4 GB only in ID 3. Each of these three EIDE drivers has a partition size of 1 GB, while the SCSI drive has four partitions that are 1 GB. To better explain the present example, these partitions are numbered from 1 to 7, wherein the partitions 1 and 2 identify the magnetic disk 1 and 2 on the main passage of the EIDE controller, and the partition 3 is located on the second channel, partition 4, 5 6 and 7 are located on the SCSI drive. Depending on the partition you use to install Windows NT, one of the following ARC paths will appear in Boot.ini. This example assumes that Windows NT is installed in a directory called Winnt35: WINDOWS NT installed in the corresponding ARC path.

Partition 1 (Main EIDE Channel) Multi (0) Disk (0) RDisk (0) Partition (1) / Winnt35

Partition 2 (Main EIDE Channel) Multi (0) Disk (0) Rdisk (1) Partition (1) / Winnt35

Partition 3 (Auxiliary EIDE Channel) Multi (0) Disk (0) RDisk (2) Partition (1) / WinNT35

Partition 4 (on Adaptec 2940) SCSI (0) Disk (3) RDisk (0) Partition (1) / Winnt35

Partition 5 (on Adaptec 2940) SCSI (0) Disk (3) Rdisk (0) Partition (2) / WinNT35

Partition 6 (on Adaptec 294) SCSI (0) Disk (3) RDisk (0) Partition (3) / Winnt35

Partition 7 (on Adaptec 2940) SCSI (0) Disk (3) RDisk (0) Partition (4) / Winnt35

Note: Loading Windows NT from partitions 4 to 7 requires NTBootdd.sys files are a copy of AIC78xx.sys.

Example 3: The startup variable on the DEC Alpha Ax 10 is on the RISC computer, defines all startup paths through the firmware. When you create a new startup entry for the RISC computer, the firmware will provide you with a range of prompts to help you correctly define the path; therefore, you will never have to be directly available unless you are editing the startup entry that no longer works. Edit the ARC path on the RISC computer.

The following example is the startup entry on the DEC Alpha Axp 150, which has a single hard drive, which is located in ID 0 and is partitioned as follows:

• A system partition with a size of 4 MB. • A startup partition with a size of 396 MB. Windows NT is installed in the directory named WINNT35 on the startup partition; the name of the OSLoader directory is also OS / WinNT35, but it is located on the system partition. The start-up entry has the following values:

SystemPartition SCSI (0) Disk (0) RDisk (0) Partition (1)

Osloader SCSI (0) Disk (0) RDisk (0) Partition (1) /OS/winnt35/osphoter.exe

OsloadPartition SCSI (0) Disk (0) RDisk (0) Partition (2)

OsloadFileName / WinNT35

The information in this article applies to: • Microsoft Windows NT Advanced Server 3.1 • Microsoft Windows NT Server 3.5 • Microsoft Windows NT Server 3.51 • Microsoft Windows NT Server 4.0 Enterprise Edition • Microsoft Windows NT Workstation 3.1 • Microsoft Windows NT Workstation 3.5 • Microsoft Windows NT Workstation 3.51 • Microsoft Windows NT Workstation 4.0 Developer Edition • Microsoft Windows NT Advanced Server 3.1

Lost from the startup menu in a multi-launch computer

symptom

After installing Windows XP on a multi-started computer, one of the installed operating systems may be lost from the boot menu and the boot.ini file (the file is the source of the startup menu). The result is caused to be unable to start the operating system.

Windows XP, Microsoft Windows 2000, or Microsoft Windows Millennium (ME), Microsoft Windows Millennium (ME), Microsoft Windows 95, or Microsoft Windows 95 is also installed on the computer.

solution

To resolve this issue, use one of the following methods to add a lost operating system to the startup menu:

• Use the bootcfg / review command in the failed recovery console. • Edit the boot.ini file manually.

Use the bootcfg / recuild command in the fault recovery console

Note: If the hard disk does not have enough free space to install the fault recovery console, or if you do not want to install the fault recovery console, the startup order in the computer BIOS is set to include the installation CD function, you can start Load the fault recovery console when a computer. Insert a Windows XP installation disc in a CD-ROM or DVD-ROM drive, and then press the R key in the Welcome Setup screen. For additional information about using the Windows XP failure recovery console, click the article number below to see the article in the Microsoft Knowledge Base:

314058 Description of Windows XP Fault Recovery Console

307654 How To: Fault Recovery Console for Installing and Using Windows XP

For additional information about the bootcfg command, click the article number below to see the article in the Microsoft Knowledge Base:

291980 bootcfg command and its use discussion

The following steps assume that the computer has the following settings, and Windows XP is the operating system that is lost from the startup menu and the boot.ini file:

• Windows ME is installed on the first (main) partition. • Windows 2000 Advanced Server is installed on the logical drive on the second (extension) partition. • Windows XP is installed on another (main) partition.

1. Log in into the Windows 2000 Advanced Server on your computer as an administrator. 2. Click Start, click Run, type the following command (where e represents the drive letter of the CD-ROM or DVD-ROM drive), then press ENTER:

E: / i386 / winnt32 / cmdcons

3. Restart your computer. When the startup menu appears, select the Microsoft Windows Fault Recovery Console. 4. Select Option 1 to log in to the installed Windows 2000 Advanced Server. 5. If you do not enable an administrator password to log in, type the administrator password. 6. Type the command below, press Enter: Bootcfg / Rebuild

The following information will appear: Total Identified Windows Installs: 2

[1]: D: / WinNT

Add Install to Boot List (YES / NO / ALL)

Choose "Y" (ENTER)

ENTER load IDENTIFIER: TYPE "Microsoft XP"

ENTER OS LOAD OPTIONS: TYPE "/ fastdect"

[2]: f: / windows

Add Installation to Boot List? (YES / NO / ALL) Choose "N"

(Optional) To view the boot.ini file and verify that an entry is added correctly to the startup menu, type the following command, then press Enter:

Type boot.ini

The following example shows the appearance of the boot.ini file before running the bootcfg / rebuild command: [boot loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (2) / WinNT

[Operating Systems]

Multi (0) Disk (0) rdisk (0) Partition (2) / Winnt = "Microsoft Windows 2000 Advanced Server" / FastDetect

C: / = "Microsoft Windows"

The following example shows the picture of the boot.ini file after running the bootcfg / rebuild command: [boot loader]

TIMEOUT = 30

DEFAULT = MULTI (0) Disk (0) RDisk (0) Partition (3) / WinNT

[Operating Systems]

Multi (0) Disk (0) rdisk (0) Partition (3) / Winnt = "Microsoft Windows 2000 Advanced Server" / FastDetect

Multi (0) Disk (0) RDisk (0) Partition (2) / Windows = "Microsoft Windows XP Professional" / FastDetect

C: /cmdcons/bootsect.dat= "Microsoft Windows Recovery Console" / cmdcons

C: / = "Microsoft Windows"

Note that the Advanced RISC Computing Specification (ARC) path now includes Windows XP and Fault Recovery Console. 7. Type an exit exit The fault recovery console. The computer will automatically restart and display the updated startup menu:

Microsoft Windows XP Professional

Microsoft Windows 2000 Advanced Server

Microsoft Windows Fault Recovery Console

Microsoft Windows

The default operating system is now the entry you just added ("Microsoft Windows XP Professional") is now available. 8. (Optional) You can specify the default startup operating system in the multi-boot computer by using the System and Fault Recovery settings. Follow these steps: a. Right-click on my computer, then click Properties, or launch the Control Panel, start the Performance and Maintenance tool, and then click System. b. On the Advanced tab, click Settings under Startup and Fault Recovery. c. Select the default operating system from the drop-down menu under the system startup. This operating system will list the first list on the startup menu and is an operating system that the computer starts after the timeout expires.

Manually edit the boot.ini file If you are unable to access the failed recovery console, you can edit the boot.ini file manually, according to the first section of this article, perform the same changes. Specifically, you must provide an ARC path to specify the operating system that is lost from the startup menu. For additional information about the ARC path, click the article number below to see the article in the Microsoft Knowledge Base:

102873 Boot.ini and ARC path naming agreement and usage

For additional information about editing a boot.ini file in Windows XP, click the article number below to see the article in the Microsoft Knowledge Base:

289022 How to: Edit boot.ini files in Windows XP

status

Microsoft has confirmed that this is a problem in Microsoft products listed in this article.

More information

Bootcfg.exe is a fault recovery console utility that can fix or rebuild the Boot.ini file, but it does not detect Windows 95 or Windows 98 operating systems.

For additional information about Boot.ini files, fault recovery console, and related issues, click the article number below to see the article in the Microsoft Knowledge Base:

314081 The role of the boot.ini file in Windows XP

170756 Available Switch Options for Windows NT Boot.ini File

227704 Windows may use Signature () syntax in the boot.ini file

234048 How Windows 2000 Assigns, RESERVES, AND Stores Drive Letters

229077 Mirroring Prevents Pre-Installing The Recovery Console

The information in this article applies to:

• Microsoft Windows XP Home Edition • Microsoft Windows XP Professional Edition

Create a boot disk for NTFS or FAT partitions

summary

This article describes how to create a Windows boot disk on a computer based on the Intel X86 processor to access the launch order.

Remarks: The steps based on RISC-based computer are different, and this article does not introduce.

The Windows boot disk can access a drive installed with a Windows NT File System (NTFS) or File Allocation Table (FAT) file system. The process in this article is useful for solving the following startup problems:

• The start sector is corrupted. • The main start record (MBR) is corrupt. •virus infection. • Lost or damage NTLDR or NTDetect.com. • NTBootdd.sys driver is incorrect. • The boot disk can also be used to start from image captured image, although this may need to change the Boot.ini file. The Windows boot disk cannot be used to solve the following questions:

• The device driver already installed in the Windows system directory is not correct or corrupted. • The startup problem that occurs after the OsLoader screen. To resolve or fix these issues, run an emergency repair disk, load the last correct control set, or reinstall Windows if necessary. How to create a Windows boot disk Windows floppy disk must include file NTLDR (setupldr.bin in Windows NT 3.5), NTDetect.com, Boot.ini, and hard drives.

Note: NTLDR, NTDETECT.COM and BOOT.INI file file properties are usually set to "System", "Hide" and "Read". You don't need to reset these properties that the disk will work properly. For additional information about the Boot.ini file structure, click the article number below to view the article in the Microsoft Knowledge Base:

102873 Boot.ini and arc path naming convention and usage (Boot.ini and ARC path naming conventions and usage)

To create a Windows boot disk, use one of the following methods:

Method 1: If you cannot access a computer running Windows

1. Use the diskcopy command to create a copy of the Windows first installation disk, then delete all the files on the new disk. 2. Copy the NTDetect.com and NTLDR files from the I386 folder on the CD-ROM to the new disk. 3. Rename the NTLDR file as "setupldr.bin". 4. Create a boot.ini file. The following example is applicable to the single-partition SCSI drive that is installed under / Winnt; however, the exact value in the [Operating Systems] section depends on the configuration of the Windows system to be started:

[boot loader]

TIMEOUT = 30

DEFAULT = SCSI (0) Disk (0) RDisk (0) Partition (1) / WinNT

[Operating Systems]

SCSI (0) Disk (0) rdisk (0) Partition (1) / Winnt = "Windows NT"

If the computer is started from the IDE, EIDE, and ESDI hard drives or SCSI adapters that do not have a built-in BIOS, use MULTI (0) to replace SCSI (0). Note: If you run Windows NT 3.5 or 3.51, and the system is started from the first or second SCSI drive, SCSI (0) can also be replaced with MULTI (0). 5. If you use SCSI (X) in Boot.ini, copy the correct device driver of the SCSI controller that is being used on your computer, and rename it ntbootdd.sys. If you use Multi (x) in Boot.ini, you don't have to do this. 6. Start your computer with this floppy disk and log in to Windows.

Method 2: If you can access a computer running Windows

1. Format a floppy disk with a format tool for Windows. 2. From the Windows Installation CD, Windows Install the floppy disk or copy NTLDR from the computer that is running the same Windows version with the computer that is accessible with the boot disk. You may need to expand this file from NTLDR._ by using the following command line to NTLDR:

Expand NTLDR._ NTLDR

3. Copy the NTDetect.com file to the disk. 4. Create a Boot.ini file or copy the file from the computer that is running Windows, and then modifies it to match the computer attempted. The following example applies to the uniform SCSI drive that is installed under / Winnt, but the exact value in the [Operating Systems] section depends on the configuration of the Windows computer that is trying to access: [Boot loader]

TIMEOUT = 30

DEFAULT = SCSI (0) Disk (0) RDisk (0) Partition (1) / WinNT

[Operating Systems]

SCSI (0) Disk (0) rdisk (0) Partition (1) / Winnt = "Windows NT"

If your computer starts from the IDE, EIDE or ESDI hard drive, replace SCSI (0) with MULTI (0). Note: If you run Windows NT 3.5 or 3.51, and the computer starts from the first or second SCSI drive, SCSI (0) can also be replaced with MULTI (0). 5. If you use SCSI (X) in Boot.ini, copy the correct device driver of the SCSI controller that is being used on your computer, and rename it ntbootdd.sys. If you use Multi (x) in Boot.ini, you don't have to do this. 6. Start using the floppy disk and log in to Windows.

Method 3: If there is a Windows NT version 3.51

1. In Windows NT 3.51, an empty 3.5 "1.44MB floppy disk. 2. Copy NTDetect.com and NTLDR to the new disk. 3. Create a boot.ini file with the following command line: Note: Examples apply to a single partition SCSI drive to install Windows NT in the default directory C: / WinNT35.

[boot loader]

TIMEOUT = 30

Default = MULTI (0) Disk (0) RDisk (0) Partition (1) / WinNT35

[Operating Systems]

Multi (0) Disk (0) rdisk (0) Partition (1) / WinNT35 = "Windows NT 3.51"

4. Start and log in to Windows from the floppy disk.

Troubleshooting When you try to start your computer with a Windows boot disk, you may have the following and multiple questions:

• If the path to the system file is not correct or includes the drive number, you may receive the following error message:

Windows could not start because of the following ARC firmware boot configuration problem: Did not properly generate ARC name for HAL and system paths.Please check the Windows (TM) documentation about ARC configuration options and your hardware reference manuals for additional information.Boot Failed.

• If you select an error, the SCSI driver or ntbootdd.sys file does not exist, you may receive the following error message:

Windows could not start because of a computer disk hardware configuration problem.Could not read from selected boot disk.Check boot path and disk hardware.Please check the Windows (TM) documentation about hardware disk configuration and your hardware disk configuration and your hardware reference manuals For additional information.boot failed. This article is available:

• Microsoft Windows XP Home Edition • Microsoft Windows XP Professional Edition • Microsoft Windows XP 64-Bit Edition

Error Message: Due to the problem of computer disk hardware configuration, Windows cannot start

symptom

When trying to start Windows XP, one of the following error messages may be received:

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.

Please check The Windows Documentation About Hardware Disk Configuration And Your Hardware Reference Manuals for Additional Information.

- or -

Windows Nt Could Not Start Because The Following File is Missing or Corrupt:

Winnt_root / system32 / ntoskrnl.exe

Please re-install a copy of the above file.

- or -

Winnt_Root / System32 / Hal.dll Missing or Corrupt:

Please re-install a copy of the above file.

In addition, you may also encounter one or more questions:

• If you start your computer to the fault recovery console, you may display a command prompt, which does not contain options to log in to the Windows installation. • If you try to access the Windows folder, you may receive the following error message:

Access denied.

• If you try to perform a "repair" operation from the Windows XP CD-ROM, the system will not detect Windows installation, so Windows cannot be fixed.

the reason

This may happen when any or certain conditions:

• The default value in the [Boot Loader] section of the Boot.ini file is lost or invalid. • Windows XP is not installed in the location specified in the boot.ini file. • NTOSKRNL.EXE file is lost or corrupted. • The partition path setting in the Boot.ini file is incorrect. • General hardware failure.

solution

To resolve this issue, use any of the following methods.

Method 1 Edit the boot.ini file to recover or correct

The DEFAULT item and make sure that other items in the [Operating Systems] section of the Boot.ini file points to the correct directory.

For additional information about how to edit the boot.ini file, click the article number below to see the article in the Microsoft Knowledge Base: 289022 How to: Edit Boot.ini files in Windows XP

Method 2 Use the Bootcfg utility in the fault recovery console corrected boot.ini files:

1. Start your computer using the Windows XP CD-ROM. 2. When receiving the R key to repair Windows messages using the fault recovery console, press the R key. 3. Select the desired Windows installation and type the administrator password after the prompt appears. 4. Type Bootcfg / Rebuild and press Enter. 5. After finding the Windows installation, the following instructions will be displayed:

"Add Installation to Boot List? (Yes / No / ALL)"

Type

Y responded to this message. ]

ENTER load IDENTIFIER:

This is the name of the operating system. Type

Windows XP PROFESSIONAL or

Windows XP Home Edition. ]

ENTER OS LOAD OPTIONS:

[Keep this field as empty, then press Enter].

After performing the above steps, restart your computer and select the first item in the boot menu. This should be able to start Windows XP normally. After successfully loading Windows XP, you can modify boot.ini to delete incorrect items. For additional information about how to edit the Boot.ini file, click the article number below to see the article in the Microsoft Knowledge Base:

289022 How to: Edit boot.ini files in Windows XP

Method 3

1. Start your computer using the Windows XP CD-ROM. Press any key from the CD boot. 2. After loading the installation file, press the R key to use the failed recovery console to repair. 3. In the failed recovery console, select the installation to log in (usually its number 1), then press Enter. 4. Log in to the administrator account by typing the password of the administrator account and press ENTER. 5. Under the command prompt of the failed recovery console, type the following command, then press ENTER: For a single processor system:

Expand CD-ROM: /i386/ntoskrnl.ex_ drive: / windows / system32

For multiprocessor systems:

Expand CD-ROM: /I386/NTKRNLMP.EX_ drive: /Windows/system32/ntoskrnl.exe

The CD-ROM is the drive letter of the CD-ROM drive, the drive is a drive letter for the hard disk of the Windows. 6. If you receive a prompt to overwrite this file, press Y. 7. Type EXIT and press Enter to the Command Prompt.

Method 4 Start the computer using the fault recovery console, then run

Chkdsk / r command.

Note: You don't have to include in the Chkdsk command line

/ p switch, because

The / r switch will enable the Chkdsk utility to find a bad sector and restore readable information. This command is implicit

/ P switch.

More information

If the box of the Boot.ini file is in the [Boot Loader] section

The default value is lost, and Windows XP will display a new item "Windows" in the OS Loader menu and then default to this new item. "Windows" item points to the following path to load Windows XP:

Multi (0) Disk (0) RDisk (0) Partition (1) / Windows

For additional information about the Boot.ini file, click the article number below to see the article in the Microsoft Knowledge Base:

102873 Boot.ini and ARC path naming agreement and usage

For additional information about the failure recovery console in Windows XP, click the article number below to see the article in the Microsoft Knowledge Base:

307654 HOW TO: Install and use Windows XP Recovery Console

The information in this article applies to:

• Microsoft Windows XP 64-Bit Edition • Microsoft Windows XP Professional Edition • Microsoft Windows XP Home Edition

How to create a boot disk for NTFS or FAT partitions

summary

This article describes how to create a Windows boot disk on an Intel-based computer to access the launch order.

Note: For RISC-based computers, this process is different, this article does not introduce.

More information

You can start the operating system using the Windows boot disk to run on a computer running Windows NT or Windows 2000. Use the procedure in this article to resolve the following startup issues:

• Start sector corruption • Main start recording (MBR) corruption • Virus infection • NTLDR or NTDETECT.COM file Loss or corruption • NTBootdd.sys driver incorrect • Start from damage to the image, please note, do this, You may have to modify the Boot.ini file. Please also note that you can't use the Windows Emergency Repair Disk (ERD) to help solve the following questions:

• The device driver installed in the system folder is not correct or corrupted. • The startup problem occurred after the Windows startup (OSLoader) screen appears. To resolve or fix these issues, run ERD, load the last correct control set, or reinstall Windows.

How to create a Windows boot disk The Windows boot disk must include NTLDR (setupldr.bin in Windows NT 3.5), NTDetect.com and Boot.ini files, and may require NTBootdd.sys (hard disk controller device driver) to rename For ntbootdd.sys.

Note: NTLDR, NTDETECT.COM, and the properties of the Boot.ini file are usually set to the system, hide, or read only. You don't have to reset these properties, you can run the boot disk. For additional information about the Boot.ini file structure, click the article number below to see the corresponding article in the Microsoft Knowledge Base:

102873 boot.ini and arc path naming convention and usage

To create a Windows boot floppy disk, use one of the following methods.

If you don't have access to a computer running Windows

1. Create a copy of the first Windows installation disk using the diskcopy command. To do this, you need:

a. Click Start, and then click Shut. b. Click "Restart your computer and switch to MS-DOS mode", then click Yes. c. On the command prompt, type the following command, where is a drive containing a Windows mounting disk, is a drive that contains a blank floppy disk to be used as a Windows boot disk:

转载请注明原文地址:https://www.9cbs.com/read-94476.html

9cbs

New Post(0)