Category : OS/2 Files
Archive   : FLIST58.ZIP
Filename : ZSHELL.DOC

 
Output of file : ZSHELL.DOC contained in archive : FLIST58.ZIP
OS/2 ZSHELL version 1.1 Copyright (C) TJD Software 1990 all rights reserved.

This is the documentation for TJD Software's ZSHELL program for
OS/2. This material is part of the FLIST package and you should read
the terms and conditions stated in the package. If you have received
ZSHELL without the accompanying FLIST package then you are in breach
of the terms and conditions for the use of this material.

What it does.
ZSHELL is a 'front end' for use in conjunction with PKWARE's PKZIP2
and PKUNZIP2 products and TJD Software's FB (file browse) program. It
allows you to manipulate entries in a ZIP file by making choices from
a list of the contents of the archive.

What it requires.
ZSHELL requires the presence of PKWARE's PKUNZIP2.EXE and
PKZIP2.EXE programs. The PKZIP package is marketed as SHAREWARE and
is available from most good Bulletin Board Systems and from PKWARE
directly. ZSHELL also requires TJD Software's FB.EXE program which is
part of the FLIST package that ZSHELL itself is part of. ZSHELL
requires OS/2 1.0 (or higher). It will NOT run under DOS or in the
OS/2 compatibility box. Note that ZSHELL will NOT work with the bound
(family API) versions of the PKZIP and PKUNZIP programs.

How to use it.
The best way to use ZSHELL is to 'drive' it from a user defined
keystroke sequence using the FLIST program. If you wish to run it
from the command line the usage is:

ZSHELL filename[.ZIP]

If you are running ZSHELL from FLIST you could set up so that FLIST
runs ZSHELL when a ZIP is 'executed' as follows:

SET $FZIP=%comspec% /c ZSHELL $FN.$FE

Or you can select a user-definable key (such as '9') as follows:

SET $FUSR9$=%comspec% /c ZSHELL $FN.$FE

Once ZSHELL is running you can use the F1 key to show a list of the
available commands. If you use the browse function ZSHELL will create
a temporary subdirectory called $FSZTEMP$.TJD. If this directory
cannot be created or removed ZSHELL will terminate abnormally.

All programs used by ZSHELL must be in the current directory or
a directory that has been included in your PATH statement.

The screen.
When ZSHELL is started with the name of a valid archive it displays
a list of the archive entries and allows you to scroll through the
list at will. ZSHELL will work in 25, 30, 43, 50 and 60 line mode
provided that your OS/2 and video adapter support such modes.
You may change modes at any time simply by pressing Alt and the
first digit of the number of lines required (i.e. Alt-6 to switch to
60 line mode).

You may scroll through the list by using the Up and Down arrow
keys, PgUp and PgDn, Home and End.

Commands.
ZSHELL allows you to enter single keystroke commands that greatly
simplify the handling of archives. Some commands take IMMEDIATE
effect when you enter them whilst others won't be obeyed until you
press the ENTER key.

Currently supported commands are 'S' (browse entry), 'X' (extract
entry), 'D' (delete entry), ^T (set extraction target), F6 (shell to
the OS/2 command processor), ^X (extract ALL files from the archive).
^I (test zipfile integrity) and ESC (quit). You can get help by
pressing the F1 key when the member list is visible.

You can decide whether PKUNZIP will make subdirectories as it
extracts files from an archive by using the ^M command. You can
decide what action PKUNZIP will take when it encounters a file that
already exists by using the ^R command.

The editing keys that may be used when you are being prompted for
the output (target) directory are the same as for the main FLIST
program.

Please refer to the FLIST documentation for details of how to contact
TJD Software for support and enhancements.


  3 Responses to “Category : OS/2 Files
Archive   : FLIST58.ZIP
Filename : ZSHELL.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/