This page last updated March 19, 1996
Thanks for taking the time to check out the test drive version of ArchiveLib 2.0! This demo package gives you a chance to get some hands-on experience with ArchiveLib, and should help you decide whether it's the product you need.
The test drive version provides static libraries and DLLs that let you work with the following products:
The test drive library comes with some important restrictions, including:
These are only some of the restrictions. Please be sure to read LICENSE.TXT in your DOCS directory after you install the test drive library. You will find a full copy of the license agreement which governs your use of the library.
To install this package, first download ALTD201A.EXE into a temp directory. Executing the file will extract all the components needed to perform an installation. Once you have done that, run INSTALL.EXE, either from the console command line or from Windows. You will then be led through either a DOS or Windows installation program, which will place all the library components under a root directory, by default named TD201.
After installation, you will have a set of subdirectories that includes the following:
Building C and C++ (but not MFC!) examples in the EXAMPLES directory is done using the BUILD???.EXE and BUILD???.INI files appropriate to your compiler. Move to the directory that contains the libraries for your compiler, which will be B45, V1x, or V40. At that point, execute the BUILD???.EXE command without any arguments. The resulting display will show you which libraries you have access to under the test drive. A typical output line from BUILD???.EXE will look like this:
Models: 32 Bit Flat Model Console : FC, FCD 32 Bit Flat Model Windows : FW, FWD Windows DLL for Win32 : 20FW, 20FWD Console DLL for Win32 : 20FC, 20FCD 32 Bit Flat Model Windows : MFC, MFCD Windows DLL for Win32 : 20MFC, 20MFCD Windows DLL for VB4 32 bit : 20FVB, 20FVBD Test Drive Libraries : TDFC, TDFW, TDMFC, TDMFCD, TD20FVB
The libraries listed on the bottom line are the test drive libraries available for your compiler. Libraries that you can use to build C/C++ example programs are limited to:
You might see some other libraries listed on the last line (For example, the listing above contains TDMFC, TDMFCD, and TD20FVB), but they will be used with different types of examples.
The example programs for C and C++ are contained in the EXAMPLES directory. At this time, shipping examples include:
To build one of these programs, all you need to do is run BUILD???.EXE from the command line in the appropriate directory, using the following format:
BUILD???.EXE -exe libname full-example-path
A typical command line will look like this:
BUILDB45 -exe TDFC ..\examples\ex25con.cpp
Note that Windows examples come with many file components, so if you want to copy the examples to a specific directory, be sure to copy all the files the same name (and differing extension.)
The EXAMPLES directory also contains prebuilt versions of these example programs (in 16 bit models.) If you are having trouble getting your examples to work, you can try using the supplied executables as reference points.
At this time there is only one MFC example in the EXAMPLES.MFC directory. We ship a MAK file that contains all of the information needed to build the example using VC++ 4.0. To use this make file from your IDE, just Open|Project workspace, select file type of *.MAK, and open the appropriate makefile. You should be able to build the projects at that point. If you have changed the directory layout of ArchiveLib, you may need to modify your include path and library path information as well.
The MFC projects have a slightly modified directory structure, but they will still work with the environment and Class Wizard. The debug libraries work properly with the debug versions of MFC, but they do not contain any source debuggging information!
The EXAMPLES.MFC directory also contains a prebuilt version of this example program (in a 32 bit model.) If you are having trouble getting your examples to work, you can try using the supplied executable as reference points.
Using these example programs is just a matter of starting VB or Delphi, then opening the project in the correct directory. The required DLLs and support files are all in place. The following VB examples are provided:
Delphi programs have a different set of example programs to work with:
All the VB and Delphi examples have some online explanation that can be found by pressing the About button on the main form.
The HELP directory has a single file called GALSI.HLP. It has a complete description of the Simplified Interface for ArchiveLib 2.0. The simplified interface gives you a powerful set of tools to manipulate ZIP files, yet is limited to just eight functions. You should be up and running in no time!
You can get online support for the test drive version of ArchiveLib via email at support@gleaf.com or via CompuServe mail to 71333,106. You can also get support on our CompuServe forum via GO PCVENB.
To check for commonly encountered problems, you should check forum message and files in PCVENB before submitting your message. If you don't use CompuServe, check the ArchiveLib bulletins on our Web page at http://www.gleaf.com/~gleaf before submitting messages.
Finally, I would appreciate any positive or negative comments you have about the test drive. Please mail them to markn@airmail.net. I want to make ArchiveLib useful for you and profitable for Greenleaf. Your comments can help with both of these goals.
-Mark Nelson http://web2.airmail.net/markn