Select the product you need help with

Error When EMS Memory Is Configured for MS-DOS App in .pif File

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

This article was previously published under Q196875

SYMPTOMS

You may receive the following error message after you modify the custom configuration settings for an MS-DOS or Win16 application:

%systemroot%\System32\Config.Nt. The system file is not suitable for
running MS-DOS and MS Windows applications.

This error occurs when a .pif file is used to establish EMS memory and a custom Config.nt and Autoexec.nt are specified in the PIF file. Either the application will use the default configuration files in the %SystemRoot%\System32 folder, if they exist, or it will generate the error message listed above. Settings in the custom configuration files in a folder other than %SystemRoot%\System32 will not be used if EMS is specified in the .pif settings.

Back to the top | Give Feedback

CAUSE

The location of the custom configuration files is lost when EMS memory is established. The default configuration file location is used.

Back to the top | Give Feedback

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

Windows Service Pack Center
(http://windows.microsoft.com/en-US/windows/downloads/service-packs)
-or-
152734
(http://support.microsoft.com/kb/152734/EN-US/ )
how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

(http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS)

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Back to the top | Give Feedback