ftp.update.uu.se/ftp.update.uu.se.2014.03.zip/ftp.update.uu.se/pub/rainbow/msdos/util/nusq.doc

Text File | 1987-10-13 | 8KB | 169 lines

            NUSQ - File unsqueeze utility

        Documentation for CP/M-86 and MS-DOS versions
             Cliff Sharp   March 31, 1984



     NUSQ is a utility for restoring squeezed files. Two separate
versions of NUSQ are available, one for CP/M-86 and one for the MS-DOS
operating system.

     NUSQ has two operating modes.  In the command mode, a single
instruction to NUSQ is passed from the command line which invokes
NUSQ.  The command mode requires less effort to use when you have only
one file to unsqueeze, or when the names of the files you wish to
unsqueeze can all be specified by one "wildcard" name.  However, when
you have more than one file to unsqueeze and a "wildcard" won't do the
job right, or when the files you want to unsqueeze are on more than
one disk, the interactive mode allows you to specify only those files
which you want processed, without reloading the program every time.
In the interactive mode, NUSQ executes one command, then waits for
another.

     To unsqueeze only one file, the command mode invocation

               A>nusq nerts.aqm

will unsqueeze the file NERTS.AQM.  You don't need to specify the name
of the output file (in fact, you can't); the name was stored within
the squeezed file at the time it was squeezed, and that name will be
used to create the new file.  (If you want to call it by another name,
use the REName command when NUSQ is finished.)

     You can unsqueeze all squeezed files on a single disk by issuing
the command

                 A>nusq *.?q?

Theoretically at least, all file squeezers create an output file whose
name is the same as that of the original file, except that the
filename extension field is modified by changing the middle letter to
a "Q".  (When a file has been renamed after being squeezed, this
cannot be the case; hopefully, the person who renamed it remembered
the "Q".)  The "wildcard" file specification shown above tells NUSQ to
unsqueeze any file it finds (on the default disk) which has a "Q" in
the filename extension; that should get NUSQ to unsqueeze every
squeezed file on the disk.  NUSQ will display the name of each file it
finds, and the name of the output file it produces, as it proceeds:

        NERTS.AQM -> NERTS.ASM
        ORGPLOTZ.DQC -> ORGPLOTZ.DOC

     NUSQ will also accept more than one filename on the command line.

        A>nusq nerts.aqm orgplotz.dqc frop.cq

     To use a different disk for output than for input, end the
command line with just the drive designation. Example:

             A>nusq giggle.tqt b:

will write the output file (ostensibly GIGGLE.TXT) on drive B:.

     Let's suppose now that you have a lot of squeezed files on your
disk, and you only want to unsqueeze some of them at the moment.
Unless you can specify only those files by using a "wildcard" name,
you'll probably find it easier to achieve your goal by using the
interactive mode of NUSQ.  Another instance where it would be easier
to use interactive mode is one where the files you wish to unsqueeze
are on more than one disk, in more than one drive.  The command

                A>nusq

displays the startup screen, then prompts for command input with an
asterisk ("*").

NUSQ  Version x.xx
Dave Rand, Paul Homchick and Cliff Sharp  xx/xx/xx
Use: NUSQ afn [afn afn ...] [destination drive:]
*_

(The underline shows the cursor position; my name appears only in the
MS-DOS version.)  At the asterisk, you type a filename ("wildcards"
are allowed here, too).  NUSQ will unsqueeze the file, then print the
asterisk prompt again and wait for more commands.  When you're
finished and want to exit NUSQ, a blank line or ^C will return you to
the operating system.




              IN CASE OF TROUBLE


     First, no matter HOW sure you are that you're doing things
correctly, try another method of using NUSQ.  If you tried command
mode without luck, try the interactive mode; if you were in the
interactive mode when it bombed, try command mode.  Make sure you try
at least one command that is just like one shown in this document
(but, of course, use the name of your file instead of NERTS or
ORGPLOTZ) before you conclude that things are awry.

     Occasionally, for one reason or another, it's possible to get a
bad copy of a program or file; transmission errors and disk errors
have been known to cause many problems.  (If you can successfully
unsqueeze at least one squeezed file, you probably have a good copy of
the program; if so, your copy of the file you're trying to unsqueeze
may be the culprit.)  The best way to tell if this is the case is to
use a utility like CRCK on the original copy of the offending
file/program, and on your copy; if the numbers you get don't match,
you most likely have a bad copy of the file/program you checked and
should obtain another copy of it.  (Check the new copy, too, when you
get it.)

     This may sound silly, but do you have the correct version for
your operating system?  If you try to run the CP/M-86 version under
MS-DOS, strange things may happen; same for the MS-DOS version under
CP/M-86.  The MS-DOS version has an "M" in the version number.  Also,
try using TYPE to actually type the executable file on your screen;
you'll most likely see the author's name.  (See the history later in
this document to see who wrote what.)

     If all that checks out, the logical next step is to compare notes
with someone locally to see if anyone else is experiencing problems.
The system operator ("sysop") of the system from which you obtained
the software can usually be of help if you tell him which program
you're using (CP/M-86 or MS-DOS) and the name of the file you're
trying unsuccessfully to unsqueeze.  Alternatively, you can leave a
message addressed to "ALL" on a local bulletin board; usually some
helpful person will jump in with suggestions.

     If you've tried all this, and you're still sure you have a
problem, then it's last-resort time.  Contact the author of your
version of the program.  His name, and a way to contact him, is in the
very beginning of the NUSQ.COM file; TYPE NUSQ.COM and you should see
it.  (If that doesn't work, use DDT, SID or DEBUG.)  This is by far
the slowest method of resolving problems, and people who contact
program authors with problems caused by operator error are usually
looked upon unfavorably, so do this only if all else fails.  Be sure
to include the name of the system where you got your copy of the
program, the name of the file you're trying to unsqueeze and the place
where you got the file, and a description of what went wrong.  It
might also be nice to know the names of any people who have tried to
help you with your problem so far.

     Dave, Paul and I all breathe fire and spit nails when asked for
source code for NUSQ.



                   HISTORY


     NUSQ is a file unsqueezer utility written entirely in assembly
language.  The first file squeezer and unsqueezer in the public domain
were written by Richard Greenlaw, in the C programming language.  The
predecessor of NUSQ was USQ120, produced by Dave Rand in 8080 assembly
language for CP/M systems, and was probably the only assembly-language
unsqueezer in existence for some years; Paul Homchick assumed the task
of converting it to 8086/8088 assembly language under CP/M-86 in early
1984, and I converted Paul's version to run under MS-DOS a bit later.



CP/M and CP/M-86 are trademarks of Digital Research, Inc.
MS (as in MS-DOS) is a trademark of Microsoft, Inc.