inst-bcb1.txt

zip算法的源码

TZipBuilder, for Borland C++ Builder version 1, 3, 4 , 5 and 6
Version 1.73
Original  by Chris Vleghert, [e-mail]
Latest adaptions by Roger Aelbrecht, [e-mail]

TZipBuilder is a translation of TZipMaster from Delphi to C++.
It is functionally identical in every way possible, but it has 
been coded in C++ to make it easier for C++ users to understand 
and modify.

I am going to use the term "BCB" to mean "Borland C++ Builder".

----------------------------------------------------------------------

Before You Start
----------------
You need to copy the redistributable modules to your desired
directory on your development computer.  

Copy \dll\*.DLL to your Windows System directory.
Copy \sfx\*.BIN to your Windows System directory.


Compiler Options
----------------

From version v1.70 there are compiler options that allow you to build
a smaller version of TZipBuilder. This means that certain options are
left out, making the final product smaller.

There are three options:

NO_SPAN : if this options is defined (or set) then the possibility of 
					spanning the archive over several disks (floppy disks) is no
					longer available.
					
NO_SFX  : if this options is defined (or set) then the possibility of 
          creating "self-extracting" archives is no longer build in 
          into the component, other components can still be used to 
          have the same result.
          
NO_STREAM : if this option is defined (or set) then the possibility of
         Zipping, unzipping data in streams is no longer provided.

INTERNAL_SFX : if this option is defined (or set) the old sfx code inside
				the component is included. Setting this option will un define 
				the option NO_SFX. This option is defined as default in ZipBuidler.h
        See also remark on internal sfx below
         
Any combination of these options is allowed.
Defining the options can be done by  uncommenting 
( = remove the '//' at the start of the lines) the lines with 
 the #define statements at the beginning of ZipBuilder.h  immediately 
  after the #include statements   
  
REMARK on INTERNAL SFX  
  
The use of the internal sfx code is not recommended. We strongly recommend the
use of an external package such as : 
- "TZipBuilderSFX" a plug-in for TZipBuilder that can be found at my web pages 
  http://web.wanadoo.be/driehoeksw				
- "ZipSFX" a Delphi package that works for both ZipMaster and ZipBuilder and
  can be found at http://www.mirkes.de/en/delphi/dzsfx.php
    

Installation
------------

This is one of the biggest freeware software releases for C++Buider and
Delphi.  To get going quickly and correctly, please follow these
instructions.  Read them over once before starting.  If you don't
understand a step, get help before you start the install!


1.  You HAVE TO install this package on a computer that has BCB.
    
2.  The files required to support the VCL are located in the
    VCL subdirectory.  You have two choices for how to proceed
    (option A is recommended):

      A) add the directory C:\...    \VCL to your VCL search path
         (C:\.. being the directory where you copied all files.)
                             or
      B) copy the files in \VCL to another directory
         already in your VCL search path

    If you want to use option A, the instructions for this are
    included below.  If you want option B, then please copy those
    files now.
  

3.  Install the VCL in C++ Builder:

    This procedure will install the VCL into the IDE.  After
    this, you will be able to see it on the "ZipComponents" tab.

      a) Select the "Component...Install" choice from the menu.

      b) Click on the Add button.
      c) Click on the Browse button.
      d) Select the path and filename of where the ZipBuilder.cpp 
         file is located. 
      e) Add the path where ZipBuilder.cpp is located to the
         Searchpath       (eg:  ;$(BCB)\YourPath  )
      f) Click on OK.  The component library will rebuild.
         If you have "warnings" enabled, you can get lots
         of warning messages not related to this new package.
         Ignore these


   If something went wrong:

     There is some instability in the code that builds
     the VCL library for version 1 of CBuilder. This is a
     manageable problem as long as you are aware of it.

     You must always keep a good copy of your component
     library on a floppy disk (or another hard disk directory)
     for safe keeping.  Sometimes, problems during the build
     of the VCL library can cause it to be corrupted, which
     then prevents CBuilder from even starting.

     The Component Library file is named 'CMPLIB32.CCL' and
     the Options file 'CMPLIB32.OPT'. These are in the 'bin'
     subdirectory under the main CBuilder directory.
  
     If the component library becomes corrupted, restore
     the automatic copy made by BCB of "CMPLIB32.CCL", named
     CMPLIB32.~CC and delete the temporary files in that
     directory: CMPLIB32.I* and CMPLIB32.TDS.  Now, go back
     into CBuilder and fix the problem that caused the library
     to become corrupted. (Just recompiling will probably enough).
     Sometimes it is also neccesary to restore the old version
     of 'CMPLIB32.OPT' Named: 'CMPLIB32.~OP'.
 
     If you have corrupted the automatic backup files BCB make
     you should restore them with your own saved versions.



                       C++ BUILDER HELP

