Dec 092017
An excellent tool box for Word Perfect users. Contains several excellent utilities that will allow you to get the most from WP.

Full Description of File

6TOOLS v. 1.0. 10 essential utilities
for WordPerfect 6.0 (5 more for
registered users). The successor to
WPTOOLS. Shrink files, protect macros,
use document summaries, browse files,
etc. Shareware, $25. From Software by

File 6TOOLS.ZIP from The Programmer’s Corner in
Category Word Perfect
An excellent tool box for Word Perfect users. Contains several excellent utilities that will allow you to get the most from WP.
File Name File Size Zip Size Zip Type
6TOOLS.DOC 70352 21506 deflated
BOOKS.EXE 19472 10905 deflated
COMMENTS.EXE 21072 11403 deflated
FILE_ID.DIZ 241 185 deflated
FONTLIST.EXE 18304 10451 deflated
MERGESUM.EXE 23056 12638 deflated
OTHERS.TXT 15713 5324 deflated
SIXPRE.EXE 15424 8716 deflated
SWAPREF.EXE 11408 6797 deflated
TARGETS.EXE 20144 11049 deflated
TEXTSIZE.EXE 9952 6008 deflated
WP6LOOK.EXE 143136 61585 deflated
WPMCRUSH.EXE 13696 7998 deflated

Download File 6TOOLS.ZIP Here

Contents of the 6TOOLS.DOC file

David Seidman
Software by Seidman
2737 Devonshire Place, N.W.
Washington, D. C. 20008

October 1993

Copyright (c) 1993 by David Seidman



Essential Utilities for WordPerfect(r) 6.0


6TOOLS includes 15 utility programs for use with WordPerfect 6.0 (WP6).
Much of it is based on WPTOOLS, a popular collection of utility
programs for use with WordPerfect Versions 5.0, 5.1, and 5.2 (WP5).
The shareware distribution of 6TOOLS consists of this documentation
file in ASCII format and ten programs: BOOKS, COMMENTS, FONTLIST,
Registered users will also receive five additional programs, DOCINFO,
SIXTXT, STYLIST, WPMSUM and 5or6. All are described here.

NOTE: WordPerfect is a registered trademark of WordPerfect
Corporation. There is no connection between WordPerfect Corporation
and Software by Seidman.

Briefly, this is what the 6TOOLS programs do:

BOOKS Writes a list of the bookmarks in a WP6 document, including
each bookmark's type and the number of the page on which it

COMMENTS Reads WP6 and WP5 document files, extracts the comments, and
writes them to standard output, indicating the pages on which
they appear.

DOCINFO Extracts and lists useful information about WP6 document

FONTLIST Writes a lists of the fonts used in a WP6 or WP5 document and
shows the PRS file the document calls for.

MERGESUM Makes a WP6 secondary merge file (data text file) from
document summaries and DOS directory information, creating a
simple document management system.

SIXPRE Removes deleted (and optionally other) data packets from the
prefix of WP6 document files and removes deleted data packets
from WP6 .SET files. SIXPRE will often significantly reduce
the size of files. It optionally deletes styles, document
summaries, and printer-related information.

SIXTXT Removes unnecessary bytes from the body of a WP6 document,
making the document file smaller.

STYLIST Lists names and descriptions of styles, optionally sorted.

SWAPREF Changes automatic cross references from one type to another
(such as footnote to endnote).

TARGETS Lists the automatic reference targets and references (and
their page numbers) in a WP6 document file, indicating
unreferenced targets and references to nonexistent targets.

TEXTSIZE Shows the size, in bytes, of the prefix and the body of WP6
and WP5 document files.

WP6LOOK Displays one or more WP6 (or WP5) document files specified on
the command line, piped to the program, or entered in response
to prompts. WP6LOOK may be more convenient than WP6 itself
for browsing through documents. Also displays other kinds of

WPMCRUSH Reduces the size of macros by deleting unneeded prefix data
and optionally eliminating the macro source code.

WPMSUM Writes document summaries to standard output for reading,
printing, or processing in useful ways. Can read document
summaries in protected macros, which WP6 and other programs

5or6 Allows batch files to identify WP6, WP5.1, and WP5.0 files.

Running most of these programs from the DOS command line without any
parameters will produce a brief explanation of program usage.

Notes on Command Line Switches

Most of these programs require or allow you to select options by using
"switches" on the DOS command line. The switches for each program are
described below. (Brackets indicate that the switches are optional.)
The discussion indicates that switches are preceded by a hyphen or
minus sign (for example, -P is an optional command line switch for
SIXPRE), but you can always use a slash ("/") instead. Thus, -P and /P

on the command line have the same meaning.

Each item you enter on the DOS command line is separated from the next
by a blank space. Thus, if you use the -C and -R switches with
MERGESUM, your command line might look like this:

MERGESUM *.* -omydocs -R -C

In most cases, where options must consist entirely of single letters,
you can combine them:

MERGESUM *.* -omydocs -RC

Note that case does not matter. The previous example could just as
well be written this way:

MERGESUM *.* -Omydocs -rc

Notes on Input and Output

You normally supply one or more input file names ("Infile") and
sometimes an output file name ("Ofile") on the DOS command line. The
file name may always include drive and path specifications. The
program descriptions mention where wildcards (* and ?) can be used.

Many of the programs write their output to "standard output." By
default, standard output means the screen, so output goes to the screen
in a continuous flow. Instead of letting standard output go directly
to the screen, you can, and usually should, pipe it to another program,
or redirect it to either the printer or a file. For example, screen
display is more useful if you pipe output to the DOS filter MORE:


You can also redirect the output to your printer:

STYLIST *.* >prn

or to an ASCII text file:

STYLIST *.*>outfile



BOOKS lists the names of the bookmarks in a WP6 file, in alphabetical
order. Bookmarks marking blocks are indicated with a B next to the
name. The quick mark is indicated with a Q. The page number on which
the bookmark appears is also listed. Deleted bookmarks sometimes
remain in a WP6 file. They are indicated by a D before the page
number. (A page number of zero will generally indicate that the
reference to a deleted bookmark does not exist.) Since WP6 also
provides a list of bookmarks, BOOKS is useful primarily if you find the
page numbers useful.

Usage: BOOKS Infile

Infile is a WP6 document file
Output written to standard output.


