ID: Q113969
The information in this article applies to:
- Microsoft Visual C++ for Windows, version 1.5
The integrated debugger in Visual C++ 1.50 uses a DLL (TLW0NCL.DLL) that is unecessarily allocated in low memory (below one meg) and fixed there. This uses a valuable system resource that should be available for other applications.
The most common behavior is the appearance of a message box containing this error message:
Could not load debugee. Windows is Out of Memory (1)
This occurs when trying to run an application in the Visual Workbench
debugger. One reason this can occur is because all of the memory below one
megabyte is full. Typically, this will happen when many drivers are loaded,
such as network or SCSI drivers.
Microsoft has released a patch to Visual C++ 1.5 which will allow the DLL for the debugger to load where Windows has room. This patch will modify the Visual Workbench 1.50, the new one will be version 1.50.01.
The following file is available for download from the Microsoft Software Library:
~ VC1501.exe (size: 81078 bytes)
For more information about downloading files from the Microsoft Software
Library, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q119591
TITLE : How to Obtain Microsoft Support Files from Online Services
In addition, this patch will fix another problem with Visual C++ 1.50. The
problem occurs when long strings are passed to OutputDebugString(), or when
OutputDebugString() is called successively with no new-line characters.
This may cause a general protection (GP) fault or cause the computer to
hang (stop responding). For more information on this problem, query in the
Microsoft Knowledge Base using these keywords:
OutputDebugString and Workbench and patch
This patch should only be applied when one of these problems is
specifically encountered. These are the only two changes to Visual
C++, version 1.5.
Additional query words: GPF
Keywords : kb16bitonly kbDebug kbide
Version : WINDOWS:1.5;
Platform : WINDOWS
Last Reviewed: March 29, 1998