Dec 132017
WPMD -- The File Doctor for Word Perfect 5.x. Version 3.0. Includes new menu driven interface. Attempts to automatically repair damaged Word Perfect files. Files that have lost headers, damaged codes, etc.

Full Description of File

WPMD 3.0 - The File Doctor for WPerf5.x.
Fixes broken WordPerfect 5.x (DOS and
Windows) files. Major upgrade from prior
versions. Now interactive; easier to use,
improved file fixing. Shareware, $35. From
Software by Seidman.

File WPMD3.ZIP from The Programmer’s Corner in
Category Word Perfect
WPMD — The File Doctor for Word Perfect 5.x. Version 3.0. Includes new menu driven interface. Attempts to automatically repair damaged Word Perfect files. Files that have lost headers, damaged codes, etc.
File Name File Size Zip Size Zip Type
FILE_ID.DIZ 236 187 deflated
WHATS.NEW 2340 845 deflated
WPMD.EXE 116896 49439 deflated
WPMD3.DOC 38211 12098 deflated

Download File WPMD3.ZIP Here

Contents of the WPMD3.DOC file

Copyright (c) 1989-92
by David Seidman
September 1992

Software by Seidman's


The File Doctor for WordPerfect(r)

Things can go wrong with WordPerfect 5 (that is, 5.0 or 5.1) document
files. Text may disappear. WordPerfect 5 (WPerf5) may stop
recognizing a file as a WPerf5 document file. And other strange things
may happen. We don't always know why they happen, but we can do
something about them when they do.

If your WPerf5 files get sick, WPMD, the WordPerfect 5 File Doctor, may
be able to help. It cannot help if what should be in your file has
simply vanished from your disk, but that is not what usually happens.
Check the size of your file with the DOS DIR command. If the number of
bytes is not too small, your text is probably still there, and it is
time to call the File Doctor. WPMD cannot cure all the maladies that
may afflict WordPerfect files, but it can cure many of them.

WPMD has two ways of operating. The Ordinary Way is very simple to
use. The other way, Drastic Surgery, is a bit more complicated. The
Ordinary Way is usually all you need, but sometimes you need Drastic
Surgery and sometimes you need both.

What The Ordinary Way Does

WPerf5 function codes are stored as series of bytes that have meaning
to WPerf5, not as what you see in Reveal Codes. If even one byte in a
code is incorrect, WPerf5 can get hopelessly confused. This confusion
can have dramatic results. For example, the entire text of your
document may disappear from the screen; even though the text is
actually all there in the file, WPerf5 shows nothing but a blank
screen. Less dramatically, you may lose part of the text, a "loop" may
develop so that moving the cursor down in the document brings you to an
earlier part of it, or the text may become incorrect in other ways.

WPMD handles this problem by looking for messed up codes. Usually when
it finds them, it deletes them and leaves the message **FIX** in their
place. If WPMD's cure works well, you just retrieve the fixed file
into WPerf5, search for **FIX** (use an Extended Search, because WPMD
may have fixed a problem in a footnote, endnote, header, footer, or
text box), and see if anything is missing at that point. At least one
code is likely to be missing. In addition, you will often see garbage
-- erroneous characters and codes -- after the **FIX** message. The
garbage is the remains of broken codes. Simply delete it.

In rare cases, WPMD will cure the problem without leaving a **FIX**
message. This happens when WPMD figures out exactly what the incorrect
bytes should be and replaces them with the correct ones.

In all cases, when WPMD fixes the file, PROOFREAD carefully. WPerf5
may have changed characters in your text in ways WPMD cannot detect.

What Drastic Surgery Does

Use Drastic Surgery when (a) WordPerfect does not recognize your
document as a WP5 document file ("incompatible file format" is the
usual tipoff to this problem); (b) WordPerfect tells you there is
insufficient space on the WP disk to retrieve the file and you suspect
there is enough space; or (c) all else fails (that is, after you have
tried the Ordinary Way, and after you have tried FIXPRE, which is
briefly described below).