COMMENTS extracts the comments (if any) in one or more WP5 or WP6
document files and writes them to standard output. This allows you to
read all the comments in a document without retrieving the document
into WordPerfect and searching for the comments individually. The
COMMENTS output is sent to standard output, so you can read it on the
screen, send it to the printer, or capture it in an ASCII text file.
The output identifies the page on which the comments appear (for
comments in footnotes that are split between pages in printed output,
the page indicated is the page on which the footnote starts). The
page number for comments in headers or footers is the page on which the
header or footer code is located.

Usage: COMMENTS Infile [-c]

Infile is a WP5 or WP6 document file specification.
It may include DOS wildcards, path, and directory.

Output is written to standard output.


-c Do not include high ascii characters in the
output. Note that a few high ascii characters
may be incorrectly treated in versions of
WordPerfect that do not use the Roman
alphabet. Note also that characters not part
of the standard ascii character set are
displayed as an upside down question mark.



The comments in Myfile are written to standard output.

COMMENTS *.* >prn

Comments in all files in the default directory are printed.

COMMENTS Myfile -c >Comments.out

Comments in Myfile are written to the ASCII text file
Comments.out in the default directory. High ascii characters,
such as letters with accents, are not included in the output.


DOCINFO extracts a variety of useful information from WP6 document
files and writes it to standard output. Here is sample DOCINFO output,
for a single file:

Report for file TEST
Baseline placement is not set
Redline indicator: Font change
Document does not need to be formatted
Document does not need to be generated
Automatic display pitch
Width of screen char: 0.1"
Links should not be updated on retrieval
Links codes should be displayed
Text Quality: High
Graphics Quality: Medium
Show full merge codes
Ink Color: Full color
Hypertext mode is not active
Hiding text not marked for hiding
Set up for printer HP LaserJet IIP
Uses prsfile HP2P.PRS
Personal style library: DS.STY
Shared style library: LIBRARY.STY

Usage: DOCINFO Infile [... Infile]

Infile is a WP6 file specification that may include
drive, directory, and wildcards. Up to 5 Infiles may
be listed.

Output to standard output.



Pipes reports for the files My.Let and My.Mem to the DOS
program MORE for convenient viewing.


