This article leads from the Microsoft Knowledge Base (slightly Typography): http://support.microsoft.com/default.aspx? Scid = kb; zh-cn; 833721
Most of the switch options should be used on Windows2000, not testing, interested, you can try it.
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 use the switch with the / SOS switch. 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 the debug port 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, the / debug switch is automatically enabled.
/ 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.)
/ 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. Unlike / crashdebug switches, / debug will use COM ports regardless of whether it is debugging. This switch can be used when you debug regularly.
/ debugport = COMNUMBER
This switch specifies the communication port used as the debug port, where Number is a communication port you want 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.
/ 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 memory, 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.
/ NOGUIBOOT
This switch displays a bitmap of the progress bar when Windows starts. (The progress bar appears before the login prompt.)
/ nodebug
This switch turns off the 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 number of processors. 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 close the NTDetect.com file for 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, enter / fastitect: COMNUMBER, where Number is a serial port number. A comma can be separated by multiple port numbers to close more than one port. If the communication port is used to use / fastdetect, the serial mouse detection function on all communication port will be turned off. Note: In the earlier versions of Windows NT 4.0, the switch is named / NoserialMice.
/ SOS
The / SOS switch displays its name when the device driver is loaded. By default, the Windows Loader screen shows only the progress point. The switch can be used with the / basevideo switch to determine the driver that causes a fault.
/ PAE
Using / PAE switches in Boot.ini and the appropriate entry allows the computer to support 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
Using this switch, the hardware abstraction layer (HAL) that is actually loaded during the startup process can be defined. For example, enter /hal=halmps.dll load 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 do this, use the switch with the / kernel switch.
/ kernel = filename
With this switch, you can define the kernels actually loaded during the startup process. For example, enter / kernel=ntkrnlmp.exe load 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, and the launch log is recorded in the 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, input / burnMemory = 128 reduces physical memory available to Windows 128 MB.
/ 3GB
In X86-based systems, the switch is forced to assign 3 GB of virtual address space for the user program 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.
/ safeboot: parameter
This switch causes 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 / NOGUIBOOT switches are 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
You can use this switch to customize the amount of memory 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.
/ redirect
The Emergency Management Service (EMS) can be started using this switch 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:
1234
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 with one of the following values:
96001920057600115200
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
Use this switch with the / debug switch and / debugport switch to configure Windows to send debug information through institution 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 = 1394SET_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.
