Select the product you need help with

MS-DOS-based programs do not run as expected on a computer that is running Windows Server 2003, Windows XP, or Windows 2000

Article ID: 890067 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

You try to run a MS-DOS-based program on a computer that is running one of the following operating systems:

Microsoft Windows Server 2003
Microsoft Windows XP with Service Pack 1 (SP1)
Microsoft Windows XP with Service Pack 2 (SP2)
Microsoft Windows 2000 with Service Pack 3 (SP3)
Microsoft Windows 2000 with Service Pack 4 (SP4)

However, the program does not run as expected.

Back to the top | Give Feedback

This problem occurs if you run a 16-bit MS-DOS-based program at a command prompt, and you do not include a space between the .exe file name extension and the parameter switch (/). A space is always added between the .exe file name extension and the parameter switch when a MS-DOS-based program is run from a command line.

For example, your MS-DOS-based program may try to run the command as Program.exe/Parameter. Even though a space is not specified in the command, the command is run as Program.exe /Parameter.

Back to the top | Give Feedback

RESOLUTION

Windows Server 2003

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 service pack 1 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   08-Sep-2005  01:17  5.2.3790.405      420,864  Ntvdm.exe        
   08-Sep-2005  02:10  5.2.3790.2525     443,392  Ntvdm.exe        
   08-Sep-2005  02:12  5.2.3790.2525      32,256  Arpidfix.exe

Windows XP

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows XP service pack 2 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

Windows XP with SP1 or with SP2

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   06-Jul-2005  22:59  3.10.0.103         92,224  Krnl386.exe
   06-Jul-2005  22:56                     33,840  Ntio.sys
   06-Jul-2005  22:56                     34,560  Ntio404.sys
   06-Jul-2005  22:56                     35,648  Ntio411.sys
   06-Jul-2005  22:56                     35,424  Ntio412.sys
   06-Jul-2005  22:56                     34,560  Ntio804.sys
   06-Jul-2005  23:49  5.1.2600.1715     397,312  Ntvdm.exe        
   04-Jun-2004  00:43  5.1.2600.1562     245,760  Wow32.dll        
   06-Jul-2005  23:38  5.1.2600.2715     420,864  Ntvdm.exe      
   06-Jul-2005  23:41  5.1.2600.2715      30,720  Arpidfix.exe

Windows 2000

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows 2000 service pack 3 installed to apply this hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

Windows 2000 with SP3 or with SP4

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-Jun-2003  20:05  3.10.0.103         92,032  Krnl386.exe
   19-Jun-2003  20:05                     33,824  Ntio.sys
   19-Jun-2003  20:05                     34,544  Ntio404.sys
   19-Jun-2003  20:05                     35,648  Ntio411.sys
   19-Jun-2003  20:05                     35,408  Ntio412.sys
   19-Jun-2003  20:05                     34,544  Ntio804.sys
   15-Dec-2004  19:24  5.0.2195.7011     398,608  Ntvdm.exe        
   16-Dec-2004  05:02  5.0.2195.7009     239,888  Wow32.dll

Hotfix installation information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756

(http://support.microsoft.com/kb/322756/ )

How to back up and restore the registry in Windows

After you apply this hotfix, you must add the following entry to the registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WOW\CmdLine\NoSpace

To do this, follow these steps:

Click Start, click Run, type regedit, and then click OK.
Locate and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WOW
Right-click WOW, point to New, and then click Key.
Type CmdLine, and then press ENTER to name the new subkey.
Right-click CmdLine, point to New, and then click DWORD Value.
Type NoSpace, and then press ENTER to name the new value.
Right-click NoSpace, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor.

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

Back to the top | Give Feedback