Select the product you need help with
Long PATH Environment Variable Causes 16-bit Apps to HangArticle ID: 169171 - View products that this article applies to. This article was previously published under Q169171 On This PageSYMPTOMS
Certain 16-bit programs may stop responding (hang) or not run. When you
look at Processes in Task Manager, it shows NTVDM at or around 100 percent
CPU time.
CAUSE
This problem occurs when the PATH statement is approximately 200
characters or more in length.
This problem has also been seen when security on the files in the %SystemRoot%\System32 folder has been made too restrictive. Specifically, the users running 16-bit programs must have at least Read (RX) access to all files in the folder and all subfolders. This is the configuration by default. RESOLUTION
Use one of the following methods to resolve this problem:
Method 1The PATH statement can be found in two locations. Shortening one or both statements should fix the problem.PATH in System Properties:
Method 2Increase the environment size in Config.nt:
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
Properties |


Back to the top








