home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Simtel MSDOS 1992 December
/
simtel1292_SIMTEL_1292_Walnut_Creek.iso
/
msdos
/
arc_lbr
/
arcindx2.arc
/
ARCINDEX.DOC
next >
Wrap
Text File
|
1988-06-26
|
5KB
|
113 lines
ARCINDEX.DOC
Version 2.0
06-26-88
Introduction
Archived data files can be a mixed blessing. They surely take up
less disk space, but it is not always so easy to find files that
have been archived. Unless you keep detailed records of where
your files are stored, they can become lost forever amongst all
the other nameless files. ARCINDEX combats this problem by helping
to make the files more visible. Using this program you extract
relevant file information from the archive and save it in catalog
form. The catalog is really no more than an ASCII file that can be
loaded by a database programs, like Reflex (R), where you have easy
access to the file names and the archives in which the files are
stored. Once inside the database, any one of 8 file related
categories can be searched using database commands.
Extracting ARCINDEX
ARCINDEX should contain this document and one EXE file with the
same name. Use any of the dearchiving programs to extract
ARCINDEX. Place the EXE file in the subdirectory where you
normally place PKARC.COM. It is most useful there because from
there it can be called to any other subdirectory without having
to reset your existing path.
Things to know before using ARCINDEX
You really only need to know five things about ARCINDEX to use it
effectively. First, ARCINDEX expects to find the archive to be
cataloged in drive a. Both the drive and path specifiers can be
reset. Second, ARCINDEX saves its extracted information to a
catalog file in its own directory unless otherwise specified. The
file name is CATALOG.TXT and no provision has been made to change
the name in the current version. Third, ARCINDEX creates two temporary
files. The default file names are:
TEMP0.$$$ and TEMP1.$$$
These names are also fixed. You should make sure that these names do
not conflict with existing files because no request will be made
by ARCINDEX before writing to these files. More importantly,
both files are "killed" upon program completion. If the
temporary file names conflict with your application, I will be
more than happy to alter them. Fourth, the extracted data will
be appended to the catalog file. Five, ARCINDEX utilizes PKXARC
to extract file information. Because the differing dearchiving
programs use different command lines, ARCINDEX cannot be used
with programs other than PKARC.
The following information is saved:
filespec, parent archive, disk label, original file size,
... compacted file size, compaction ratio, date stamp, and
... time stamp.
Catalog Procedure
Move to the subdirectory where the catalog to be appended to is
located. Place the diskette containing the archived data files
in drive A. Type ARCINDEX. The rest is pretty much self
explanatory. ARCINDEX uses a Lotus-like menu structure. The original
routines were written by Peter Traversly and modified to fit this
particular application. The menu is quick and provides options to
change configuration and do directory listings using wildcard
filespecs.
What to do with the catalog file
I personally prefer REFLEX. I translate the catalog then merge
the result with a parent database. REFLEX offers most of the
more important search commands. However, since the catalog is in
ASCII, you can also use most word processors or editors. Some offer sort
routines that work much like the filter commands of the nicer
databases.
Usage
ARCINDEX is not copyrighted. You may use it freely in whatever
application you so choose. If you find it useful, spread it
around. I request that you keep the DOC file
attached with the ARC file. If you need help running this
program, or find it has some bugs, write me. I'm of course,
interested.
Necessary information
In running this program you have agreed that you will not hold
me responsible for any damages that may result.
ARCINDEX utilizes library routines extracted from Thomas Hanlins
ADVBAS library, version 4.0 (Copyright (C) 1987, Thomas Hanlin III)
Lotus-like menu structure comes from Peter Traverslys' QBUTIL.BAS. The
routines were modified to fit this particular application.
David A. Wilson
37 Pikehall Pl
Baltimore, MD 21236
======================== Revisions =========================
06-18-88 initial release. Original program contained only windowing
routines and was difficult to setup.
06-26-88 Lotus-like menu structure added. Provisions for directory
listings added.