Copyright: © Copyright 1992 Robert Salesas


EDI Install Pro - User Manual

For information on how to use the Help system, press F1 or choose Using Help from the Help menu.

Basics

•	Introduction

•	Installation procedure

•	General INF information

•	Distribution

Advanced

•	File compression

•	File splitting

•	Custom DLLs

Reference

•	Sample INF file

•	INF Sections

Legal information

•	Copyright

•	Disclaimer

•	License agreement

•	Shareware concept

Order information

•	License registration

•	Order form

Company information

•	Product line

•	Upgrades

•	Contact Eschalon Development Inc.


Introduction

Welcome to EDI Install Pro for Windows!

This manual will guide you through the process of using and understanding EDI Install Pro, and how it can be of benefit to you.

What is EDI Install Pro?

EDI Install Pro is a complete installation utility that you can use "right out of the box". It allows your users to easily copy and set up your application on their system. With today's complex applications it is no longer enough to use a batch file to copy your files to their drives. Users demand friendly, easy to use utilities, that provide a simple and precise method of installing applications. This is especially true of Windows, a market so fierce that the first impression can make or break your product.

What does it do?

EDI Install Pro creates the proper directories, copies the files to be installed, creates the Program Manager group items, displays README.TXT files, plus much much more.

The user is always has control over the installation, but doesn't feel burdened by too much information. EDI Install Pro is easy to use by you and your customers, yet allows both of you great leeway in customization.

How does it work?

EDI Install Pro reads the file INSTALL.INF (refered to as an INF file from now on), which contains the necessary information describing the layout of your files on the distribution disks, as well as a variety of settings and options. To customize your installation process you simply modify the INF file to suit your application.

Unlike some other installers, there are no scripts to write nor new languages to learn. You just list your disk, directories, files, and you're off! But don't worry, you won't miss out on any features. EDI Install Pro is so complete, and so customizable, that almost anything you need can be easily accomplished.

With EDI Install Pro you won't spend days writing scripts, and your users won't be infuriated trying to set up your product. Trust EDI Install Pro and your installation hassles will disappear.


Installation procedure

EDI Install Pro is extremely easy to use. Your users will be asked a few simple questions and then the installation will begin. They will always have the choice to proceed or cancel the installation, at any point, if they feel uneasy about an operation.

User interaction

EDI Install Pro first asks the user for a destination directory, displays the minimum amount of free space required and advises the user if the selected drive doesn't have sufficient spce. Optionally, it allows the user to select which components to install.

Throughout the installation EDI Install Pro displays when a file is copied or a Program Manager group is created. This allows the user to feel comfortable with the installation process and not to worry about what is being done to their system. The only intervention required is when a new disk needs to be inserted. The user will be prompted for the disk and asked to continue the installation.

Aborting the installation

The installation process can be aborted at any time by choosing Exit Install or Cancel from any of the dialog boxes. EDI Install Pro will report that the installation was not completed and that the application should not be used in this condition. The files that have been created will have to be manually deleted. This is done as a precaution, since most users would not like the installer to deleting files from their drive.

Completing the installation

If the installation has been properly completed and the INF file specifies a Program Manager group , the user is asked whether or not it should be created. If Program Manager is not loaded, the group will not be created.

Finally, if a README.TXT file was specified, it will be displayed for the user to read. It is a good idea to include last minute, or very important information, that the user must be aware of before using your application.


General INF information

Below is some general information that you should keep in mind while preparing your installations.

Preparing the INF file

EDI Install Pro uses an INF file, typically named INSTALL.INF, to determine what needs to be done. The INF file is actually a compressed version of a file you prepare using a plain ASCII editor, such as Windows' Notepad. That file is typically named  INSTALL.TXT. To compress the text file, you use the INFCOMP.EXE utility, which can be found in the UTILS directory. You must only distribute the INSTALL.INF file, not the INSTALL.TXT file. For example, a typical editing session would consist of:

1.	Using Notepad to create the INF file.

2.	Saving the file as INSTALL.TXT to a working directory.

3.	Using INFCOMP.EXE to compress the file to the installation disk. It will automatically be named INSTALL.INF.

NOTE:	The unregisted version does not include INFCOMP.EXE. It expects INSTALL.INF to be a plain ASCII file. You should create your INSTALL.TXT file and then copy it to the installation disk as INSTALL.INF. Once you register, you will receive INFCOMP.EXE.

INF File information

The INF file is parsed very carefully and you must insure that everything is properly specified. Here are a few things to remember:

1.	You can use as many spaces as you want after the equal sign and they are simply ignored by EDI Install Pro.

2.	If you use extra spaces before the equal sign, EDI Install Pro will interpret them and it can cause problems.

3.	Any line that starts with a semi-colon is treated as a remark and is ignored by EDI Install Pro. Use it to document your INF file.

4.	If you don't use Notepad to create your INF file, you should make sure that your editor does not use a CTRL-Z character to terminate the file. EDI Install Pro will read beyond the CTRL-Z and report an error. To make sure you don't have any CTRL-Z characters at the end of your INF file, load it into Notepad and remove any little black squares at the end of the file. The black squares generally look like this: .

Debugging the INF File

You must remember that the INF file is like a program's source code. It needs to be tested and debugged under various conditions. We have used and tested the installation program thoroughly, and so far, to the best of our knowledge, there are no major bugs. Still, this only means that the installation program itself is safe, the INF file that you write can still contain bugs. Check that you have properly labeled the disks, that all files have the correct directories and disks, and you have checked that all compressed files are properly marked. If the user attempts to run a compressed file they will be angry when it doesn't work!


Distribution

Below are the general guidelines and rules for distributing your application.

Placing files on disk

