install.txt

borland c++ 4.0 用于学习ucos的

   A hotspot can link to Help topics or run Help macros when
   clicked. Using Hot-Spot Editor, you can assign hotspots
   to a bitmap and assign attributes to each hotspot. These
   bitmap files generally have a .SHG filename extension.

   Win32s Reference:            \BC4\BIN\WIN32S.HLP
   This icon launches the on-line reference for Microsoft's
   Win32 Application Programming Interface (API).   

   Multimedia Reference:        \BC4\BIN\WIN31MWH.HLP
   This icon launches the on-line reference for the
   Multimedia Application Programming Interface (API) of
   Windows 3.1. The Multimedia API includes the functions,
   messages, and data structures you can use to create
   multimedia applications for Windows.

   MCI Reference:               \BC4\BIN\MCISTRWH.HLP
   This icon launches the on-line reference for the Media
   Control Interface (MCI). MCI is a high-level command
   interface to multimedia devices and resource files.

   Hot-Spot Reference:          \BC4\BIN\SHED.HLP
   This icon launches the on-line reference for the Hot-Spot
   Editor.

   Windows Socket Reference:    \BC4\BIN\WINSOCK.HLP
   This icon launches the on-line reference for Open
   Interface for Network Programming under Microsoft
   Windows. Windows Sockets is an independent
   specification which defines a network programming
   interface for MS Windows. 

   BCW and Library Reference:   \BC4\BIN\BCW.HLP
   This icon launches the on-line reference for Borland C++
   for Windows.

   ObjectWindows Reference:     \BC4\BIN\OWL.HLP
   This icon launches the on-line reference for
   ObjectWindows.

   Windows API Reference:       \BC4\BIN\BWINAPI.HLP
   This icon launches the on-line reference for Windows API.

   Resource Workshop Reference: \BC4\BIN\WORKHELP.HLP
   This icon launches the on-line reference for Resource
   Workshop.

   Winsight Reference:          \BC4\BIN\WINSIGHT.HLP
   This icon launches the on-line reference for WinSight.

   Winspector Reference:        \BC4\BIN\WINSPCTR.HLP
   This icon launches the on-line reference for WinSpector.

   Creating Help:               \BC4\BIN\CWH.HLP
   This icon launches the on-line reference documents that
   tell you how to create an on-line Help system using the
   Microsoft Windows 3.1 Help compiler and application
   called "WinHelp".

   Master Index:                \BC4\BIN\MINDEX.HLP
   This icon launches the master index to all of the printed
   manuals that come with BC++ 4.0.


SECTION -9-  LAN WINDOWS CONFIGURATION

BC++ 4.0 provides a LAN Windows Configuration option during
installation. This option must be used when you run Windows
from a network or plan to install BC++ 4.0 to a network.

If you run Windows from a network, this option is required
because access to the WINDOWS\SYSTEM directory is usually
read-only. If you plan to install BC++ 4.0 to a network,
the LAN Windows Configuration option centralizes the
location of these files to a location on your hard disk that
can be read from and written to.

The LAN Windows Configuration option places the following files
normally installed to the WINDOWS\SYSTEM directory
in the BC4\BIN subdirectory.   

BW32000C.DLL       BW320007.DLL  
BW320009.DLL       BWCC.DLL      
BWCC000C.DLL       BWCC0007.DLL  
BWCC0009.DLL       BWCC32.DLL     
CTL3DV2.DLL        CTL3D32.DLL   

You will want to ask your Network Administrator to move the
files above to the WINDOWS\SYSTEM directory to maintain standard
file locations.

If you are installing BC++ 4.0 to a network, you will also want
to use this option.  If users who will be running BC++ 4.0 from
the network copy the files listed above into their own 
WINDOWS\SYSTEM directory on their local machine, they can be
removed from the BIN directory on the network.  Otherwise, you 
must make sure that the BC4\BIN subdirectory appears in each 
path on each machine that will run BC++ 4.0 and those DLLs 
should remain in the BIN directory. For example, if you 
installed BC++ 4.0 to the network drive W:, then each machine 
that runs BC++ 4.0 should have W:\BC4\BIN in its path.

Note that selecting the LAN Windows Configuration option
will not automatically setup BC++ 4.0 to work on a network.
Additional configuration adjustments also have to be made
to your system. To find out more about network installations,
obtain Technical Information Document number 1738. Refer to
Section 10 on how to obtain this document.


SECTION -10-  HOW TO GET A TECHNICAL INFORMATION DOCUMENT
Technical Information Documents contain tips, techniques, 
and enhanced information on using Borland development tools,
and information on commonly asked programming questions.  
Such documents often include programming examples.  These
documents can be accessed via modem or fax.	 Technical
files which contain binary modules, such as patches for 
released Borland products, are normally available only from 
thos services that can be accessed by modem.  Documents can 
be accessed from the following sources:
 
A) Fax the document from Borland's TechFax Service.
   Call [phone] from a touch-tone phone. When
   prompted, enter your FAX number, then enter the document
   number you want to receive. The document will be faxed to
   you shortly.

   Here is a list of common Technical Information Documents:
      * 3       General Catalog of All Documents Available
      * 649     General Protection Faults
      * 1171    Problem Report Form
      * 1010    Installing and Configuring BC++
      * 806     Network Installations
      * 738     Memory Corruption
      * 1561    Clean Boot