While the Ordinary Way fixes your text, Drastic Surgery does nothing to
the text of your document. Instead, it amputates the document prefix,
the beginning part of the document file you do not see in WPerf5, and
replaces it with another document prefix. This amputation loses a good
deal of information, including graphics, styles, and initial codes
(unless you have the same information available in the prefix of
another file). If the only problem is a problem in the prefix, Drastic
Surgery may be all the cure you need. But Drastic Surgery may simply
allow WPerf5 to get to the rest of the document, where there could also
be problems. So if Drastic Surgery does not fully cure your file, try
the Ordinary Way again, using the re-prefixed file produced by Drastic
Surgery as the input file.

Running WPMD

You can give instructions to WPMD from the DOS command line, or you can
use the program interactively. To use it fully interactively, you
start the program by typing its name at the DOS command line and
pressing ENTER:


WPMD does not allow you to change the colors it uses in interactive
operation. If you do not like the colors, you can start the program
this way:


The program will then run in monochrome mode.

If you start the program like this:


WPMD will display a summary of the instructions for using it in command
line mode.

If you start WPMD with either just WPMD or WPMD -M, the program will
ask you to enter an input file name. Type the name (including drive
and directory, if necessary) of the sick file. When you have finished
typing and editing the file name (conventional editing keys work), hit
the ENTER key. If you include a DOS wildcard (* or ?) in the filename,
a window with a list of files matching the file specification you
provided will appear. Move the cursor to the file name you want to
select and hit the ENTER key. The selected file name will appear as
the response to the program's request for an input file name. You can
then edit it or hit the ENTER key to accept it. If you change your
mind and want to exit the program without selecting an input file,
delete the response to the prompt and hit ENTER.

WPMD will then ask you for the name of an output file, the fixed file
it is to create. It will propose a file name, which you can accept by
hitting the ENTER key. Usually, the name it proposes will be the name
(including path) of the input file, but with the extension FIX. If a
file with that name already exists, WPMD will try extensions from X01
to X99. If all of those are in use with that file name, WPMD will not
propose a file name. If you like the proposal but would like to edit
it a bit, move the cursor with an arrow key before doing any editing.
If you do not like the proposal and would like to enter a new name,
just start typing; the proposed name will vanish. If you would like to
restore the original proposal, hit CtrlR.

If there are problems with the input or output file name you supply,
WPMD will ask you to take corrective action. It should be obvious how
to respond.

After you have supplied the input and the output file names, WPMD will
ask you whether you want to use the Ordinary Way or Drastic Surgery.
If you want to use the Ordinary Way, type O or hit the ENTER key. If
you want to use Drastic Surgery, type D.

Once the Ordinary Way starts, WPMD may ask you if you are sure the
input file is a WordPerfect 5 document file. If it asks, answer with
either Y or N. If the answer is Y, the program continues. If the
answer is N, the program quits. WPMD may also ask you if the input
file is "locked," or password protected. If the answer is N(o), the
program continues. If the answer is Y(es), the program quits, because
WPMD cannot work with locked files. It may also quit in the face of
various problems, which it will explain.

Using The Ordinary Way From The Command Line

In addition to using the Ordinary Way as described above, you can also
start it from the DOS command line:

C>WPMD Infile Outfile [-M]

Infile is the name (including drive and directory, if necessary)
of the sick file.

Outfile is the name (including drive and directory, if
necessary) of the fixed output file.

-M, which is optional, controls colors, as described above. (Do
not use the brackets; they simply indicate that -M is optional.)

For example,

C>WPMD c:\wp50\letters\John.wp5 c:\wp50\letters\John.fix -M

When run from the command line, rather than interactively, WPMD may
respond with various messages and then stop. If it does, you have to
figure out what to do next. For example, WPMD may tell you it can't
find the input file. In that case, you should see if there is an error
on your command line. But some messages make clear that WPMD thinks
there are problems in the input file that it cannot handle in the
Ordinary Way. At that point, you have two choices. First, you can
give up. Second, you can try Drastic Surgery.

Using Drastic Surgery

As with the Ordinary Way, you can use Drastic Surgery entirely from the
DOS command line. That is complicated, and we will explain interactive
operation first.

