FIX: What's New: Bug Fixes Made in Visual C++ Version 1.52b |
Q135388
The information in this article applies to:
-
Microsoft Visual C++ for Windows, 16-bit edition, version 1.52b
SUMMARY
This article lists fixes made to Microsoft Visual C++ for Windows in
version 1.52b. This information can also be found in the What's New
help file that is available from Books Online or from the initial
Setup dialog box.
MORE INFORMATION
All of the following bugs were corrected in Visual C++ version 1.52b.
MFC 2.52b
- Error L2025 occurred on CWnd::DoDataExchange.
For more information, please see the following article in the Microsoft
Knowledge Base:
Q134984 FIX: L2025 Error on CWnd::DoDataExchange or CObject::Serialize
- CArchive::ReadObject sometimes caused an assertion in a CPtrArray
object because CPtrArray can hold a maximum object size of 16K in a
large memory model application. CArchive did not take the memory
model into account; Because CArchive enforced a 32K limit, objects of
32K could be written but an assertion was generated if CArchive
read in more than 16K.
- There was a memory leak in 16-bit AUX_DATA. The three pens used in the
CPropertySheet class were leaking.
For more information, please see the following article in the Microsoft
Knowledge Base:
Q128604 FIX: Three Pens Leaked By MFC in Visual C++ 1.52
- The CArchive buffer pointer could wrap around the end of a segment
unintentionally.
- If AfxSocketInit failed, applications sometimes produced a General
Protection Fault.
For more information, please see the following article in the Microsoft
Knowledge Base:
Q130653 FIX: MFC Sockets Application Causes GP Fault on Exit
- The MAPISendMail dialog box did not stay modal.
- The DLGPROP.CPP source file had non-near data. This could prevent
applications from being able to run multi-instance.
Additional query words:
1.52b 2.52b 2.53