Index
WinSetup

Professional Installation Utility for Windows

Copyright 1993 by Money Smith Systems Inc.

All Rights Reserved

Index

Using WinSetup:

About WinSetup Description of WinSetup and Setup utilities.

Using WinSetup Using WinSetup and Setup to install your programs.

Installing Self-Extracting Archives Using archived installation options.

Multiple Disk InstallationInstalling from multiple disks.

Hints Special hints for giving your program a professional finish!

License InformationInformation on licensing.

Commands:

File New command Reset WinSetup fields.

File Open command Open an existing file.

File Save command Save current file.

File Save As command Save file to new file name.

File Exit command Exit WinSetup.


About WinSetup

WinSetup is a simple alternative to writing your own specialized installation program for Windows.  We license WinSetup and our Setup.exe program to authors, vendors and distributors for a reasonable fee to save them the time and effort of writing installation programs.

Step by Step Instructions:

Using WinSetup to install your own programs involves these four simple steps:

1. Create a sample distribution diskette with all of your distribution files on it.

2. Copy SETUP.EXE to the distribution diskette.

3.  Use the WinSetup program to create a SETUP.INF file on your distribution diskette.  Follow the instructions included in this guide when filling in the WinSetup dialogs.

4.  Run SETUP.EXE from your sample distribution diskette to test your installation.

WinSetup:

This program builds a configuration file called SETUP.INF on you installation diskette.  You specify the files to copy, where you want them installed, and which programs are to be installed in the Windows Program Manager.  The SETUP.INF file is then used by the actual SETUP program to install your files.

Setup.exe:

This program is the actual setup program to be tested for installing your programs.  You need to order a registered license before actually distributing SETUP.EXE with your programs.  Full details on ordering are in the README.TXT file.  You can also obtain custom installation programs logos or other customizations from us.  This program will run under either Windows 3.1 or Windows 3.0.

Related Commands:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


Using WinSetup

Using WinSetup to customize installation of your own programs is quite simple.  Follow the following procedure:

Procedure:

1.  Prepare a sample installation diskette with all of the files for your program.  If you need to include a self extracting archive to put your entire program on one diskette, copy this archive to the diskette.

2.  Copy the SETUP.EXE program to your sample diskette.  This is the installation program that users will run to install your program from diskette.   It is important that you leave SETUP.EXE, SETUP.INF and any documentation  files you want users to be able to view before installation uncompressed on the diskette.

3. Run the WinSetup program, filling in the fields as described below.  If you are using a self-extracting archive on your diskette, please refer to the section on Installing Self-Extracting Archives later in this document.  When you have entered all information, use the File Save command to save a file called SETUP.INF on your sample diskette.

4. Test your installation by running SETUP.INF from your diskette.  Check to see that all files were correctly installed on the hard drive, that documentation can be viewed correctly, and any self-extracting versions are correctly installed and unpacked.

Description of WinSetup fields:

When you run WinSetup a dialog will appear with the following fields and controls on it.  Default information will already be in the dialog to help guide you through installation.  You need to fill it in as follows:

Window Title: This string will appear in the title bar of the Setup Window when setup is run.  Usually you will want your company or program name as in 'Gizmo Installation Program'.

Destination Path:  This is the default path for installation of your program.  Typically this is a directory on the C:\ drive.  By default this directory is created on the drive if it does not exist.

Command to View Documentation: This is an optional command that lets a user view the documentation before installing the program.  Usually this command will invoke either the Windows notepad or write application to view a documentation file as in 'notepad readme.txt'.   It is very important that the documentation file be uncompressed on the installation diskette, since a user views the file before installing it.  Also - remember that the Windows notepad cannot be used to view large text files.  If you don't have a documentation file to view, leave this field blank and the documentation button will not appear.

Maximize Docs: If you check this button, the documentation command will be run maximized.

Disk XX of XX:  These two edit boxes can be used to specify individual disks in a multi-disk installation.  See the section on Multiple Disk Installationfor a description of installing from multiple disks.