B) Download the document from:
   -The Borland Download Bulletin Board Service (DLBBS)
    [phone], protocol 8N1
   -The Borland Automated Online Service (OAS)
    [phone], protocol 8N1
   -The Borland-supported FTP site on Internet
    ftp.cica.indiana.edu, IP address [129.79.20.27]
   -Borland-supported forums on CompuServe, Genie, BIX.
     for CIS type: go BCPPWIN 
                     or
                   go BCPPDOS 
                   and choose library 2
     for BIX type: join Borland 
     for GENIE type: Borland
 
   Below are steps to download a Technical Information
   Document from the Borland DLBBS.

   For proper display, your communication software should
   provide ANSI terminal support. Most packages provide
   VT-100 terminal emulation, which is fine for the DLBBS.
   If you're using a Windows based package, select a screen
   font (such as: Terminal) that includes extended ASCII
   characters.

   Once connected, you'll be prompted to enter your first
   and last name and a password. If you haven't used the
   service before, you'll be asked to verify your name and
   then answer a few questions. The menu-driven system
   guides you through the various product and file
   areas. You'll always receive a list of options when you
   are prompted to make any choice.

   MANEUVERING THE MAIN MENU
   First join the C++ Conference.  The Main Menu shows the
   product whose files you can access. At the Main menu, 
   type "F" to select the Files	menu.

   DOWNLOADING FILES
   Once you know the name of the file you want to download,
   type "D" for download at the File menu. When prompted,
   type the full name of the file or files. All Technical
   Information Documents have the form "TI#.ZIP". Replace
   the # with the appropriate document number. For example,
   to download Technical Information Document number 649,
   the full name of the file is TI649.ZIP.  If you do not
   know the protocol or download keys to press, refer to 
   your telecommunications manual.

   WORKING WITH DOWNLOADED FILES
   Most of the files on the Download BBS are stored and
   transferred in an archived (compressed) format and need
   to be unarchived before they can be used. If you don't
   have the unarchiving utility PKUNZIP v.204G or newer,
   download PKZ204G.EXE from the DLBBS and execute it.
   You'll receive PKUNZIP and PKZIP utilities. To unarchive
   the file, type the name of an unarchive utility
   (UNPACK, UNZIP or PKUNZIP) and then the name of the
   archived file. For example:
        PKUNZIP TI649.ZIP


SECTION -11-  BOOT CLEAN
This section describes the process of "booting clean" on
IBM PC's and compatible computers with DOS and/or windows.
This document assumes you have MS-DOS version 5.00 or higher.
"Booting Clean" is the process of booting without loading
device drivers and TSRs.  Device drivers such as mouse 
drivers, network drivers, TSRs, etc. can cause memory 
conflicts.

These device drivers and TSRs are usually loaded in two
files (AUTOEXEC.BAT and CONFIG.SYS typically located on
the root directory of your hard disk). The safest
method of booting clean is to create a "bootable" floppy
disk in drive A:. See the "Making a Boot Disk" section
below.

If you are using a program that runs under Microsoft
Windows, then you might need to make changes to some Windows
configuration files in order to ensure a "clean system
configuration" under Windows. The two files you will need
to examine are WIN.INI and SYSTEM.INI. These files are
located in the WINDOWS subdirectory on your hard disk. The
changes that you will need to make to these files (if any)
are outlined below. 

Making a Boot Disk
In order to make a bootable floppy disk, follow the
instructions below.  NOTE: These instructions assume that
your hard disk is C: and your DOS and WINDOWS subdirectories
appear on this disk. (Most cases)
     1) Place a blank disk in drive A:
     2) type  format a: /s (format the disk)
         
At this point you now have a bootable floppy disk.  Using
EDIT, ensure your AUTOEXEC.BAT and CONFIG.SYS look like
one of the configuration choices below. 

Your "clean" system configuration should be exactly like
one of the choices below except replace "<Insert REQUIRED
drivers here>" with any required drivers. The ONLY
required drivers are, for example, disk compression and/or
hard disk access drivers. This does not include mouse
drivers and disk caching utilities such as SmartDrive.

Clean Configuration DOS 5.0 and DOS 6.x running Windows
-----------------------------------------------------------
   1) Insert your "bootable floppy" in drive A:
   2) Type  edit A:\CONFIG.SYS
   3) Type in the following:
          <Insert REQUIRED drivers here>
          DEVICE=C:\DOS\HIMEM.SYS	 
          FILES=40
          BUFFERS=40
   4) Exit the editor (Alt-F, then X, then Y)
   5) Type  edit A:\AUTOEXEC.BAT 
   6) Type in the following:
          <Insert REQUIRED drivers here>
          PATH=C:\WINDOWS;C:\DOS;C:\BC4\BIN
          PROMPT $P$G
   7) Exit the editor (Alt-F, then X, then Y)
   8) type  CD \WINDOWS
   9) type  copy WIN.INI WIN.BAK
  10) type  copy SYSTEM.INI SYSTEM.BAK
  11) type  edit WIN.INI
  12) Make sure that the "load=" and "run=" lines in your
      WIN.INI file look like the following:
          ------------
          [windows]
          spooler=yes
          load=
          run=
          Beep=yes
          ------------
  13) Exit the editor (Alt-F, then X, then Y)
  14) type  edit system.ini
  15) Ensure that your "shell=" line in your SYSTEM.INI file
       looks like the following:
          ------------
          [boot]
          shell=progman.exe
          ------------
  16) Exit the editor (Alt-F, then X, then Y)
  17) Make sure your "Bootable floppy" is in drive A: and
      reboot your computer.

-------------------END OF FILE INSTALL.TXT------------------