install.txt

borland c++ 4.0 用于学习ucos的

SECTION -4-  WIN32s INSTALL ISSUES
A) An Explanation of Win32s
   Win32s is a subset of Windows NT. It lets 32-bit
   programs run under Windows 3.1 (16-bit) by simulating a
   32-bit operating system. If you are using Windows 3.1,
   these extensions (provided by Microsoft) are required to
   run 32-bit applications created with BCW. Note that
   you need a minimum of 8 MB of memory to run Win32s. If
   you plan to create 32-bit applications, you must install
   these extensions. If you are unsure, and you have 8 MB of
   memory, install Win32s. The Win32s extensions don't
   affect the normal operation of Windows 3.1.

B) Adding Win32s to your system
   If you haven't installed BC++ 4.0 yet, make sure you
   check the "Install WIN32s" install option.

   If you already installed BC++ 4.0 without Win32s on
   your system, insert disk 1 in your A: drive. Run Windows
   and then choose File/Run/a:setup.

C) Removing Win32s from your system
   To remove Win32s from your system refer to Section 2
   "Outdated versions of Win32s" in the README.TXT file.


SECTION -5-  TROUBLESHOOTING - INSTALL PROBLEMS
This section explains common errors encountered during
installation. System configuration and software conflicts
might cause the installation process to fail. If the
installation fails, follow the instructions in Section 11
on how to boot clean.  This will eliminate any	possible
software conflicts.  If booting clean doesn't solve the
problem, or you encounter a problem not mentioned here, 
contact Borland Technical Support.

A) Data Integrity or Bad Sector on Disk Errors
   If you receive either one of these error messages, you
   need to get a replacement disk set. Contact Borland's
   Disk Replacement Line at (800-621-3132). 

B) Install Program Terminates Prematurely 
   If the install program stops for no apparent reason without 
   error messages, it is possible that certain support files
   are write protected. To check this, do the following:
          1) Go to your WINDOWS directory
          2) Type  attrib *.*
          3) Check for the "r" attribute. If any file has this
             flag set, then you must clear it by typing:
                     attrib -r <filename>
          4) Repeat steps 2-3 for the WINDOWS\SYSTEM directory.

C) Disk Full or Insufficient Disk Space Errors
   You could get either one of these errors if there is 
   insufficient hard disk space available to install
   BC++ 4.0. Here are some suggestions:

   - Boot your system with a clean configuration. Refer to
     Section 11 for instructions on how to boot clean.

   - Make sure your system meets the minimum installation
     requirements. Refer to Section 1 for a list of the
     minimum installation requirements.

   - If you are using disk compresion read Section -2- A) 
     on reported available disk space when using disk 
     compression.

   - Make sure that at least 3Mb of disk space is available
     on the drive where you have Windows installed, regardless
     of which drive you are installing Borland C++ to.

   - Run Windows in standard mode (win /s). During a
     Windows-hosted installation process, a swap file is
     used to simulate extra memory while running Windows.
     This only happens if you are running Windows in 386
     Enhanced Mode and have virtual memory (under control
     panel) turned on. While Windows is running, the
     temporary swap file can grow dynamically thereby
     using up hard disk space. Starting Windows in standard
     mode (win /s) before installing prevents this problem.

D) GP Fault/Unhandled Exception 
   GP Fault or Unhandled Exception errors can occur for a
   variety of reasons. Possible reasons for these errors are
   explained in Technical Information Document number 649.
   Refer to Section 10 for instructions on how to obtain
   this document. Here are a few suggestions for solving
   these errors:

   - Make sure your system meets the minimum requirements.
     Refer to Section 1 for a list of the minimum
     installation requirements.

   - Boot your system with a clean configuration. Refer to
     Section 11 for instructions on how to boot clean.

   - Run Windows in standard mode (win /s) to eliminate swap
     file usage.

   - Turn off Disk Caching and Video/Shadow RAM in CMOS.
     Refer to the documentation for your computer.


SECTION -6-  TROUBLESHOOTING - RUN TIME PROBLEMS
This section describes common errors encountered when
trying to use BC++ 4.0. System configuration and software
conflicts might cause BC++ 4.0 to fail. If BC++ 4.0 fails,
you should boot your system clean to eliminate any possible
software conflicts. Refer to Section 11 for instructions
on how to boot clean. If booting clean does not solve the
problem or you encounter a problem not mentioned here,
contact Borland Technical Support.

A) Out of Memory
   If you are using command-line tools and are getting 
   "Out of Memory" errors you might have	exhausted your 
   extended (or XMS) memory pool. This is especially true if
   you only have 2MB available extended RAM and do not have
   a memory manager that provides virtual memory. If you are
   experiencing this, please consult Technical Information
   Document number 1737. For information on how to receive
   this document, refer to Section 10.

B) GP Fault/Unhandled Exception/System Hang 
   GP Fault or Unhandled Exception errors can occur for a
   variety of reasons including: not enough memory
   available, not enough hard disk space available,
   conflicts with optimizations set in the CMOS, and
   software conflicts. Technical Information Document
   numbers 649 and 1328 address these issues. Refer to
   Section 10 for information on how to obtain these files.

C) Turbo Debugger for Windows 
   If you experience any strange behavior from the Turbo
   Debugger, such as a garbled screen or a system hang upon
   execution or exit:
   1)  Make sure that you have the latest Windows drivers 
       for your video card.
   2)  Run TDWINI and test a different DLL to resolve a 
       possible compatibility problem with your specific 
       card.
   3)  Check TD-HELP!.TXT, TD_RDME.TXT, and README.TXT for
       additional information. 
   4)  If you are still experiencing difficulties your
       problem might not be related to the video mode. At 
       this point contact Borland Technical Support via 
       phone or online help.  Refer to Section 11 for more 
       information about online options and procedures. 
   