Space Required: This box specifies the amount of space required to complete an installation of the program in kilobytes.  Setup will check for this amount of free disk space on the destination drive before installing the program files.  When using self-extracting archives, be sure to include the space needed to uncompress the files, since both compressed and uncompressed versions will be on the drive during decompression.

Files List:  This is a complete list of files to be installed from the diskette to the destination drive.  You can edit this list using the Add, Edit and Delete buttons described below.  When using a self-extracting archive installation, this list represents the unpacked version of the files.  See Installing Self-Extracting Archives for a full discussion of packed and unpacked file lists.

Add Button:  Press this button to add to the installation disk.  The program will bring up an Add Files dialog where you can select of type in individual file names.  HINT: If you are using Windows 3.1, you can select multiple files from the Add Files dialog box, hold down the Control or Shift key while selecting with the mouse.

Edit Button:  Select a file on the file list and then press this button to change the name of that file.  This will bring up a small edit dialog, where you can type in your changes.

Delete Button: Select a file on the file list, and press the delete button to delete this file from the list.

Self-Extracting Version:  Press this button to set up a separate file list for a self-extracting version, as well as specify the self-extracting file and command to extract.  See the section on Installing Self-Extracting Archives for a full discussion.

Group Name: The name of a program group in the program manager to install to.  This may be either an existing program group or a new one.

Group File Name: The name of the group file associated with the program group.  For a new program group, you may put any file name you choose, but the file name must have a .GRP file extension on it.

Executable: The name of the executable to install in the program manager.  This is typically the main program on the diskette.

Name of Program: This name will appear under the program icon in the program manager.  Usually it is the text name of the program as in 'My Program'.

Install Additional Programs: Brings up a list of additional programs to be installed in the program manager.  You may add to, edit, or delete from this list.  These programs will be installed in the same program group as the main executable listed above.

Pre-Install Command: Lets you specify a command to run when Setup first runs.  Generally vendors use this option to view specific documentation or display licensing information.  For example you might put "notepad license.txt" in this file to display a license or vendor file on your disk on startup.  If you don't want to run a command, leave this field blank.

Post-Install Command: This line lets you specify the program to run after installation is complete.  Most often you will want to put the user into your main program.  If you don't want a program run, leave this field blank.

Maximize Buttons: The two maximize buttons will run the pre-install and post-install commands respectively as maximized windows.

New Button: Shortcut for running the File New Command.

Open Button: Shortcut for the File Open Command.

Save As Button: Shortcut for the File Save Ad Command.

Related Topics:

Contents Index of help topics.

Installing Self-Extracting Archives Using archived installation options.

Multiple Disk InstallationInstalling from multiple disks.


Installing Self-Extracting Archives

WinSetup supports both a packed and unpacked file list.  The packed list may include a self-extracting archive file.  Having a packed list lets users easily install from a diskette, with the setup program unpacking the file and removing the archive from the hard disk.  Having support for an unpacked list lets the user install the program from a hard diskette in unpacked form.  Both forms are supported since many Windows shareware programs are packed on diskette, but may appear in unpacked form if downloaded from a bulletin board.  Setup dynamically determines which list to use based on the existence of the packed archive.

Procedure:

1. Run WinSetup, filling in the dialog as described in the section on Using WinSetup .

2. Use the main File list in WinSetup to record your complete unpacked file list.

3. Press the Self-Extracting Version button to bring up the packed file list.  Add all files that will appear in a packed diskette version to this file list using the Add, Edit and Delete buttons in this dialog.

4.  Place name of the self-extracting archive file in the Archive File Name field.  Be sure to include the extension (*.EXE) of the file as in 'MYARC.EXE'.

5.  Place an optional command to unpack the file in the Command to Unpack field.  If you include no command to unpack in this field, the program will run the Archive File Name by default.

Note: If you decide to later disable the packed file list option, simply delete all files from the packed file list and clear the Archive File Name field.

Note:When you have archives on multiple disk sets you can de-archive a file from each diskette.  Follow the procedure above when building each disk in the set.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


Multiple Disk Installation
Multiple Disk Installations

A multiple disk installation is done the same way a single disk installation is, except that each disk in the set has its own SETUP.INF file on it.

