Windows 2000 Solution Center

Top issues

How to multiple boot Windows XP, Windows 2000, Windows NT, Windows 95, Windows 98, Windows Me, and MS-DOS
This article describes how to configure an Intel-based computer to multiple boot the following Microsoft operating system: MS-DOSMicrosoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me)Microsoft Windows NTMicrosoft...
How to Create a Network Installation Boot Disk
This article explains how to add an NDIS driver for Network Interface Cards (NIC) that were not originally included in the Network Client Administrator. This information applies to the Network Client version 3.0 for MS-DOS and Windows Startup...
How to Print to Network Printer from MS-DOS-Based Programs
This article describes how to print to a network printer from an MS-DOS- based program in Windows. By default, most MS-DOS-based programs print directly to either LPT1 or LPT2. However, the output is not automatically routed across a redirector to...

CAPS LOCK Key State in MS-DOS Programs May Be Incorrect
If you are using an MS-DOS-based program, you change the CAPS LOCK key state while another program is active, and you then switch back to the MS-DOS-based program, the CAPS LOCK key state may be incorrect in the MS-DOS-based program. For example,...
16-Bit MS-DOS-Based Programs Cannot Change Label with CreateNewFile() Function
16-bit MS-DOS-based program behave differently under Windows 2000 than under MS-DOS when they call the CreateNewFile function (INT 21h, AH=5Bh) to write a disk label (CX=08h). Windows 2000260910How to Obtain the Latest Windows 2000 Service PackTo...
Wrong Value for InDOS Flag After Absolute Disk Read and Write Functions in 16-Bit MS-DOS-Based Programs
This article applies only to MS-DOS-based 16-bit programs. Some MS-DOS-based programs (including terminate-and-stay-resident, or TSR programs), make use of the InDOS flag to manage synchronization. The InDOS flag is usually set to 1 when MS-DOS is...

"16-bit MS-DOS Subsystem" error message when you run an MS-DOS or 16-Bit Windows program in Windows Server 2003 or Windows 2000 Server
Explains that you may receive a "16-bit MS-DOS Subsystem" error message when you run an MS-DOS or 16-bit Windows program in Windows Server 2003 or in Windows 2000 Server if the Autoexec.nt, Config.nt, or Command.com files are corrupted.
"Config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications" error message when you try to run a program in Windows 2000
Explains how to work around an issue that may occur if you have installed the MS04-032 Security Update for Microsoft Windows on a computer that is running 16-bit programs on a Windows 2000-based computer.
Slow Performance When Copying File from MS-DOS Client to Windows 2000-Based Computer
You may observe a long delay when you copy a file from an MS-DOS client to a Microsoft Windows 2000-based computer using the TCP/IP protocol. NOTE : This behavior does not occur when you copy a file from an MS-DOS client to a computer running...