Files on the distribution disks should be placed in such a way as to minimize disk swapping. Note that an INF file for low density disks will not be the same as one for high density disks. Since the high density disks can hold more files, you won't need as many disks. Keep this in mind when planning the INF file.

Required distribution files

When you have completed the INF file and you have created your distribution disks, you will need to copy INSTALL.EXE, INSTALL.BIN, INSTALL.INF, and optionally UNPACK.EXE or DUNPACK.EXE, to the first disk in your package. This disk should be clearly identified so the user can locate it easily. You might also consider writing a message similar to this, on the label:

INSERT DISK AND RUN INSTALL FROM WINDOWS.

NOTE:	You may not distribute PACK.EXE, DPACK.EXE, INFCOMP.EXE, or your INSTALL.TXT with your package. Only the files listed above may be distributed. Including other files is a violation of the license agreement.

Using a Readme file

We suggest you add a README.TXT file to your disk and include something like the following passage, to let customers know about the compressed files:

The executable and library files in this package are compressed. If you don't use the installation program or you need to copy one of the original files onto your hard disk, use the UNPACK.EXE file located in the WinCLI Pro directory or on the diskette.

Renaming INSTALL.EXE

If you prefer to name the installer something else, such as SETUP.EXE, you can do so using the DOS RENAME command or with Windows' File Manager. For example, to change the installer to Setup, you would rename the files INSTALL.EXE, INSTALL.BIN, and INSTALL.INF, to SETUP.EXE, SETUP.BIN, and SETUP.INF. Remember, you must rename all three files, or the installer won't be able to locate the proper files. Also, note that the extensions on all three files must remain the same. Only the base name can change.

Modifying resources

Both INSTALL.BIN and UNPACK.EXE may be modified using a resource editor, such as Borland's excellent Resource Workshop or Whitewater's Resource Toolkit. With them you'll be able to change any of the strings, the fonts used in the dialogs, and even the dialog layouts themselves. The only thing you are not allowed to change, is the special About dialog box and copyright labels. The About dialog is a "secret" dialog box that only appears if you press ALT-I at the main dialog (secret in that the user never gets to see it).

To modify INSTALL.BIN you will have to uncompress it, modify it, and then re-compress and rename it. Follow these steps and you'll have no problems:

1.	Using UNPACK.EXE, uncompress INSTALL.BIN to a separate temporary directory. The uncompressed file will be named INSTALL.EXE. Don't confuse this with the other, smaller file, of the same name. That's why you must uncompress to a different directory.

2.	Modify the resources using the resource editor of your choice.

3.	Compress the file, INSTALL.EXE, using PACK.EXE. It will create a new file name INSTALL.EX$.

4.	Finally, rename INSTALL.EX$ to INSTALL.BIN, and copy it to the original directory.

That's it! You now have a customized installer. You could use this technique to create French, Spanish, German, etc., installers for your different international markets.

NOTE:	When modifying any file, make sure you have a backup of the original. You must never modify the original file, or you won't have anything to revert to if you make a mistake.


File compression

EDI Install Pro supports a reasonable compact and very fast, file compression method. File compression is an integral part of EDI Install Pro, and is therefore very easy to use.

Advantages of compressed files

Compressed files require less space on the disk and generally take less time to copy, since the CPU usually decompresses faster than the disk drive can transfer the original file. This allows you to use fewer disks, especially if you have a lot of large data files, and decreases the installation time.

Compressing a file

Included with EDI Install Pro is a file compression utility. The Windows utility PACK.EXE, and its DOS counterpart DPACK.EXE, can be found in the UTILS directory. With it you can compress any of your product's files. When you compress a file, the name is changed by adding one or more dollar signs ($) to the extension. The original name is stored in the file. When you install the application, the real name is extracted and used for the creation of the new file. In the files section, you must specify the name of the compressed file and not the original name.

Manually decompressing a file

Compressing the files saves a lot space and reduces installation time. However this has one big disadvantage - the files may not be manually copied to the drive, as they are useless if not decompressed. Sometimes your users are going to want, or need, to extract only few files.

It would be very incovenient to redo the installation just for one or two files. To resolve that problem we supply you with a distributable unpacking utility, UNPACK.EXE, and its DOS counterpart, DUNPACK.EXE. Since UNPACK.EXE is a Windows application, it is simpler and more convenient to use then the typical DOS command line utilities supplied with most installation programs, including DUNPACK.EXE. However, the DOS version is much smaller, and therefore more attractive when space is limited.


File splitting

EDI Install Pro supports file splitting, allowing you to place very large files across mutliple disks.

Advantages of splitting files

If you have a file that will not fit on one disk, you don't usually have many options. You can use a larger disk, but that still limits you to 1.44 Mb with a high-density 3½" disk. EDI Install Pro includes a special utilty to split files across multiple disks, thereby removing the limit on file sizes.

Disadvantages of splitting files

Currently, splitting files has one big disadvantage, but only if you compress the file as well as split it. If you compress the file, it will have to be joined to a temporary file before it can be decompressed. This means that the user must have enough free space for the installation, plus for the largest compressed split file. One easy solution to this problem is to install the compressed split file first. This will leave a lot of space available for the temporary file, since most files have not yet been installed.

Splitting a file

Included with EDI Install Pro is a file splitting utility. The DOS utility, SPLIT.EXE, can be found in the UTILS directory. With it you can split any of your product's files. When splitting a file, the name is changed by adding a number to the extension. The original name is stored in the file. When you install the application, the real name is extracted and used for the creation of the new file. In the files section, you can specify the name of the first split file or the original name, it doesn't matter.

Manually joining a file

