InstArch/UnstArch Main Help Index
ZipPiz Main Help Index

Preliminaries

An Overview of ZipPiz - what it is and what it does

The License Agreement

How to Register your copy of InstArch

Where to send comments and suggestions

Warranty

How to use InstArch

The Unpack Dialog

The Main Screen

The File Menu

Edit menu

View menu

Tools menu

Sort Menu

Help menu

The Installation Dialog

The Properties Dialog

File Actions

Archivers

Storage

Behaviors

Virus Scanners

Viewers

Configuring InstArch as a Viewer	File Name Patterns

Variable Substitution

Trivial Archives

Unix and DOS Text files

How to use UnstArch

The Main Screen

The File Menu

Edit menu

View menu

Sort Menu

Help menu

Sundry Items

How to use AddIcon

How to use UNGZPTAR

How to use ZPZUNZIP


UnstArch Main Help Index

Preliminaries

An Overview of InstArch/UnstArch - what it is and what it does

The License Agreement

How to Register your copy of InstArch

Where to send comments and suggestions

Warranty

How to use UnstArch

The Main Screen

The File Menu

Edit menu

View menu

Sort Menu

Help menu


Overview

What ZipPiz Does

ZipPiz is a collection of programs specifically designed to help you unpack and deal with archives downloaded from a network.  It includes two programs, InstArch, which deals with unpacking the archive and installing it on your hard drive, and UnstArch, which helps you manage the files after you have downloaded them, and can help you clean them off of your hard drive, should you decide you no longer need the files.

InstArch is a utility that is specifically designed to help you unpack archives.  It not only understands the major archive formats, it can be configured to understand just about any archiving format, encryption or compression scheme.  After the archive is unpacked, the contents can be viewed or even tested out using programs that you specify, allowing you to assess whether the contents are of interest to you.  If you are interested in using the files, InstArch can automatically perform whatever actions are necessary to make the files of the archive ready for use on your system.  After you have installed the files, you can then use UnstArch to view, move, and if necessary, remove the files associated with the archive.

The Terms

InstArch and the rest of the ZipPiz programs are shareware programs, which means that they are not free!  You may use InstArch and the rest of the ZipPiz programs for 30 days without cost or obligation; however, after that evaluation period is over, you must either remove them from your computer or you must purchase a registered copy.  See the License Agreement for the exact terms under which you may use and redistribute ZipPiz.  The registered version of InstArch provides some additional features, such as automatic virus-checking and automatic Unix-to-DOS conversion.  If you choose to buy the full boxed version (when available), you will also receive a collection of some of the most popular shareware and freeware archiving programs and viewers, as well as a printed manual and updates of new versions and other new offerings.  For information on how to register your copy, see Registering.

How to use InstArch

InstArch can be invoked from the program manager or from the Windows File Manager, but its usefulness really comes to the fore when used as a viewer for World Wide Web browsers like NetScape.   For information on how to set up InstArch to work with various viewers, see Configuring InstArch as a Viewer

When invoked from the Program Manager, InstArch behaves just as it does as a viewer, except that it immediately brings up a dialog asking for an archive to install.

The unpacking procedure goes through three major dialogs - the first one allows you to specify details of how the archive is to be unpacked.  For information on this screen, see The Unpack Dialog.   After the archive is unpacked, the next screen you see is the main screen, which allows you to view the files in the archive and arrange for their disposition after they are installed.  If you choose to install the files, you will be presented with the installation dialog in which you can further fine-tune the installation procedures.

InstArch is designed to be configurable to your needs.  It should be possible for you to have InstArch set up so well that you can actually skip the unpacking and installation dialogs, allowing you to just click on the archive that you want to download, allow InstArch to automatically unpack it, view the contents just by double-clicking the files you need to look at, and click on the Install button to place the files as you want them.  For information on the various configuration parameters, see Configuring InstArch.

How to use UnstArch

UnstArch can be invoked from the program manager, but is really best invoked from the File Manager, where there is an association between Installation Records (.PIZ files) and the UnstArch program.

It is possible to use UnstArch to relate several files, and thus use these files as if they were installed with UnstArch.  You can do this by invoking UnstArch from the command line and adding the files to be grouped (using the Add Command from the Edit Menu).


Registering

When you register your copy, you have three pricing options.  The base cost is $35, after which you will receive a copy of the Registered version of InstArch electronically and access to Pragma's registered users' FTP sight.  For another $5 to cover shipping and handling costs ($40 total), you can receive a diskette copy of InstArch.  This disk also includes a sampling of the more popular archiving schemes found on the Internet.  At some point in the future, Pragma systems will offer a full boxed edition of InstArch which will include a printed copy of this manual, a copy of the registered version of ZipPiz, and a compendium of our favorite shareware and freeware archivers and viewers.  If this version interests you, make a note of this in your payment.

You can register by phone (with a credit card) at (800) 294-1302 within the USA, or 619-729-4541 from outside the US.  To pay with a check, please print (using "Print Topic" from the "File" menu) the Registration Form and mail it to:

Pragma Systems, Inc.

13706 Research Blvd

Austin, TX 78750

NOTE!  The 800 number will put you in touch with the company that takes orders for us, not Pragma Systems or the author, they do not take support calls or answer any questions other than those directly pertaining to ordering the product.  Calls placed to that number for any other purpose than ordering will be ignored.

When ordering, please indicate how many copies of InstArch you want, and how you want them distributed.  Again, the prices are:

$40	1 Licensed copy of InstArch distributed through regular mail on a 1.44MB floppy disk.

$35	1 Licensed copy of InstArch distributed through uuencoded e-mail or downloaded from our FTP server.

For purchases of more than 30 copies, call our offices at (512) 219-7270 for volume pricing information.

When registering your copy, you are encouraged to use the order form in the file ORDER.FRM, in this distribution, or just click here and then select "Print Topic" from Windows Help's "File" menu.


ZipPiz Registration Form

NOTE!  Credit card customers can phone in their order at (800) 294-1302, within the USA or 619-729-4541 internationally.

Mail To:	Pragma Systems, Inc.
13706 Research Blvd
Austin, TX 78750

Shipping Information: (Name and address of licensee)

Name:	____________________________________________________________

Address:	____________________________________________________________

____________________________________________________________

____________________________________________________________

I wish to register ____ copy(ies) of ZipPiz, at $35(US) each:	_____

I wish to receive my copy via:

   [   ]	1.44MB Floppy disk shipped through regular mail.
I am enclosing $5US for shipping and handling:	_____

   [   ]	UUencoded e-mail.

   [   ]	FTP from Pragma's FTP sight - I wish to be informed of the address and password for this sight by e-mail.

I understand that if I elect to receive my copy via e-mail that I am responsible for unpacking the message, if I cannot do so, I must send an additional $5(US) to cover shipping costs to receive the product on 1.44MB floppy.  I understand that if I elect to receive my copy via FTP and I, for whatever reason, cannot do this, I must inform Pragma Systems, Inc. of my difficulty and I must then elect to either receive my copy of the program via e-mail or send an additional $5(US) to receive a copy on 1.44MB floppy disk.

My e-mail address is:  _________________________________________

TOTAL ENCLOSED:	_____


InstArch License Agreement
ZipPiz License Agreement

This version of ZipPiz, including the INSTARCH, UNSTARCH, and ADDICON programs and all the other files and programs found herein except GUNZPTAR are provided for demonstration and evaluation purposes only.  You may use this software free of charge for up to 30 days from the day you install ZipPiz.  After this period is over, you must either remove the ZipPiz software and related files from your hard drive or purchase the licensed version.  Use of this software denotes acceptance of the terms and conditions set forth in this agreement and the terms of the warranty information also set forth in this document.

You may copy and redistribute the demonstration version of ZipPiz provided that none of the files in the distribution is modified or altered, that no fee or other remuneration is sought for such redistribution, and no attempt is made to misrepresent the terms of this agreement.

Anyone distributing ZipPiz for any kind of remuneration may only do so with the expressed written consent of Pragma Systems, Inc.  This authorization will be automatically granted to distributors recognized by the Association of Shareware Professionals (ASP) as adhering to its guidelines for shareware distributors, and such distributors may begin offering ZipPiz immediately.

ZipPiz includes one program, GUNZPTAR, which is not covered under the license terms described above, it is distrubuted under the terms of the Free Software Foundation's General Public License (GPL).  That program and the source code for it may be freely distributed under the terms of the GPL.  For more information regarding the terms of the GPL see the file COPYING in the GUNZPTAR source archive (GUNZPTAR.ZIP).


InstArch/UnstArch Warranty
ZipPiz Warranty

InstArch, UnstArch, and all other programs and information provided in the ZipPiz distribution are provided as-is, without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose.  In no event shall Pragma Systems Inc. or Steve Benz be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Pragma Systems, Inc. or Steve Benz have been advised of the possibility of such damages.


NetScape

The NetScape Navigator (tm), a product of Netscape Communications Corporation, is one of the best ways we know of to access the internet.  InstArch was written with just this product in mind, though it can be effectively used in other ways as well.  An evaluation copy of the NetScape navigator can be downloaded from ftp://ftp.mcom.com/netscape/windows or you can get the commercial version by calling 1-800-NETSITE (in the US) or 1-415-428-4330 (outside).


Configuring InstArch as a Viewer

Many programs, including NetScape and the Windows File Manager have a concept of a "viewer" (in NetScape it is called "Helper Application" and in File Manager the term loosely translates to "association").  But whatever the name, it is simply a program that handles files of a certain type for the calling program.  InstArch can act as a "viewer" for a very wide array of file types.

During Setup, InstArch can automatically configure itself as a viewer for the File manager and NetScape, if you have it.  If you need to change the configuration, see the documentation about how to configure viewers in the calling program, and add an entry for InstArch bearing in mind the following:

-	InstArch supports one important command line option, /T or /TEMPORARY, which indicates to InstArch that the caller will delete the archive (or other) file being viewed upon exit.

-	NetScape, and perhaps other programs, do not support command options for their Helper Applications.  InstArch has a provision for this: another version of the executable called instarc1 which supports no command line options and defaults to treating the archives as temporary files.  Therefor, when configuring InstArch as a helper application for NetScape, we suggest using instarc1 - at least if you want to be reminded about saving copies of the archives.

We are looking to broaden our array of command line options; if you are using InstArch in a way which we may not have anticipated and would like to make suggestions on how the command line could be enhanced, please tell us about it.


Comments, Suggestions, and Further Help
Comments, Suggestions and Further Help

Pragma Systems can be contacted via e-mail at

pragma@infiniy.ccsi.com

Through regular mail at:

Pragma Systems, Inc.

13706 Research Blvd

Austin, TX 78750

And by phone:

(512) 219-7270

We welcome suggestions and comments almost as much as we do registration fees :-)

Note that the shareware version of this product is not supported, so questions about how to use InstArch/UnstArch are not likely to get answered unless you have registered.

The author, Steve Benz, can also be reached through e-mail at steveb@realtime.net.

PLEASE DO NOT CALL THE 800 NUMBER for purposes other than placing orders!


The Main Screen

The main screen is where you view the files in the archive and where you select what you want to do with the files during installation.  The main feature of the screen (shown below) is the large list, which shows all the files in the archive and the actions that will be taken on those files during installation.

In most cases, the first thing you will want to do with this dialog is to view the files in the archive.  For information about this, see viewing a file.  After that, you may decide that the contents of the archive either are of no immediate interest, if so, you can exit the tool without installing the files.  NOTE!  If you simply exit, all the files that were extracted from the archive will be deleted!  If you want to simply keep the unpacked files as-is, the way to approach that is to install the files (as discussed in the next paragraph).

