1On Windows, please read this file using WordPad to format lines properly.
2
3This directory contains a short example on how to use the Win32 UnZip DLL
4with Visual Basic.  The example code consists of a simple dialog form and
5a standard module containing the interface code to call unzip32.dll.
6The code assumes that the unzip32.dll binary is available somewhere on the
7execution path. The easiest way to satisfy this rule is to keep a copy of
8unzip32.dll in the directory where the VB executable is stored, but if
9it's in the command path it should be found.
10NOTE: Whenever a VB program is run from the VB6 IDE, the "path of the VB
11executable" is the path where the IDE program file "VB6.EXE" is stored,
12NOT the storage directory of the VB project file (= result of the App.Path
13property accessed from within the VB program).
14
15The example code has been edited last with Visual Basic 6, but should be
16compatible with VB 5. To maintain compatibility with VB5 after having modified
17the example project in VB6, the project file has to be edited using a standard
18text editor (e.g.: Notepad), to remove the line specifying the "Retained"
19property.  This property line is not recognized by VB 5 and would prevent
20correct loading of the project in VB 5.
21
22This VB example makes use of the "Windows Common Dialogs" ActiveX control
23comdlg32.ocx, supplied with Visual Basic. Unfortunately, there are different
24revisions of this control available which are not binary compatible. In order
25to maintain compatibility of the source code with all available versions of
26comdlg32.ocx, the source files may have to be edited manually after the
27program has been saved from the VB environment on a system containing the
28latest release of comdlg32.ocx:
29
30Both vbunzip.frm and vbunzip.vbp should contain a reference line for the
31common dialog ocx reading like:
32Object = "{F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.1#0"; "COMDLG32.OCX"
33                                                 ^^^
34The important section of this line is the revision number "1.1" (marked by
35the "^^^" signs). On a system with a more recent version of comdlg32.ocx
36installed, this version number is updated to "1.2" (or higher) by VB
37automatically. This number has to be changed back to "1.1" manually,
38otherwise the example code can no longer be used on systems with old versions
39of comdlg32.ocx.
40
41When fetching the VB example code from the UnZip source distribution, one
42has to make sure that the files are stored in the correct "DOS/Windows-native"
43text format with "CR-LF" line endings. Visual Basic does not accept Unix style
44text format (LF line terminators) for Form class modules (*.frm) and the
45project file (*.vbp).  You may use unzip's -a option to convert the project
46on extraction. If this is a full source distribution, see the Where file for
47where to download the compiled unzip DLL for a specific platform which includes
48this example project in native format for that platform.
49
50For more information, see the comments within the VB source.
51