Drastic Surgery, as noted above, replaces your document's prefix by
another prefix. It can create a prefix by itself, but that prefix will
not have a good deal of useful information that is stored in the prefix
of your document, such as Initial Codes, Graphics, Styles, and so
forth. If you have a good WordPerfect document with a similar prefix -
- that is, a prefix likely to have much the same information as the
prefix on your sick document -- WPMD can use that prefix instead. Once
you tell WPMD that you want to use Drastic Surgery, it asks you whether
you want to use the prefix from another document. Answer with a Y or
N. If you answer Y(es), WPMD then asks you to supply the name of
another file, the file with the prefix you want to use. (You can
respond with wildcards, as in the case of the input file.) If you
leave that filename blank, or if you supply the name of either your
input or your output file, WPMD will use the prefix it creates;
otherwise, it will take the prefix from the file you named.

In order to put a new prefix before the text of your document, Drastic
Surgery needs to know the "offset," the location, in the file where the
text part of your document begins. That information is stored very
close to the beginning of a normal WordPerfect document. Of course,
you would not be using Drastic Surgery if your document were a normal
WordPerfect document. Therefore, the information stored in the file
where the offset of the start of the text is supposed to be stored may
not be valid. Nevertheless, that information is worth trying. WPMD
reads the information. If it thinks that indicates a plausible file
offset, WPMD asks you whether you want to try Drastic Surgery using
that offset. To help you decide whether to try that offset, WPMD also
tells you the number of bytes there would be in the text part of your
document if that were the offset of the beginning of the text. If you
think that number of bytes is at all plausible, you might as well let
WPMD run Drastic Surgery using that offset. At best, it is the right
offset. At worst, it is wrong, the output file is not very good, and
you try Drastic Surgery again. In other words, let WPMD try Drastic
Surgery with the internally stored offset information unless you have a
very good reason not to. The usual good reason is that you have
already tried that once. There can be other good reasons. If the file
you are trying to fix is a 200 page document and WPMD says that, based
on the internally-stored offset, the text of the file is 500 bytes, the
internally stored value is not likely to be right.

