[psac]

Available switch options for the Windows XP and the Windows Server 2003 Boot.ini files
適用於
SUMMARY
You can add many different switches to the Boot.ini file that will modify the way that Microsoft Windows XP or Microsoft Windows Server 2003 start.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
102873 Boot.ini and ARC path naming conventions and usage



MORE INFORMATION
You can add the following switches to the Boot.ini file.

Note These switches apply to Microsoft Windows XP and to Microsoft Windows Server 2003, unless otherwise specified.
/basevideo
The /basevideo switch forces the system into standard 640x480 16-color VGA mode by using a video driver that is compatible with any video adapter. This switch permits the system to load if you selected the wrong video resolution or refresh rate. Use this switch in conjunction with the /sos switch. If you install a new video driver, and it does not work correctly, you can use this parameter to start the operating system. You can then remove, update, or roll back the problem video driver.
/baudrate=number
This switch sets the baud rate of the debug port that is used for kernel debugging. For example, type /baudrate=9600. The default baud rate is 9600 kilobits per second (Kbps) if a modem is attached. The default baud rate is 115,200 Kbps for a null-modem cable. 9,600 is the normal rate for remote debugging over a modem. If this switch is in the Boot.ini file, the /debug switch is automatically enabled.

For additional information about modem configuration, click the following article number to view the article in the Microsoft Knowledge Base:
148954 How to set up a remote debug session using a modem

For additional information about null modem configuration, click the following article number to view the article in the Microsoft Knowledge Base:
151981 How to set up a remote debug session using a null modem cable

/crashdebug
This switch loads the kernel debugger when you start the operating system. The switch remains inactive until a Stop message error occurs. /crashdebug is useful if you experience random kernel errors. With this switch, you can use the COM port for normal operations while Windows is running. If Windows crashes, the switch converts the port to a debug port. (This action turns on remote debugging.)

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
151981 How to set up a remote debug session using a null modem cable

/debug
This switch turns on the kernel debugger when you start Windows. The switch can be activated at any time by a host debugger that is connected to the computer, if you want to turn on live remote debugging of a Windows system through the COM ports. Unlike the /crashdebug switch, /debug uses the COM port whether you are debugging or not. Use this switch when you are debugging problems that are regularly reproducible.

For additional information about remote debugging, click the following article number to view the article in the Microsoft Knowledge Base:
121543 Setting up for remote debugging

/debugport=comnumber
This switch specifies the communications port to use for the debug port, where number is the communications port, such as COM1, that you want to use. By default, /debugport uses COM2 if it exists. Otherwise, the switch uses COM1. If you include this switch in the Boot.ini file, the /debug switch becomes active.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
151981 How to set up a remote debug session using a null modem cable

/maxmem=number
This switch specifies the maximum amount of RAM that Windows can use. Do not make this setting less than 12. Use this parameter to confirm whether a memory chip is faulty. For example, if you have a 128-megabyte (MB) system that is equipped with two 64-MB RAM modules, and you are experiencing memory-related Stop messages, you can type /maxmem=64. If the computer starts Windows and operates without problems, replace the first module to see if this action resolves the problem.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
108393 MAXMEM option in Windows NT Boot.ini file

/noguiboot
This switch disables the bitmap that displays the progress bar for Windows startup. (The progress bar appears just before the logon prompt.)
/nodebug
This switch turns off debugging. This scenario can cause a Stop error if a program has a debug hardcoded breakpoint in its software.
/numproc=number
This switch sets the number of processors that Windows will run at startup. With this switch, you can force a multiprocessor system to use only the quantity of processors (number) that you specify. This switch can help you troubleshoot performance problems and defective CPUs.
/pcilock
For x86-based systems, this switch stops the operating system from dynamically assigning hardware input, hardware output, and interrupt request resources to Peripheral Connect Interface (PCI) devices. With this switch, the BIOS configures the devices.
/fastdetect:comnumber
This switch turns off serial and bus mouse detection in the Ntdetect.com file for the specified port. Use this switch if you have a component other than a mouse that is attached to a serial port during the startup process. For example, type /fastdetect:comnumber, where number is the number of the serial port. Ports may be separated with commas to turn off more than one port. If you use /fastdetect, and you do not specify a communications port, serial mouse detection is turned off on all communications ports.

Note In earlier versions of Windows, including Windows NT 4.0, this switch was named /noserialmice.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
131976 How to disable detection of devices on serial ports

/sos
The /sos switch displays the device driver names while they are being loaded. By default, the Windows Loader screen only echoes progress dots. Use this switch with the /basevideo switch to determine the driver that is triggering a failure.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
99743 Purpose of the Boot.ini file in Windows 2000 or Windows NT