Changing The File Actions

If you are interested in installing the files in the archive, you will need to tell the program how you want to do this.  In most cases, the first step in doing this is to select one of the items from the File Actions list.  The entries in this list are the actions that you usually apply to archives of certain types.  For instance, if you download an archive which is a Windows application that comes with a Windows Setup program, then the way to install that archive is to run the Setup program, then delete all the files in the archive (as the files in the archive were only of interest to the Setup program - and thus have no further value.)  Applying this rule to other archives, say those that contain sampled audio or video, would probably not be at all desirable.  A better approach to those files would be to move  the clips that you wanted to keep to an audio/visual repository somewhere, so that you can browse them conveniently.  Yet another possibility is that of a Windows program which does not have a Setup program; for such archives, the usual action would be to simply leave the files as-is.

A default list of these "Action Sets" is created for you during installation, but you can customize these yourself.  For information on this, see File Actions Properties.  If you want to make small changes to the way particular files are being,  you do this with the commands on the Edit Menu.

The two choice boxes above the main list and below the tool or menu bar are concerned with changing the action set.  The first one (labeled "File Actions") indicates which action set is currently chosen, and the second one, labeled "When File Actions change, reset" indicates which, if any, of the files in the list, should have their actions changed to those indicated by a newly selected action set.  In almost all cases, the default value of "Unchanged Files" will be the best value.  If this is selected and the action set is changed, then all files that you have not manually changed will be reset to the default action of the new set.  The other values work in a similar fashion: "None" means that changes to the action set will have no effect on the files; "Selected Files" means that the new action set will only be applied to the files selected when the action set is changed; and "All Files" means that the new action set will be applied to all files, regardless of whether you have manually edited the action or not.

The Main List

The main list  is used to display the files in the archive and what is currently scheduled to happen to them when they are installed.  Each row has at least two columns of information, the name of the file and the size of the file.  However, depending on what actions you have associated with the file, other information will appear that describes these actions.  Consider the sample list below:

To illustrate this, take a look at the files in the list shown above.  The first file in this list, foo.exe, will be moved to d:\stuff.  Note that we can tell it is a move, and not a copy, as with foo.hlp, by the icon.  The [image] indicates a copy, and the [image] indicates a move.  The third file, install.com, has two actions associated with it.  The [image] indicates that this file will be executed on installation, and the [image] means that it will be deleted when the installation is complete.  The last file in the list, uninstal.com is marked with a [image], which means that it will be executed when the package is uninstalled (see Uninstall for information on how to do this).  The fact that it has none of the delete, move, or copy icons ( [image], [image], or [image]) means that this file will be kept in the unpacking directory.

Viewing, Sorting, and So Forth

You can look at (or execute, or listen to, etc.) a file on the list by double-clicking it - this is the same as invoking the View Command from the View Menu.  You can also use the options on the Sort menu to change the order of the files in the list.  The Tools Menu offers facilities for converting Unix Text files to DOS text file format and running virus scanners.  The Help Menu has a few other ways to start up InstArch's help facilities.

Installing the Files

After you have changed the file actions to your satisfaction, you can execute them by selecting "Install Files" from the File Menu (ALT- F, I), or by clicking on the install button in the toolbar, or by typing CTRL-I.  Most users will then see the Install Dialog which will allow a few details of the installation to be changed before proceeding.

Configuring Defaults

After you become familiar with InstArch, we hope that you will be able to use it by doing no more than double-clicking the files you want to view, and either exiting immediately or selecting an action set; and hitting the install button or the exit button.  To get to this blissful state, though, you will have to tell InstArch how it can help you.  You do this (for the most part) through the Properties Dialog, which you can bring up by selecting the Properties Command from the File Menu.  After you have set up some of the trickier things, such as telling InstArch how to place your files, you can do things like suppress the unpacking and installation screens (see the Behaviors Tab in the Properties Dialog).


File menu commands

The File menu offers the following commands:

Open	Deletes all files created during unpack and unpacks a new archive.
Save	Copies the archive to the archive repository, if you have set one up (see The Storage Properties Page)
Save As	Copy the archive file.
Properties	Edits the behavior of InstArch
Install	Installs the files of the archive on your system and exits InstArch.
Exit Without Unpacking	Deletes all unpacked files and exits InstArch.


File Open command
Open command (File menu)

This rarely used command would be useful if you were simply browsing archives.  It deletes all the files in the current archive (just as choosing "Exit Without Installing" does) and then unpacks the archive you select from the File Open dialog box.

Shortcuts

Toolbar:

Keys:	CTRL+O


File Open Dialog Box

The following options allow you to specify which file to open:

File Name

Type or select the filename you want to open.  This box lists files with the extension you select in the List Files of Type box.

List Files of Type

Select the type of file you want to open.  This list, contains entries for each of the archive file types you have configured in the Archiver Page of the InstArch Properties

Drives

Select the drive that stores the file you want to open.

Directories

Select the directory which contains the file you want to open.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


File Save command
Save command (File menu)

InstArch uses this command to save the archive file.  This is typically used if you have invoked InstArch as a viewer for a program like NetScape which will delete the archive after InstArch exits.  If you have not invoked InstArch in that way, then this command will do nothing.

If you have specified an archive repository, then this command will copy the archive to that repository.  (For information on how to specify an archive repository, see the Storage Configuration property page, brought up by selecting the "Storage" tab in the dialog brought up by selecting the Properties Command from the File Menu.)

Shortcuts

Toolbar:

Keys:	CTRL+S


File Save As command
Save As command (File menu)

Use this command to copy the archive to another location.  Upon selecting this item, InstArch displays the Save As dialog box so you can select where you want to copy the archive to.  Note that if you have configured an archive repository, that directory will be chosen as the default.


File Save As dialog box

The following options allow you to specify the name and location of the file you're about to save:

File Name

Type a new filename to save a document with a different name.

Drives

Select the drive in which you want to store the archive.

Directories

Select the directory in which you want to store the archive.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


Directory Selection Dialog Box

The following options allow you to specify a directory to be used by InstArch:

Drives

Select the drive in which you want to store the archive.

Directories

Select the directory in which you want to store the archive.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


Edit menu commands

The Edit menu offers commands for changing the action that will be taken for a file during installation:

Delete	Causes the file to be deleted.
Keep	Causes the file to be kept in the unpacking directory.
Copy	Causes the file to be copied.
Move To	Causes the file to be moved.
Execute	Causes the file to be run as an installation script or used as input to an installation script..
Execute on Uninstall	Causes the file to be run when the archive is uninstalled.
Reset	Resets some or all the files to the default for the currently selected action set.


Delete (Edit Menu)
Delete Command (Edit Menu)

This command causes the currently selected file(s) to be deleted when the archive is installed (with the Install command on the File Menu.)  Note that this option is mutually exclusive with Keep, Move To, and Copy To, from this menu - that is, selecting a file for copy-to and then delete will result in the file being deleted, not moved.

Shortcuts

Toolbar:

Keys:	CTRL+D


Keep Command (Edit Menu)

This command causes the currently selected file(s) to remain in the unpacking directory when it is installed.  This cancels any previous Delete, Move To, and Copy To, commands previously enacted on the selected file(s).Shortcuts

Toolbar:

Keys:	CTRL+K


Copy To Command (Edit Menu)

This command can be used to cause the currently selected file(s) to be copied to another drive or directory during installation.  When this command is invoked, a dialog is popped up in which you should enter the destination of the file.

In most cases, you will enter the directory where you want the file to go, or, if you have selected a single file and you wish not only to relocate it but also rename it, you can enter the complete path name of the destination file.  InstArch provides a powerful Variable Substitution mechanism, the facilities of which are available here.  For example, if you are unpacking an archive named "GOOBER.ZIP" and have selected a number of files with a .CC extension, you can enter "D:\SRC\%a\%r.cpp to cause a directory named "D:\SRC\GOOBER" to be created, and the selected files to be copied into that directory with their extensions changed to .CPP.

Shortcuts

Toolbar:

Keys:	CTRL+C


Entering File Destinations, Execution Commands, and View Commands

This dialog is used by a variety of commands, such as the copy, move, and execute on install commands.  To specify a value, just type it into the edit box.  If you wish to cancel a previous value, just clear the checkbox or delete all the text in the edit box.


Move To Command (Edit Menu)

This command can be used to cause the currently selected file(s) to be moved  to another drive or directory during installation.  When this command is invoked, a dialog is popped up in which you should enter the destination of the file.

In most cases, you will enter the directory where you want the file to go, or, if you have selected a single file and you wish not only to relocate it but also rename it, you can enter the complete path name of the destination file.  InstArch provides a powerful Variable Substitution mechanism, the facilities of which are available here.  For example, if you are unpacking an archive named "GOOBER.ZIP" and have selected a number of files with a .CC extension, you can enter "D:\SRC\%a\%r.cpp to cause a directory named "D:\SRC\GOOBER" to be created, and the selected files to be moved into that directory with their extensions changed to .CPP.

Shortcuts

Toolbar:

Keys:	CTRL+M


Execute Command (Edit Menu)

This command can be used to cause the currently selected file(s) to be used during the installation process.  These files can either be executed themselves or provided as input to some other program.  When this command is invoked, a dialog is popped up in which you should enter the command line that should be executed during the installation.  As with the Move To and Copy To commands, InstArch's Variable Substitution facilities can be used to help in dealing with large selections.

One thing that is important to note:  the command line will be executed from the unpacking directory, so if the program or script is in a subdirectory, it is important to qualify the file name with the subdirectory name.  Also note that the command is invoked as a command shell, so shell features such as '&' can be used to cause several things to happen in sequence.

Shortcuts

Toolbar:

Keys:	CTRL+X


Execute On Uninstall Command (Edit Menu)

This command can be used to cause the currently selected file(s) to be used during the uninstallation installation process.  These files can either be executed themselves or provided as input to some other program.  When this command is invoked, a dialog is popped up in which you should enter the command line that should be executed during the installation.  As with the Move To and Copy To commands, InstArch's Variable Substitution facilities can be used to help in dealing with large selections.

Unlike Execute, these commands are executed from whatever directory the file ended up in.  That is, if the file is moved, then the command will be executed in the destination directory.  For information on how to uninstall a previously installed archive, see Uninstalling.

Shortcuts

Toolbar:


Reset To Default Sub-Menu (Edit Menu)

The Reset submenu encompasses three menu items, "Just Selected Files", "All Files", and "All Files Not Manually Changed".  These commands will change the action of the affected files to that indicated by the currently selected file action.

The commands on this sub-menu serve two primary purposes - to allow a way to easily recover from mistakes, and to allow you to easily cope with archives that contain sets of files for which different action sets can apply.


View menu commands

The View menu offers two commands, "View" and "View With..."  Choosing "View" causes the default viewers for the currently selected files to be invoked.  "View With..." offers you the opportunity to edit the viewing command before it is invoked, thus allowing you to override the default viewer.  If there is no default viewer for the selected file, then "View" behaves like "View With...", prompting you for the view command.

Note that in this context, the term "View" is fairly broadly defined.  One can, for instance, configure a "viewer" for sound files which simply plays the sound file on your audio device.  Or, one could configure a "viewer" for executables which simply runs the program.

Most of the time, the "viewer" is the command "Associated" with files with the currently viewed file's extension in the file manager - that is, "viewing" a file is, most of the time, just the same as double-clicking a file in the file manager.  Within InstArch, you can override these associations with commands more appropriate for viewing files within InstArch.  For instance, within the file manager, you may want to associate an interactive sound editing program with sound files, but within InstArch, you may want to use a simpler program, say one that just plays the sound file.  You can configure this through the  Viewer Configuration Property Page, which is available by choosing Properties from the File Menu and then choosing the Viewers Tab.