Essentially SETUP.EXE views multiple disk sets as one long install.  SETUP.EXE expects each diskette to have its own SETUP.INF file with the appropriate disk numbering as in "Disk 1 of 3", "Disk 2 of 3", "Disk 3 of 3".  SETUP.EXE begins the install using the first disk's (optional) documentation command and pre-install command.  Next SETUP.EXE uses the packed and unpacked file lists from each diskette's SETUP.INF file to install all files.  Finally SETUP.EXE uses the last diskette's SETUP.INF to determine which programs to install in the program manager and a post-install command to run, if any.  Because of the way SETUP.EXE handles multiple disks, only the first disk's documentation and pre-install commands are run and only the last disk's program manager and post-install commands are used.  All interim program manager information and pre- or post- install commands are ignored.

Note: Inactive fields will be greyed out in WinSetup as you edit each successive diskette.

Procedure:

1.  Copy the SETUP.EXE program to your first installation disk.  SETUP.EXE only needs to be put on the first diskette, as this is where the user will begin an installation.

2.  Use the WinSetup utility to build a SETUP.INF file for your first diskette.  In the fields where it says "Disk 1 of 1" enter in the correct number of total disks in your set.  For example if you have three disks in your set, enter "Disk 1 of 3" in these fields.  Enter any pre-install command and documentation commands on this disk, as the first disk is the only one that will use those commands.  Enter your file list and packed file list as appropriate.  Ignore the greyed out program manager information as SETUP will not install any files in the program manager until it reaches the last diskette.  Save the file SETUP.INF to your first diskette.

3.  Use WinSetup to build a SETUP.INF file on your second diskette with the list of files from that disk.  Include the list of packed and unpacked files on each disk and number each disk appropriately as in "Disk 2 of 3", "Disk 3 of 3" etc...

4.  When you reach your final diskette, include in the program manager section a list of all of the executables you want installed as well as any post-install command you want run.  When SETUP.EXE reaches this final diskette, it will use the final diskette's program manager list and post-install command.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


Hints and Tips

This section contains simple hints and tips on giving your installation a professional finish.  As always, be sure to carefully test your installation to make sure it works.

Multiple Select: If you are running Windows 3.1, you may select multiple files in the File Add dialog by holding down the control or shift key while selecting files with the mouse.  This is a great time saving feature when you are setting up a number of programs.

Built a SETUP.INF template: If you are a vendor who uses the same basic settings across a large number of files,  you can save time by building a SETUP.INF file that has your title, documentation, and other information in it, with no files.  You can then open this template file each time you go to configure a new disk.  This will save you the trouble of having to enter the same information over and over again.

Use the Pre-Install Command: To display information about your company, its license policy, and running information.  For example the vendor XYZ might want to run the command NOTEPAD XYZ.TXT on pre-install to display licensing information and installation instructions.

Use the Post-Install Command: To display program instructions, welcome messages, or run the program itself.  Often after installing a program the user wants to know what to do next.  Take this opportunity to help them get going!

Unpack with a PIF: If you don't like the way that some DOS self-extracting archives install by taking over the whole screen, you can create a program information file (PIF) to run your self extracting archive in a Window.  To do this, use the Windows PIF editor (see your Windows manual) to create a PIF file with the same name as your self-extracting archive.  For example, if your archive is named MYARC.EXE, you would create a PIF file called MYARC.PIF.  When creating your PIF be sure to set the command argument to be your archive command, and make sure that the current directory field is set to a single dot "." which corresponds to the current installation directory.  The PIF field for running in a Window should be checked as well.  Be sure that you include your PIF file in the list of files to install, and as always test the installation to make sure you have it right.  We also recommend testing any PIF installation under Windows 3.0 as well as Windows 3.1 since slight differences in PIF formats could cause problems.

Install Documents in Program Manager: You can install Write documents and short text files in the Windows program manager.  This gives the user an icon to click on to view your document files.  To do this, add the names of the files, including the *.TXT or *.WRI extensions to the list of files using the "Install Additional Files" button under the program manager installation section of WinSetup.  For example you might install the file MYPROG.WRI with a description of "MYPROG Manual".  This is an easy way for users to view your documents. An example is in the SETUP.INF included with WinSetup.