FONTLIST displays a list of the names of the fonts used in a WP5 or WP6
document file. (This list is found in the document's prefix.) The
output also identifies the PRS file and printer assumed by the
document. This can be particularly helpful if you have received the
file from someone else.

FONTLIST output may be misleading in several ways. First, the initial
font, or any font specified in initial codes, or any font specified in
a document's initial font setting, may appear on the list even if you
did not use it in the document.

Second, fonts once used in a document but later replaced or removed may
also appear in the list. To avoid listing these fonts, you can FIXPRE
(for WP5 documents) or SIXPRE (for WP6 documents) the document, read it
into WP5 or WP6, and then save it. FONTLIST should then produce a
better list of fonts.

Third, WP6 may list fonts in sizes you did not think you used. Because
you select a font name and a point size separately in WP6, the list may
show combinations of names and point sizes that were not used. And if
you use a character not in a font's character set, WP6 may use
unexpected fonts for that character, with resulting surprises in the

Output for WP5 files lists the fonts in the order found. Output for
WP6 fonts lists them in alphabetical order. Output for WP6 also
indicates whether the font is installed via the PRS file or the DRS
file. Generally, scalable fonts will be installed in the DRS file.
Some WP6 files do not include a list of fonts used, but do include
identification of each font indicated as intended for use. If there is
no list of fonts in the file, FONTLIST lists the individual fonts as
intended, but the point size is not indicated. The PRS and DRS
designations may not be meaningful in that case.

Usage: FONTLIST Infile

Infile is a WP5 or WP6 document file.

Output goes to standard output.


MERGESUM extracts document summaries from WP6 files and writes or
appends them, along with DOS file directory information, to a WP6 data
text file (secondary merge file). The result is a database of document
summaries. You can then use the WP6 Merge and Sort functions to
manipulate the output, creating whatever reports you desire. If you
then convert the WP6 file to a WP5 secondary merge file, you can also
use WordPerfect's Notebook program, a part of Office and Library, or
its DB program, a part of WordPerfect Works, to display and manipulate
the document summaries. MERGESUM can therefore be the basis of a
simple system of document management.

Every MERGESUM output file includes the following fields, which are
taken from the DOS directory information, not the document summary:

1: Volume Label
2: File path (directory)
3: File name (without extension)
4: File extension
5: File size (bytes, 7 column field, right justified)
6: File date (yyyy/mm/dd) from DOS directory (this is the
same as the Revision Date in the document summary)

The remaining fields in the output file depend on your choices. By
default, MERGESUM uses the same fields as are the default fields in a
WP6 document summary. They appear in alphabetical order. Thus, by
default, the remaining fields are the following:

7: Abstract
8: Account
9: Author
10: Creation Date (yyyy/mm/dd)
11: Descriptive Name
12: Descriptive Type
13: Keywords
14: Subject
15: Typist

Note that Revision Date, although one of the default document summary
fields, does not appear on this list, because it is always included as
Field 6 in the secondary merge file.

Using a configuration file, as described below, you can select other
fields to appear after the first six fields in the output secondary
merge file. You specify them by number. The numbers assigned to each
of the predefined fields in the document summary are indicated in the
following list:

1 Abstract
2 Account
3 Address
4 Attachments
5 Author
6 Authorization
7 Bill To
8 Blind Copy
9 Carbon Copy
10 Category
11 Checked By
12 Client
14 Creation Date
15 Date Completed
16 Department
17 Descriptive Name
18 Descriptive Type
19 Destination
20 Disposition
21 Division
22 Document #
23 Editor
24 Forward To
25 Group
26 Keywords
27 Language
28 Mail Stop
29 Matter
30 Office
31 Owner
32 Project
33 Publisher
34 Purpose
35 Received From
36 Recorded By
37 Recorded Date
38 Reference
39 Revision Date [always included as Field 6]
40 Revision Notes
41 Revision #
42 Section
43 Security
44 Source
45 Status
46 Subject
47 Telephone #
48 Typist
49 Version Date
50 Version Notes
51 Version #

Obviously, you would want MERGESUM to include those fields you have
chosen to have appear in your document summaries. Specified fields
that are not in document summaries appear in the output file as blank

With two exceptions, Fields 7 and up in the output record for a file
contain whatever is found in the corresponding field in the document
summary. The first exception is that dates include only the year,
month, and day (and always in the format yyyy/mm/dd, for convenient
sorting). The second exception is the Abstract field. By default, if
you select the Abstract field, the Abstract field in the output will
contain whatever the Abstract field contained in the document summary.
However, you can specify that it instead contain roughly the first 400
characters of the document itself (a) always, (b) if there is no
document summary in the document, (c) if there is a document summary
but it does not contain an Abstract field, or (d) if there is a
document summary with an Abstract field, but the Abstract field is
empty (blank).

By default, the output file does not include records for WP6 document
files that lack document summaries. However, DOS directory information
for these files is available. One option (-S) writes this information
to standard output, so you can capture it to an ASCII text file or send
it to the printer. You can also choose to include records for these
files in the output file, using just the DOS file directory information
(-A) or also including the first roughly 400 characters of the document
text as the abstract (-C) (assuming you selected Abstract as one of the
fields in the output).

MERGESUM permits use of an "indirect" input file specification. If an
input file name on the command line is preceded by @ (e.g.,
@c:\wp60\flist), the file is not a WP6 document, but an ASCII text file
containing a list of input file specifications, one per line. (If you
want to use MERGESUM on a WP6 file whose name begins with @, you must
specify that file in an indirect file, not on the command line.)

Usage: MERGESUM Infile [Infile] -oOfile [-Gconfigfile] [Options]

Up to 5 Infiles, which may include wildcards.

If Infile is specified as @Infile, infile is an ASCII
text file containing a list of filenames

-oOfile the secondary merge output file

-gConfigfile (Optional)

Configfile is an ascii text file containing the
numbers of the document summary fields you wish to
include in the output file. Fields 1 through 6 of the
output will be included in any event. If you do not
include a Configfile, the default fields are selected.
If you do include a Configfile, the default fields are
NOT selected unless you include their numbers in the

Options: (separated by blanks, e.g., -A -U, or single
letter options, but not -D, can be combined, e.g.,

-U Update the output file (appends to the output
file if it already exists, but does not check
for duplicates). IMPORTANT NOTE: each record
in a data file must have the same fields
defined, and they must appear in the same
order. Therefore, if you use a Configfile,
make sure you use the same Configfile each time
you update the output file as you did when you
first created the output file.

-E Process Infile through directory trEE. Thus,
if an infile is c:\*.* and you use the -E
option, MERGESUM will process every file on
drive C. Similarly, c:\wp60\*.* with the -E
option will process every file in directory
c:\wp60 and each of its subdirectories.

-A include All WP6 files in Ofile, even if they
have no document summary.

-C like -A, but includes the beginning of the
document text as the Abstract for those files
lacking a document summary.

-B replace Blank abstract fields by the beginning
of the document.

-R Replace all abstract fields by the beginning of
the document.

-Dmmddyy or mmddyyyy

Process only files dated mmddyy or later. If
yy, century is 19. For months, days, or years
less than 10, initial zero must be specified
(e.g., 060991). Year must be greater than 1979
and less than 2100.

-S information on files with no summaries written
to Standard output.

Note: You can use -S along with -A or -C.


MERGESUM c:\memos\*.* c:\notes\*.* -oe:\admin\mydocs -CRU -d010191

This example processes all the files with DOS file
dates (i.e., revision dates) of January 1, 1991, or
later in subdirectories memos and notes on drive c:,
adding the output to the existing data file
c:\admin\mydocs (or creating a new file of that name if
one does not already exist). Files are included in the
output whether or not they have document summaries
(-C). In all cases, the abstract field in the output
consists of the first 400 characters in the document
file (-C for documents without document summaries, -R
for documents with document summaries). The default
field selections are used.

The Configuration File

The optional configuration file is an ASCII text file, each line of
which specifies one and only one document summary field to include in
the output file. Fields are indicated by number, and the number must
begin in the first column on the line. You may find it convenient also
to indicate the name of the field on the line. You can leave a blank
following the number of the field and then enter its name and any other
information you want. For example, here is what a short configuration
file might look like (remember that the numbers begin at the extreme
left of the line, with no leading blanks):

5 Author
16 Department

This file would cause document summary fields 5 (author), 12 (client),
and 16 (Department) to appear in the output file, in addition to the
six fields that always appear. Note that because document summary
field 1 (abstract) is not included, abstracts will not appear in the
output file no matter what command line switches you use.


A. WP6 Document Files

WP6 document files have two sections: the prefix (created by WP6),
which contains document default settings, font information, styles,
footnotes, and much more information; and the document body, which
contains text and codes the user entered. SIXPRE strips certain
information out of the prefix, including both obsolete information
("deleted data packets") that is simply taking up space unnecessarily,
and other information (depending on your choices). Much of the
optionally stripped information concerns printers and fonts. When you
retrieve the stripped file back into WP6, WP6 restores the printer and
font information. (Note: SIXPRE leaves in the file the information
about which fonts you selected, so the document should use the same
fonts after restoration -- unless they are no longer available.) The
restored PRS file is the default PRS file at the time you retrieve the
document, not necessarily the original PRS file.

The most common reason for using SIXPRE is simply to make document
files smaller, which SIXPRE can do in several ways. Getting rid of the
obsolete information obviously leads to smaller files. Getting rid of
printer and font information can save space on disk while you are
simply storing a file; if the file is used again, the information gets
added back. And once you have finished spell checking a document for
the last time, there is no longer any need to take up space on disk
with the list of words you told the spell checker to skip for this
document only, the document's own dictionary. You can also use SIXPRE
on macros; none of the information SIXPRE removes from a prefix is
essential to macros (but WPMCRUSH is a better choice for shrinking

SIXPRE's predecessor, FIXPRE, which performs similar functions for WP5
files, is useful in a number of other situations as well. It often
cures strange and puzzling problems with files. The same appears to be
true of Sixpre.

B. WP6 .SET files

SIXPRE can also remove deleted data packets from your WordPerfect 6.0
.SET file, which is usually named WP{WPC}.SET (the .SET file normally
has a different name if you are using WordPerfect on a network).


Usage: SIXPRE Infile [Outfile] [-Option] . . [-Option]

Infile is the WP6 document or .SET file to be fixed.
May include wildcards, path, and directory.

Outfile is not required. It will not be used if
Infile contains wildcards. If Outfile is used, Infile
will be unchanged, and the SIXPREd file written to
Outfile. If Outfile is not used, Infile will be
renamed (as a backup), and the SIXPREd file will be
written under the original Infile name. The backup
file name is based on the Infile name. It is the main
part of the Infile name, with a new extension. The
backup file will NOT overwrite any existing file.
Suppose the Infile you supply is LETTER.DOC. The
program tries to use the name LETTER.F01 for the
backup. If a file with that name exists, the program
tries LETTER.F02, and so on through F99 (where the
program gives up and asks you to provide an output
file name). When the program is finished, LETTER.DOC
will be the SIXPREd file.

Options: (Each may be listed with - and separated
from the next by a blank, or you may combine options
after a single -. Thus -K -E and -KE are both valid.)

-K Kill (do not preserve) the backup file. The
.Fxx file will be deleted when the program
finishes. This option can be DANGEROUS. Use
it only after careful testing shows that
SIXPRE will do exactly what you want to do.

-E Process input wildcard specification through
the directory treE. For example, if Infile is
c:\wp60\*.*, SIXPRE will process all files in
c:\wp60 and all files in the tree of
subdirectories branching from subdirectory
wp51. Thus it would process all files in
subdirectories c:\wp60\memos, c:\wp60\letters,
c:\wp60\letters\jan, etc.

-T DOS directory entry for the output file has
the date and Time of the input file.
Otherwise, current date and time are used.

-A Process wildcard files only if Archive bit is
set. Useful if you use SIXPRE to save space
before backing up your files. Avoids re-
SIXPREing files already backed up.

The remaining options are ignored if the input file is
a setup file.

-D With this option, SIXPRE strips only Deleted
data packets from the document prefix.
Without it, other information is also

The remaining options have no effect if -D is chosen.

No Strip Options:

-P With this option, SIXPRE does not strip
Printer-related information from the prefix.
-P is equivalent to -BLR. There is little
reason to use any of the options PBL and R,
and still less reason to use BL or R instead
of P.

-B Do not strip proportional spacing taBles.

-L Do not strip font List.

-R Do not strip PRS file information.

Strip Options:

-U Strip document sUmmary.

-S Strip all Styles from the prefix (but the
similarly-named structures related to
graphics, such as box styles, are not
stripped; outline styles themselves are not
stripped, but the styles for each level of the
outline are stripped). This option has no
effect if the "document" has no body.
Therefore, the option can be used safely even
if the file specification causes SIXPRE to
process style libraries. If you want to
delete all styles from the prefix of a style
library, you might as well simply delete the
file entirely. Note that stripped styles
disappear not only from the prefix, but also
from the document (but the codes placed in the
document by the style remain). The effect is
equivalent to choosing Delete Leaving Codes
from the Style menu in WordPerfect.

-C Strip the document's diCtionary.

WARNING: If SIXPRE has stripped the printer-related information, do
not attempt to print the document file from disk before WP6 has
restored the printer-related information.


In addition to unnecessary bytes in its prefix, a WP6 document also
contains unnecessary bytes in the document text itself. (Some of these
are in the prefix, because the text of substructures, such as
footnotes, is actually stored in the document prefix.) Two types of
bytes are unnecessary. The first has formatting information placed in
the document by WordPerfect itself. These bytes are unnecessary while
your document is simply stored on disk, because WordPerfect will
recreate them when the document is retrieved. The second results from
the Undo function. These bytes are unnecessary because the Undo
function allows you to undo actions taken only within the current
WordPerfect session. Nevertheless, bytes related to the Undo function,
including deleted text, may be stored in the document.

SIXTXT deletes these unnecessary bytes from a document. The result is
a smaller document, so that you save disk space, although the saving is
not large. You may want to use both SIXPRE and SIXTXT on a document,
retrieve the document, save it, and then use SIXPRE and SIXTXT again.
This is likely to produce the maximum savings in bytes.

Note that SIXTXT also removes identification of the document's PRS file
from the document prefix. When you retrieve the document after using
SIXTXT, the default PRS file will be selected for use with the
document. While this may sometimes be inconvenient, it is necessary so
that WordPerfect will know it has to replace missing bytes in the

SIXTXT gives you a number of options for processing files. These are
identical to options available in SIXPRE, and they are more fully
discussed under that heading.

Usage: SIXTXT Infile [Outfile] [-Option] .. [-Option]

Infile: WP60 Doc. May include wildcards.
Outfile:output file - not used with wildcard input.
If no Outfile, output written to Infile,
backup created (in .T01 pattern).

Options: (format: e.g., -K -T or, e.g., -KT)

-K Kills the backup if no outfile specified
-T output gets Time and date of input file
-A process wildcard files only if Archive bit set
-E process wildcard through directory treE


STYLIST produces a list of up to 1000 styles in document files and
style libraries. The list includes the filename, the name of the
style, and the style description, as well as code indicating the style
location and style type and whether the style is linked to another
style or includes another style. By default, the output is sorted by
filename and within filename by style name. Other sorting options are

Here is a small sample of the output, sorted by style name, from
running STYLIST on the single file LIBRARY.STY that comes with WP6.
Usually, of course, the output would be based on many more files.

LIBRARY .STY Caption O L S - I Caption
LIBRARY .STY Document C D - - - Document Style (Turns on Doc Outline)
LIBRARY .STY FooterA O L S - I Footer A
LIBRARY .STY FooterB O L S - I Footer B
LIBRARY .STY Header 1 O D - - - Alternating Headers with "Page n"
LIBRARY .STY HeaderB O L S - I Header B
LIBRARY .STY Level 1 P L S - - Level 1
LIBRARY .STY Outln Tech 1 P D - L - Level 1 for Technical Outline Style

The first column is the file name, the second is the extension, and the
third is the style name. After the style name there are five columns
with a single character each. The first indicates the type of style (O
for Open, C for Character, P for Paragraph). The next indicates
whether the style is a document style (D) or a library style (L). The
third indicates whether it is a system style (S) or not (-). The
fourth column indicates whether the style is linked to another style
(L) or not (-). The fifth indicates whether the style includes another
style (I) or not (-). The last column has the style description.

Usage: STYLIST Infile [... Infile] [-sortoption]

Up to 5 Infiles may include drive, directory, and

Output to standard output

Sort options (default is sort by filename):

-N No sort
-D Sort on style Description
-M Sort on style naMe
-T Sort on style Type (Open, Paragraph, Character)
-E Sort on file Extension
-L Sort on Location (Lib, Doc)

Example: STYLIST c:\wp\*.sty c:\wp\*.doc -D>styles

List all the styles in the files in subdirectory c:\wp
with extensions .sty and .doc, sorted on the style
description, and write the results to the ascii text
file Styles in the default directory.


SWAPREF changes all the automatic cross references of one type to
another type. For example, it can make all automatic cross references
to footnotes into cross references to endnotes.

The most obvious reason to do this is if you have used the macro that
comes with WP6 to convert all your footnotes to endnotes (or endnotes
to footnotes) in a document. The macro does not fix up your cross
references. If you created a document using footnotes and included
statements like "see n. 1 supra" using automatic cross references,
after you convert the footnotes to endnotes and generate the document,
those statements will no longer work, because there are no longer any
footnotes to refer to -- "see n. ? supra" is not quite what you had in
mind. SWAPREF fixes up the problem.

You might also want to, for example, change references to outline
sections to references to pages, simply because you changed your mind
about which is preferable. In that event, the text ("See section A")
may need changing as well ("See page 1"). For that, you can use the
search and replace function in WP6.

SWAPREF cannot handle references to counters.

SWAPREF does not change the numbers already generated. After using
SWAPREF, you must Generate again so that the new references are updated

Usage: SWAPREF Infile Outfile [-Option] .. [-Option]

Infile is WP6 doc file to change.
Outfile is a new file with the changed references

Options: one or more. Each indicates two types of
references and tells SWAPREF to change the first to
the second. E.g., -FE changes all Footnote references
to Endnote references

Use these letters:
P - Page
S - Secondary page
C - Chapter
V - Volume
E - Endnote
F - Footnote
G - paraGraph/outline number
N - caption Numbers


TARGETS lists the automatic reference targets and references in a WP6
document. It first lists the targets by name, with the number of times
that target name is used. Targets not referenced in the document are
marked by an asterisk. The list of targets is followed by a list of
references, which includes the name of the target referenced, the type
of reference, and the number of references of that type to the
particular target. References to targets not found in the file are
marked with an asterisk. By default, the line after the listing for
each target or reference lists the page numbers on which that target or
reference can be found. (For targets or references in notes, the page
listed is the page where the note call appears.)

Usage: Targets Infile [-n]

Infile is a WP6 document.
Output is written to standard output.
-n Do not include page numbers in output


TEXTSIZE shows the sizes, in bytes, of the two parts of a WP6 or WP5
document file, the prefix (see discussion under SIXPRE above) and the
body. It also shows the sum of those two sizes, which is the total
size of the document. This information may not be useful, but it can
be interesting. If nothing else, it can help you understand better
what SIXPRE and SIXTEXT do.

You should not leap to any conclusions about efficiency from
comparisons of WP6 and WP5 documents with TEXTSIZE. WP6 stores in
document prefixes a good deal of information that WP5 stores in the
body. For example, comments, footnotes, header, and footers are all
stored in the WP6 document prefix, but in the WP5 document body.

Usage: TextSize Infile [-E]
Infile: WP5 or WP6 file specification. May include
wildcards and full path.
-E process wildcard through directory trEE
Output to standard output. Pipe or redirect as needed.


WP6LOOK is a file browsing program for WP6 and WP5 (for simplicity
here, just "WP") document files (but it will also browse other files).
It displays WP document files listed on the command line, supplied in
response to prompts, selected from pick lists, or piped from another
program, such as a file uncompressor. The document summary is
displayed if it exists. The program pauses as each screen is
displayed. If there is more information in the document, you can page
forward. Generally, you can also page backward, although only for a
few screens (the number varies, but is never more than nine). At each
screen, you also have the options of going back to the beginning of the
file (Home), jumping to the end of the file, going on to the next file,
adding to the list of files to browse, or quitting the program. (If
there are no more files, the next file and quit options produce the
same results.) If you chose the file from a pick list, you can return
to the pick list to select another file. You can also search for
strings in the displayed file. And you can "dump" the information on
the screen to an ASCII text file. The top line of the display
indicates the corresponding WordPerfect page numbers.

Because WP6LOOK will accept piped input, it can be used with many file
manager and shell programs to display files. If the program with which
you want to use it allows you to specify the file browser, you simply
specify WP6LOOK. Some programs do not allow you to specify the file
browser, and then some ingenuity is required. For example, QFiler, an
excellent file management program, assumes the file browser is You can use WP6LOOK with QFiler by renaming WP6LOOK.EXE as

WP6LOOK does not correctly format files, but it usually does a
reasonable approximation. The program is designed for use when you
need to rummage through one or more WP documents quickly (or when not
enough memory is available to use WP itself), not for when you care
about the details of formatting. Here are some of the formatting

By default, WP6LOOK reformats documents so that they fit
within the confines of the screen width (although an option
allows lines of up to 254 characters, so that you must scroll
the screen to see the entire line). Paragraphs are
reformatted by default to a 75-character line, although you
can change the number; the right margin is ragged, because
WP6LOOK does not hyphenate. Margin changes and line spacing
are ignored. Multiple columns are placed end to end.

Everything is displayed in the same font.

Tab settings are ignored. Ordinary tabs are displayed as five
spaces, more exotic tabs as a single space. Indent codes are
all treated as ordinary, not left-right. An indent code is
represented as five spaces. Indented text is indented five
spaces, regardless of how deeply the text is indented.

Characters a standard IBM PC cannot display and overstruck
characters are displayed as upside down question marks.

Footnotes and endnotes are displayed embedded in the text
where they occur. They are set off by line breaks and
enclosed between markers (each on its own line) identifying
them. The markers are slightly different for WP6 and WP5, and
for WP5 there is no difference in marking between footnotes
and endnotes. The footnote (or endnote) number is indicated
for WP6 but not WP5.

Initial codes are ignored.

Text within boxes is displayed. Other box content (graphics,
equations) is ignored, although the presence of a box is
indicated and the caption is displayed.

Tables are not displayed as tables. The cells are listed in
sequence, identified by row and column. Certain kinds of cell
contents are not displayed.

If a file selected for viewing is not a WP document file (and if you
are not using piped input), the file is also displayed -- but in a very
different way, with a different kind of display and a different set of
commands. This alternative display mode is described below.

Usage: WP6LOOK [options] [Infile] .. [Infile]

Options and Infiles may appear in any order. Infile may
include wildcards. You may specify as many Infiles as fit on
the command line. If no input file is specified and input is
not piped to the program, you are prompted for a file
specification. If the input file specification you supply in
response to the prompt contains wildcards, you are asked
whether you want to view all files matching the file
specification. If you response N (for no), a list of files
matching the file specification is displayed. You may browse
this list using standard cursor movement keys and select a
single file to browse by hitting the Return key while the file
is highlighted.


-R(Y/N) Reformat text. The default is RY. If you select RN,
text is not reformatted, and the display may be
scrolled so that you can view long lines.

-P Pick list. If you have wildcard file specifications
on the command line, -P produces a pick list (for the
first file specification, and later for the others
when they are encountered as files are processed)
instead of a display of the first file matching the
wildcard specification.

-M Force Mono. If you have a color computer system and
do not like WP6LOOK's color choices, use this option.

-Wnn Screen Width in characters (default is -W75). This
option is like key W, discussed below. It has no
effect if you select RN.

-H Displays help messages.

-? Same as -H

The command line options (other than -H and -?) may also be provided by
means of a configuration file. On startup, WP6LOOK looks for a
configuration file, WP6LOOK.CFG, in the default directory and then, if
you are using DOS 3.0 or greater, in the directory where WP6LOOK is
located. The configuration file is an ASCII text file that includes
one or more of the command line options, one per line, exactly as they
would appear on the command line. (If you include an option in the
configuration file and also on the command line, the command line
option overrides the option selected in the configuration file.)

Once the program starts, operation with WP files is prompted and for
the most part intuitive. The bottom screen line indicates which
keystroke options may be chosen (except for W, D, P, and Alt- F, which
are never indicated explicitly). In some cases, you can use different
keystrokes to achieve the same result. The prompt does not indicate
that flexibility. Here is the full set of options, only some of which
may be available at particular screens:

Move one screen forward: PgD, [space], [return]
To last screen in file: [End]
Move one screen Back: PgU, b, B
To first screen in file: [Home]
To next file (or pick list
if you started there): N
New file spec: Alt-F
Scroll right (left): -> (<-)
Scroll full left: Ctrl <-
Exit from the program: Q, [esc], F7
Search (exact match): S
Find (match ignoring case): F
Line Width: 10-80 chars: W
Dump screen to file: D
Display Pick List P, F5

Displaying Pick Lists

Choosing P (or F5) displays the pick list generated from the most
recently evaluated wildcard file specification. Normally this will be
the wildcard specification that resulted in the file you were viewing
when you chose P, but it will not always be. Note also that if you
used a pick list to select the file currently displayed, the N command
returns you to a pick list.

New File Spec

Alt-F allows you to add a file specification to those you are already
browsing. The prompts work in much the same manner as the prompts
resulting from omitting file specifications from the command line.
Alt-F in effect interrupts the sequence of files to be browsed and
begins a new sequence. After the program finishes browsing the files
resulting from Alt-F, it returns to the sequence it had temporarily

Searching and Finding

Search and Find prompt for a search string. Search looks for an exact
match to your search string. Find looks for a match but ignores
differences in case. (Searching for cat will not match CAT, but
Finding cat will match CAT.) If you have previously done a Search or
Find in the same WP6LOOK session, you will be shown your previous
search string. If you want to use the same search string, simply hit
. You can also edit the search string. If the first keystroke
you hit is a character rather than an editing key, the previous search
string will disappear, and you simply enter (and edit) a new one. If
you are using the RN option, the match may not be located in the
visible part of the screen, but you can scroll the screen to view it.

Search and Find search from the currently displayed screen to the end
of the file. The first screen containing a match is displayed, with
each line containing the match highlighted. After each match, you are
asked whether you want to continue looking for the same string. To
search the entire file, you must start the search at the beginning of
the file (which you can reach with the Home key).

Leading and trailing blanks in the search string can be used if you
want to limit searches to matching whole words. For this purpose,
screen display lines of your WP document file are treated as beginning
and ending with blanks. The search string may include blanks, so you
can search for phrases (limited to 60 characters). However, matches
are limited to a single line if a phrase is split between lines in the
display, you cannot match it.

The search string can be edited using the cursor keys and other keys.
WordStar editing commands are also available. A complete list of
editing commands follows (commas indicate alternatives):

() Accept line
Quit without changing line; don't search
, Cursor left one character
, Cursor right one character
, Cursor left one word
, Cursor right one word
, Cursor to line beginning
, Cursor to line end
, Delete character at cursor
,,Delete character to left of cursor
, Delete to end of line
, Delete entire line
Delete from beginning of line
Delete word to right of cursor
Toggle insert mode on or off. Size of
cursor indicates the mode. Default is
insert mode off.
, Restore original contents of line
after editing

These editing commands work with responses to other prompts as well.

Dumping Screens to a File

When you type a D to dump a screen to an ASCII text file, you are asked
for a file name. The next time you type a D, the same file name will
be proposed. Hit Return to append to that file, or enter a new file
name to use a different file.

Piped Input

Piped input can present problems when more than one file is piped.
Suppose you want to pipe all the files in MYDOCS.ZIP to WP6LOOK, using
Phil Katz's PKUNZIP program. The command line would look something
like this:


This works well if all the files in MYDOCS.ZIP are WP document files.
It will also work well if all the files that are not WP document files
are extracted before the WP document files are extracted. But if the
WP document files are interspersed with the other files, there can be a
problem. The reason is that when input is piped, WP6LOOK can locate
the beginning of a WP document file, but it cannot locate the end of a
WP document file. So once WP6LOOK begins processing a piped WP
document file, it will continue processing until either the end of all
piped input or the beginning of the next WP document file. Thus an
ASCII file which follows a WP document file in a stream of piped input
will be displayed as part of the preceding WP document file. The same
is true of binary files, such as EXE and COM files. However, binary
files may contain information that will cause WP6LOOK to behave in very
strange ways.

Browsing non-WP files

If WP6LOOK finds a file that is not a WP document file, it displays it
in an entirely different way -- the screen looks different, and there
are different commands. The display is not page oriented. Instead, you
can simply scroll backwards and forwards.

Here is a summary of the commands:

Cursor movement: The cursor arrow keys move you one line, or one
column, in the appropriate direction. and move
ten columns right or left. moves to the first column,
moves to display the end of the longest line on screen. and
scroll one screen up or down. and move to
the beginning or the end of the file. (For all these movements,
WordStar-like commands also work.) To jump to a particular line, use
and you will be prompted for the line number.

Searching and Finding: To search for a string, use S or F (or
). You will be prompted for a string, as in WP display mode.
After you have entered the string, you will be prompted for options;
enter as many as you need. Option U yields a case-insensitive search
(like Find in WP5 mode); otherwise the search is case sensitive (like
Search in WP5 mode). Option G searches the entire file, instead of
just from the cursor. Option B searches backward instead of forward.
To repeat the last search, use .

Other Commands: toggles between the normal ASCII display mode
and hex mode. strips the high bit of each character, which
is useful for viewing WordStar files. toggles the display
of tabs between spaces and tab characters. , , and exit
from the program. ,

, and all exit from the display of the
particular file; if you selected the file from a pick list, you are
returned to the pick list, and otherwise you move to the next file.

Memory Requirements

WP6LOOK takes a fair amount of memory. Loading the program requires
about 175K, and once loaded the program demands additional memory. If
not enough is available to meet the demand (the amount demanded depends
on the dimensions of your screen display), the program exits with an
explanation. Beyond that point, insufficient memory may affect program
functions. The number of screens you can move backward is limited by
memory -- with tight memory constraints, there may be no ability to
move backward. Display of non-WP files requires additional memory,
which may not be available. It is even possible there will not be
enough memory to display a pick list under certain circumstances.


WPMCRUSH makes macros smaller in several different ways, which serve
several different purposes. A WP6 macro file has two parts, the text
(or "source code"), which is just ordinary document text, and the
executable code, which is stored in the prefix, and which WordPerfect
creates when it "compiles" the macro. WPMCRUSH always removes from the
prefix of a macro file all the information that is not related to the
executable code (except for the document summary, but you can also
delete that if you wish), which is all WordPerfect needs to run the
macro. Depending on the options you select, it will also remove the
source code, or the executable code, but never both at the same time.

Once you have finished writing and debugging a macro, you no longer
need to keep the source code in the file with the executable macro
code, because WordPerfect needs only the executable code to run the
macro. (You should, of course, save the source code in case you ever
want to modify the macro, but you can save that in another file.
WPMCRUSH by default always makes a backup, which you should generally
keep.) By default, WPMCRUSH deletes not only the prefix information
not necessary for running the macro (except the document summary), but
also the source code. Whenever WPMCRUSH deletes the source code, it
also changes the byte in the macro that tells WordPerfect that the file
is a WP6 document file. This means you can no longer retrieve the
macro file into WordPerfect (although you can still run the macro).
The resulting file format is identical to the file format WordPerfect
Corporation uses for the Coaches it distributes with the program. The
file type is changed because if you retrieve and then save a macro file
that has no source code, the executable code will also disappear,
leaving you with a useless file.

If you delete the source code from a macro, only the file name (or what
the macro displays on the screen when it runs) indicates what the macro
does, and it is easy to forget what it does. You may therefore want to
put some explanation into the document summary. However, because
WPMCRUSH changes the file identification byte when it deletes the
source code, you cannot read the document summary using WordPerfect (or
WP6LOOK or MERGESUM). But you can use WPMSUM, described below, to read
the document summary. If you do not want to use the document summary
for this purpose and the file contains one, you can delete it with the
-U option.

You can also tell WPMCRUSH to preserve the source code. This will
reduce the size of the macro file by getting rid of unnecessary prefix
information, while still leaving a modifiable macro. (The file will
still be identified as a WP6 macro file.) But you will lose certain
kinds of formatting information, such as styles.

Finally, you can tell WPMCRUSH to delete the executable macro code.
(If you tell WPMCRUSH to delete the executable macro code, it will not
delete the source code even if you tell it to delete the source code.)
The macro must then be compiled again before it can be run. This
format is useful if you wish to transmit the file electronically so
someone else can use the macro. By reducing the file size in this way,
you save transmission time. It is also useful if you want to archive
the source code while keeping the executable macro on your hard disk.

Usage: WPMCrush Infile [Outfile] [-Option] .. [-Option]

Infile: WP60 Macro. May include wildcards.
Outfile:Crushed macro - not used with wildcard input.
If no outfile, output written to Infile,
backup created (in .M01 pattern).

Options: (format: e.g., -K -T or, e.g., -KT)

-K kills the backup if no outfile specified
-T output gets new time and date
-A process wildcard files only if archive bit set
-E process wildcard through directory trEE
-S preserve Source text
-U delete document sUmmary
-N Non-running macro (executable code deleted)


WPMSUM extracts document summaries and writes them, in more or less the
format displayed by WP6LOOK, to standard output. You can, of course,
pipe the output to another program or redirect to your printer or a

Although WPMSUM will extract the document summary from any WP6 file
that has one, for most users it is useful mainly because it, unlike
WP6, MERGESUM, or WP6LOOK, will allow you to examine the document
summary of a macro that has been protected so that you cannot retrieve
it into WP6. WPMCRUSH produces such macros. And the Coaches that ship
with WP6 are also macros of this kind. If you want to read the
document summaries of these files, WPMSUM may be your only alternative.

If you use 4DOS (or NDOS), there is another use for WPMSUM. When used
in conjunction with awk, it can turn your WP6 descriptive filenames
into 4DOS file descriptions, so that a 4DOS directory listing will show
those names. awk is a very handy cross between a utility program and a
programming language. Originally a Unix program, it has been ported to
DOS. At least two DOS versions of awk that will serve the purpose
(MAWK, version 1.1.1 or later) and GAWK (Version 2.15 is suitable;
perhaps earlier ones are also) are available for use without charge.
You can find them on various BBS systems, commercial services, and ftp
sites. Instructions for handling the descriptive filenames are given

Usage: WPMSUM Infile [-Option] .. [-Option]

Infile: WP6 macro or WP6 document). May include wildcards.

Options:(format: e.g., -A -E or, -AE)

-A process wildcard files only if archive bit set
-E process wildcard through directory trEE

Output to standard output. Pipe or redirect as needed.



Extracts the documents summaries of all the WordPerfect
coaches and pipes them to MORE for reading.

Moving Descriptive Filenames to 4DOS

To move WP6 descriptive filenames to 4DOS descript.ion files as
descriptions, simply run this 4DOS batch file (see the REM lines in the
batch file for further instructions):

REM This NDOS (4DOS) batch file takes a wildcard filespec
REM on the command line. For any files matching the wildcard
REM filespec, it extracts the WP6 descriptive file name and makes
REM that the description of the file in the NDOS (4DOS) descript.ion
REM file for the appropriate directory, assuming there is not already
REM a description for that file in descript.ion.
REM As written, this batch file requires that ATTRIB, WPMSUM, and
REM MAWK be in the current directory or pathed, and that sum.awk be
REM in the current directory. ATTRIB is a utility included with DOS.

@echo off
if ".%1"=="." quit
set df=%@path[%@full[%1]]descript.ion
attrib -H %df%
wpmsum %@full[%1] | mawk -f sum.awk -v descfile=%df%
attrib +h %df%

Here is the awk program sum.awk that the batch file requires:

# This awk script was written to be used with MAWK 1.1.1.
# It should work with other versions of new awk, except that
# it assumes a built-in function tolower, which many awks do not
# include. But you can write a tolower function. The function should
# lower case a string.

BEGIN{ while (getline < descfile > 0)
ion[tolower($1)] = 1
/^FILE:/{file = $NF}
/^DESCRIPTIVE NAME:/{file = getname(file)
if (file in ion)
print file, substr($0,19,40) >>descfile
function getname(f, a,n)
a[n] = tolower(a[n])
return a[n]

XV. 5or6

5or6 allows a batch file to determine whether another file is a WP5.0,
WP5.1, or WP6.0 document file (WP5.2 files are identified internally as
WP5.1 files, so 5or6 reports them as 5.1 files). It does this by
setting the DOS errorlevel.

Usage: 5or6 Infile

Resulting errorlevel:

50 WP50 document file
51 WP51 document file
60 WP60 document file
98 Other file
99 File not found, etc.

If WordPerfect Corporation follows its recent pattern, a WordPerfect
6.1 file should produce an error level of 61, and so forth. Of course,
at this point there is no way to be certain.

How can you use this? Suppose you had all your WordPerfect files in a
single directory but wanted to separate them out so that the 6.0 files
were in subdirectory WP60, the 5.1 files in subdirectory WP51, and the
5.0 files in subdirectory WP50, while leaving all other files uncopied.
The following two batch files would handle the problem.

First batch file:

for %%f in (*.*) do call mover %%f

Second batch file (Mover.bat)

5or6 %1
if errorlevel 98 goto quit
if errorlevel 60 goto WP60
if errorlevel 51 goto WP51
if errorlevel 50 goto WP50
goto quit
copy %1 \wp60
goto quit
copy %1 \wp51
goto quit
copy %1 \wp50

You might also find 5or6 helpful if certain of your programs work with
5.1 files but not 6.0 files.


Help in using 6TOOLS is available by mail, telephone, and several forms
of E-mail. The best time for telephone calls is weekdays 8pm-11pm
Eastern time. At other hours, you are likely to reach only an
answering machine. E-mail and fax are recommended.

David Seidman
Software by Seidman
2737 Devonshire Pl. NW
Washington, DC 20008
FAX: 202/462-8601
CompuServe: [70441,2414]
Internet: [email protected]


6TOOLS is not in the public domain. Both the collection and the
individual programs are fully protected by copyright.

For purposes of evaluation and testing only, some of the programs in
6TOOLS are distributed as shareware, along with the documentation in
ASCII format only. The first page of this documentation indicates
which 6TOOLS programs are included in the shareware distribution. As
to those programs and the ASCII documentation only, everyone is granted
without charge a license which permits (a) use of the programs for a
period of 30 days for evaluation and testing; (b) making copies for
distribution to others without charge, provided the programs and the
accompanying documentation are distributed together and without
modification; (c) posting the programs, together with the accompanying
documentation, on electronic bulletin board systems. The permissions
granted in this paragraph do NOT apply to the programs, indicated on
the first page of this documentation, that are NOT included in the
shareware distribution.

Use after the 30 day evaluation and testing period requires payment of
a license fee (sometimes referred to as a registration fee). For a
single copy (plus necessary archival copies), to be used on only one
computer at a time, the fee is $25.00. For large quantities, discounts
and site licenses are available. Write for information. Any license
for which payment is properly made is valid for this version of 6TOOLS
and all subsequent minor version changes. For major version changes
(the major version is indicated by the number to the left of the
decimal point -- this version is 1.0, and the next major version would
be 2.0), we reserve the right to charge a license upgrade fee, but we
may or may not require such a fee for major version upgrades.

What do you get for your license fee? You get the latest version of
the all the 6TOOLS programs, including the programs which are not
distributed for evaluation. You get permission to use the programs on
a one computer at a time (and to make archival copies). You get the
warm feeling that you are not violating the copyright laws. You get a
copy of the complete documentation in WordPerfect format. We will
generally send you notification of new versions. And if you let us
know about any problems you have with the programs, we will try to
solve them.

The United States Department of Justice is granted a license, without
payment of fee, for all official use of 6TOOLS.


These programs are distributed without warranties of any kind, express
or implied, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose.

No representation or other affirmation of fact, including but not
limited to statements regarding suitability for use, or performance of
the programs, shall be or be deemed a warranty by the licensor for any
purpose, nor give rise to any liability or obligation of the licensor

In particular, no statement in program documentation shall be deemed a
representation or warranty that the programs will perform in any
particular manner, or perform in any manner whatsoever, or that the
programs are suitable for any particular use or any use at all.



David Seidman
Software by Seidman
2737 Devonshire Place, N. W.
Washington, D. C. 20008




Description Qty. Price

Licensed copy of 6TOOLS @US$25.00 $_____.__

Licensed copy of 6TOOLS for _____.__
registered user of WPTOOLS
@US$15.00 _____.__

Total: $_____.__
D.C. Residents add 6% D.C. Sales Tax: ___.__

Total Charge: $_____.__

Make checks payable to Software by Seidman. Please mark checks

For Credit Card orders, Circle one: VISA MasterCard Diners Club

Card Number: __________________________ Exp. Date: _____________

Name on card: __________________________________________________

Signature: __________________________________________________

 December 9, 2017  Add comments

Leave a Reply