文件列表:

bc45\32SINST.INF (10214, 1994-11-17)
bc45\32SINST.MST (21971, 1994-11-17)
bc45\ACLOCK.PAK (21754, 1994-11-17)
bc45\APPLAUNC.PAK (33230, 1994-11-17)
bc45\ARRAYS.PAK (11225, 1994-11-17)
bc45\ASSOCS.PAK (11967, 1994-11-17)
bc45\AUTOCALC.PAK (38275, 1994-11-17)
bc45\BAGS.PAK (9709, 1994-11-17)
bc45\BCEXAMS.PAK (8946, 1994-11-17)
bc45\BCSUPRT.PAK (46813, 1994-11-17)
bc45\BCW.CA1 (1456640, 1994-11-17)
bc45\BCW.CA2 (1456640, 1994-11-17)
bc45\BCW.CA3 (56658, 1994-11-17)
bc45\BGI.PAK (97215, 1994-11-17)
bc45\BGILIB.PAK (15571, 1994-11-17)
bc45\BIDSAPI.PAK (1061, 1994-11-17)
bc45\BINTREES.PAK (9889, 1994-11-17)
bc45\BIVBX.PAK (36667, 1994-11-17)
bc45\BIVBX32.PAK (65291, 1994-11-17)
bc45\BIVBXLIB.PAK (4457, 1994-11-17)
bc45\BMPVIEW.PAK (47909, 1994-11-17)
bc45\BOCOLE.PAK (131076, 1994-11-17)
bc45\BOLBIN.PAK (101550, 1994-11-17)
bc45\BOLEUI.PAK (92456, 1994-11-17)
bc45\BOLEUI32.PAK (272412, 1994-11-17)
bc45\BOLINC.PAK (4176, 1994-11-17)
bc45\BORERR.PAK (9424, 1994-11-17)
bc45\BUTTON.PAK (9492, 1994-11-17)
bc45\BWCC.PAK (68647, 1994-11-17)
bc45\BWCC32.PAK (130379, 1994-11-17)
bc45\C16DYDLL.PAK (24389, 1994-11-17)
bc45\C16DYLIB.PAK (14358, 1994-11-17)
bc45\C16STAT.PAK (127555, 1994-11-17)
bc45\C32DYDLL.PAK (20113, 1994-11-17)
bc45\C32DYLIB.PAK (14909, 1994-11-17)
bc45\C32STAT.PAK (30391, 1994-11-17)
bc45\CALC.PAK (12134, 1994-11-17)
bc45\CARDS.DL_ (44963, 1994-11-17)
bc45\CHELP.PAK (12403, 1994-11-17)
bc45\CLASSHLP.PAK (657348, 1994-11-17)
... ...