SECTION -7-  MODIFICATIONS INSTALL MAKES TO YOUR SYSTEM
This section describes the files that are added by the
install program to your Windows directory and modifications
that are made to the Windows configuration files.  Please 
note that these are example modifications based on a 
default installation.  

Files changed in the Windows directory:
   WIN.INI modifications:
             [Extensions]
     added:  IDE=BCW.EXE^.IDE
             [BCW4.0 INSTALL]
             Reserved1=C:\BC4

   PROGMAN.INI modifications:
               [Settings]
     changed:  Order= 1 6 2 3 4 5

               [Groups]
     added:    Group6=C:\WINDOWS\BCW40.GRP
             
   SYSTEM.INI modifications:
               [386Enh]
     added:    device=C:\BC4\BIN\WINDPMI.386
               device=C:\BC4\BIN\TDDEBUG.386

   Files added to WINDOWS directory:
     BCW.INI            BCW40.GRP 
     BORHELP.INI        HELP.ICO 
     SYSTEM.OLD         TDW.INI 
     WINHELP.INI 

   Files added to the WINDOWS\SYSTEM directory:
     BW32000C.DLL       BW320007.DLL
     BW320009.DLL       BWCC.DLL
     BWCC000C.DLL       BWCC0007.DLL 
     BWCC0009.DLL       BWCC32.DLL 
     CTL3DV2.DLL        CTL3D32.DLL
     OWL.INI


SECTION -8-  ICONS IN THE BC++ GROUP WINDOW
A) Creating a Program Group Window for BC++ 4.0. 
   If the Borland C++ Program Group Window didn't appear
   after installation you can create one by choosing one of
   the following options:

   - Generate icons by downloading the BC4GRPS.ZIP file.
     (If you need help on downloading refer to Section 10 of
     this document.) At the DOS prompt type: PKUNZIP
     BC4GRPS.ZIP. This uncompresses the files, including a
     readme.txt file containing instructions on using the
     BC4GRPS.EXE program.

   - Manually creating the icons. Load Windows, choose
     File|New|Program Group, and click on OK. Type the
     name you want for the program group window in the
     "Description:" text box, such as Borland C++. Leave
     "Group File" line blank. Click OK. A new Window appears.
     Choose File|New|Program Item to create icons for the
     Windows programs and click OK. Select one of the
     Windows executable programs to create an icon for, such
     as BCW.EXE (you can also use the Browse button). Type
     the name of that executable program in the Description
     text box. Type the full pathname to the executable in
     the Command Line text box. Typing a pathname for the
     working directory is optional. The default is the
     WINDOWS directory. Click OK. The icon appears in 
     the active program group window. Repeat these steps
     for executable program you want to use.

B) List of executable files that each icon calls:
   Borland C++:                 \BC4\BIN\BCW.EXE
   Borland C++ launches Borland's Integrated Development
   Environment (IDE). From within the IDE, you can edit,
   compile, and run C or C++ programs.

   Turbo Debugger for Win32:    \BC4\BIN\TD32.EXE
   This icon launches the 32-bit debugger.

   TD32 Configuration:          \BC4\BIN\TD32INST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for Win32.

   TD Video Configuration:      \BC4\BIN\TDWINI.EXE
   This icon launches the configuration utility that lets
   you configure the Debugger to run with your video card.

   Turbo Debugger for Windows:  \BC4\BIN\TDW.EXE
   This icon launches the 16-bit Turbo Debugger for Windows.

   TDW Configuration:           \BC4\BIN\TDWINST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for Windows.

   Remote Debugging:            \BC4\BIN\WREMOTE.EXE
   This icon launches the Remote Debugger.

   Remote Setup:                \BC4\BIN\WRSETUP.EXE
   This icon launches the configuration utility that lets
   you configure your system to do remote debugging.

   Turbo Debugger for DOS:      \BC4\BIN\TD.EXE
   This icon launches the DOS Turbo Debugger.

   TD Configuration:            \BC4\BIN\TDINST.EXE
   This icon launches the configuration utility for Turbo
   Debugger for DOS.

   WinSpector:                  \BC4\BIN\WINSPCTR.EXE
   This icon launches WinSpector. WinSpector helps you
   performing a post-mortem examination of Unrecoverable
   Application Errors (UAE) or General Protection Errors.

   WinSight:                    \BC4\BIN\WINSIGHT.EXE
   This icon launches WinSight--a program that lists
   debugging information about Windows classes, windows,
   and messages. Using WinSight, you can study how any
   application creates classes and windows, and you can
   monitor how Windows sends and receives messages.
   WinSight is a passive observer: it intercepts and
   displays info about messages, but does not
   prevent messages from getting to applications.

   FConvert:                    \BC4\BIN\FCONVERT.EXE
   This icon launches the utility to convert text files from
   OEM to ANSI format or vice versa.

   Workshop:                    \BC4\BIN\WORKSHOP.EXE
   This icon launches Resource Workshop, a tool that
   integrates the entire process of designing, editing,
   and compiling resources for applications.

   Hot-Spot Editor:             \BC4\BIN\SHED.EXE
   This icon launches the Hot-Spot Editor, which creates
   and edits a bitmap that includes one or more hotspots.