File New command

The File New command resets the WinSetup fields to their original state.  It will also ask you if you want to save an existing file before saving.

Procedure:

1.  Choose the File New command from the menu.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


File Open command

The File Open command opens an existing SETUP.INF file for editing.  Use this command to edit a SETUP.INF file you have previously saved.

Procedure:

1.  Choose the File Open command from the menu.

2.  Select the SETUP.INF file you wish to edit from the file list and press OK.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


File Save command

The File Save command saves an existing SETUP.INF file to the disk.  Use this command to save a SETUP.INF file after you have edited it with WinSetup.

Procedure:

1.  Choose the File Save command from the menu.

2.  If this is a new file, select a location for the SETUP.INF file from the directory list and press OK.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


File Save As command

The File Save As command saves a SETUP.INF file to the disk.  Use this command to save a SETUP.INF file after you have edited it with WinSetup.

Procedure:

1.  Choose the File Save As command from the menu.

2.  Select a location for the SETUP.INF file from the directory list and press OK.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


File Exit command

The File Exit command exits WinSetup.

Procedure:

1.  Choose the File Exit command from the menu.

Related Topics:

Contents Index of help topics.

Using WinSetup Using WinSetup with your programs.


Licensing Terms

WinSetup

Copyright  1993 by Money Smith Systems Inc.

All Rights Reserved.

Author: Bradley J. Smith

Obtaining registered licensed versions

You can obtain a registered licensed version of WinSetup from Money Smith Systems Inc. by remitting payment as described in the REGISTER.TXT file.  You can look at and print this file using the windows notepad application.  Site licenses are available - write for details.

License Agreement

This is a legal agreement between you (either individual or entity) and Money Smith Systems Inc, a corporation under the laws of the state of Texas.  If you have purchased a registered version and do not agree to the terms of this agreement, promptly return the disk and accompanying items within 90 days for a full refund.

Limited Distribution Rights

A limited license is granted to copy and distribute the unregistered shareware version ONLY of WinSetup and SETUP.EXE subject to the conditions below and the following:

1) No fee, charge or compensation may be accepted for distribution of WinSetup except:

A)   Time related usage fees for electronic bulletin boards not directly related to the downloading of this program.

B) Association of Shareware Professionals (ASP) member distributors may charge a nominal fee of no more than $7 to distribute this shareware version.

C)  Others wishing to charge a fee not provided for above can do so only with the express written consent of Money Smith Systems Inc.

2) No one may modify WinSetup  files, documentation, or executables in any way, including reverse engineering the program.

3) The full machine readable documentation, help files, executables, and examples must be included with each copy.

4) SETUP.EXE must not be used by any unregistered user as an installation utility for any other program or programs.

Registered Author's License

An author's license permits unlimited distribution of the SETUP.EXE and SETUP.INF files generated by WinSetup to serve as installation utilities for no more than 5 programs which the purchaser has written.  An author's license permits the purchaser to use WinSetup only on a single computer.  Licensed users may use the program on different computers as long as the program is not used on more than one computer at a time.   Site license  or network use requires a separate license.

Registered Vendor's License

A registered vendor licensee may distribute an unlimited number of copies of SETUP.EXE and SETUP.INF files generated by WinSetup to serve as installation utilities with their line of Windows programs as specified on the registration form.  Distributing a separate line of programs generally requires a new license.

Notice

WinSetup  is not and has never been public domain software, nor is it free software. Unregistered users are granted a limited single user license to use the shareware version of this product on a 30-day trial basis for the purpose of determining whether this program is suitable for their needs.  Use of WinSetup, beyond the initial 30-day trial requires registration.  Distribution of WinSetup as an installation utility also requires registration.  The use and distribution of unlicensed copies of WinSetup products outside of the initial 30-day trial without registration, by any person, business, corporation,  government agency or any other entity is strictly prohibited.

Limited Warrantee for Registered Users