**************************** WELCOME TO BORLAND C++ 4.5 **************************** This README file contains important information about BORLAND C++. For the latest information about Borland C++ and its accompanying programs, read this entire file. ***************** TABLE OF CONTENTS ***************** 1. How to Get Assistance -- Sources of information 2. Installation -- Installing Borland C++ on your hard disk 3. New Features 4. Important Information -- ObjectComponents Framework (OCF), OLE 2.0, and ObjectWindows 2.5 -- New files in WINDOWS\SYSTEM directory -- New tools for registering OLE servers and automation controllers -- Registering a debugger to run an OLE server -- Debugging OLE applications under Windows NT -- WinSight -- OLE error codes -- OLE2 applications -- OLE implementation under Windows NT -- OLE2 compiler options -- VBX Support (including 32-bit) -- OpenHelp -- OpenHelp with TASM and PowerPack -- Out of Memory and MAKESWAP -- Threads -- DDVT functions and RTTI -- Inline assembly and interrupts -- Creating 16-bit import libraries from .DEF files -- New Compiler Back-end and Pentium scheduler support -- New Compiler Switches and Linker Optimizations -- NOEHxx Libraries -- IDE/Integrated Debugging -- InProc servers and the IDE -- Turbo Debugger for Windows -- Using Tools with NTFS -- CTLDATA statements in Win32 -- Running from a Windows 3.1 DOS Prompt -- Converting Borland C++ 3.1 to Borland C++ 4.5 code -- Floating-Point Formats -- WinRun -- AppExpert and OWL -- Online Registration ********************************************* 1. HOW TO GET ASSISTANCE ********************************************* If you have any problems, please read this file, the HELPME.WRI and other files in your DOC subdirectory, and check the on-line help. If you still have a question and need assistance, help is available from the following sources: 1. Borland offers a wide variety of Technical Support plans providing a range of assistance from installation and general usage of Borland C++ to language syntax, programming, and debugging help. For information about these support programs, call 1-800-523-7070. 2. For immediate assistance with everything from configuring Borland C++ to C++ programming or debugging, call our C++ Programmer's Advisor Lines ($2/minute, first minute free): * Windows / Win32: 1-900-555-1002 or 1-800-782-5558 (MC/Visa) * DOS : 1-900-555-1004 or 1-800-368-3366 (MC/Visa) For assistance outside of North America, contact your local Borland representative. 3. To receive Technical Support for Borland Database Tools, please call: 1-800-839-9777 4. For on-line access to the Borland CompuServe forums, with their libraries of technical information and answers to common questions, type GO BCPPDOS - for questions pertaining to DOS GO BDEVTOOLS - for questions pertaining to Borland Database Tools GO BCPPWIN - for questions pertaining to Windows If you are not a member of CompuServe, see the enclosed special offer, and write for full details on how to receive a free IntroPak containing a $15 credit toward your first month's on-line charges. 5. Borland's TECHFAX service. Call (800) 822-4269 for a FAX catalog of technical document entries. For assistance outside of North America, contact your local Borland representative. 6. Borland DLBBS. Dial (408) 431-5096 (up to 9600 baud, 8-N-1) for a host of free technical documents and example programs. 7. Technical information on Borland C++ is available on the Internet via anonymous ftp at our ftp site ftp.borland.com and via the World Wide Web at the URL http://www.borland.com. 8. Subscribe to Borland's free electronic newsletter and get a regular update on the hottest programming tips and tricks. Send your full name and address via electronic mail to tech-info@borland.com. =============== 2. INSTALLATION =============== IMPORTANT! Do not install Borland C++ 4.5 over previously installed Borland C++ directories from versions 4.5 or earlier. The files in this distribution will not work with previously shipped tools and libraries. This is particularly true for configuration files from previous shipping releases, like TDCONFIG.TDW and BCCONFIG.BCW. If you used Turbo Assembler 4.0 or the Borland Power Pack for DOS with a previous installation of Borland C++, you must reinstall those products after installing Borland C++ 4.5. If you used CodeGuard for Borland C++ 4.5 with a previous installation of Borland C++, you must reinstall CodeGuard after installing Borland C++ 4.5. Also, be especially careful when using object files and libraries from earlier Borland C++ versions with binaries created with this release. There are several potential problems when linking with old objects or libraries. Exceptions won't work correctly (destructors won't get called) when a pre-BC4 stack frame is unwound due to an exception. Do not use long file names when installing under Windows NT. ----------------------------------------------- Installing Borland C++ 4.5 on your hard disk ----------------------------------------------- For information about installing Borland C++ 4.5 from CD-ROM, see the CD booklet. To install Borland C++ 4.5 from floppy disks, 1. Put disk 1 in your floppy drive. 2. In Program Manager, choose File|Run. 3. Type A:\INSTALL. (If your disk drive is not drive A, type the appropriate letter instead.) 4. Choose OK. 5. Follow the instructions on the screen. Diagnostic and debug version of OWL are not installed to the hard disk, but they can be copied from the CD or built from OWL source using the makefile provided. Users of ObjectWindows 1.0, Turbo Vision 1.0, or the Paradox Engine should read the COMPAT.TXT file for information on using these products with Borland C++ 4.5. To get Turbo Profiler, you must install the debuggers. **** Note to Windows NT, OS/2, and Windows 95 users **** If you intend to use Borland C++ under any of these platforms you must follow some additional installation steps, which are listed in the INSTALL.TXT file. If you fail to read and follow these configuration guidelines, you may encounter several significant problems when using Borland C++. The following files which appear in the BC45\BIN directory are intended for Windows 3.1 and may not work correctly in conjuction with 32-bit applications running under Windows 95: DIB.DRV YESMOUSE.DRV VGAP.DRV MSMOUSE.DRV However, certain 16-bit applications require these drivers to run. For more information about installing and configuring Borland C++, see the file INSTALL.TXT which can be found in the following locations: * Borland C++ floppy disk 1 (INSTALL.TXT) * Borland C++ CD-ROM (\BC45\INSTALL.TXT) *************** 3. NEW FEATURES *************** Borland C++ 4.5 is an update to 4.0. The main difference is the upgrading of header files and import libraries to support the Windows 95 programming. There is a new version of the OWL libraries (2.52) to accommodate some altered structure definitions in the new Win32 headers. In addition, 4.5 makes small improvements to our VBX support. For a more specific list of updated files, see INSTALL.TXT. The rest of this section describes what was new in 4.5 for users who are upgrading from earlier versions. Borland C++ 4.5 includes the following new features: * A complete encapsulation of OLE2 via new ObjectWindows classes and the ObjectComponents Framework, a new set of C++ classes. This allows you to develop applications that support the following OLE capabilities in both 16 and 32-bits: - Linking and embedding containers - Linking and embedding servers - Automation servers (automatable servers) - Automation controllers - OLE clipboard operations - OLE drag and drop operations - In-place editing - OLE user interface, including menu merging, pop-up menu for activated object, verbs on container's Edit menu - Compound file storage - Registration - Localized strings for international support - Type libraries * IDE enhancements to TargetExpert, AppExpert, and ClassExpert to support the new OLE2 capabilities. * A new, faster, default compiler back-end. * The 16-bit Profilers (TPROF and TPROFW) have returned to the product. * VBX support for 32-bit programs. * OpenHelp, a utility that enhances the functionality of Windows Help by allowing you to quickly search for topics across Help files, as well as the ability to add your own Help files (or remove them) from the search. * Visio OLE Testbed, a subset of Shapeware's drag-and-drop drawing program. You can use Visio OLE Testbed to test OLE compound documents, objects, and automation with applications you create using Borland C++. * WinRun allows you to launch Window application from the MS-DOS prompt in Windows 3.1. * For CD-ROM users, the complete Borland C++ manual set is now available online in the DynaText document viewing browser. Using DynaText, you can search through the entire collection of books to find selected topics. You can view the contents of a single book page by page or even print the complete documentation set. See the booklet in your Borland C++ 4.5 CD-ROM case for information about how to launch and use the DynaText Browser. Complete information on how to use DynaText is available in the online Help for the Browser. * Improved EasyWin provides scrolling and printing support for character based Windows applications. * Software based correction for the FDIV flaw in older Pentium chips. For more information, see BCW.HLP. ************************ 4. IMPORTANT INFORMATION ************************ This section contains important information not found in the manuals, online Help, or online text files. Please read through this material in its entirety. ---------------------------------------------------------------- ObjectComponents Framework (OCF), OLE 2.0, and ObjectWindows 2.5 ---------------------------------------------------------------- New file In WINDOWS\SYSTEM directory ------------------------------------- Borland C++ 4.5 installs new files called BOCOLE.DLL and BOCOF.DLL in your WINDOWS\SYSTEM directory. These libraries must be present in order for 16 and 32-bit ObjectComponents programs to execute respectively. BOCOFW.DLL is a unicode implementation of BOCOF.DLL which can be rebuilt from source or copied from the CD-ROM. BOCOFW.DLL is for use on Windows NT only. New tools for registering OLE servers and automation controllers ------------------------------------------------------------------ The program tool AUTOGEN simplifies the task of writing proxy classes for an automation controller. AUTOGEN reads type libraries (*.OLB; *.TLB) and emits C++ source files containing the proxy objects. The REGISTER and GUIDGEN utilities provide a means of registering and unregistering servers and generating unique identifiers. Registering a debugger to run an OLE server ------------------------------------------- To make OLE invoke your server through the debugger, add the following entry to the appropriate registration table. REGDATA(debugger, "TDW") You can specify a complete path to the debugger as well as command-line options for the debugger. Do not place the name of the server program on the debugger command line. That will happen automatically. If you want to choose at runtime whether to invoke the server with or without the debugger, then each application or document must essentially be registered twice, using different CLSIDs, progids, and descriptions. The debug and non-debug entries will appear simultaneously in object browsers. The debug invocation will have the /Debug flag on the command line; this will in turn register the application class factory for the debug registration instead of the normal registration. To test for the presence of /Debug on the command line, call this function: TOcModule::IsOptionSet(amDebug); If you register debugprogid, you should also register both debugdesc and debugger. The debug description string distinguishes the debugging and non-debugging registry entries for the user. If you register debugprogid, the debugger entry will be used only for the debug registration. These are typical debug entries: REGDATA(debugprogid,"MyDocument.Debug") REGDATA(debugdesc, "MyDocument Debug Object") REGDATA(debugger, "TDW") There is also a debugclsid entry, but you don't have to register it yourself because ObjectComponents generates it for you automatically by offsetting the application's clsid. The application registration is used for automation invocations, and document registrations are used for linking and embedding invocations. Any or all can be set up for dual registration. For DLL servers, the registration debug entries are completely ignored. To debug DLL servers, use the REGISTER tool with the -Debug command-line option. This will launch the DLL and break inside, allowing breakpoints to be set. Do not close the message box until the debugging session is complete. Debugging OLE applications under Windows NT ------------------------------------------- When debugging OLE applications under Windows NT 3.5, you may experience a lock up if a program is forced to terminate. This will happen when any OLE application is running under the IDE and you explicitly request Debug | Program Terminate, or implicitly request program termination by closing a project. This problem will not occur under Windows 3.1 or Windows 95, and will not happen with non-OLE applications. Borland recommends that all developers running under NT accept any updates to the NT OLE DLLs if and when they are made available by Microsoft. WinSight -------- When WinSight spies on an ObjectWindows OLE container, it sometimes causes corruption of the container's menus. This behavior is expected. If it occurs, quit the application and start again. OLE error codes --------------- The file DOC\OLE_ERRS.TXT contains a list of the error codes OLE defines. The list is sorted in numerical order. Refer to it for help in interpreting OLE-related error returns. OLE2 applications ----------------- Many commercial products are now offering their first generation of OLE2 enabled applications. Some of these applications are more complete OLE implementations than others. Borland has observed several major commercial applications that exhibit errant behavior when asked to perform certain OLE operations. This is especially true when asked to embed DLL servers, which many OLE applications appear to be unprepared to handle. If you experience problems when using OLE applications you create with Borland C++ in conjunction with third party products, do not jump to the conclusion that the problem is yours. Until OLE applications in the market place mature, it is not yet a safe assumption that just because a product comes from a leading company that it is robust. Changes introduced between OLE 2.0 and OLE 2.02 are responsible for exposing some of these problems. When reporting bugs in OLE applications to third parties, be sure to specify that they should be developing and testing under the latest version of OLE. OLE implementation under Windows NT ----------------------------------- The 16 bit OLE implementation originally shipped in Windows NT 3.5 may exhibit problems with DLL servers and may behave differently than the version of OLE that MS recommends for Windows 3.1. Borland recommends that all NT developers update to later versions of the NT OLE DLLs if and when they are made available by Microsoft. OLE2 compiler options --------------------- 1) 32 bit OLE2 projects must increase the identifier length to 55. You can do this with the command line compiler -i switch or in the IDE with the Options|Project|Compiler|Source edit field. 2) When using 32-bit OLE2, INC_OLE2 must be defined. You can do this on the command line with -DINC_OLE2 or in the IDE in the Options|Project|Compiler|Defines edit field. 3) When linking 16 or 32 bit OLE2 modules, the OLE2 import library (ole2w16.lib or ole2w32.lib) must come before the RTL import library (import.lib or import32.lib respectively). ----------------------------- VBX Support (including 32-bit) ------------------------------ The BIVBX102.DLL has been renamed to BIVBX11.DLL. BIVBX11.DLL has been tested with a large number of VBX controls written to the Microsoft Visual Basic 1.0 CDK specification. If you have a problem with a specific control, make sure that it does not require VB 2.0 or VB 3.0 CDK functionality. VBX 2.0 and 3.0 controls will usually display a message saying that they require VB 2.0 or 3.0 support. In some cases, though, the control might appear to work but exhibit instability. Please contact the control vendor and explain the problem. They might have an updated control or might be able to contact Borland to find a solution. The following functions in BIVBX.H are limited to 16-bit only and should be replaced as follows: Old (16-bit only) New (16-bit and 32-bit) ----------------- ----------------------- VBXGetBasicStringPtr VBXGetBasicStringBuf VBXGetCStringPtr VBXGetCStringBuf VBXGetEventName VBXGetEventNameBuf VBXGetPropName VBXGetPropNameBuf VBXLockCString VBXLockCStringBuf VBXMethod N/A To build any 32-bit application that uses VBX controls, link with BIVBX32.LIB instead of BIVBX.LIB. VBX support for 32-bit applications requires that the following files are present in the Windows \SYSTEM directory at run-time: All: BIVBX11.DLL Win32s: BIVBX11S.DLL and BIVBX11.32S NT: BIVBX11N.EXE and BIVBX11.32N (installed in \SYSTEM32) For more information, see the BIVBX.WRI file. TargetExpert now manages libraries for VBX controls. If you have an IDE project which uses VBX controls, make the following change to your project to take advantage of TargetExpert support: - In the project window, delete the bivbx.lib node. - In the project window, right click on your EXE node. - From the resulting SpeedMenu, select TargetExpert. - In TargetExpert, enable the VBX checkbox and press OK. ---------------------------------- ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：