Shortcuts (For the View command)

Toolbar:

Keys:	CTRL+V


Tools menu commands

The first two items on the "Tools" menu are concerned with converting Unix Text files to DOS text files.

The menu option labeled "Find and convert Unix text to DOS text" searches for Unix text files and converts them to DOS text.  Note that this scan is very conservative, and thus you may have occasion to use the second menu option, "Convert Selected UNIX file(s) to DOS Text" which will convert the files selected in the file list to DOS Text.  Note that if a selected file looks like something other than a Unix text file, you will be given a chance to cancel the operation.

The second two menu items allow you to run the primary and secondary virus scanners.  Selecting one of these invokes the chosen virus scanner in the unpacking directory.  Note that these options will not be available if you have not set up any virus scanners.  The virus scanners can be defined with the Virus Scanner Property Page which is available by choosing Properties from the File Menu and then choosing the Virus Scanners Tab.


Sort menu options

The options under this directory allow you to change the order of the files in the files list:

By Name	Sorts the files alphabetically by name, with files listed before directories.
By Size	Sorts the files by size, with the largest files first
By Type, then Name	Sorts the files by type (as defined by the action set), with files of the same type being sorted by name.
By Type, then Size	Sorts the files by type (as defined by the action set), with files of the same type being sorted by name.
You can change the kind of sorting that you would like to do by default by editing the sort options under  the behaviors tab of the properties screen (ALT-F, P) (see The Behavior Page).


Help menu commands

The Help menu offers the following commands, which provide you assistance with this application:

Index	Offers you an index to topics on which you can get help.
Using Help	Provides general instructions on using help.
About	Displays the version number of this application.


Unpacking the Archive