Money Smith Systems Inc. warrants that the disks provided with the registered version of WinSetup are free from defects for a period of 90 days from the purchase date.  You may return defective disks to us for replacement or a full refund.  For refunds the complete package including documentation must be returned in a salable state.  Money Smith Systems Inc. also agrees to provide mail software support for a period of 90 days from the original purchase date.  Direct questions to Money Smith Systems Inc, P. O. Box 333, Converse, TX 78109.

LIMITATION OF LIABILITY:

MONEY SMITH SYSTEMS INC HEREBY LIMITS THEIR LIABILITY TO, AT MONEY SMITH SYSTEMS INC'S SOLE DISCRETION 1) THE ORIGINAL PURCHASE PRICE OF THE SOFTWARE OR 2) REPLACEMENT OF A DEFECTIVE DISK.  PURCHASER OF SOFTWARE AGREES NOT TO HOLD MONEY SMITH SYSTEMS INC OR ANY OF ITS DIRECTORS, OFFICERS, EMPLOYEES, OR REPRESENTATIVES LIABLE FOR ANY DAMAGES WHATSOEVER BEYOND ONE OF THE TWO REMEDIES DESCRIBED ABOVE.

Assign to Successor Clause

Purchaser of this software hereby agrees that Money Smith Systems Inc. may at any time without notice or consent of purchaser assign this license to a successor corporation, business, or heir.  Any rights, liabilities and warranties may be transferred at Money Smith System Inc's sole discretion along with this license to the successor corporation, business or heir.

GENERAL TERMS:

Use of this program for any period of time equates to agreement to all terms of this license.  WinSetup is only one possible tool for Windows Installation.  Money Smith Systems makes no warranty as to the suitability of this software for any particular purpose or application.  This software is provided  strictly AS IS.

EXCEPT AS PROVIDED ABOVE MONEY SMITH SYSTEMS INC DISCLAIMS ALL WARRANTIES WITH RESPECT TO THIS PRODUCT, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  SHOULD THE PRODUCT PROVE DEFECTIVE IN ANY WAY THE PURCHASER ASSUMES THE RISK OF SERVICING, REPAIR, CORRECTION, INCIDENTAL, OR CONSEQUENTIAL DAMAGES. (INCLUDING BUT NOT LIMITED TO DAMAGES RESULTING FROM INVESTMENT DECISIONS MADE, BUSINESS PROFITS LOST, INTERRUPTION OF BUSINESS,  LOSS OF INFORMATION AND THE LIKE) USING THIS SOFTWARE.

This agreement is governed by the laws of the state of Texas and shall inure to the benefit of Money Smith Systems Inc. and any successors, administrators, heirs, and assigns.  Any action or proceeding brought by either party against the other arising out of or related to this agreement shall be brought only in a STATE or FEDERAL court of competent jurisdiction located in Bexar County, Texas.  The parties hereby consent to personam jurisdiction of said courts.

Association of Shareware Professionals (ASP) Ombudsman Statement

"Bradley J. Smith is a member of the Association of Shareware Professionals (ASP).  ASP wants to make sure that the shareware principle works for you. If you are  unable to resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able  to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide  technical support for members' products. Please write to the ASP Ombudsman at 545 Grover Road, Muskegon, MI 49442 or send a CompuServe message via CompuServe Mail to ASP Ombudsman 70007,3536."

U.S. Government Domain Use

If you would like to use WinSetup for U.S. government domain use, please send a self-addressed stamped envelope to get information.  We intend to make a version of this program available for government domain use.

Acknowledgments

WinSetup, Money Smith and the Money Smith Calculator are trademarks of Bradley J. Smith.

IBM is a trademark of International Business Machines

Microsoft, Windows, Paintbrush, Notepad, DOS, Word, Excel are all trademarks of Microsoft Corp.

Borland C++ is a trademark of Borland International.

The Association of Shareware Professionals (ASP) is a non-profit group dedicated to the shareware profession.

PKZIP, PKUNZIP, PKSFX are all trademarks of PKWARE, INC.

Many thanks to Charles Petzold and Jeffrey Richter for their fine books and examples of Windows programming.

If I missed any other credits, it was unintended, so please write and I'll be sure to include them in future versions.