If you decide not to use the offset stored internally, you have to tell
WPMD where the text part of the document begins. So that you can do
this, WPMD displays your file in a conventional "hex mode" manner. As
an example, we use a simple file, which contains nothing but the
sentence "This is an example." The hex mode display looks something
like this (some blank columns have been deleted, for better fit on the

000000 FF 57 50 43 3B 01 00 00 01 0A 00 00 00 00 00 00 .WPC;...........
000010 FB FF 05 00 32 00 FF 00 00 00 07 00 0F 00 00 00 {...2...........
000020 42 00 00 00 02 00 56 00 00 00 51 00 00 00 0C 00 B.....V...Q.....
000030 57 00 00 00 A7 00 00 00 03 00 01 00 00 00 FE 00 W...'.........~.
000040 00 00 43 6F 75 72 69 65 72 20 31 30 20 63 70 69 ..Courier 10 cpi
000050 00 00 00 FF FF 6D 00 5B 00 78 00 78 00 78 00 0A .....m.[.x.x.x..
000060 00 01 00 00 00 00 00 C2 01 40 1D C2 01 78 00 14 [email protected]
000070 1E 0C 17 8C 0A 00 00 00 04 11 40 C9 00 29 73 E5 [email protected])se
000080 01 1B 00 FE FE FE FE FE FE FE FF FE FF FF FF FF ...~~~~~~~.~....
000090 FF FF FE FF FF FF FF FF FF FF FF FF FF FF FF FF ..~.............
0000A0 FF FF FF FF FF FF FF 50 61 6E 61 73 6F 6E 69 63 .......Panasonic
0000B0 20 4B 58 2D 50 31 30 39 31 00 00 00 00 00 00 00 KX-P1091.......
0000C0 00 00 00 00 00 00 00 00 00 00 00 00 50 41 4B 58 ............PAKX
0000D0 50 31 30 39 2E 50 52 53 00 DB 01 78 00 14 1E 0C P109.PRS.[.x....
0000E0 17 8C 0A 00 00 00 04 11 40 C9 00 87 CF 01 00 01 [email protected]
0000F0 00 00 00 00 00 00 00 58 02 18 3D 13 22 04 82 FB .......X..=."..{
000100 FF 05 00 32 00 00 00 00 00 06 00 08 00 00 00 31 ...2...........1
000110 01 00 00 08 00 02 00 00 00 39 01 00 00 00 00 00 .........9......
000120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
000130 00 00 23 7C 00 78 00 00 00 00 00 54 68 69 73 20 ..#|.x.....This
000140 69 73 20 61 6E 20 65 78 61 6D 70 6C 65 2E is an example.

Press [ESC] when cursor is at doc start

Most users will care only about the sixteen columns at the right of the
screen, where the cursor will stay. Those columns display the bytes in
your file (including the bytes in the prefix), usually as ascii
characters, although some are displayed as dots. In the rest of the
screen, the first column of six digit numbers has the offset, in
hexadecimal, of the first byte displayed on the line -- most users of
WPMD will, and should, ignore this column. The next sixteen columns of
two digit numbers are the hexadecimal representation of the sixteen
bytes shown on the right. Again, most users will, and should, ignore
the hexadecimal values.

In the example, the entire file fits on a single screen. Most files
will not. You need to move around the document looking for the
beginning of the text and then put the cursor on the first character in
the text (in this case, the T in This). In moving around the file, you
can use conventional cursor keys, PageUp and PageDown, Home to get to
the beginning of a line of sixteen characters, End to get to the end of
it, CtrlPgDown to get to the end of the file, and CtrlPgUp to get to
the beginning.

In addition to moving around with the cursor movement keys, you can
search for text automatically. To search for a text string, hit CtrlQ
and then F. You will be asked to enter the string. Type it and hit
the Enter key. You will be prompted for search options. The valid
options are U, G, and B. Enter as many of them as you want to use and
hit enter. Option U is used if you want a case insensitive search; if
you do not use it, the search is case sensitive. The other two options
control the search direction. By default, the search is from the
cursor to the end of the file. Option B results in a backward search
to the beginning of the file. Option G will search the entire file.
To repeat a search, hit CtrlL.

You may find it convenient to set "markers" in the file -- candidate
locations of the start of the text. You can set up to four markers,
numbers 0 through 3. To set a marker at the cursor location, type
CtrlK followed by the number of the marker. You can jump to a marker
you have previously set by typing CtrlQ followed by the number of the

It is not always easy to find the beginning of the text of the
document. Document prefixes can be many thousands of bytes long, so
you may have to do a lot of paging down. And the prefix may contain
information that looks like it should be part of the text. For
example, the document summary is contained in the prefix, and it may
contain a copy of part of the document text. Styles are stored in the
prefix, and they may contain chunks of text. Examine the display
carefully and try to avoid treating these chunks of text as the
beginning of the document. (There is, unfortunately, another
circumstance making it impossible to find the beginning of the text
part of the document. It is not always there. If you do not see
anything resembling the start of your text anywhere in the display of
the file, your document is too badly damaged to be recovered, or else
it is a "locked" -- that is, password protected -- document. WPMD
cannot fix locked documents.)

When you find the first word in the text, it may nevertheless not be
located at the true beginning of the text part of the document. For
example, if the sentence in our example file had been indented with a
tab, the beginning of the text part of the file would actually have
been a string of nine bytes very few people would recognize as
representing a tab. Other function codes at the start of a document
are also represented by unrecognizable strings of bytes. For a reason
explained below, function codes like this are not a serious problem,
and you should not worry about them. Codes that contain text, however,
including headers, footers, and comments, are more of a problem. If
you treat text within a header, footer, comment, style, or similar
structure as the beginning of the text of your document, the results
will not be satisfactory, and it may be necessary to use the Ordinary
Way on the output of Drastic Surgery.

When you have decided on what to take as the beginning of the text of
the document, move the cursor to it and hit the ESC key. WPMD will
then display the hexadecimal offset of that location in the file. You
can edit that number, or you can simply hit ENTER to accept it. It is
difficult to imagine any circumstance in which you would want to edit
that number.

WPMD then asks you whether you want it to search backwards through the
file for codes. Unless you have a very good reason for answering N(o),
you should answer Y(es). If you do, WPMD will move backwards in the
file from the offset you located, seeing if there are valid WordPerfect
codes. If there are any, WPMD will consider them as part of the text
part of the document and adjust the offset accordingly. That is why
you need not worry too much about codes like tabs before the character
you identify as the start of the text of the document. (This
description may make it sound as though you could simply move the
cursor to the end of the file, treat that as the offset of the
beginning of the text, and let WPMD do the work of finding the
beginning of the text part of the document. Unfortunately, that will
not work, for two reasons. First, WPMD will search backwards only for
about 15,000 bytes. Second, WPMD will stop searching backwards the
first time it finds an invalid code. Since you would not be using WPMD
if you knew the file to be in perfect shape, there is a risk that there
are invalid codes. If you leave the cursor inside a function code,
such as a header, footer, or comment, WPMD will think the beginning of
that function code is an invalid code.)

Once you have answered the backward searching question, WPMD proceeds
to process your file.

If you prefer, you can use Drastic Surgery from the DOS command
line, avoiding some or all of the interactive program operation.
The DOS command line looks like this:

C>WPMD Infile Outfile -d[hex] [-gfilespec] [-m]

The optional -gfilespec identifies the file from which you want
to take a prefix to use on your output document, as described

If you use -d without the optional hexadecimal offset value,
WPMD will proceed to find the offset, with your help, as
described above. Alternatively, you can supply the offset
immediately following the -d, for example, -dF14, and avoid all
interactive operation. The user will rarely know the offset, so
this option will rarely be used. But you may sometimes know it.
For example, if your file gets completely trashed, and you use a
disk sector editing tool to recover it, you might well recover
only the text part of the document, so the file would have no
prefix. In that case, the offset of the start of the text part
of the document is 0.

When Drastic Surgery finishes, the next step is to read the output file
into WordPerfect. If all has gone well, you will have a healthy
document again. If not, you should try using the Ordinary Way on the
new document.

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

In addition to WPUSERS on CompuServe and the WordPerfect RT on GEnie, I
monitor three networked WordPerfect BBS conferences more or less
regularly, and you can leave questions or suggestions for me in any of
them. You are likely to get a faster response if you leave the message
on the BBS I call than if you count on the network to get your message
to me and mine to you. The networks are listed below, along with the
BBS I call for each.

Smartnet Arlington Software Exchange, 703-532-7143
Metrolink/RIME D.C. Information Exchange, 703-836-0748
FIDO Free Spirit, 301-283-8917

NOTE: WordPerfect is a registered trademark of the WordPerfect

WPMD is not in the public domain. It is fully protected by copyright.

WPMD is distributed as shareware (without the documentation in
WordPerfect format). If you obtain a copy without paying the license
fee, you are granted without charge a limited license which permits (a)
use of the program for a reasonable period for evaluation and testing;
(b) making copies for distribution to others without charge, provided
the program and the accompanying documentation are distributed together
and without modification; (c) posting the program, together with the
accompanying documentation, on electronic bulletin board systems.

How long is a reasonable period? The idea of shareware is that you
should be able to try a program before deciding to buy it. But unless
you have a broken WordPerfect 5 file, you really are not in a position
to try WPMD. You probably would like to keep WPMD around as a kind of
insurance policy, hoping that if a problem ever develops with a
WordPerfect 5 file, WPMD can help fix it. Although I would prefer that
you sent your license fee simply because you have heard WPMD is a good
program, it is reasonable that you would not do so.

Once you have tried WPMD on one of your broken files and found that it
does work, the clock starts ticking on reasonableness. After all, if
WPMD saved a single file of any substantial size for you, you should
not have to wait for more information before deciding it is worth the
registration fee. I think more than two weeks after that point is
unreasonable. And that is what a "reasonable period" means for
purposes of this license.

Use after the reasonable evaluation and testing period requires payment
of a license fee. For a single copy (plus necessary archival copies),
to be used on only one computer at a time, the fee is $35.00. For your
convenience, an invoice form is included below. 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
WPMD and all subsequent versions.

What do you get for your license fee? Aside from permission to use the
program and the warm feeling that you are not violating the copyright
laws, not very much, but a little. You will receive the latest version
of the program, along with the documentation in WordPerfect format, and
you will receive notice of significant program upgrades, which you may
order for a small shipping and handling fee. Further, if you let me
know about any problems you have with the program, I will try to solve
them. A license if valid for all versions of WPMD, not just the
current one. The only upgrade fee is for shipping and handling.

Users groups and other not-for-profit organizations may distribute
unmodified copies of WPMD, together with its accompanying
documentation, for a fee to cover duplication and related costs, not to
exceed $6.00. Certain organizations may have been granted permission
to distribute the program for a fee larger than $6.00, the larger fee
to include the license fee for a single copy. If the organization from
which you received a copy of the program has been granted that
permission, it should tell you so.

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


WPMD is 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
WPMD, shall be or be deemed a warranty by the licensor for any purpose,
nor give rise to any liability or obligation of the licensor whatever.

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



FIXPRE, which is also useful in curing the ills of WPerf5 files, is
part of the shareware package WPTOOLS. The description below gives
some idea of the situations in which FIXPRE may solve problems with
WordPerfect files. We cannot describe all the circumstances, because
FIXPRE often helps with problems new to us.

WPTOOLS is a collection of 14 shareware utilities for use with WPerf5,
with an additional six provided to registered users. These utilities
are DOS programs intended for use with WPerf5 for DOS, but most of them
are also useful with WPerf5 for Windows. At this writing, the latest
version of WPTOOLS is 5.1b. WPTOOLS is available on many BBSs, on
CompuServe in the WPSGA forum, and on GEnie in the WordPerfect RT. Or
you can order it for $25 from Software by Seidman, plus $2.00 for
shipping and handling. For your convenience, an order form appears

Here are brief descriptions of all 20 WPTOOLS programs:

COMMENTS Reads one or more WP5 document files, extracts the
comments, and writes them to a WPerf file or to standard output.

DISKFONT Searches a directory for specified soft font files and,
optionally, lists descriptive information about the fonts it finds.

ENDFOOT Converts all footnotes (endnotes) to endnotes
(footnotes), changing automatic references appropriately.

FIXPRE Removes deleted (and optionally other) data packets
from the prefix of WP5 document files and removes deleted data packets
from WP5 (and other WPCorp) setup files (e.g., WP{WP}.SET). For
document files, this will often facilitate changing the printer driver
used with the file and shrink the file. Setup files grow as you modify
your setup; FIXPRE shrinks them again. And FIXPRE sometimes helps when
WP5 just seems to be acting strangely. Optionally deletes styles,
initial codes, document summaries, and graphics.

FONTFILE Lists the file names of the soft font files specified
in a PRS file.

FONTLIST Lists the names of the fonts used in a WP5 document
and the PRS file the document calls for.

IS5XDOC Identifies WP5 document files. Useful in batch files.

LISTMACS Lists the names and descriptions of macros in WPM and
WPK files (and the keys for WPK macros), optionally sorted. Also works
with PP5 and DR macro and keyboard files.

MAKETABS Converts an ASCII text file to a WP50 document,
replacing spaces by tabs. Used with columnar material.

MASTER Reads a WP5 master document and lists the unexpanded
subdocuments it calls for.

MERGESUM Creates (or adds to) a WP50 secondary merge file, each
record containing the information from a WP5 document summary (or,
optionally, the first 400 or so characters of a document if no summary
was created), along with information from the DOS file directory. In
effect, creates a database of document summaries that can be processed
using the WP5 Merge and Sort functions, or WordPerfect's Notebook

PRINTIT Paginates and formats an ASCII text file for printing.

PRSFONTS Lists and optionally numbers the names of the fonts
available in a WP5 PRS file.

STYLIST Lists names and descriptions of styles, optionally

STYLEUSE Lists the styles used in the text of a document.
Lists the styles found in the prefix but not used in the document.
Optionally deletes unused (or all) styles from the prefix. Optionally
deletes style on and off codes from the text of a document, leaving the
codes added by the style.

TARGETS Lists the automatic reference targets and references
in a WP5 document file, indicating unreferenced targets and references
to nonexistent targets.

WHATPTRS Lists the printers described in ALL files, optionally
sorted by printer name.

WP5LOOK Displays one or more WP5 document files specified on
the command line, piped to the program, or entered in response to
prompts. Particularly because files can be specified with wildcards,
WP5LOOK may be more convenient than WP5 itself for browsing through WP5
documents. Also displays non-WP5 files.

WPGSIZE Extracts and lists the dimensions of the image
coordinate space for WPG files. Useful in getting the aspect ratio

WPSNOOP Determines, in greater or lesser detail, the file type
of many, but not all, files associated with recent WordPerfect
Corporation products. For WP5 document files, lists the document
summary and the PRS file. For macro files, lists the description.
Optionally reveals the structure of WP5 document file prefixes and of
set file prefixes.



Reveal Codes can be very helpful in figuring out what went wrong with a
WPerf5 document. But it is difficult to examine a lengthy document in
Reveal Codes. SHOWCODE allows you to print out almost exactly what you
would see in Reveal Codes if you used Reveal Codes on an entire
document. SHOWCODE is part of MORE TOOLS.

MORE TOOLS is a collection of 9 shareware utility programs (plus two
additional utilities, including SHOWCODE, for those who register) for
use with WPerf5, including both Windows and the DOS versions. All of
the programs are useful with WPerf51 for DOS. A few are not useful
with WPerf51 for Windows or WPerf50. When released, MORE TOOLS will be
available on many BBSs, on CompuServe in the WPUSERS forum, and on
GEnie in the WordPerfect RT. Or you can order it for $25 from Software
by Seidman, plus $2 for shipping and handling. An order form appears
below. Release of MORE TOOLS is expected in October 1992.

Here are brief descriptions of the MORE TOOLS programs:

ADDPRS A tool for network administrators, allowing selective
updating of printer definitions in personal setup files from the
definitions in the master setup file. More flexible than NWPSETUP.

AUTHOR A tool for managing legal table of authorities
marking. Generates (as a secondary merge file) a list of the full
forms and associated short forms used in a document.

CONCATWP Combines a group of WP5 files into a single file, with
or without separators between files. Useful for combining text and
saving disk space.

FREEZE "Freezes" styles, cross-references, and paragraph
numbers, converting them to ordinary text so that they are no longer
subject to change without explicit editing.

LFSD Simulates List Files, but allows the files to be
sorted in reverse date order (most recent first), date order, by
extension, or by file name. For WP51 for DOS.

MPSET Sets environmental variables in the DOS master
environment. Aids communication between WP5 and other programs through
environmental variables.

PRIMO Converts merge codes to (bolded) ordinary text, for
convenient printing and debugging of primary (or secondary) merge
files. Much faster than the CODES macro.

SHOWCODE Converts a WP5 file into more or less what you would
see in Reveal Codes. A much more complete conversion than the CODES
macro provides, and much, much faster.

SHOWSET Lists most of the information in SET files. Find out
what the default settings are without searching in WP5, print for
future reference.

STYLIB Helps manage your styles. Create a new style library
by selecting styles from any or all of your existing style libraries
and documents.

WFWP Computes and lists the frequencies of words in WP5 files.

* * * * * * * * * * * * * * *


David Seidman
Software by Seidman
2737 Devonshire Pl. NW
Washington, DC 20008




Description Price

License for WPMD $ 35.00

additional licenses @ $35.00 _____.__

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

Total Charge: $_____.__

Make checks payable to Software by Seidman.

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

Card Number: __________________________ Exp. Date: _____________

Name on card: __________________________________________________

Signature: __________________________________________________



David Seidman
Software by Seidman
2737 Devonshire Pl. NW
Washington, DC 20008




Description Price

__ Licensed copies of WPTOOLS @$25.00 $ _____.__

__ Licensed copies of MORE TOOLS @$25.00 _____.__

Total: $_____.__
D.C. Residents add 6% D.C. Sales Tax: ___.__
Shipping and handling: 2.00

Total Charge: $_____.__

Make checks payable to Software by Seidman.

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

Card Number: __________________________ Exp. Date: _____________

Name on card: __________________________________________________

Signature: __________________________________________________


 December 13, 2017  Add comments

Leave a Reply