There is currently no way to manually join a split file. Once the file is split, the only way to put it together again is using the installer.


Custom DLLs

EDI Install Pro supports custom DLLs to expand the available capabilities and to tailor itself to almost any installation's needs. By creating routines to handle special parts of your installation (such as extra setup information or copying specially encoded files), you can completely customize EDI Install Pro without having to write your own installer.

Using DLLs, there's very little that EDI Install Pro can't handle. Custom DLLs expand your possibilities and personalize your installation. Plus, since the DLL can be written in almost any language, you don't have to learn to program in some strange new script language, as with many other installation utilities.

For more information on creating a custom DLL, see the INSTLIB.PAS and INSTLIB.C files. The example files are in Turbo Pascal for Windows and Borland's C++, but a DLL can be written in any language that supports creation of DLLs.

If you aren't too sure about what you need to do or you don't want to write the DLL yourself, we can often create a custom DLL for a reasonable fee.


Sample INF file

Below is a sample INF file for EDI Install Pro.

; WinCLI Pro V1.0 - Installation Script

; Eschalon Development Inc.

[Application]

Name=WinCLI Pro

Title=WinCLI Pro - Installation

Background=Dithered

Bitmap File=INSTALL.BMP

Install DLL=INSTLIB.DL$ Y

Directory=C:\WINDOWS\WINCLI

Free Space=1070

Files Total=750

PM Group=WinCLI Pro

ReadMe=README.TXT

[Components]

1="Applications & Utilities" 680

2="Documentation & Help"     270

3=Extras                     120

[Directories]

1=Extended

2=Extras

3=Extras\C

4=Extras\Pascal

[Disks]

1=WinCLI Pro Disk #1

2=WinCLI Pro Disk #2

[Windows Files]

WinHelp=WINHELP.EX$               1 0 1 C C

WinHelp Help=WINHELP.HL$          1 0 1 C C

[System Files]

Custom control library=BWCC.DL$   1 0 1 C C

[Files]

ReadMe text file=README.TXT       2 0 1 N A

WinCLI Pro=WINCLI.EX$             1 0 1 C A

Control Panel=WCLICTRL.EX$        1 0 1 C A

WCLIUtls library=WCLIUTLS.DL$     1 0 1 C A

WCLIExts library=WCLIEXTS.DL$     1 0 1 C A

WinCLI Pro help=WINCLI.HLP        2 0 1 N A

Control Panel help=WCLICTRL.HLP   2 0 1 N A

WC FileApp help=FILEAPP.HLP       2 0 1 N A

WC FileApp=FILEAPP.EX$            3 2 1 C A

WC SysInfo=SYSINFO.EX$            3 2 1 C A

WC Drives=DRIVES.EX$              3 2 1 C A

WC ClkSvr=WCCLKSVR.EX$            3 2 2 C A

WC ClkSvr - Hook=WCCSHOOK.DL$     3 2 2 C A

WC Password=PASSWORD.EX$          3 2 2 C A

WC CalcApp=CALCAPP.EX$            3 2 2 C A

STUtls - DLL=STUTLS.DL$           3 3 2 C A

UUCode - DLL=UUCODE.DL$           3 4 2 C A

[INI Files]

1=WIN.INI "WinCLI Pro" Directory %%

2=%%\WINCLI.INI Settings Advanced True

[PM Group]

WinCLI=1 %%\WINCLI.EXE

ReadMe=2 "NOTEPAD.EXE %%\README.TXT" NOTEPAD.EXE

Help=2 "WINHELP.EXE %%\WINCLI.HLP"

WCLICtrl=3 WCLICTRL.EXE WCLICTRL.EXE 3

Related topics

•	INF Sections


INF Sections

The INF file is separated into various sections that control different aspects of the installation process. By modifying them you configure EDI Install Pro for your own application.

Section	Description

Application	This section contains basic information about your application and the installation.

Components 	This section lists the names and sizes of the file components (sets or groups of files) that the user has the option of installing.

Directories 	This section lists the names of the directories required for the installation.

Disks 	This section lists the names of the disks required for the installation.

Files,

Windows Files,

System Files 	These sections lists all the files that EDI Install Pro must copy to the user's drive.

INI Files 	This section lists entries for EDI Install Pro to create or modify in .INI files on the user's system.

PM Group	This section describes the Program Manager group that EDI Install Pro will create.

Related topics

•	Sample INF file


Application section

The Application section contains basic information about your application and the installation.

Section contents

An application section must contain at least the following fields: Name, Title, Directory, Free Space, and Files Total. The other fields are optional. A complete section would look like this

[Application]

Name=WinCLI Pro

Title=WinCLI Pro - Installation

Background=Dithered

Bitmap File=INSTALL.BMP

Install DLL=INSTLIB.DL$ Y

Directory=C:\WINDOWS\WINCLI

Free Space=1070

Files Total=750

PM Group=WinCLI Pro

ReadMe=README.TXT

A minimal section would look like this

[Application]

Name=WinCLI Pro

Title=WinCLI Pro - Installation

Directory=C:\WINDOWS\WINCLI

Free Space=1070

Files Total=750

Application entries

The following table describes each of the entries available in the Application section.

Entry	Description

Name	The name of the application that is to be installed. The name appears in portions of the text and in some dialog boxes.

Title	The title that should appear in the caption of every dialog box. Typically this will be "Application Name - Installation".

Directory	The default directory where you want the application to be installed. The user may change this by specifying a different drive and directory.

PM Group	The name of the Program Manager group to create. This entry is optional and is only required if you want EDI Install Pro to create a group. If you don't want a group created, don't include this label or leave it blank.

Free Space	The amount of free kilobytes required for the installation. This amount should equal the total size of all the files to be installed, uncompressed, plus whatever extra operating overhead is required.

