Windows Server Solution Center

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-DOS Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition (Me) Microsoft Windows NT Microsoft...
HOW TO: Enable and Disable QuickEdit Mode for MS-DOS Programs in Windows 2000
If you enable QuickEdit mode, you can use a mouse to copy and paste MS-DOS text. This step-by-step article describes how to disable and enable the QuickEdit mode for both the command prompt window and MS-DOS programs. In QuickEdit mode, you can...
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...

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...
MS-DOS-based communications program experiences intermittent transmission problems after you upgrade to Windows 2000 SP3
Fixes a POS application transmission problem after you upgrade the NTVDM.EXE file to Windows 2000 SP3.
Event 2510 is Logged on a Windows 2000 Server-based Server
Fixes a problem where Event 2510 is logged in the system log. Event 2510 occurs when error code 1230 or 1240 are sent from a Windows NT-based computer, and these errors cannot be mapped to the correct MS-DOS error.

"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...