This is the dialog in which you specify how you want the archive to be unpacked.  The choice box at the top lists all the archiving schemes which apply to the archive type.  (Archivers can be configured through the Archivers Page of the Property Sheet (under "Properties" in the File Menu.)  If you have some alterations to the unpacking program suggested by this configuration, you can make them in the combo-box's edit control.

The next field to worry about is the unpacking directory.  If you have configured a default unpacking directory, it will be the default value here.  To configure a default unpacking directory, see the Storage Page of the Property Sheet (under Properties in the File Menu).  This directory must be empty, but it need not necessarily exist yet, as if you have the "Create this directory if necessary" checkbox checked.  If you choose the "Browse" button, you can select an existing directory.  It will bring up a dialog box with which you can conveniently select the destination directory or part of the destination directory.  See The Directory Selection Dialog for details on how to use this dialog.

The next checkbox to be concerned with is the one labeled "Treat this as temporary storage".  It should be checked if, after the archive has been installed, all the files should be removed from the directory.  If this box is checked, a warning will be given if your installation instructions leave any files in the unpacking directory.  The default value of this checkbox can be configured in the same place as the default unpacking directory.

In the registered version of InstArch, you can automatically arrange for Unix text files to be converted to DOS text file format by checking the "Convert Unix text files to DOS text files" checkbox.  Whether this box comes checked by default depends on how you have things set up in your Behavior Configuration, accessible through the Properties command in the File Menu.  As the detection of Unix text files is extremely conservative, it is generally worthwhile to have this box checked at all times, however, as it does add slightly to the unpacking time, you may wish to disable it.  In the demo version of InstArch, this option is unavailable.

The next checkbox, "Skip the virus scan" is enabled if you have the registered version of InstArch and you have configured a virus scanner to run automatically and the archive contains a file which could contain a virus (i.e. if your archive only contains text files, there is no chance of a virus.)  Virus Scanners can be configured in the Virus Scanner Page of the property sheet.

Finally, we have the checkbox labeled "In the future, skip this dialog".  If you check this box, then, in the next invocation of InstArch, this dialog will not appear unless, for whatever reason, the default choices will not work.  This dialog can be re-enabled by clearing its analog in the Behavior Configuration.


Properties (File Menu)

Choosing "Properties..." from the File Menu brings up a tabbed dialog box that allows you to edit various aspects of InstArch's behavior.  From this dialog, select the tab of the aspect of the behavior you wish to change from the list.  The tab names and the behaviors they affect are listed below:

File Actions	The Action Sets that may be applied to files.
Archivers	The Archiving programs, what files they apply to and how they are run.
Storage	The default locations where InstArch will put various files.
Behaviors	Aspects of InstArch's behavior.
Virus Scanners	The Virus Scanning programs which InstArch uses and when and how they should be run.
Viewers	The programs used to view and otherwise inspect the files in the archive

When you have finished, press the "OK" button to make these changes effective, or "Cancel" to cancel all the changes which you made.


File Actions (Properties)

Choosing the "File Actions" tab of the property sheet brings up this dialog in which you may describe ways in which files should be handled.  The first field, a combo-box, allows you to enter or edit the name of the action set.  The "New" and "Delete" buttons to the right of this field allow you to create or delete action sets.  If you press the "New" button, you must then enter the name of the action set and edit the other aspects of the action set in the fields below.

The second field in the dialog box, labeled "File Type" lists the name of a category of files that is currently being edited (as a part of the action set).  As with the action set name, you can edit this field to change the name, or use the "New" and "Delete" buttons to add a new file type or delete the current file type.

The "Extensions" edit box contains the filename patterns that will identify files that match this type.  Note that if patterns from two different file types within the same action set match the same file, the one that matches most closely (matches the most characters exactly) will be chosen.  If both match equally well, one will be chosen arbitrarily.  For information on file name patterns, see File Name Patterns.

The remaining fields identify how files of this type will be handled during install.  The radio button set identifies whether the files will be deleted, kept, moved, or copied, and the text fields beside the copy and move items can be used to specify exactly where they should be copied and moved to.  If you wish, you can also use the "Browse" buttons to the right of these boxes to select a directory to place the files in from the Directory Selection Dialog Box.

Note that InstArch provides a mechanism called variable substitution whereby the names given in the move and unpack edit boxes can be computed on a per-file basis, thus allowing one to do things like automatically rename or change the extension of files and to install them in new directories based on the name of the archive from which they came.

The last two lines allow you to specify that a file should be used either as an installation or un-install script/program.  The checkbox should be checked if you actually wish the execution to be done, and the edit boxes should be filled with the appropriate command line.  Note that the Substitution mechanism discussed with move and copy applies here as well.  A good program to run in these two spots is AddIcon, which will add an icon to the program manager.  For example, the "Windows Application" action-set invokes AddIcon for every .EXE and .HLP file, using "%h\AddIcon.exe %1 %a".  This might expand to "C:\ZIPPIZ\AddIcon.exe .\eudora.exe weudora".  AddIcon wants to know the archive that the file came from so that it can know what to remove when it is used as a run-on-uninstall program.  In the "Windows Application" action set, AddIcon is also used as an uninstaller, with this line ":%h\AddIcon.exe /u %1 %a", the "/u" tells AddIcon to remove, rather than add the given icon.  AddIcon will check its records for the archive/file combination given, and delete whatever icon was added for it.  If the last item from a program group is removed, AddIcon will remove the group as well.


File Name Patterns

InstArch uses a mechanism called pattern matching to recognize different types of files.  A typical pattern would be "*.exe", which matches all the files with the ".EXE" extension.  The thing that makes this pattern work and most others is a concept known as a "Wildcard", which is a character (in this case "*")  which can "match" one or more other characters.  To illustrate this, let us look at another wildcard character, "?", which can match any other character, that is, just as we look at "F" as equal to "F", we also see "?" as equal to "F", just as we commonly consider the "Joker" in cards to be equal to the 5 of diamonds.  The "*" character is just like "?", except "*" can not only equal "F" but also "FOO" and "BAR" etc.  Thus, if we wanted to write a pattern that recognized backup files that we commonly see floating about our hard disks and whose distinguishing feature is that the last character of the extension has been replaced with a tilde (~), then we would write that pattern like this: "*.??~".

All this, however, is really more than you usually need to know.  Almost all filename patterns can be written like our original example, "*.exe" or "*.zip" etc.  However there is one common feature that is important, and that is the semicolon, which allows you to specify a number of possible patterns.  For instance, we can write "*.exe;*.com" which will match files ending in .EXE and those ending in .COM.

One other thing that is important to understand is that if InstArch finds two patterns that match a file, it will select a "best" one, based on which pattern matched the most characters exactly.  Thus if you configure a viewer for "*.au", and another for "*.*", then the one associated with "*.au" will be chosen for all files with that extension.  If, however, both patterns match exactly the same number of characters, then all bets are off, as InstArch will choose one randomly.  Note, however, there is one trick that can be employed here, as InstArch considers matching a "?" as slightly better than matching a character against "*", so one could perhaps have two patterns, "*.au", and "?*.au", where the latter would consistently be chosen over the former.  This trick could be useful in configuring archivers where it is impossible to tell two archiving schemes apart based on their names, but one scheme is more common than the other.

The pattern "*" will, as in DOS, match any file.  If you wish to make a pattern that matches only files with no extension, use "*.".


Variable Substitution

InstArch uses a mechanism called Variable Substitution to allow you to use a single string to describe file destinations and command lines in a manner specific to the file being dealt with.  If, for example, in one of the edit boxes affected by variable substitution, you type "%f", then when the substitution is applied, the name of the file currently being dealt with will replace the "%f".  For instance, if you have selected a file named "foo.bar" and then choose "Copy To" from the Edit Menu, and type "D:\%f" in the ensuing dialog, then you will have done the same thing as typing "D:\FOO.BAR" in that dialog.

In this dialog, %f is not a very interesting variable.  But in the "File Actions" screen, it becomes more important, as, in those dialogs, it is mandatory to give the name of a file for the destination and, as we probably only know a part of our file name, we must have a variable like %f to work with.

Under certain circumstances, only certain variables are available.  For instance, when specifying the unpacking directory, %d, the variable that usually expands to the path where the archive was unpacked is, obviously, unavailable.  The variables are listed below:

%h	The directory in which ZipPiz is installed - most probably C:\ZIPPIZ
%a	The archive name, without the directory and extension.  For instance, if we are editing "GOOBER20.ZIP", %a will expand to "GOOBER20"
%p	The fully qualified name of the archive, e.g. "C:\NETSCAPE\CACHE\GOOBER20.ZIP"
%e	Extension of the archive file, i.e. "ZIP" (note no period).
%d	The unpacking directory - the directory which contains all the files that were unpacked.
%1	The file currently being installed or having its actions changed.  This includes the sub-directory, if any, that the file resides in.  For instance, if the archive contains a file called "SRC\GOBBLER.CPP" then when we deal with this file, %1 will be "SRC\GOBBLER.CPP".
%f	The file currently being installed or having its actions changed.  Note that this does not include the sub-directory, if any, that the file was found in.  That is, if the archive contains a file called "SRC\GOBBLER.CPP", then when we deal with this file, %f will be "GOBBLER.CPP".
%s	The sub-directory under the unpacking directory which %f can be found in.
%r	Just the name of the file; in our running example, it would be "GOBBLER".
%x	The extension of the file; in our running example, it would be "CPP".
The distinction mentioned above about "%f" not having the filename is rather an unfortunate trickiness, as %f would work quite well by itself in so many circumstances, and then fail incomprehensibly in others.  The general rule of thumb is that if you are using "%f" in a destination, that is okay, but if you are using the file in a source context (i.e. in a viewing command or an install command), you probably want to use %1.


File Actions (Properties)
Archivers (Properties)

Choosing the "Archivers" tab of the property sheet brings up this dialog in which you may describe ways in which archives should be handled.  The first field, a combo-box, allows you to enter or edit the name of the archiver.  The "New" and "Delete" buttons to the right of this field allow you to create or delete archiver configurations.  If you press the "New" button, you must then enter the name of the archiver and edit the other aspects of the archiver in the fields below.

The next field, labeled "Extensions" is an edit box wherein you should specify the file name pattern used to identify which archives will be considered archives that can be unpacked with this archiver.

The final field is an edit box where you must enter the command line that should be used when archives of this type are unpacked.  Variable Substitution applies in this field, and the variables %a, %p, %e and %d are available, although you will probably only need %p (the full path name of the archive) as the current directory when the unpack command is executed is the unpacking directory.  Thus, for pkunzip, we would use "pkunzip -d %p" as our command line.  Note that when configuring an archiver, be sure to use whatever options, if any, are required to expand subdirectories (with pkunzip, it is -d).

We have pre-set InstArch with what we think is a fairly exhaustive list of archiving schemes.  If you come up with one that we have not planned for, please tell us about it.

In this screen you will notice one archiving scheme known as Trivial Archives, which the mechanism by which InstArch can deal with just a single file.


Trivial Archives

Suppose, however, we want to combine the nice aspects of some viewer, say WPLANY, which is a nice program for playing just about any sound file, with the nice features of InstArch - being able to play the sound file as often as we like and then automatically copy it to a directory of nice sound files.  This is actually quite possible, by using the "Trivial Archiver" that is set up for you during the install process.  This archiver can be used with any file, and its "unpacking" command simply copies the "archive" (actually a regular file, in this case) to the unpacking directory.


Unix and DOS Text files

InstArch provides facilities for the conversion of text files created for Unix machines to a form suitable for use in MS-DOS environments.  Accessible from the main screen through the Tools Menu and the Unpack Dialog.

Unix text files are different from DOS text files in how lines are separated.  Lines of Unix text are separated from each other by a special character known as a linefeed, while in MS-DOS, lines of text are separated by two characters, a carriage-return and a linefeed.  Therefor, conversion between these two formats is accomplished just by inserting the carriage return characters at the appropriate points in MS-DOS files.  The danger here is that one cannot just do this blindly: as non-text files contain characters that, in text files, would be interpreted as newlines, but in non-text files, they may carry other connotations that would be lost or corrupted if a new character was inserted before them.

InstArch has a very conservative mechanism for determining what files constitute Unix text.  It will not automatically convert any file that contains characters not in the usual (non-extended) ASCII set.  That is, it will take the presence of characters with codes greater than 126 or with codes less than 32 (excepting carriage return, newline, formfeed, tab, and bell).  This conservative policy ensures against accidental corruption of data, but is, unfortunately, easily fooled by documents containing foreign characters (umlauts, for example).


File Actions (Properties)
Storage (Properties)

Choosing the "Storage" tab of the property sheet brings up this dialog in which you can select where InstArch stores certain things.

The first items in this dialog box deal with your "archive repository".  If you give a directory here, it will be used as the default location for storing temporary archives - that is, for storing archives that would normally be deleted by the program which invoked InstArch.  The "Browse" button can be used to select a directory using the Directory Selection Dialog.

In the edit box labeled "Default Unpacking Directory" you can specify the default directory for unpacking archives.  Variable substitution applies in this field, the only with %a, %p, and %e being defined and really only %a (the archive name, sans directory and extension) will be of use.  Typically, a value such as "D:\NETSTUFF\%a" is best here.  Some people may want to operate in a mode where files never stay in the unpacking directory - they are always moved to a better home or deleted.  If this is for you, then you will probably want to go with a fixed directory name (no %a in it) and have the checkbox labeled "Consider this directory to be temporary storage" checked.

The edit box labeled "Store installation records in" should be used to specify the directory where the installation records (.PIZ files) should be stored.  These files describe what files came from what archive, where they are on your system, and how to run any un-install programs you may have specified.  The value supplied here will be the directory used in the initial value of the "Store installation information in" the Install Files dialog.


Behaviors (Properties)

Choosing the "Behaviors" tab of the property sheet brings up this dialog in which you can set certain aspects of InstArch's behavior.

Show installation dialog

If this checkbox is not checked, the Installation Dialog will be shown only if there is more than one program set for execution during the install.  Users should probably leave this box checked until they are genuinely sick of pressing "OK" in the Installation Dialog.

Automatically do Unix-to-Dos conversion after unpacking

If you check this box, InstArch will, by default, scan for and convert Unix Text files to DOS Text file format after the archive is unpacked.  For a description of the scanning and conversion process and what this is all about, see Unix and DOS Text files.

Show unpacking (initial) dialog

If this checkbox is cleared, then the unpacking dialog (the dialog that usually shows up first) will only be shown if there is some reason why the default values cannot be used or there is no single best archiver for the archive to be unpacked.  If you have cleared this box and continue to see the unpack dialog, see The Archivers Property Page and File Name Patterns for information that will help you fix this.  As with "Show installation dialog", users should only clear this box after they are quite comfortable with InstArch.

Enable tool-tips

Check this box if you want tool-tips, clear it if you do not.  Typically, only experienced users on slower machines will be interested in clearing this.

Confirm Overwrites

Check this box if you want to be consulted whenever a file is going to be overwritten.  If it is cleared, then you will only be hassled if the file in question is read-only.

Sort Files By

This indicates the default sort order you prefer.  See the Sort Menu for more details about what this will do.

Backup overwritten files

This indicates under what conditions do you want overwritten files to be backed up.  The first two options, "Yes" and "No" mean "Always" and "Never" respectively, and the last one allows you to specify that you only want files smaller than a certain size backed up.


Virus Scanners (Properties)

Choosing the "Virus scanners" tab of the property sheet brings up this dialog in which you can set up virus scanning programs for use with InstArch.  You can have as many as two different virus scanning programs set up for use with InstArch at any given time, these are referred to as the "primary" and "secondary" scanners.  The difference between the two is that the "primary" scanner can be invoked automatically after unpack, and the primary scanner appears first in the Tools Menu's virus scanner options.

Accordingly, both the primary and secondary scanners have fields for the name of the scanner, the command line that will invoke the scanner, and a checkbox that indicates whether the scanner will also check files in subdirectories.  As usual, Variable Substitution applies in the "Command" fields, where %a, %p, %d, and %e all have meaning.  Another thing to note is that the scanner is assumed to be a DOS program, and is invoked in a command shell.  Further, InstArch expects the program to return an indication of whether it found any viruses or not in an exit code (0 if the archive scanned clean, non-zero otherwise).  Further, since the command shell immediately disappears after the scanner is finished, it may be wise to use the "askok" program provided in this distribution.  This trivial little program just waits for a key to be hit, if that key is an escape, it exits with a non-zero exit code, and if it is any other character, it returns with a zero exit code.  Thus it can be very handy for virus scanners which either do not return an indication of the result of a scan or which you are not certain of by entering a command like "scan /sub /nomem . & askok".

You can cause the primary virus scanner to be run automatically by entering a filename pattern in the editbox for "Run automatically after unpack if archive contains files matching".  Typically, you will want to use the pattern "*.exe;*.com" here as these are the only files which at the moment can have detectable virii.


Viewers (Properties)

The Windows File Manager allows you to set up "associations" between file types and commands to run when you double-click files of that type.  InstArch uses these associations, but there can be occasions where, within InstArch, you want to use a different mechanism to view the files than the one you like to use in the program manager.  This page allows you to define these overrides.

The combo box labeled "File Type" allows you to edit and enter the name of the file types which the viewer you are configuring can work with.  In the "Extensions" field you should enter a file name pattern which matches the files that you want this viewer to work with.  The "View Command" field should be filled in with the command line to invoke when viewing files of this type.  Variable Substitution applies in this field, with all the variables defined.  The big one to use here is %1, which expands to the pathname of the file you are currently looking at.

Remember that the term "viewer" is used here in a fairly broad way.  It just refers to a command which allows you to inspect the file in question.  For instance, one might configure a viewer for sound files with a command like "wplany %1", or a viewer for executables like "%1", which would just run the program.


Install Files
Install Files (File menu)

To install the files, select "Install Files" from the File Menu, or access it via one of these:

Shortcuts

Toolbar:

Keys:	CTRL+I

Unless you have specifically instructed InstArch otherwise, a dialog will appear that allows you to specify various details about how the installation should be done.  The gadgets in this dialog are described below.  As usual, "OK" proceeds with the installation with the values you have supplied and "Cancel" returns you to the Main Screen without changing things.

Order of execution

The first segment of this dialog is concerned with the order of execution of the file(s), if any, marked for execution during installation.  The various command lines that are to be run are listed in the list along with "DELETE/COPY/MOVE files".  Commands listed before this line are done before InstArch moves all the files around, and commands listed after this are done afterwards.  You can change the order of execution by selecting a command line whose timing needs adjustment, then clicking on the "Sooner" or "Later" buttons to make the command happen earlier or later in the installation process.  As it is actually fairly rare to use an execute-on-install program, in most cases this section will need no attention.

Copy archive to:

The items below this list box concern whether you want to make a copy of the archive and where you want to put it.  Typically, one would only use these fields if you were invoking InstArch from a program that will remove the archive after InstArch exits.  The edit box should be filled in with the appropriate destination, possibly by using the "Browse" button at its right, which brings up a File Save Dialog which you can use to select the destination.  If the checkbox is checked, the file will be copied, if not, the archive will be lost.

Save installation information to:

The next series of gadgets, associated with the prompt, "Save installation information to:" dictates where InstArch should store the information about the things that happened during this information.  This file can be used later to remove all the files associated with this file should you no longer need them or, get an upgraded version of the package.  Again, the "Browse" button can be used to select a destination through the File Save Dialog.

Confirm before overwriting

Skipping to the top, right, just below the "OK" and "Cancel" buttons, we have a checkbox labeled "Confirm before overwriting", which, if checked, indicates that InstArch check with you before overwriting any existing files during installation.  If it is cleared, it will only confirm overwriting read-only files.

Backup Overwritten Files

The next section, titled "Backup overwritten files", tells InstArch whether or not to make backup copies of files that it overwrites.  If the radio button "No" is selected, then backups are never done, if "Yes" is selected, then all overwritten files are backed up, and if the "If smaller than" is checked, then backups are only done for files smaller than the number of kilobytes listed in the editbox.

In the future, skip this dialog unless there is more than one install script

At the bottom of the dialog is the checkbox labeled "In the future, skip this dialog unless there is more than one install script".  If you check this, in future invocations of InstArch, when you tell InstArch to install the files and there are no more than one files marked for execution during installation, this dialog will not be displayed and installation will proceed according to the default values that you have established.

Default Values

The default values of all of the fields on this dialog except for "Order of execution" can be changed via the Property Sheet, which can be accessed by selecting the Properties Command off of the File Menu.  The default values for the fields associated with "Copy archive to:" and "Save installation information to:" can be set in the Storage Page, while the rest, "Confirm before overwriting", "Backup overwritten files", and "In the future, skip this dialog..." can be adjusted in the Behaviors Page.


File Exit command
Exit command (File menu)

Use this command if you decide not to unpack the archive.  It, like the Close command on the application Control menu, will delete all the files that were extracted from the archive and exit InstArch.  If InstArch was invoked from a program that will delete the archive (such as NetScape) and you have not saved the archive, you will be given the opportunity to save the archive.

Note that this behavior is dependent upon having InstArch properly configured in the invoking application.  See Configuring InstArch as a viewer for details on how this should be done.

Shortcuts

Mouse:	Double-click the application's Control menu button:

Toolbar:

Keys:	ALT+F4


The UnstArch Main Screen

The main screen is where you view the files and where you select what you want to do with the files during uninstallation.  If you have no plans to actually uninstall the files, but instead are just interested in modifying the list of files, you may simply ignore the information and commands associated with the uninstallation process.  The only item on this dialog, shown below, is the list of files.  Through the File List Information command, you may access and modify other bits of information about the files.

Unless you are entirely certain about what the archive contains, you will probably want to start out by taking a look at the files in the list.  For information about this, see viewing a file.  After that, you may modify the list of files and/or the actions that will be taken on them during uninstall, then uninstall, none, some, or all the files in the list, and then exit.

Changing The Uninstall Actions

In most cases, your intent when using UnstArch will be to either view the files, or uninstall the files.  If you simply wish to view the files, you may exit the tool using the Exit Command from the File menu.

You can specify either a full uninstallation or a partial one by indicating which files are to be kept and which removed through commands on the Edit Menu.  If, InstArch was obliged to overwrite a file during installation and you told it to create backups of overwritten files, then it may be possible to restore the file from the backup which InstArch created (if it is still present).  Choices about the disposition of backups can also be made through commands on the Edit Menu.

Changing The File List

UnstArch can also be used in a maintenance role to handle cases such as additional files to be considered part of the installation record, files which should not be considered part of the record, to move files in the record to other drives or directories, or to update the record in the event that a file has been moved by some other mechanism (i.e. the File Manager).

The Move Command off of the Edit Menu can be used to specify where files have moved to and/or move files to a new location.  Note that this command, unlike the move and copy commands in InstArch moves the files immediately - not during uninstall.

The Add and Remove commands can add or remove files from the list.  Note that the remove command does not delete the file, it simply specifies that the file should not be considered part of the file list.

After you have made changes to the file list with these commands, you will probably want to save the Installation Record before exiting - use the Save and Save As commands from the File Menu to do this.

The Main List

The main list  is used to display the files in the archive and what is currently scheduled to happen to them when they are uninstalled.  Each row lists a file, its size, and a variety of glyphs that indicate whether its disposition, the disposition of its backup, and what will happen to the file during the uninstallation.

The leftmost column indicates the file's size, or the message "missing" if the file is not in the place InstArch installed it (again, if has been relocated by another package, use the Move Command to tell UnstArch where it went.)  The next column indicates the status of any backup of the file made during installation.  The column can either be blank or contain one of the following icons:

The smiling face indicates that a backup was made, is still extant, and is identical to the file InstArch created.  The yellow circle with the not-equal sign indicates that the backup was made, the backup file is present, but the backup file is not the same as when InstArch created it.  The yellow circle with the exclamation point in it indicates that InstArch created a backup file, but no backup file can be found for the file.  If none of these icons are present in a line, that means that no backup was made for the file.

The next column indicates what will happen to the file if the files are uninstalled, it can either be blank or contain one of these icons:

The gravestone indicates that the file will be deleted, and the red cross indicates that the file will be restored from its backup.  If none of these icons is present in a row, that means the file will be retained.

If this symbol appears in a row:

It indicates that the file is to be used either as or by a program during the uninstall (i.e. it is a program or input to a program that performs some complex uninstallation procedures.)

Viewing, Sorting, and So Forth

You can look at (or execute, or listen to, etc.) a file on the list by double-clicking it - this is the same as invoking "View" from the View Menu.  You can also use the options on the Sort Menu to change the order of the files in the list.  The Help Menu has a few other ways to start up UnstArch's help facilities.

Uninstalling the Files

After you have changed the file actions to your satisfaction, you can execute them by selecting Uninstall Files from the File Menu (ALT- F, I), or by clicking on the install button in the toolbar, or by typing CTRL-U.  Be careful with this, as,unlike InstArch, no dialog appears after you invoke this command.  Hence, you could easily delete a bunch of files if you choose this option too quickly.

Configuring Defaults

InstArch and UnstArch share information about how you want them to work.  You can modify these properties by selecting the Properties Command from the File Menu.  There are only a few options that affect UnstArch, these can be found under the "Behaviors" tab and the Viewers Tab.


UnstArch's File menu commands
File menu commands

The File menu offers the following commands:

New	Creates a new file list.
Open	Opens a new file list.
Save	Saves the current state of the file list.
Save As	Saves the current state of the file list to a new file.
Uninstall	Uninstalls the files in the list and exits UnstArch.
Properties	Edits the behavior of InstArch/UnstArch
1, 2, 3, 4 command	Opens the file list corresponding to the number.
Exit	Exits UnstArch without uninstalling the files in the list.


UnstArch's UnstArch's New command (File menu)
UnstArch's New command (File menu)

This command creates a new list of files.  Before actually performing this command, InstArch will check to see if you have made any changes either to the currently open file list or the actions associated with those files.  If any changes were made, you will be given the opportunity to save/uninstall the files.

After the new command succeeds, you will then want to add some files to the list with the Edit Menu's Add Command and possibly add some information to the File List Info dialog.

Shortcuts

Toolbar:

Keys:	CTRL+O


UnstArch's UnstArch's File Open command (File menu)
UnstArch's Open command (File menu)

This command opens a new list of files.  Selecting this file brings up the File Open dialog box from which you can choose the Installation Record you want to work with.

Shortcuts

Toolbar:

Keys:	CTRL+O


UnstArch's File Save command (File menu)
Save command (File menu)

This command stores any changes you have made to the file list to disk.

Shortcuts

Toolbar:

Keys:	CTRL+S


UnstArch's File Save As command (File menu)
Save As command (File menu)

Use this command to save the installation record to a different file from the one it was loaded from.  Upon selecting this item, UnstArch displays the Save As dialog box so you can select where you want to write the file list.


UnstArch's Uninstall command (File menu)
Uninstall command (File menu)

This command performs the uninstallation of the files in the list in the manner you have specified with the Edit Menu.  Note that unlike InstArch's Install command, no dialog is presented - as soon as you select this item, the uninstallation gets underway.  If the installation completes successfully and all the files in the list have been deleted, the .PIZ file associated with this file list will be deleted.

After the uninstall finishes, UnstArch will exit.

Shortcuts

Toolbar:

Keys:	CTRL+U


File 1, 2, 3, 4 command
1, 2, 3, 4 command (File menu)

Use the numbers and filenames listed at the bottom of the File menu to open the last four documents you closed.  Choose the number that corresponds with the document you want to open.


UnstArch's Exit command (File menu)
Exit command (File menu)

Use this command if you decide not to uninstall the files.  If you have made changes either to the file list or to the uninstall-actions of the files, you will be prompted to confirm that you want to exit without saving/performing the actions.

Shortcuts

Mouse:	Double-click the application's Control menu button:

Toolbar:

Keys:	ALT+F4


UnstArch's Edit menu commands

The Edit menu offers commands for changing files in the list and the the action that will be taken during uninstallation:

File List Info	Brings up a dialog which allows you to edit various trivia about the file list.
Delete File	Causes the file to be deleted during uninstall.
Keep File	Causes the file to be retained (unmodified) during uninstall.
Recover File	Causes the file to be replaced with its backup during uninstall
Move File	Causes the selected file(s) to be moved, if they are present, or indicates where they have moved to, if not.
Execute On Uninstall	Causes the file to be run as an uninstallation script or used as input to an uninstallation script..
Add File	Adds a file or files to the list.
Remove File	Removes the selected file(s) from the list.


File List Info (UnstArch's Edit Menu)
File List Info... (UnstArch's Edit Menu)

This command brings up the File List Information dialog which you can use to change various bits of trivia about the files in the archive.


The File List Information Dialog

This dialog which can be accessed through the File List Info... command from the Edit Menu, is used to view and change various bits of trivia about the files in the archive.  This includes the archive from which the files came from, where the archive came from, when it was installed, the directory where the bulk of the files reside, and you can add any notes or comments of your own.

The only field which has immediate importance is the "Installation Directory:"  If you change this, then UnstArch will look at all the files which have relative path (i.e. that do not start with "C:\" or somesuch) and see if they are in the directory you list as the new installation directory.  If so, those files will now be associated with the entry in the new installation directory.  This functions in a manner quite similar to the Move File command, except that relative paths are preserved.

The real importance of this dialog has yet to be realized as future Pragma products are planned which will take advantage of these fields and others.  For instance, the "Archive Came From" field is ultimately intended to work with a product capable of automatically downloading and installing new versions of the archive.  Future versions of UnstArch may be able to re-pack an archive, rather than simply deleting all the files and assuming that the archive is still present somewhere...


Delete File (UnstArch's Edit Menu)

This command indicates that the file should be deleted during uninstall.  It will only be available if you have selected at least one file that is present and not currently marked for deletion.

Shortcuts

Toolbar:

Keys:	CTRL+D


Keep File (UnstArch's Edit Menu)

This command indicates that the file should be not be affected by the uninstall.  It will only be available if you have selected at least one file that is present and currently marked to either be deleted or recovered.

Shortcuts

Toolbar:

Keys:	CTRL+K


Recover File (UnstArch's Edit Menu)

This command indicates that the file should be replaced by its backup during uninstall.  It will only be available if you have selected at least one file that is present, has a backup present, and is not currently marked for recovery.

Shortcuts

Toolbar:

Keys:	CTRL+R


Move File (UnstArch's Edit Menu)

This command serves two purposes - it can either be used to indicate where file(s) have moved to, or where a file should be moved to.

If you have selected a single file and selected this command, a dialog will appear in which you can specify a filename.  If the file you have selected is present (i.e. not marked "missing" in the list), then the name you give here will be where you want the file to be moved to.  If the file is missing, then you must select an existing file, and that file is taken to be where the missing file can now be found.

If you have selected multiple files, then a a dialog will appear from which you can select a directory.  If the selected files are present then they will be moved to the directory you have selected.  If the files were missing, then UnstArch looks for the files in that directory.

Shortcuts

Toolbar:

Keys:	CTRL+M


Execute Command (Edit Menu)
Execute On Uninstall Command (Edit Menu)

This command can be used to cause the currently selected file(s) to be used during the uninstallation process.  These files can either be executed themselves or provided as input to some other program.  When this command is invoked, a dialog is popped up in which you should enter the command line that should be executed during uninstallation.  InstArch's Variable Substitution facilities can be used to help in dealing with large selections.

One thing that is important to note:  the command line will be executed from the directory which contains the file - which may be different from the unpacking directory.

Shortcuts

Toolbar:

Keys:	CTRL+X


Add File (UnstArch's Edit Menu)

This command can be used to add new files to the list.  It brings up a file selection dialog from which you can select either one or several files to add to the list.

Shortcuts

Toolbar:

Keys:	+


Remove File (UnstArch's Edit Menu)

This command indicates that the selected file(s) should not be considered a part of this list anymore.  This command does not delete or in any way alter the files on the disk, it just removes them from this list.  This command is available any a file is selected on the list.

Shortcuts

Toolbar:

Keys:	-


Toolbar

The toolbar is displayed across the top of the application window, below the menu bar.  The toolbar provides quick mouse access to many tools used in the application


Status Bar

The status bar is displayed at the bottom of the InstArch window.  It is used to display messages that let you know what InstArch is doing.

The left area of the status bar describes the type and modification state of any files that you select in the main screen.  The same area shows the actions of menu items as you use the arrow keys to navigate through menus as well as messages that describe the actions of toolbar buttons as you depress them, before releasing them.  If after viewing the description of the toolbar button command you wish not to execute the command, then release the mouse button while the pointer is off the toolbar button.

The right areas of the status bar indicate which of the following keys are latched down:

Indicator	Description

CAP	The Caps Lock key is latched down.

NUM	The Num Lock key is latched down.

SCRL	The Scroll Lock key is latched down.


Index command (Help menu)

Use this command to display the opening screen of Help.  From the opening screen, you can jump to step-by-step instructions for using InstArch/UnstArch and various types of reference information.

Once you open Help, you can click the Contents button whenever you want to return to the opening screen.


Using Help command (Help menu)

Use this command for instructions about using Help.


About command (Help menu)

Use this command to display the copyright notice, license terms, and version number of your copy of InstArch.


Help Using Help Command
Context Help command

Use the Context Help command to obtain help on some portion of InstArch.  When you choose the Toolbar's Context Help button, the mouse pointer will change to an arrow and question mark.  Then click somewhere in the InstArch window, such as another Toolbar button.  The Help topic will be shown for the item you clicked.

Shortcut

Keys:	SHIFT+F1


Title Bar

The title bar is located along the top of a window.  It contains the name of the application and document.

To move the window, drag the title bar.  Note: You can also move dialog boxes by dragging their title bars.

A title bar may contain the following elements:

Application Control-menu button

Document Control-menu button

Maximize button

Minimize button

Name of the application

Name of the archive

Restore button


Scroll bars

Displayed at the right and bottom edges of the document window.  The scroll boxes inside the scroll bars indicate your vertical and horizontal location in the document.  You can use the mouse to scroll to other parts of the document.


Size command (System menu)

Use this command to display a four-headed arrow so you can size the active window with the arrow keys.

After the pointer changes to the four-headed arrow:

1.	Press one of the DIRECTION keys (left, right, up, or down arrow key) to move the pointer to the border you want to move.

2.	Press a DIRECTION key to move the border.

3.	Press ENTER when the window is the size you want.

Note:  This command is unavailable if you maximize the window.

Shortcut

Mouse:	Drag the size bars at the corners or edges of the window.


Move command (Control menu)

Use this command to display a four-headed arrow so you can move the active window or dialog box with the arrow keys.

Note:  This command is unavailable if you maximize the window.

Shortcut

Keys:	CTRL+F7


System Minimize Command
Minimize command (application Control menu)

Use this command to reduce the window to an icon.

Shortcut

Mouse:	Click the minimize icon [image] on the title bar.

Keys:	ALT+F9


Maximize command (System menu)

Use this command to enlarge the active window to fill the available space.

Shortcut

Mouse:	Click the maximize icon [image] on the title bar; or double-click the title bar.

Keys:	CTRL+F10 enlarges a document window.


Close command (Control menus)

Use this command to close the active window or dialog box.

Double-clicking a Control-menu box is the same as choosing the Close command.

Shortcuts

Keys: 	CTRL+F4 closes a document window

ALT+F4 closes the InstArch window.

Note that closing the InstArch window has the same effect as choosing "Exit without installing" from the file menu.


Restore command (Control menu)

Use this command to return the active window to its size and position before you chose the Maximize or Minimize command.


Switch to command (application Control menu)

Use this command to display a list of all open applications.  Use this "Task List" to switch to or close an application on the list.

Shortcut

Keys:	CTRL+ESC

Dialog Box Options

When you choose the Switch To command, you will be presented with a dialog box with the following options:

Task List

Select the application you want to switch to or close.

Switch To

Makes the selected application active.

End Task

Closes the selected application.

Cancel

Closes the Task List box.

Cascade

Arranges open applications so they overlap and you can see each title bar.  This option does not affect applications reduced to icons.

Tile

Arranges open applications into windows that do not overlap.  This option does not affect applications reduced to icons.

Arrange Icons

Arranges the icons of all minimized applications across the bottom of the screen.


How to use AddIcon

AddIcon is a program that can help you add program items and program groups to the Windows Program Manager.  It is designed to be invoked during installation and uninstallation for each program or document that is to have an icon in the program manager.  Look at the File Actions property page for more information on how to set this up.

The command line of AddIcon must be as follows:

addicon [ /u ] <file> <archive>

File is the name of the executable or document that is to be invoked from the program manager (i.e. this is the thing that the icon will be associated with.)  Archive is the root name of the archive, AddIcon records this information so that when the program is uninstalled, AddIcon will know exactly which items to remove.  The "/u" option, if present, indicates that this is an uninstall, rather than an install.  In this mode, AddIcon will remove icons that it installed in a previous installation.

If AddIcon is invoked to install an icon in the program manager (i.e., the /u option is not used), then it will ask you to specify the details of the item to the program manager.


AddIcon's main screen

AddIcon is a fairly simple program, and only has one important dialog, which looks like this:

The first line indicates the file for which the icon will be added.  This field is not editable.

The second line is the command-line that will be run when the icon is clicked.  AddIcon will make a fairly good guess at this through looking at the associations in the file manager for the document type.

The "Icon Caption" field will become the caption for the icon in the Program Manager.  The default for this is the root of the file name.

The "Add to program group" choice box is where you specify the group to which you will add the icon.  You can either choose one of the existing groups from the drop-down list, or you can type in a new one.  If AddIcon has been run for another executable/document in this archive, this field will default to the group used in the previous invocation.

The "Working Directory" can be used to specify a directory to change to when the program is invoked.  This option is rarely needed, but if it is, the most likely choice would be the directory which the file is in, you can set it to this just by clicking on the drop-down list and selecting that directory.

If the executable specified in the Command Line has more than one icon in it, you can change to one of those icons in the drop-list.

The "Add Icon" button actually adds the icon to the program manager.  The "Don't Add Icon" button indicates that you do not want to add an icon to the program manager for this file.  The "About AddIcon" button is the most important button in the dialog since it describes how to order the registered copy of ZipPiz.  The "Help" button brings up this help file.


How to use UNGZPTAR

UNGZPTAR is a DOS application for use with ZipPiz that can unpack Unix TAR and compressed TAR formats.  It has already been set up as the default unpacking command for these archive types, so only those folks who want to delve into the nitty-gritties of archive unpacking will need to read further.

You could invoke UNGZPTAR just like this:

ungzptar foo.tgz

However, it supports a number of command-line options, the three that are most important to ZipPiz are /VERBOSE, which tells it to churn out messages for each file that is unpacked, /WAIT which tells it to prompt you after unpacking errors are encountered, and /TOPDIR.  /TOPDIR exists because most Unix archives include the top level directory in the archive - that is, if you get a .TAR file called fubar, with two files in it, foo.txt and bar.txt, unpacking it will probably create a directory called 'fubar' that contains those two files.  This is in contrast to the usual MS-DOS way of packing things, where all the files are in the top level directory of the archive.  (I.e. if you unzipped FUBAR.ZIP, you would almost always see FOO.TXT and BAR.TXT in the current directory, not some new directory.)  If you use the /TOPDIR option and all the files in the archive are unpacked into a common top-level directory, UNGZPTAR will move the files and directories in that common top-level directory into the current directory and delete the top-level directory.  To sum things up, /TOPDIR tells UNGZPTAR that you have already CD'ed to the directory that you want to unpack things in, and this top level directory should override any top-level directory chosen when the archive was created.

Another option that is interesting for folks who invoke this program outside of ZipPiz is /CONTENTS, which just lists the files in the archive, without unpacking it.

UNGZPTAR decides whether the archive is a regular TAR file or a compressed TAR file based on the extension - i.e. .TGZ is taken to be a compressed TAR file and .TAR is taken to be a regular TAR file.  If you have a file that is one or the other of these types, but does not have one of those extensions, you can tell UNGZPTAR what it is by using one of the /UNZIP or /UNTAR options, which inform UNGZPTAR that the given input is compressed or regular TAR, respectiviely.  These options are also important if you invoke UNGZPTAR from the command line and you re-direct the input (i.e. using "<" or "|".)

COPYRIGHT ISSUES:  UNGZPTAR was built from a program called UNZIP which was written by the Free Software Foundation.  The terms of the copyright for this work (GNU's General Public License, aka GPL) specify that any derivative work (such as UNGZPTAR) must be distributed under the same terms as the original.  That means that the source for this program must be provided along with the executable.  The source for UNGZPTAR is provided as part of the ZipPiz distribution, and you were given the opportunity to either install the source code or not, depending on whether you want to or not.  Since, as far as I can tell, there is no public-domain program capable of, by itself, unpacking compressed TAR files, this program may be of some use in its own right, and some enterprising soul could certainly create a distribution of just UNGZPTAR according to the terms of the GPL.  If you choose to, understand that neither Steve Benz or Pragma Systems will not provide any sort of support for such a distribution.


How to use ZPZUNZIP

ZPZUNZIP is a little program which unzip's archives.  It is wholly inferior to PKUNZIP, WINZIP, or just about any other ZIP package except inasmuch as it can legally be distributed as part of ZIPPIZ.  We have provded it, rather than using PKUNZIP or somesuch simply to simplify the installation process and so that our users only do not have to not only pay the ZipPiz registration fee, but PKZIP's as well.  As ZPZUNZIP is incapable of creating a ZIP archive, we encourage users interested in that functionality to look into the following ShareWare products: WinZip, Zip Manager (ZIPMGR), and PKZIP.

ZPZUNZIP's usage is simple - it requires one command-line argument, the name of the ZIP file to unpack.


Modifying the Document

<<TODO: How do you get here?>>

<< Write application-specific help here that provides an overview of how the user should modify a document using your application.

If your application supports multiple document types and you want to have a distinct help topic for each, then use the help context i.d. generated by running the MAKEHELP.BAT file produced by AppWizard.  Alternatively, run MAKEHM as follows:

makehm IDR_HIDR_,0x2000 resource.h

If the IDR_ symbol for one of your document types is, for example, IDR_CHARTTYPE, then the help context i.d. generated by MAKEHM will be HIDR_CHARTTYPE.

Note, AppWizard defines the HIDR_DOC1TYPE help context i.d. used by this help topic for the first document type supported by your application.  AppWizard produces an alias in the .HPJ file for your application, mapping HIDR_DOC1TYPE to the HIDR_ produced by MAKEHM for that document type. >>


Bad Archiver Name

The archiver name you have entered is blank or invalid.  Valid names must be anything but totally blank.


Duplicate Archiver Name

The archiver name you have entered is already the name of another archiver, you must choose a unique name.


Bad Extensions

The list of extensions you have given is illegal.  This field should be filled in with a legal File Name Pattern.  Some examples of valid entries for this field (sans the quotes) are: "*.zip" or "*.exe" or "*.txt;read.me".


Bad Command

The command you have entered is invalid or blank.  Typically, commands use Variable Substitution and look like "notepad %1" or, equivolently, "notepad".


Cannot Delete Last Archiver

InstArch requires that there be at least one archiver program configured, so you cannot delete the last one.  Instead of deleting it, just rename the archiver and change its fields to suit the first archiver you plant to create in your new configuration.


Confirm Archive Deletion

This dialog is just asking to make sure you really intend to delete the archiver.  If you really mean to delete it, answer "Yes" and it will be deleted.  If you did not mean to delete it, press "No" or the escape key or close the dialog box.


Path Name Not Fully Qualified

A fully qualified path name is required here.  Fully qualified paths start with a drive letter, a colon, and a backslash, i.e. "C:\" is a fully qualified name, while "\MYDIR" and "D:MYDIR" are not.


Invalid File Type Name

The file type name you have entered is blank or invalid.  Valid names must be anything but totally blank.


Duplicate File Type Name

The file type name you have entered is already the name of another file type in this action set, you must choose a unique name.


Illegal File Destination

The destination you have selected is invalid.  It must be a fully-qualified path to either a file or an existing directory.  Fully qualified paths start with a drive letter, a colon, and a backslash, i.e. "C:\" is a fully qualified name, while "\MYDIR" and "D:MYDIR" are not.  Variable Substitution applies in this dialog box, so you may use strings like "C:\SRC\%a\%f" to specify that several files are to be moved to a directory that is created during installation.


Invalid Name for an Action Set

The action set name you have entered is blank or invalid.  Valid names must be anything but totally blank.


Duplicate Name for an Action Set

The action set name you have chosen is already the name of another action set.  Since action set names must be unique, you must choose another.


Cannot Delete Last File Type

InstArch requires that there be at least one file type listed under every action set, so you cannot delete the last one.  Instead of deleting it, just rename it and change its fields to suit the first file type you plant to create in your new configuration.


Cannot Delete Last Action Set

InstArch requires that there be at least one action set, so you cannot delete the last one.  Instead of deleting it, just rename it and change it to suit the first action set you plant to create in your new configuration.


Confirm Deletion of Action Set

This dialog is just asking to make sure you really intend to delete the action set.  If you really mean to delete it, answer "Yes" and it will be deleted.  If you did not mean to delete it, press "No" or the escape key or close the dialog box.


Confirm Deletion of File Type

This dialog is just asking to make sure you really intend to delete the file type.  If you really mean to delete it, answer "Yes" and it will be deleted.  If you did not mean to delete it, press "No" or the escape key or close the dialog box.


Bad Archive Repository Directory

InstArch does not believe that after Variable Substitution is performed that the archive repository you have specified will be a valid, fully qualified directory name.


Bad Unpacking Directory

InstArch does not believe that after Variable Substitution is performed that the unpacking directory you have specified will be a valid, fully qualified directory name.


Bad Installation Information Directory

InstArch does not believe that after Variable Substitution is performed that the installation information directory you have specified will be a valid, fully qualified directory name.


Cannot Read Configuration File

InstArch stores its configuration information (the stuff that you find in the property sheet) in a file called instarch.cfg.  This file is usually stored in the same directory with instarch.exe, but at the moment, either this file has been deleted, renamed, or otherwise corrupted.  For the time being, InstArch is proceeding with a minimal (very minimal) set of configuration information.  The best plan from here is to attempt to restore instarch.cfg to its rightful place alongside instarch.exe, if you cannot, you will have to re-create it through the property sheets.


Failed to Write the Configuration File

InstArch stores its configuration information (the stuff that you find in the property sheet) in a file called instarch.cfg.  This file is usually stored in the same directory with instarch.exe, it may be elsewhere (like the invoking directory or in your WINDOWS directory).  Wherever it got it from, though, InstArch is having a tough time writing it back.  The problem is most likely a lack of disk space or, through some bizarre incident, instarch.cfg is now read-only.  If you can correct this, do so and press "Retry".  Otherwise you will have to hope for the best and press "Cancel".  In this event, it is very likely that InstArch will be unable to read the configuration file and will thus fail - meaning that you should delete the copy that is out there and replace it with a backup, if you have one.


The Unpacking Command Returned A Warning

The Unpacking Command returned a non-zero exit code (exit codes are indicators passed between programs - zero indicates that the program executed its task without a quibble, while non-zero exit codes indicate anything from utter failure to minor warnings.)

It did, however, unpack some files, so it is probably just a warning.  If you think so too, just answer "Yes" here.  If you think it is definitely more serious than that, answer "No" and you will be returned to the Unpack Dialog where you can adjust the command to get past this problem.  If you are uncertain about what happened, say, because the screen flashed by too quickly, answer "No" here, then amend your unpacking command with something like "& ASKOK" and run it again.  (Note, do not forget to press "ESC" in response to ASKOK's prompt if you see something that you don't like in the unpacking command's work.)


Unpacker Failed to Unpack

The unpacker command indicated total success, but there did not create any new files in the unpacking directory.  Either the archive is empty, or the unpacking command somehow managed to disgorge the contents of the archive in the wrong place.


Unpacker Failed

The unpacking command failed, press OK to return to the Unpack Dialog.


The Argument List For the Command is Too Long

DOS has a hard limit of 256 characters for command line lengths.  Pitiful isn't it?

If you have the option to "Retry", you will be given a chance to change the command line.  If you receive this message during installation, then choosing "Abort" will cancel the installation and return you to the main screen if this error happened before the files were copied, and will cancel all remaining on-execute commands and continue the installation if done after the files have been placed.


The Command Was Not Found

The command you gave was not found.  Perhaps you misspelled it or it is not in your PATH.

If you have the option to "Retry", you will be given a chance to change the command line.  If you receive this message during installation, then choosing "Abort" will cancel the installation and return you to the main screen if this error happened before the files were copied, and will cancel all remaining on-execute commands and continue the installation if done after the files have been placed.


The Command Was Not an Executable

The file that you tried to execute was not an executable - executables are files with the extensions "exe", "com", "bat", and "cmd".

If you have the option to "Retry", you will be given a chance to change the command line.  If you receive this message during installation, then choosing "Abort" will cancel the installation and return you to the main screen if this error happened before the files were copied, and will cancel all remaining on-execute commands and continue the installation if done after the files have been placed.


Ran Out of Memory

The command could not be executed because it required more memory than you have available at the moment.  Perhaps you are running out of disk space on the drive that has your Windows Swap file (a bad bad bad bad thing, trust me.)


Non-zero Exit Code

The Command returned a non-zero exit code (exit codes are indicators passed between programs - zero indicates that the program executed its task without a quibble, while non-zero exit codes indicate anything from utter failure to minor warnings.)

If you have the option to "Retry", you will be given a chance to change the command line.  If you receive this message during installation, then choosing "Abort" will cancel the installation and return you to the main screen if this error happened before the files were copied, and will cancel all remaining on-execute commands and continue the installation if done after the files have been placed.


Could not Change Directory

This probably means that your unpacking directory is invalid.  Perhaps you have removed a fixed disk, or your network setup has changed.


Cannot Read Unpacking Directory

The unpacking directory could not be opened for reading...  Are you sure you have access to this directory?


Unpacking Directory is not Empty

InstArch likes to see an empty directory to unpack in.  Doing otherwise can lead to a jumbled mess, and that is one thing that InstArch has no plans to propagate.  Your problem could be any one of the following:

1.	You did not know this was going to be a problem and you specified a big dumping ground directory for your unpacking directory.  Instead of doing this, use an unpacking directory like "d:\NETSTUFF\%a" - where %a will be expanded through the Variable Substitution process to the name of the archive.  Then you can have a big jumbled directory full of directories instead of a directory of files...

2.	You have done that and are downloading an archive with the same name as an archive you have already downloaded.  Just press here, go to "OK", and change the name of this archive.  Or, you could go into file manager or something and blast the old directory, if this archive figures to be a replacement.


The Unpacking Directory is Read-Only

You do not seem to have permission to write to the directory you specified for the unpacking directory.  Press "OK" here and you will be sent back to the Unpack Dialog.  From there, either get writre-permission in that directory somehow and try again or change the unpacking directory.


Cannot Create Unpacking Directory

InstArch was unable to create the unpacking directory.  Press "OK" to go back to the Unpack Dialog and pick another directory.


No Such Directory

The directory you gave as the unpacking directory does not exist and you gave instructions not to create it.  Press "OK" to go back to the Unpack Dialog, change the name or select "Create this directory if necessary" to create it.


Unexpected I/O Error

Being unexpected, not much is known.  But it is probably something like out of disk space, a network error, or out of memory, or something like that.  There is a chance that the file is now trashed.


Could Not Figure Out Free Space

For some reason - most likely a floppy drive door not closed or a network problem, InstArch was unable to determine how much free space was on the drive.  It needs to know this information to make sure that the installation you have indicated will actually go through.  If you can fix this problem, press "Retry" else press "Cancel" to cancel the installation until you can fix this (You will be returned to the main screen.)


Not a Regular File

The file was something other than a regular file - i.e. a directory, a drive, a named pipe, or something strange like that.  InstArch is afraid of messing with such files.


Confirm File Overwrite

This message is checking to see if you want to overwrite the given file.  If you choose "Yes", it will be overwritten and a backup will be made if you so indicated.  You can control whether you receive this message or not or not and how backups are done through the Installation Dialog and you can set the defaults for that window in The Behaviors Property Sheet.

If you choose "No", the file will either not be copied or not moved, depending on the action you have chosen for it.


Confirm Overwrite of Read-Only File

This message is checking to see if you want to overwrite the read-only file.  The answer is probably no, because if you choose "Yes" it will be overwritten and thus potentially lost.  But maybe not because a backup may be made depending on how you have set things up.  (Check out the backup-related items in the Installation Dialog and the Behaviors Property Sheet.

If you choose "No", the file will either not be copied or not moved, depending on the action you have chosen for it.


Overwrite Failed

InstArch was unable to overwrite the indicated file - probably due to insufficient permission or perhaps a hardware/network error.  Note that in all probability, InstArch has detected this error prior to the installation actually starting, so pressing "Abort" here will simply return you to the main screen where you can straighten this mess out.  If the moving and copying of files has already started, choosing "Abort" here will also return you to the main screen, however all the files that have already been dealt with will no longer be in the list.  If you can fix this problem outside of InstArch, do that and press "Retry", and InstArch will try to overwrite it again.  If you choose "Ignore", things will stay just like they are (i.e. the destination file will stay as it is and the source file will not move.)


Directory Could Not Be Created

The Directory indicated could not be created.  This is probably because of an illegal directory name in the path or a permission problem (i.e. trying to create a directory on a read-only disk, etc.)  If you can fix this problem, do so and press "Retry".  If you need to change the directory name or something, press "Abort" and you will go back to the main screen.  If you choose "Ignore", the file will not be moved.


File Could Not Be Created

InstArch was unable to create the indicated file - probably due to insufficient permission or perhaps a hardware/network error.  Note that in all probability, InstArch has detected this error prior to the installation actually starting, so pressing "Abort" here will simply return you to the main screen where you can straighten this mess out.  If the moving and copying of files has already started, choosing "Abort" here will also return you to the main screen, however all the files that have already been dealt with will no longer be in the list.  If you can fix this problem outside of InstArch, do that and press "Retry", and InstArch will try to overwrite it again.  If you choose "Ignore", things will stay just like they are (i.e. the destination file will stay as it is and the source file will not move.)


File set for Delete and Uninstall

You indicated that a file was to be deleted during installation and then used when the archive is uninstalled - illogical, no?  It needs to be kept somewhere, InstArch has picked a spot that is as good as any.  If you like this spot, installation can proceed, if not, you will be sent back to the main screen to straighten this thing out.


Files Left in a Temporary Directory

When you checked or left checked the box labeled "Treat this directory as temporary storage" in the Unpacking Dialog you were telling InstArch that you planned to have all the files out of the directory when you were through.  If that is really what you want, and you just left the files here as an oversight, press "Yes" and they will all be marked for deletion.  If you didn't mean it, you can just answer "No" here and the files will be left in this directory.  If this option comes up by default and you do not want this, you can change this in the Behavior Properties Page.  If you press "Cancel", you will be sent back to the main screen to straighten things out.


No More Room On Device

InstArch does not think the installation will succeed because it will run out of space while copying the listed file.  If you think it is right, press "Abort" and you will be sent back to the main screen where you can re-think your strategy.  If you think InstArch is mistaken, you can press ahead anyway with the "Ignore" button - however, running out of disk space and then having to abort the installation could leave things a little gimpy for you.  If you can clear up some space on the drive, press "Retry" after you have done this and InstArch will take another look.


Install Commands Have Run

InstArch is pointing out the possibility that running the install-on-execute commands that have already been run again may or may not be right, thus you may want to cancel their run-on-execute state when you get back to the main screen (select "Run on install" from the Edit Menu, and clearing the checkbox in the ensuing dialog will do the job for you.)


Unable to Remove File

InstArch was unable to remove the listed file.  If you can fix this, fix it and press "Retry", otherwise you should probably just press "Ignore".  Pressing "Abort" will abort the installation - which may be a bit drastic.


Unable to Move File

InstArch was unable to perform the specified move.  If you can fix this, do so and press "Retry", otherwise you should either press "Ignore", to just leave the file where it is or "Abort" to abort the installation and return to the main screen.


Aborting the installation mid-way

This is generally something to be avoided, though InstArch does a decent job of picking up the pieces.  If you need to do this, then you will be sent back to the main screen.  All files that have already been deleted, moved, or copied will be removed from the file list.  If you had any files marked "Install on Execute" that have already run, you should consider whether or not they will like being run again.  If not, you will want to cancel their run-on-execute state (select "Run on install" from the Edit Menu, and clearing the checkbox in the ensuing dialog will do the job for you.)


Error Writing Uninstall Information

InstArch was unable to write out the uninstall information (PIZ-file).  Choosing "Retry" will try to write the file again, "Cancel" just skips writing the file.


Archive Repository Gone

The Archive Repository Directory no longer seems to exist.  You can fix this by choosing the Properties Command off of the File Menu and then the Storage tab.


Could not copy Archive

The archive could not be saved as specified.


Converting non-Text File

InstArch really and truly believes the file is a data file, not a UNIX text file.  If you really think it is, press "Yes" and InstArch will do the best it can with it.  Pressing "No" will continue on with any other files you may have selected.


Converting non-Text File

InstArch thinks there is a chance that the selected file is not a UNIX text file.  If InstArch is mistaken, press "Yes" and InstArch will go ahead and convert it.  Pressing "No" will continue on with any other files you may have selected.


Save Archive To Be Deleted By Caller Confirmation

InstArch believes that the calling program will delete the archive file and wants to give you the opportunity to save it to somewhere else before this happens.

If the calling program really will not delete the archive or you are tired of being hassled by this message, you can fix this by changing how InstArch is configured in the calling program


No Such Archive File

InsrArch could not find the archive file named.  This in all probably means that it is not properly configured for use in the calling program.


Invalid Name for an Viewer File Type

The viewer file type name you have entered is blank or invalid.  Valid names can contain anything but cannot be totally blank.


Duplicate Name for an Viewer File Type

The viewer file type name you have chosen is already the name of another viewer file type.  Since they must be unique, you must choose another.


Cannot Delete Last Viewer

InstArch requires that there be at least one viewing program configured, so you cannot delete the last one.  Instead of deleting it, just rename it and change its fields to suit the first viewer you plan to create in your new configuration.


Confirm Viewer Delete

InstArch is just making sure you really want to delete the viewer configuration.  If you are serious, press "Yes".


Invalid Name for a Virus Scanner

The virus scanner name you have entered is blank or invalid.  Valid names can contain anything but cannot be totally blank.


Invalid Name for a Virus Scanner

The virus scanner name you have entered is blank or invalid.  Valid names can contain anything but cannot be totally blank.


Virus Scanner Returned non-zero

The virus scanner command has indicated by its exit code that the files in this archive may have a virus in them.  HOWEVER!  This exit code cannot be taken as a certain indication that there was a problem - the best way to tell is to look at the output of the virus scanner.

If InstArch has correctly read the meaning of the virus scanner's exit code, though, you should answer "Yes", so that InstArch can delete the files before they do any harm.  InstArch overwrites the offending files so that they cannot be recovered.

If you have run any viewers on the files in the archive, there is a chance that you have already let the genie out of the bag.  But whether this has happened or not, we recommend running a virus scanner on your whole system as soon as possible.  A backup would probably be in order as well. NOTE!  When you run a virus scanner from InstArch, it just scans the files in the archive - a computer virus can easily jump out of this directory and infect something else, that is the reason we say that just running a viewer (which sometimes execute the program being viewed) can infect other parts of your system.

If after pressing "Yes" here you get messages to the effect of being unable to delete certain files because of "file not found" errors, that probably means that the virus scanner has already taken the liberty of deleting the infected files.  Just "Ignore" the messages, exit InstArch, and do a full virus scan.


No Unpacking Directory Specified

You must select an "Unpacking Directory" on this dialog into which the files will be unpack.  The directory you give need not necessarily exist yet, if you select the "Create this directory if necessary" option.  You can use the "Browse" button to help you choose all or part of the path.


Confirm Deletion of Read-Only File

The named file is a read-only file, UnstArch is just making sure that it really should be deleted.  If you choose "Yes" the file will be removed if possible, and if you choose "No" it will remain as-is.


Restore Failed

UnstArch was unable to replace the file with its backup, the error message indicates what prevented this from happening.  If you choose "Ignore", this problem will be skipped and the file will be left in whatever state it is currently in.  If you can fix the problem or there is some other hope that a second try might help, press "Retry".  If you press "Cancel", the uninstallation will be halted.


Confirm Exit without Uninstalling

UnstArch noticed you made some indications of what was to happen during uninstall and wants to be sure you really want to exit without performing this uninstall.  If you say "Yes", the uninstall will take place in the manner you specified.  If you answer "No", the uninstallation will not be done and UnstArch will exit.  If you answer "Cancel", you will be returned to the main screen.


File Unreadable

The named file was inaccessible for the reason given.  If the reason is "Permission denied" or "Sharing violation", and the file is an executable and you have specified that the file should be deleted or moved, it in all probability means that an instance of that executable is currently running - Windows does not permit changing the file that contains an executing program.  If that is the case, just Switch To that program, exit from it, switch back to here if necessary, and press "Retry".

If that is not the case, but you can somehow fix the problem, press "Retry".  If you press "Abort", you will be returned to the main screen with no harm done.  If you press "Ignore", the problem will be ignored.  This means that if the file is marked for anything other than "keep", that operation will in all likelihood fail.


No Caption

You need to specify a caption for the new icon.  For information about how to do this, look at the help for the main screen of AddIcon.


No Command Line

You need to specify a command-line for the new icon.  For information about how to do this, look at the help for the main screen of AddIcon.


No Program Group

You need to specify a program group for the new icon.  If you want to use an existing program group, select it from the list of groups in the drop-down list.  To create a new group and add the icon to that group, just type in the name of the group you want to create.  For more information about how to do this, look at the help for the main screen of AddIcon.


Bad Command Line

The command-line did not specify a valid executable or document.  If you are invoking AddIcon for an executable, then a fully-qualified path to that executable should appear as the first thing in the command line, optionally followed by a space and any command-line arguments that you need to pass to that executable.  If you are invoking AddIcon for a document, use the "Browse" button to find the executable that you want to use to view the document.

For more information about how to do this, look at the help for the main screen of AddIcon.


Create Group Failed

AddIcon asked the Program Manager to create or select the program group that you specified, but  the Program Manager refused.  This could be caused if you are not running the Windows Program Manager.  If this is the case, then you probably cannot use AddIcon to add things to your Program Manager, and you will not want to run AddIcon as part of the installation process for Windows Applications.  To delete the invocation of AddIcon, go to the File Actions property page, select the Windows Application action-set, and un-check the "Run-on-install" options for all file types that run AddIcon.

Another possibility is that your system is currently heavily loaded, and the Program Manager was unable to respond in time.  If this might be the case, wait for the jobs that are currently bogging down your system to complete, and then try again.


Create Item Failed

AddIcon asked the Program Manager to create the program item  that you specified, but  the Program Manager refused.  This could be caused if you are not running the Windows Program Manager.  If this is the case, then you probably cannot use AddIcon to add things to your Program Manager, and you will not want to run AddIcon as part of the installation process for Windows Applications.  To delete the invocation of AddIcon, go to the File Actions property page, select the Windows Application action-set, and un-check the "Run-on-install" options for all file types that run AddIcon.

Another possibility is that your system is currently heavily loaded, and the Program Manager was unable to respond in time.  If this might be the case, wait for the jobs that are currently bogging down your system to complete, and then try again.


Illegal Option given to AddIcon

The listed command-line option is not one of the options currently supported by AddIcon.  Currently, AddIcon only supports one command-line argument, /U.  Click here for more information on the AddIcon command.


Bad Argument List given to AddIcon

AddIcon was not invoked with the proper command-line arguments.  For information on how to properly use AddIcon, click here.


Invalid Working Directory

The working directory you have specified is not the name of a valid directory on your system.  If you specify a value for this field, it must be the name of an existing directory.  If, as is most often the case, the program you are running does not need to be invoked from any particular directory, you should just leave this field blank.


No Help Available

No help is available for this area of the window.


No Help Available

No help is available for this message box.


File Print command
Print command (File menu)

Use this command to print a document.   This command presents a Print dialog box, where you may specify the range of pages to be printed, the number of copies, the destination printer, and other printer setup options.

Shortcuts

Toolbar:

Keys:	CTRL+P


Print dialog box

The following options allow you to specify how the document should be printed:

Printer

This is the active printer and printer connection.  Choose the Setup option to change the printer and printer connection.

Setup

Displays a Print Setup dialog box, so  you can select a printer and printer connection.

Print Range

Specify the pages you want to print:

All	Prints the entire document.
Selection	Prints the currently selected text.
Pages	Prints the range of pages you specify in the From and To boxes.
Copies

Specify the number of copies you want to print for the above page range.

Collate Copies

Prints copies in page number order, instead of separated multiple copies of each page.

Print Quality

Select the quality of the printing.  Generally, lower quality printing takes less time to produce.


Print Progress Dialog

The Printing dialog box is shown during the time that <<YourApp>> is sending output to the printer.  The page number indicates the progress of the printing.

To abort printing, choose Cancel.


File Print Preview command
Print Preview command (File menu)

Use this command to display the active document as it would appear when printed.  When you choose this command, the main window will be replaced with a print preview window in which one or two pages will be displayed in their printed format.  The print preview toolbar offers you options to view either one or two pages at a time; move back and forth through the document; zoom in and out of pages; and initiate a print job.


Print Preview toolbar

The print preview toolbar offers you the following options:

Print

Bring up the print dialog box, to start a print job.

Next Page

Preview the next printed page.

Prev Page

Preview the previous printed page.

One Page / Two Page

Preview one or two printed pages at a time.

Zoom In

Take a closer look at the printed page.

Zoom Out

Take a larger look at the printed page.

Close

Return from print preview to the editing window.


File Print Setup command
Print Setup command (File menu)

Use this command to select a printer and a printer connection.  This command presents a Print Setup dialog box, where you specify the printer and its connection.


Print Setup dialog box

The following options allow you to select the destination printer and its connection.

Printer

Select the printer you want to use.  Choose the Default Printer; or choose the Specific Printer option and select one of the current installed printers shown in the box.  You install printers and configure ports using the Windows Control Panel.

Orientation

Choose Portrait or Landscape.

Paper Size

Select the size of paper that the document is to be printed on.

Paper Source

Some printers offer multiple trays for different paper sources.  Specify the tray here.

Options

Displays a dialog box where you can make additional choices about printing, specific to the type of printer you have selected.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.


File Page Setup Command
Page Setup command (File menu)

<< Write application-specific help here. >>