Files Total	The total size of all the files to be installed, in kilobytes, in which ever way they are stored on the diskettes (compressed or uncompressed). The progress meter dialog uses this information to determine what percentage of the installation has been completed.

Background	The type of background to use for the installation. You may use the following values:

NONE	Will not display a background.

DITHERED	Will display the familiar dithered blue background seen in many Windows installations.

BITMAP	Will display a centered bitmap file as specified in the Bitmap File field

This entry is optional. If you don't specify a value, it will default to Dithered.

Bitmap File	Specifies the bitmap file to use for a background if Dithered or Bitmap are used in Background.

If Dithered is specified for Background, then the bitmap file should be a black and white logo to display at the top of the screen. The image is inversed so that the black becomes white and the white becomes invisible.

If Bitmap is specified for Background, then the bitmap file can be any 16 color image. The file should be run-length encoded to save space (Note: Paint Brush does not support RLE files - use Borland's Resource Workshop).

This entry is optional. If you don't specify a value, and Background equals Dithered or Bitmap, it will default to INSTALL.BMP.

Install DLL	Specifies a custom DLL for EDI Install Pro to call. The entry consist of two fields - the DLL's file name and whether or not the file is compressed.

If the compressed field is "Y", EDI Install Pro will decompress the file as it is copied. If the value is "N", it will simply copy the file without decompressing it. If the file is compressed, you should specify the name with the appropriate "$" extension (example: INSTLIB.DL$). See the INSTLIB.PAS and INSTLIB.C files for more information. This entry is optional.

ReadMe	Specifies a text file to be displayed once the installation has been completed. Note that the font used is proportional, not monospaced. If you use a standard editor to do formatting, it will not look right under the built-in viewer. This file must be copied to the users drive if you wish to have it displayed. The file must be under 16 000 bytes large. This entry is optional.

Debug Mode	This is a special option that sets a debug mode on or off. When this value equals one (1), EDI Install Pro will not actually copy the files, instead it will just pretend to do so. This is useful when you have a long INF file to debug and you don't wish to wait uselessly. Make sure you either omit this field or set it to zero (0) before shipping, or your files will not be copied.

Related topics

•	Sample INF file

•	Components

•	Directories

•	Disks

•	Files

•	INI Files

•	PM Group


Components section

The Components section lists the names and sizes of the file components (sets or groups of files) that the user has the option of installing.

You do not need to include this section unless you want the user to be able to do a partial or selective installation. This is very practical with large applications, as the user can choose to install only what he needs. If this section is omitted from the .INF file, the components button of the main dialog, is not displayed during the installation.

Components entries

Each entry consists of an integer number (1 to 32000); an equal sign; the description of the component; and the size, in Kilobytes, of the component. For example,

[Components]

1="Applications & Utilities" 680

2="Documentation & Help"     270

3=Extras                     120

Component numbers

The numbers are only used internally and need not be consecutive, although it makes more sense to do so (for example: 1, 2, 3, 4, 5; rather than: 1, 45, 33, 56, 78).

Using spaces in description

Any time that you wish to use a space or a tab for anything other than separating fields, you should enclose the field in quotation marks. For example,

1="Applications & Utilities" 680

Size of component

The size of the component should be specified in kilobytes. This value should equal the size of all the files belonging to this component, plus whatever extra operating overhead is required. The total size of all components should match the Free Space entry in the Application section.

Related topics

•	Sample INF file

•	Application

•	Directories

•	Disks

•	Files

•	INI Files

•	PM Group


Directories section

The Directories section lists the names of the directories required for the installation. EDI Install Pro will attempt to create the directories as required by the installation. Only directories that are required for a file to be copied, will be created.

EDI Install Pro uses this information to determine which directory on the distribution diskette contains the file and to which directory, relative to the destination, the file is to be copied. The path is always relative to the source and destination, which the user specified.

Directories entries

Each entry consists of a number (1 to 32000); an equal sign; and the name of the directory. For example,

[Directories]

1=Utility

2=Samples

3=Samples\Pascal

4=Samples\C

Directory numbers

The numbers are only used internally and need not be consecutive, although it makes more sense to do so (for example: 1, 2, 3, 4, 5; rather than: 1, 45, 33, 56, 78). Number zero (0) is reserved and specifies the root directory. You can use zero (0) in the files section whenever you need to specify the destination directory itself. For example,

WinCLI Pro=WINCLI.EX$	1	0 1 C A

↑ Directory

would place the WINCLI.EXE file in the user specified destination directory.

Related topics

•	Sample INF file

•	Application

•	Components

•	Disks

•	Files

•	INI Files

•	PM Group


Disks section

The Disks section lists the names of the disks required for the installation.

When EDI Install Pro cannot find a file on the currently inserted disk, it will prompt the user to insert the appropriate disk. The user has the option of changing the source path each time EDI Install Pro prompts for a new disk.

Disks entries

Each entry consists of an integer number (1 to 32000); an equal sign; and the name of the distribution disk. For example,

[Disks]

1=WinCLI Pro Disk #1

2=WinCLI Pro Disk #2

Disk numbers

The numbers are only used internally and need not be consecutive, although it makes more sense to do so (for example: 1, 2, 3, 4, 5; rather than: 1, 45, 33, 56, 78).

Disk names

The disk name should be chosen so that it helps the user recognize which disk to insert. Preferably the name will be printed on the disk in such a way that the user can see it easily. They do not have to be the disks' DOS label.

Related topics

•	Sample INF file

•	Application

•	Components

•	Directories

•	Files

•	INI Files

•	PM Group


Files section

The Files section lists all the files that EDI Install Pro must copy to the user's drive, in the specified destination directory. The Windows Files section lists all the files that EDI Install Pro must copy to the users WINDOWS directory. The System Files section lists all the files that EDI Install Pro must copy to the users SYSTEM directory.

The Windows Files and System Files sections are typically used to install files such as Microsoft's Visual Basic VBRUN100.DLL or Borland's Resource Workshop BWCC.DLL.

Files entries

Each entry consists of a description, an equal sign, and 6 fields describing the file to be copied. The description is displayed in the progress dialog box, indicating which file is currently being copied. It may contain spaces, commas, quotes, and other special characters, except an equal sign.

Entry fields

The 6 fields in a Files section entry are: File name, Component, Directory, Disk, Format, and Version checking. All the fields are required and must appear in the correct order, described below.

WinCLI Pro	=	WINCLI.EX$	1	0	1	C	A

↑ File name	↑ Version checking

↑ Format

↑ Disk

↑ Directory

↑ Component

The following table describes each of the fields in a Files section entry.

Field	Description

File name	The exact name of the file to be copied, as it appears on the disk. Do not specify the path. If the file is compressed, you should specify the name with the appropriate "$" extension (example: FILENAME.EX$). EDI Install Pro will automatically create the destination file with the original name.

Component 	The component number that this file belongs to. A file will only be copied if the component was selected by the user. If you don't include a Components section, you can specify zero (0) as the component number. An item with zero (0) as the component will always be copied, regardless of what the user selects.

Directory 	The directory number that contains the file to be copied. The source path is constructed by combining the source directory, this directory, and the file name. The same process is used to construct the destination path.

Disk 	The disk number that contains the file to be copied. EDI Install Pro first attempts to read the file in the current disk and if the file cannot be located, it prompts the user to insert the specified disk.

Format	Specifies the current format of the file. The following formats are supported:

C	File is compressed and should be decompressed during installation. If you attempt to decompress a file that was not compressed using the included PACK.EXE utility, an error will be reported.

N	Copy the file normally, without decompressing it. No error is reported if a compressed file is copied without being decompressed.

S	The file is split and should be joined during installation.

SC	The file is split and compressed, and should be joined and decompressed during installation. A split and compressed file will first be joined to a temporary file, and then decompressed to the destination. This will require more free space on the users disk.

To split a large file across multiple disks you must use the SPLIT.EXE utility included in the UTILS directory. Once you have split the file to the necessary sizes, you must place each file on a separate disk. The disks must be numbered consecutively. You specify the first disk in the series with the Disks field above. Remember to include an entry in the Disks section for each disk the split files require.

Version Checking	Specifies a version checking method to use for the file. EDI Install Pro uses the date to determine if a file is newer. The possible options are:

A	Always copy the source to the destination.

B	If the destination exists, make a backup using .OLD as the extension (example: FILENAME.OLD), and then copy the source to the destination.

C	If the destination exists, ask the user to confirm before overwriting with the source.

N	Copy the file if the source is newer than the destination.

S	Search for the file in the users path, WINDOWS directory, SYSTEM directory, and in the destination directory. If the file is found and the source is newer, the file is replaced, wherever it was located. This means that the file might not end up in the directory you specified. This is generally used for system files such as BWCC.DLL or VBRUN100.DLL.

X	Copy the file if the destination doesn't exist.

Related topics

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	INI Files

•	PM Group


INI Files section

The INI Files section lists entries for EDI Install Pro to create or modify in .INI files on the user's system. This section is optional.

INI Files entries

Each entry consists of a description; an equal sign; the .INI file to create or modify; the section name; the keyword; and the value to assign to the keyword. For example, to create the following section in WIN.INI,

[WinCLI]

Color=Black

you would use

App INI=WIN.INI WinCLI Color Black

Using spaces in keys or values

Any time that you wish to use a space or a tab for anything other than separating fields, you should enclose the field in quotation marks. For example,

App INI=WIN.INI NewApp "App Exe"

Specifying destination directory

If you want to specify the destination directory in one of the fields, you must use two consecutive percent signs (%%). EDI Install Pro will replace percent signs with the destination directory, where ever it finds them. For example, to create the following section in WIN.INI,

[NewApp]

App Dir=D:\APPDIR

App Exe=D:\APPDIR\APP.EXE

you would use

[INI Files]

App INI=WIN.INI NewApp "App Dir" %%

App INI=WIN.INI NewApp "App Exe" %%\APP.EXE

Deleting .INI files, sections, or keywords

If you leave out the section name, the keyword, or the value, the missing part will be deleted from the specified .INI file. For example, to delete the App Exe entry of the NewApp section listed above, you would use:

[INI Files]

App INI=WIN.INI NewApp "App Exe"

If you wanted to delete the whole New App section, you would use

[INI Files]

App INI=WIN.INI NewApp

Finally, if you wanted to delete the .INI file itself, you would use

[INI Files]

App INI=WIN.INI

NOTE:	This is a very poweful feature. You should use it with extreme caution, as deleting entries or files on a user's system is a very dangerous thing to do.

Related topics

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	Files

•	PM Group


PM Group section

The PM Group section describes the Program Manager group that you want EDI Install Pro to create.

If you don't need or want a Program Manager group, you don't have to include it. If you exclude this section, you should also exclude the PM Group entry of the Application section.

PM Group entries

Each entry consists of the name of the item to create; an equal sign; the component this entry belongs to; the file's path name and parameters (enclosed in quotation marks if necessary); the icon file's path name; and the icon index. Only the component and the file name are required, the icon file name and the icon index are optional. A complete entry would look like this

WinCLI=1 WINCLI.EXE WINCLI.EXE 0

A minimal entry would look like this

WinCLI=1 WINCLI.EXE

Specifying destination directory

Most of the time you will want to specify the destination directory as the file's path, so that Program Manager is able to locate the file. You must use two consecutive percent signs (%%) to specify the destination directory. EDI Install Pro will replace the percent signs with the destination directory in the program and icon file specifications. For example,

EDI Install Pro=1 %%\INSTALL.EXE %%\INSTALL.EXE

ReadMe=2 "NOTEPAD.EXE %%\README.TXT" NOTEPAD.EXE

would tell EDI Install Pro to add the destination directory to the program and icon file names when creating the Program Manager item. Don't forget the backslash (\) after the percent signs.

Probably the only time that you won't need to specify the destination directory is if the program can be located on the user's path, WINDOWS directory, or SYSTEM directory.

Specifying parameters

If you wish to specify any parameters along with the file's path name, you must enclose the command line (program name and parameters) in quotation marks. For example,

ReadMe=2 "NOTEPAD.EXE %%\README.TXT" NOTEPAD.EXE

WCLICtrl=3 "WCLICTRL.EXE /C /N /S"

Any time that you wish to use a space or a tab for anything other than separating fields, you should enclose the field in quotation marks.

Specifying icon files

By specifying a different icon file Program Manager will use an icon in the specified file instead of the program file. The icon index is used to determine which icon (0..?) will be used from the icon file. For example,

WinCLI Pro=1 WINCLI.EXE WINCLI.EXE 3

would tell Program Manager to us the 4rth icon (0, 1, 2, 3 = 4rth icon) in WINCLI.EXE.

Specifying relative paths

The file names should include the destination relative path. For example, to create an item for PROGHELP.EXE located in the PROGRAM directory, you would use PROGRAM\PROGHELP.EXE as the path name.

[PM Group]

Program Help=1 %%\PROGRAM\PROGHELP.EXE

When specifying relative paths, it is usually necessary to specify the destination directory as well, using the double percent signs.

Related topics

•	Sample INF file

•	Application

•	Components

•	Directories

•	Disks

•	Files

•	INI Files


Copyright

© Copyright 1992 Robert Salesas. All Rights Reserved. This document may not, in whole or part, be copied, photocopied, translated, or reduced to any electronic medium or machine readable form, without prior consent, in writing, from Robert Salesas. All software described in this manual is © Copyright 1992 Robert Salesas. All rights reserved. The distribution and sale of these products are intended for the use of the original purchaser only. Lawful users of these programs are hereby licensed only to read the programs, from their media into memory of a computer, solely for the purpose of executing the programs on one machine at a time. Duplicating or copying for other than backup purposes, or selling or otherwise distributing these products is a violation of the law and this agreement.

Related topics

•	Disclaimer

•	License agreement

•	Shareware concept

•	License registration


Disclaimer

This information is provided "as is" without representation or warranty of any kind, either express or implied, including without limitation, any representations or endorsements regarding the use of, the results of, or performance of the information, its appropriateness, accuracy, reliability, or correctness. The entire risk as to the use of this information is assumed by the user. in no event will Robert Salesas, Eschalon Development Inc. or it's employees be liable for any damages, direct, indirect, incidental or consequential, resulting from any defect in the information, even if Robert Salesas or Eschalon Development Inc. have been advised of the possibility of such damages. This disclaimer shall supersede any verbal or written statement to the contrary. If you do not understand or accept these terms you must cease and desist using this product immediately.

Related topics

•	Copyright

•	License agreement

•	Shareware concept

•	License registration


License agreement

Your use of this package indicates your understanding and acceptance of the following terms and conditions. If you do not understand or accept these terms you must cease and desist using this product immediately.

1. Copyright: These programs and the related documentation are copyright. The sole owner is Robert Salesas. You may not use, copy, modify, or transfer the programs, documentation, or any copy except as expressly provided in this agreement.

2. License: You have the non-exclusive right to use any enclosed program only on a single computer at a time. You may load the program into your computers temporary memory (RAM). You may physically transfer the program from one computer to another, provided that the program is used on only one computer at a time. You may not decompile, disassemble, reverse engineer, modify, or translate the program or the documentation. You may not attempt to unlock or bypass any copy protection utilized with the program. You may not remove or modify any copyright notice nor the About dialog box, which can be accessed by pressing ALT-I at the main window. All other rights and uses not specifically granted in this license are reserved by Robert Salesas and/or Eschalon Development Inc.

3. Distribution: You may distribute INSTALL.EXE, INSTALL.BIN, UNPACK.EXE, and DUNPACK.EXE, as long as their intended and possible use is only to install an application, other than themselves, on a users computer. No other files or documents from EDI Install Pro may be distributed. You may not distribute copies of the complete package or the accompanying utilities and documentation.

4. Back-up and Transfer: You may make one (1) copy of the program solely for back-up purposes. You must reproduce and include the copyright notice on the back-up copy. You may transfer the product to another party only if the other party agrees to the terms and conditions of this agreement and completes and returns a registration card to Eschalon Development Inc. If you transfer the program you must at the same time transfer the documentation and back-up copy or transfer the documentation and destroy the back-up copy.

5. Terms: This license is effective until terminated. You may terminate it by destroying the program, the documentation and copies thereof. This license will also terminate if you fail to comply with any terms or conditions of this agreement. You agree upon such termination to destroy all copies of the program and of the documentation.

Related topics

•	Copyright

•	Disclaimer

•	Shareware concept

•	License registration


Shareware concept

Shareware is copyrighted software which is distributed by authors through bulletin boards, on-line services, disk vendors, and copies passed among friends. It is commercial software that you are allowed to try before you pay for it. This makes shareware the ultimate in money back guarantees!

Most money back guarantees work like this: you pay for the product and then have some period of time to try it out and see whether or not you like it. If you don't like it or find that it doesn't do that you need, you return it and you get your money back. Some software companies won't even let you try their product, since to qualify for a refund the diskette envelope must have an unbroken seal.

With shareware you get to try it for a reasonable limited time (like 30 days), without spending a penny. You are able to use the software on your own system, in your own special work environment, with no sales people looking over your shoulder. If you decide not to continue using it, you throw it away and forget all about it. You only pay for it if you continue to use it.

Shareware is a distribution method, not a type of software. You benefit because you get to use the software to determine whether it meets your needs, before you pay for it. Authors benefit because they are able to get their products into your hands without the expenses it takes to launch a traditional retail software product. There are many programs on the market today that would never have become available without the shareware marketing method.

The shareware system and the continued availability of quality shareware products depend on your willingness to register and pay for the shareware you use. It's the registration fees you pay which allow us to support and continue to develop our products. Please show your support for shareware by registering those programs you actually use and by passing them on to others. Shareware is kept alive by your support!

Related topics

•	Copyright

•	Disclaimer

•	License agreement

•	License registration


License registration

If you like EDI Install Pro and you choose to use it, you must purchase a license. You are not allowed to keep, use, or distribute EDI Install Pro with your applications unless you obtain a license.

When you register, we will send you the latest version of the package. It will not have the opening delay screen that you get with the demo version, plus it will support compression. As well, you will receive a compression utility to pack your files and a decompression utility to distribute with your product.

If you already own a copy of EDI Install Pro, versions 1.0 through 1.2, you may upgrade to EDI Install Pro for a rebate price. See the upgrades section for details.

Related topics

•	Copyright

•	Disclaimer

•	License agreement

•	Order form

•	Product line

•	Upgrades

•	Contact information


Order form

Click mouse button here to print an order form.

For information, orders, or site licenses, call or fax Eschalon Development Inc. at (604) 520-1543, or send an EMail message on Compuserve at 76625,1320.

NAME/CONTACT:

COMPANY:

STREET:

CITY:	STATE:	ZIP:

COUNTRY:	TELEPHONE:	FAX:

License registration	$120.00 Cdn.	($99.95 US)	x ___ units =	$ ________

B.C. residents add 6% PST	$ ________

Canada residents add 7% GST	$ ________

Overseas orders add $5.00 US for shipping & handling	$ ________

*Does not include license registration.

Total:	$ ________

VISA #:*	Expiration Date:

*will be charged in Canadian dollars

Name on Card:	Signature:

- OR -

Mail a check or money-order payable to:

Eschalon Development Inc.

110-2 Renaissance Square

New Westminster,  BC

V3M 6K3   Canada


Product line

Eschalon Development Inc. product line as of December 1st, 1992.

Product	Price (US $)

EDI Install for Windows 	$45

EDI Install Pro for Windows 	$99.95

EDI UnInstall for Windows 	$99.95

EDI Install for MS-DOS 	$45

EDI Threads for Windows	$99.95

EDI Power Libs for Windows 	$99.95

WinCLI/WinCLI Pro 	$35/$79.95

LZSSLib - Single/Distribution 	$25/$299.95

All of our products can be ordered directly through us. You can download the shareware "demo" versions from CompuServe (WINSDK or WINADV sections, usually).


EDI Install for Windows - Version 1.3

EDI Install for Windows is the first in the EDI Install product line. It is a simple to use, complete installation utility for Windows applications. Features include a nice Windows interface, prompting for destination directory, creation of Program Manager group, multiple disk support, and file compression. Uses a simple INF file that doesn't require programming or learning a new script language. You just list your files and go!


EDI Install Pro for Windows - Version 1.4

Finally, an advanced installation utility that doesn't take days to learn. EDI Install Pro uses an enhanced version of the familiar INF file format introduced in EDI Install for Windows. It is extremely easy to use, yet offers all the powerful features of products costing more than 3 times as much! There is very little, if anything, that you cannot do with EDI Install Pro. Here are just some of the features you'll find:

•	Dithered and/or bitmap background.

•	Selectable components allow the user to install only what is needed.

•	Program Manager group creation.

•	.INI file creation and modification. Works on WIN.INI and other .INI files.

•	Display "README.TXT" file to the user.

•	Smart progress bar displays percent completed by file size.

•	User specified source and destination paths.

•	Creates directory structure "on the fly", only as required.

•	Version checking based on "newer files" and "user confirmation".

•	Complete file compression support, including a redistributable graphical "unpacker".

•	Split file support for placing large files on multiple disks.

•	Multiple diskette installations supported.

•	Custom DLL allows you do expand the capabilities of EDI Install Pro.

You can do almost anything you need with EDI Install Pro, just as it is. However, by allowing custom DLLs, you can expand the capabilities to include anything you need, such as custom setup information, custom component selection, advertising text, file encryption, autoexec.bat or config.sys modifications, and much more. We couldn't include every possible feature, but with a custom DLL you can add anything you need.


EDI UnInstall for Windows - Version 1.0

Finally, a utility that allows users to uninstall your applications! Using a simple INF File, EDI UnInstall deletes application files, removes Program Manager groups, removes or changes .INI files or sections, and optionally deletes user data files. It will leave no trace of the previously installed application! EDI UnInstall uses the same attractive interface and simple file format as EDI Install Pro. Users and reviewers alike, are now demanding the option to uninstall. Can you risk not using EDI UnInstall?


EDI Install for MS-DOS - Version 1.0

EDI Install for MS-DOS is a complete implementation of our famous Windows installer written specifically for MS-DOS. Features a pleasant text based windowed interface which gives your users a good first impression of your product. This versions uses the same INF file format as EDI Install for Windows, making it just as easy to learn as its Windows cousin. You can even share INF files across platforms!


EDI Threads for Windows - Version 1.0

EDI Threads is a complete multi-threading library for Windows. With it you can easily create applications that use background printing, complex redrawing, repagination, serial port polling, text searches, and more. There is no need to wait for Windows NT or switch to OS/2. With EDI Threads, writing background processes for Windows applications becomes a snap. Here are just some of the features you'll find:

•	Easy to use, even when converting existing applications.

•	Almost any function can be turned into a thread.

•	Speeds up application's response time.

•	Automatic system-wide scheduler.

•	Unlimited number of threads.

•	Each thread uses it's own stack.

•	Adjustable priorities and time slices.

•	Pause or stop a thread at any time.

•	There is practically no limit to what a thread can do, including Windows and DOS calls.

•	NO ROYALTIES.

The threads operate independently of the main program. As soon as a thread is started, control is returned to the application. By applying this technique to a background operation you will drastically speed up the application's user response time. Instead of waiting for a task to finish, you can start it and return to the user without delay. No more coffee breaks during lengthy operations!

NOTE:	Source is now available for $395 US ($465 Cdn).


EDI Power Libs for Windows

EDI Power Libs provides a complete set of powerful routines to simplify your programming tasks. Use EDI Power Libs instead of re-inventing the wheel every time you need a new feature. It will save time and money, while providing greater flexibility.  Here are just some of the features you'll find:

•	Low-level functions: fast data manipulation, inline memory access, process yielding, DOS wrapper calls, easy DPMI access, debugging aids.

•	High-level functions: sound, friendly delays, timing (count-down, "dead-man", difference, etc.), string manipulation (conversions, editing & handling, parsing, DOS functions, etc.), date & time (international, calculations, conversion), pattern matching (file and buffers).

•	DOS functions: copy, move, rename, enumeration, share checking, file locking, drive type, disk labels, safety and error checking, string parsing, etc.

•	Fast inline macros for system critical requirements.

•	Full on-line documentation and examples.

•	Dynamically linked library format included for languages with DLL support (i.e. Pascal, C, C++, Visual Basic, and more)*.

•	Source code included (Pascal and Assembly).

•	Plus much, much more!

*Only some language interface modules are included; check with us regarding availability.


WinCLI/WinCLI Pro* - Version 3.0/1.0

WinCLI Pro is a complete command line interface capable of running Windows applications as well as DOS applications. It replaces the usual DOS prompt on standard and enhanced mode systems. Also included over 30 built-in file management commands (ALIAS, ASSOCIATE, ATTRIB, CD, CLS, COPY, DATE, DEL, DIR, EXIT, FINDFILE, HELP, INFO, LABEL, MEM, MAKEDIR, MORE, MOVE, PATH, PROMPT, RENAME, RENDIR, RMDIR, SYSINFO, TIME, TITLE, VER, VERIFY, VOL, WHICH and many other extended commands).

WinCLI Pro has full clipboard support, a detailed help system, command line editing, command line history, aliases (like Doskey macros in MS-DOS 5.0), a scroll-back buffer, selectable font and adjustable colors. Also included in the package is a complete File Manager replacement, settings utility, password system protector, clock & screen saver and various other small utilities.

*Some features are only available in WinCLI Pro.


LZSSLib - Version 1.0 - Single/Unlimited license

Complete compression/decompression DLL for Windows. Quickly and easily add compression support to your current applications. Supports Turbo Pascal for Windows, C/C++, Actor, Visual Basic, Object Vision 2.0 and any language product that supports DLLs*.

*Only C and Pascal interface code is included.


Upgrades

We periodically provide bug fixes and upgrades for our products.

Upgrade policy

Minor changes and bug fixes are free; major revisions carry an upgrade fee. If we come out with a new version within 15 days of your purchase, we will upgrade you for free. You always pay for shipping and handling.

Upgrading from EDI Install Pro

If you already own a copy of EDI Install Pro, versions 1.0 through 1.2, you may upgrade to EDI Install Pro for only $24.95 US ($32.00 Cdn + GST & PST). Contact us for details, or send in your order form. Make sure you order under the same name and address as the original product.

Related topics

•	Order form


Contact Eschalon Development Inc.

For technical assistance, orders, site licenses, upgrades or information on our other products, you may contact us at:

Address:	Eschalon Development Inc.

110-2 Renaissance Square

New Westminster, BC

V3M 6K3   Canada

Telephone/Fax:	(604) 520-1543

CompuServe:	76625,1320

Internet:	robert_salesas@mindlink.bc.ca


Glossary

A

•	Application

•	Associate

•	Attributes

B

•

C

•

D

•	Destination directory

•	Description

E

•	Extension

F

•	File name

•	Field

G

•	Group

•	Group icon

H

•

I

•	Icon

•	INF file

•	INI file

J

•

K

•

L

•

M

•

N

•

O

•

P

•	Program item

•	Program item icon

Q

•

R

•

S

•	Shareware

•	Source directory

T

•	Topic

U

•

V

•

W

•	Wildcard

X

•

Y

•

Z

•


Shareware

Shareware is copyrighted software which is distributed by authors through bulletin boards, on-line services, disk vendors, and copies passed among friends. It is commercial software that you are allowed to try before you buy. This makes shareware the ultimate in money back guarantees!

If you like the software, you must register with the author. This provides you with a legal copy and encourages the continued development of high quality, low cost software. Shareware works and exists through your support. When you cheat a shareware author, you are cheating yourself from future quality software.