Microsoft KB Archive/168925

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 20:27, 20 July 2020 by X010 (talk | contribs) (Text replacement - ">" to ">")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Article ID: 168925

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition



This article was previously published under Q168925

SYMPTOMS

When you attempt to run a 16-bit Windows-based program at a command prompt using the START command, you may receive the following error message:

The WIN16 subsystem was unable to enter Protected Mode, DOSX.EXE must be present in you AUTOEXEC.NT and present in your path.

However, Dosx.exe is present in the Autoexec.nt file and the file is in the path.

CAUSE

This error message occurs when all of the following conditions exist:

  • The /separate switch is used with the START command.
  • There is a .pif file for the program in the path.
  • The .pif file references custom Autoexec and Config files that do not load Dosx.exe or Himem.sys.


RESOLUTION

Rename the program's .pif file. Change the .pif file name from <Program>.pif, where <Program> is the executable file name of the program, to <Program>.xxx. Make sure to search for and rename all instances of the <Program>.pif file.

MORE INFORMATION

The START command is a command-line tool that starts a separate window to run a specified program or command. It is frequently used in batch files. The /separate switch starts 16-bit Windows-based programs in separate memory space.

When you use the START /SEPARATE <PROGRAM>.EXE command, the path is searched for any instances of a <Program>.pif file. If no <Program>.pif file is found, Windows NT loads the _default.pif file and then runs <Program>.exe. This behavior does not occur if the /separate switch is not used, nor does it occur in Windows NT version 3.51 even when the /separate switch is used.

Keywords: kbenv kberrmsg KB168925