This file details changes made to SETUPWIZ.EXE after Visual Basic 
version 3.0 shipped.

To check the internal version number of your SETUPWIZ.EXE, open a copy
of the file in an editor, and search for the string "ver:" This will
show the version number. Visual Basic version 3.0 for Windows shipped
with SETUPWIZ.EXE version 1.00.532.

VERSION      BUGS FIXED
---------------------------------------------------------------------
1.00.533     When using "Save Template", you must enter a file name
             with extension.  The extension is no longer required.
1.00.533     The "max" setting for the horizontal scrollbar on the Step
             Five screen is so large that the middle button of the scroll
             bar really can't be used. The max has been reset to a smaller
             value.
1.00.533     The standard command .PIF file may not have the EXECUTION =
             EXCLUSIVE on some computers. As a result, the DOS shells for
             compressing files may sit in the background. Now shell with
             parameter makes the task active with focus.
1.00.534     Minor tweaks to the user interface to widen the TEMPLATE
             buttons, added an accelerator to the R in Rebuild, and changed
             the accelerator in Exit to the 'x' key.
1.00.535     Start SetupWiz. Enter C:\. Click NEXT. This causes an
             untrapped error: "Path/file access error".
1.00.536     Removed line FILE10=OLE2UI.DLL under the [MSOLE2.VBX]
             section in SETUPWIZ.INI.
1.00.536     Try using Setup Wizard to create setup disks for the
             OLE2DEMO sample application after removing the OLE2UI entry
             from SETUPWIZ.INI. In step 2, select OLE. The Next button
             doesn't work. The Back button does work, and the Next button
             works if nothing is selected in step 2. The Finish button also
             works. This problem affected any OLE application.
1.00.537     Selecting more than 40 files with the Common Dialog during
             ADD FILES was not handled before. Now it is.
1.00.538     Cleaned up the MSOLE2.VBX and OLE Automation sections in
             SETUPWIZ.INI.
1.00.539     A PATH pointing to non-existing directories or drives resulted
             in a "User-defined error". Now Setup Wizard returns the
             correct error message and continues.
1.00.542     Fixed compression problems when running under Windows NT.
1.00.543     Fixed an invalid keyword in some common dialogs that asked
             where a file is located.
1.00.543     Fixed a problem if a template's .EXE file was deleted or moved.
1.00.544     SetupWizard incorrectly added VER.DL_ to the SETUP.LST file.
             Setup Wizard no longer adds this file to SETUP.LST.
1.00.545   SetupWizard will always add DDEML.DLL to SETUP.LST (Needed
           for Win 3.0).
1.00.545   SetupWiz.ini, added two files to the CRYSTAL.VBX section.
1.00.546   Fixed problem where after adding files in step 5, you can get
           a "File not Found" or "Compress error".
1.00.546   Fixed problem where after deleting your project's EXE
           (ie MYAPP.EXE) you would get an "Illegal function call in 
           CreateVBSetup1".
1.00.547   Fixed problem where you have MYAPP.EXE in same dir as MAK file,
           and PATH= in MAK file points to different drive.  Thus wrong
           file was added to list.
1.00.548   Fixed problem when a compressed file is larger than 1.2 meg.
           NOTE: this fix also requires 4 changes in the SETUP1.MAK project.
1.00.548   Fixed problem when SETUP1.MAK has a VBX or DLL file.
1.00.548   Fixed problem where after adding multiple files, another 'point
           to a file' dialog came up asking for a support file location
           resulting in a path with no filename is listed in the file
           distribution box.

PROBLEMS/LIMITATIONS:

 - COMPRESS.EXE will take only a limited length command line. If
   SetupWizard is in a subdirectory that is nested too deep, COMPRESS will
   not work correctly. You will encounter a 'File does not exist' error when
   the file does exist. To work around this problem, move the SETUPKIT
   subdir up one or more directory levels until COMPRESS works.