The information in this article applies to:
SUMMARY
The Microsoft Visual Studio 6.0 Service Pack 2 Readme file contains the
following sections:
MORE INFORMATIONOverview
If your language setting is not in this list, the English version of Setup
will run. Determining the Files That Setup Installs Setup might not install all the files included in this service pack on your computer. If you do not have a copy of the file on your computer, or if the file on your computer is a more recent version than the one in the service pack, Setup will not update the file on your computer. Updating Files You Previously Modified The primary way Setup determines which files to replace is by checking the version information in a file's resources. However, some files, such as text files and nonbinary files, have no resource information. In these cases, Setup uses the time stamp to determine which files need to be replaced. If you have altered the time stamp on any of the Visual Studio component text files or files that do not have version information, then Setup may not replace those files. Source files and header files are examples of some files you might have changed. Determining the Update History of the Products Based on File Versions To determine which updates have been made since the initial release of a product, you will need to examine the version number in the properties of one or more files. To determine the update status of a product use the following steps:
The following table lists the developer tools that have been updated in this Visual Studio 6.0 Service Pack. It also lists the key files you should check to ascertain version information.
Uninstalling the Visual Studio 6.0 Service Pack The service pack cannot be uninstalled independently of Visual Studio. To uninstall service pack updates to a Visual Studio 6.0 tool, such as Visual C++, you must uninstall the tool. The service pack updates will be uninstalled with it. Then, reinstall the tools without the updates. Notes on Fixes Fixed Visual C++ Issues The following Visual C++ issues have been fixed with Service Pack 2 and were also fixed with Service Pack 1. Microsoft Foundation Classes (MFC) Issues: Q193099 FIX: CDialog::Create() Returns Incorrect Value Calling EndDialog Q193272 FIX: MFC Doesn't Call CPrintDialog::OnInitDialog Q193102 FIX: Assert in Appui1.cpp Line 215 in MFC SDI/MDI Application Q192942 FIX: Call to CWnd::MoveWindow causes Stack Overflow Q193100 FIX: CString Serialization Causes Access Violation CRT Issues: Q193509 FIX: Exception When Calling strftime() Function The following issues have been addressed in Service Pack 2 but were not addressed in Service Pack 1. MSVCRT.DLL was modified to include the Visual C++ 5.0 heap in addition to the Visual C++ 6.0 heap for better compatibility. Visual C++ 6.0 applications will continue to use the Visual C++ 6.0 heap and pre-Visual C++ 6.0 applications will use the Visual C++ 5.0 heap. CRT Issues: Heap compatibility problems as described in the following two Knowledge Base articles: Q190536 PRB: Invalid Page Fault in Msvcrt.dll Q194550 PRB: Freeing Memory Multiple Times May Cause an Access Violation When installing Service Pack 2, several of the CRT heap management files will be overwritten by updated files that include the code for both the Visual C++ 6.0 heap and the Visual C++ 5.0 heap. If you need to rebuild the Visual C++ 6.0 static libraries, the Visual C++ 5.0 heap code will be included in your static library. It will not be used. The Visual C++ 5.0 heap was added to this release to support compatibility problems that can arise due to the problems listed above. If you do not wish the Visual C++ 5.0 code to be included in your rebuilt static library, you should rebuild the library using the original code that was released with Visual C++ 6.0. The small block heap source files in the preceding Visual C++ 6.0 file list are flagged with an asterisk. Please be aware that the source files listed match the PDB files for the DLL version of the heap and do not correspond to the static CRT libraries which were not updated in this service pack. If you need to debug into the static CRT libraries, you need recopy the original CRT source files from your product CD. Fixed Visual Basic Issue The following Visual Basic issue has been fixed with Service Pack 2 and was also fixed with Service Pack 1.
Fixed Automation Issues The following run-time issue has been fixed with Service Pack 2 and was also fixed with Service Pack 1:
Updated Visual J++ Files In response to the automation issues previously noted, the Microsoft virtual machine files have been updated. This change will be applied both on the computer where Visual J++ is installed, and also to the Visual J++ redistributable folder so that Visual J++ applications that are distributed will also include the updated Automation files. To install and use the updated versions of the core Microsoft VM class files, run either Classd.exe or Classr.exe. This service pack contains the required Visual J++ files needed to comply with the preliminary ruling issued by Federal District Court Judge Ronald H. Whyte. These changes were not included in Visual Studio 6.0 Service Pack 1. For more information, please read \vj98\extwarn.txt in your Visual Studio folder or go to http://msdn.microsoft.com/visualj Finding More Information For more in-depth information about the Visual Studio issues that are fixed in this service pack, see the Microsoft Knowledge Base articles available at: http://support.microsoft.com/s upport To build a Visual Studio Service Pack query:
http://msdn.microsoft.com/vstudio REFERENCES
NOTE: This reference is not part of the original readme text from the product release: Q197298 INFO: Microsoft Visual Studio Service Packs, What, Where, Why Additional query words:
Keywords : kbservicepack kbVS600sp2 kbVS600sp2bug kbVS600sp2fix |
Last Reviewed: July 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |