visual C++ 7.0完整安装程序

README.TXT File README file for Microsoft(R) C/C++, Version 7.0 (C) Copyright Microsoft Corporation, 1992 This document contains release notes for version 7.0 of Microsoft C/C++ and its libraries for MS-DOS(R) and Microsoft Windows(TM) operating systems. ========================< IMPORTANT REQUIREMENT >========================== Microsoft C/C++ version 7.0 requires DPMI services. If you wish to use Windows as your development environment, Windows provides DPMI services for you. TO USE MS-DOS AS YOUR DEVELOPMENT ENVIRONMENT YOU MUST INSTALL 386-Max TO PROVIDE THESE SERVICES. ================================< CONTENTS >=============================== This file has the following sections: Part 1: ESSENTIAL WINDOWS 3.0 COMPATIBILITY INFORMATION Part 2: Setup and Configuration Notes Part 3: Support for Windows 3.1 in the Microsoft Foundation Classes Part 4: List of Additional Readme Files Part 5: List of Topics in the DETAILS.TXT file =======< Part 1: ESSENTIAL WINDOWS 3.0 COMPATIBILITY INFORMATION >====== To make it easy for you to update to the latest Windows APIs and the new features of Windows 3.1, MS C/C++ supports Windows 3.1 by default. Windows 3.0 applications that are rebuilt with C/C++ will target Windows 3.1 by default. Therefore, attempting to run them under Windows 3.0 generates an error. If you do not wish to take advantage of new Windows 3.1 functionality, or if you want your applications to run on either Windows 3.0 or Windows 3.1, then follow these instructions for building Windows 3.0 applications. Building Windows 3.0 Projects with PWB -------------------------------------- New projects: Choose one of the four Windows 3.0 project templates when prompted for a project template. Rebuilding existing projects: Reset the current project template by choosing Project Templates from the Options menu and then selecting Set Project Template. Note: This resets all build options, so check the resulting options to ensure they are appropriate for your project. An alternative method is to add the WINVER=0x300 macro in the Additional Global C/C++ Options dialog box and to modify the RC Build command in the Customize Project Template dialog box. This dialog box can be accessed from the Project Templates option on the Options menu. To make this modification, change: command rc_exe "$(RC) $(RESS) $@" to: command rc_exe "$(RC) /30 $(RESS) $@" Building Windows 3.0 Projects from the Command Line --------------------------------------------------- The two methods for building Windows 3.0 projects from the command line are described in this section. Using the WINVER Macro ---------------------- To compile Windows 3.0 applications, you must either add the line: #define WINVER 0x0300 to your source file before the line including the WINDOWS.H include file, or add the /DWINVER=0x0300 option when compiling all modules in the Windows 3.0 project. This prevents any Windows 3.1-specific types, functions, or definitions from being included. Using the RC /30 Switch ----------------------- In order to ensure that your application is Windows 3.0-compatible, use the RC /30 option when combining your .EXE and .RES files. Use this option whenever RC is invoked after your .EXE file is linked, but do not use the /30 option with the /r option. Using Windows 3.1 Features in Windows 3.0 Applications ------------------------------------------------------ You can also build a Windows 3.0-compatible application that conditionally makes use of new Windows 3.1 features if the application is running on a Windows 3.1 system. To do this, use the RC /30 command-line option, but do not use the #define directive to define WINVER equal to 0x0300. Use the GetVersion() API to determine the version of Windows that is running before calling any new Windows 3.1 APIs. The sample code below demonstrates how the global constant fWin31 can be set to TRUE if Windows version 3.1 or greater is running on the system. You can use similar code in your application initialization. extern BOOL fWin31; { UINT version; fWin31 = FALSE; version = LOWORD(GetVersion()); if (((LOBYTE(version) << 8 ) | HIBYTE(version)) >= 0x030a) { fWin31 = TRUE; } } You can call new Windows 3.1 functions directly in your source as long as you link to the Windows 3.1 LIBW.LIB. In this case, no call to GetProcAddress() is needed. However, on a computer running Windows 3.0, you must make sure new Windows 3.1 functions are not called. Here's an example of how this can be done: extern BOOL fWin31; if (fWin31) { ScrollWindowEx(hwnd, ...); } else { ScrollWindow(hwnd, ...); } Using the MFC Library with Windows 3.0 and Windows 3.1 ------------------------------------------------------ The MFC library header files can build applications targeted for either Windows 3.0 or Windows 3.1. Windows 3.1 is the default target. This means that all of the new Windows 3.1 APIs are available for use. If you must target an application for Windows 3.0 only, you should define WINVER=0x0300 before including AFXWIN.H in your source files. This restricts the Windows and MFC interfaces to Windows 3.0-compatible versions only. The compiled MFC library (object code) must always be built for Windows 3.1. It will fail to compile if WINVER is defined to be 0x0300. The library is compatible with both Windows 3.0 and Windows 3.1 run-time systems. If you customize the MFC library, you should not redefine WINVER; the default value (WINVER=0x030A) is sufficient. ===================< Part 2: Setup and Configuration Notes >=============== Getting Help on Error Messages ------------------------------ To find information on any error message, you can access Help by using the stand-alone utility QuickHelp, by using the Help menu in the Programmer's WorkBench (PWB), or by checking the "Comprehensive Index and Errors Reference" manual. To find out about an error message using QuickHelp, at the operating-system prompt type: QH cxxxx where <c> is the error's alphabetic prefix and <xxxx> is the four-digit error number. To find out more about how to view errors from within PWB, choose "Errors" from the Microsoft Advisor Contents screen in PWB. (The Microsoft Advisor Contents screen appears when you choose "Contents" from the Help menu in PWB.) Some errors are documented in Help but are not in the "Comprehensive Index and Errors Reference" manual. See ERRATA2.TXT for a listing of these errors. Copying a Single File from Installation Disks --------------------------------------------- See the ANSWERS.TXT file for instructions. Installation of Graphics Sample Files ------------------------------------- Setup does not create the SORTDEMO and GRAPHICS subdirectories, or copy their associated graphics samples, unless