WELCOME TO TURBO C++(cracked) FOR WINDOWS 4.5 **************************************
This README file contains important information about TURBO C++ FOR WINDOWS 4.5 (TCW). For the latest information about TCW and its accompanying programs, read this entire file.
***************** TABLE OF CONTENTS *****************
1. How to Get Assistance -- Sources of information
2. Installation -- Installing Turbo C++ on your hard disk
3. New Features
4. Important Information -- Acrobat Reader 2.0 -- Importing Project Files from Borland C++ 4.x -- Quick Tour Help file -- ObjectComponents Framework (OCF), OLE 2.0, and ObjectWindows 2.5 -- Registering debugging versions of OLE servers under TCW -- New file in WINDOWSSYSTEM directory -- New tools for registering OLE servers and automation controllers -- Debugging OLE applications under Windows NT -- WinSight -- OLE error codes -- OLE2 applications -- OLE implementation under Windows NT -- OLE2 compiler options -- VBX Support -- VBX Controls Included with TCW -- OpenHelp -- OpenHelp with TASM -- Limitation in DOCVIEW.IDE -- DDVT functions and RTTI -- Inline assembly and interrupts -- Creating 16-bit import libraries from .DEF files -- New Compiler Switches -- NOEHxx Libraries -- IDE/Integrated Debugging -- InProc servers and the IDE -- Using Tools with NTFS -- Running from a Windows 3.1 DOS Prompt -- Converting TCW 3.1 to TCW 4.5 code -- Floating-Point Formats -- AppExpert and OWL -- C/C++ Language Features
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. ********************************************* 2. INSTALLATION ********************************************* IMPORTANT! Do not install TCW 4.5 over previously installed TCW directories. The files in this distribution will not work with tools and libraries shipped before BCW 4.5 and TCW 4.5. If you used Turbo Assembler 4.0 with a previous installation of TCW, you must reinstall it after installing TCW 4.5. Also, be especially careful when using object files and libraries from earlier TCW 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 TCW 4.5 on your hard disk ----------------------------------------------- Diagnostic and debug version of OWL are not installed to the hard disk, but they can be copied from the CD. Users of ObjectWindows 1.0, should read the COMPAT.TXT file for compatibility information. **** Note to Windows NT, OS/2, and Windows 95 users **** If you intend to use TCW 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 TCW. For more information about installing and configuring TCW, see the file INSTALL.TXT which can be found in the following locations: * TCW CD-ROM (TCWIN45INSTALL.TXT)
3. NEW FEATURES
TCW 4.5 includes the following new features: OLE SUPPORT: - 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 16-bit OLE capabilities: * 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 - New utilities to make OLE programming easier: * WinRun allows you to launch Window application from the MS-DOS prompt in Windows 3.1. (See UTILS.TXT for more information.) * AutoGen, MacroGen, GuidGen produce helpful class declarations, macro,s and OLE identifiers automatically * DllRun and Register simplify running and testing DLL servers - IDE enhancements to TargetExpert, AppExpert, and ClassExpert to support the new OLE2 capabilities. COMPILER FEATURES - Support for ANSI C++ exception handling, structured exception handling under C, and mixed C/C++ exception handling. - Support for ANSI C++ operator new and operator delete. - Runtime Library support for the ANSI C++ string class. - Support for ANSI C++ runtime type identification (RTTI). - Support for ANSI C++ new style casts dynamic_cast, static_cast, const_cast, and reinterpret_cast. - Support for three character types as provided in ANSI C++. LINKER FEATURES - Linker debug capacity expanded. IDE FEATURES - Integrated GUI debugging for 16-bit Windows applications. - A new project manager that supports multiple targets, drag-and-drop, and Style Sheets for associating options. - AppExpert, which simplifies the process of creating ObjectWindows applications through code generation. - ClassExpert, which simplifies adding and managing classes in your AppExpert application. - Transfers, Settings Notebook, SpeedMenus, and a configurable SpeedBar. - Expanded editor support, including column blocking and window splitting. TEMC now called KEYMAPR. RESOURCE WORKSHOP - Resource preview - DialogExpert - Auto ID numbering - Auto mapping of accelerators and help hints to menu items - Support for VBX controls - SpeedMenus - Dialog editor property inspector - Integrated with ClassExpert and IDE project manager OBJECTWINDOWS LIBRARY (OWL) - Complete coverage of Windows API, including GDI - Single source for Win 3.1, Win 32s, and NT (building 32-bit applications requires Borland C++) - Built in exception handling using standard C++ exceptions for robust error handling - Built-in type safety using standard C++ templates - Toolbars, status lines, and print preview - Flexible Document/View architecture - Supports VBX 1.0 controls in a dialog or window - Layout Windows - Mix-in architecture - Support for 3d controls - Support for BWCC controls - Gadgets and Widgets - Printing and print previewing support GAME EXAMPLES - Five new sample programs: EXAMPLESOWLGAMESBLAKJACK BLOCKS CRIBBAGE METEOR EXAMPLESWINDOWSMAHJONGG DOCUMENTATION FEATURES - 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. - Documentation in the Acrobat 2.0 document viewing browser. Acrobat lets you search through the entire documentation set to find selected topics. You can view the contents page by page and print sections of particular interest. VBX SUPPORT - Borland's visual tools, such as Resource Workshop, provide support of VBX 1.0 controls via a DLL called BIVBX11.DLL. You can freely distrubute this DLL with programs you create that use VBX controls. 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 may appear to work but exhibit instability. Please contact the control vendor and explain the problem. They may have an updated control or may be able to contact Borland to find a solution.
4. IMPORTANT INFORMATION
This section contains important information not found elsewhere in the product documentation. Please read through this material in its entirety. ------------------ Acrobat Reader 2.0 ------------------ The four books available online duplicate material already in the online Help. We recommend using the Acrobat Reader to read long sequences of material in order and the online Help when searching for specific information by keyword. The Acrobat Reader is capable of high-quality printed output. You might prefer to print sections of the manuals that you use frequently. -------------------------------------------- Importing Project Files from Borland C++ 4.x -------------------------------------------- When TCW loads an .IDE file created with Borland C++, it shows a dialog box warning that the project might contain target types and option settings that TCW does not support. If you click Yes to import a BC project, TCW ignores any optimization settings the project might contain. The TCW project manager displays DOS targets and Win32 targets, but attempting to build them causes errors. For more details about what project features might cause problems for TCW, click the Help button in the warning dialog box. You can disable the dialog box, if you prefer, with the following setting in your TCW.INI file. [Project] ImportBorlandIDEFile=1 With this setting, TCW automatically converts any .IDE file without warning. Borland C++ reads TCW .IDE files without difficulty. TCW 4.5 does not support development of OWL 1 applications. The differences between OWL 1 and the current OWL 2.5 are large enough to render them incompatible. You will need to convert your OWL 1 programs to use OWL 2.5 before you can build them. For help converting, see Appendix A of the ObjectWindows Programmer's Guide in the online documentation. -------------------- Quick Tour Help File -------------------- To get you started quickly with using Turbo C++ for Windows, take a look at the online Quick Tour. The Quick Tour provides an overview of the product, with animated demonstrations of its many features. System Requirements ------------------- Although you can view the Quick Tour at any screen resolution, a resolution of at least 800 x 600 is recommended. Installation Notes ------------------ If you choose to install the Quick Tour Help file, then you also need to run Microsoft's Setup program for Video for Windows. Normally the TCW install launches Setup for you automatically. If you have chosen the WinLAN configuration, however, then a system administrator will have to run the Video for Windows Setup program for you because Setup writes to the system registry. Without Video for Windows, the Quick Tour Help file cannot play animation sequences. The animation (AVI) files are stored on the CD and are not automatically installed on your hard drive. For this reason, you need to leave the CD in the drive while viewing the Quick Tour if you want to view the demonstrations. If the CD is not in the drive, an error message is displayed when you try to run a demonstration. Although compression of the animation files is optimized to run from the CD-ROM, you can also run them from your hard drive. To do so, you need to make the following changes: 1. Create a directory called AVI under the TCWTOUR directory located in your Turbo C++ for Windows directory (TCWIN45, by default). 2. Copy all the files from the TCWIN45TCWTOURAVI directory on the CD-ROM to the TCWTOURAVI directory on your hard disk. 3. In WINHELP.INI, change the value of CdTcPath so it points to the drive and directory in which you installed TCW. If you used the default directory (TCWIN45), you will only need to change the drive letter to that of the hard drive where TCW is installed. The Quick Tour page that describes features for internationalizing applications allows you to launch the INTLDEMO example program directly from the Help file. If you chose not to install the Borland custom control library (BWCC.DLL) then INTLDEMO.EXE cannot run. Starting the Quick Tour ----------------------- You can start the Quick Tour from the following places: - From the Quick Tour icon in the Turbo C++ 4.5 desktop group. - From the Quick Tour button in the About Turbo C++ dialog box which displays the first time you start the IDE. - From the Quick Tour command on the Help menu. Uninstalling the Quick Tour --------------------------- You can uninstall the Quick Tour after viewing it by deleting the TCWTOUR directory located under the directory where you installed Turbo C++ for Windows (TCWIN45, by default). ---------------------------------------------------------------- ObjectComponents Framework (OCF), OLE 2.0, and ObjectWindows 2.5 ---------------------------------------------------------------- Registering debugging versions of OLE servers under TCW ------------------------------------------------------- The debugger, debugid, and debugdesc registration keys require the use of a debugger that can be invoked from the command line. Turbo C++ for Windows 4.5 does not provide a command-line debugger. You can purchase Turbo Debugger for Windows as part of the Borland TASM assembler product. New file In WINDOWSSYSTEM directory ------------------------------------- TCW 4.5 installs a new file called BOCOLE.DLL in your WINDOWSSYSTEM directory. This library must be present in order for any ObjectComponents program to execute. 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 DOCOLE_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 TCW 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 --------------------- When linking 16 bit OLE2 modules, the OLE2 import library (ole2