Installation
------------
1) Copy ZipHelp.hlp and ZipHelp.cnt from \ZipBeta\Help
   to BCB's help directory.

2) In BCB's HELP subdirectory, edit BCB.cnt and add the
   following two lines to the appropriate sections in this 
   small file:
   :Index ZipBuilder Component Help=ZipHelp.hlp
   :include ZipHelp.cnt

3) If you want to see the component in the bookshelf, then:
   Edit BCBMain.cnt and add the following line:
   :include ZipHelp.cnt

4) Delete the *.FTS and *.GID files from the BCB Help
   subdirectory. This can be done easily from Explorer. 
   Make sure BCB is NOT running when you do this.
   If you want to do it from an MS-DOS prompt:
   C> del *.GID
   C> del *.FTS

5) The next time you use BCB's Help feature, it'll say
   "preparing help file for first use".  This is when it
   is rebuilding the .GID files to include the new Help topics.
   The next time you do a full text search in Help, it'll rebuild
   *.FTS files.

You now have context-sensitive help on the TZipBuilder
component inside the BCB IDE!


                       C++ BUILDER DEMO

Installation
------------
1.  The CDemo directory has sub directories one for BCB1, one for
    BCB3 specific files and so on. The files that are common
    to all environments are in the CDemoX directory.
    To install a demo you have to copy the files from the sub
    directory BCB1 to the CDemoX directory. Sometimes you will
    be asked to overwrite an existing file this is NOT an error
    and you should confirm the question.

2.  Important:
    a) You have to set the include and library path in your project,
       not only for the demo's but also for new projects.
       1) Open a project.
       2) Select the "Options...Project" choice from the menu.
       3) Select the Directories/Conditionals tab.
       4) Add to 'include path': The path where ZipBuilder.h is located.
       5) Add to 'Library path': the path where ZipBuilder.obj is located.
       6) Click on the Ok button.
       7) Save your project.

    b) The ZipBuilder component uses a language resource file for
       error and warning messages. This file must be linked into
       your project. (i.e. in your project source file.)
       This file must contain a statement like:
          USERC( "..\ZipMsgUS.rc" );
       Where ..\ is the path to this resource file.
       (normaly the directory which also contains ZipBuilder.h etc.)
    	

                    DESCRIPTION OF DEMO PROJECT

    Demo1 is a native C++ Builder port of the Delphi Zip Demo 1.
    This is a very complete File Manager type of program that lets
    you create archives, view archives, extract files, etc.  It can
    also turn .zip files into .exe files (and vice-versa).


                  Deployment of Your Programs

Any program you write using this package will require the two 
DLLs: ZIPDLL.DLL and UNZDLL.DLL to be present of each user's
hard disk.  You should have your install procedures put these
files into the WINDOWS SYSTEM directory (which is named differently
on some systems - especially WinNT systems).  If that isn't 
possible, then you should put them into the same directory as 
your .EXE program that uses them.

Also, the ZipSFX.BIN module must be installed into the same
directory as the DLLs.  This module is only needed if your
application program needs to make .EXE archives.

IMPORTANT: Any .EXE archives you make with this package do
NOT need any supporting files on the end-user's computer!
This is very handy!

Of course, there are no distribution fees for the DLLs, or
any other part of the package.  This whole package is 
freeware, but does have some minor distribution restrictions
(mainly that you can't profit from the ZIP DLLs, and you need
to document where users can get source code). Please see 
README.TXT and LICENSE in the help for these restrictions.