(Excerpts from a message dated 09-15-99, Kenneth Abrams to Murray
Lesser)

Hi Kenneth--

KA>So, tell me, how do *you* squeeze a 3-4M ZIP file onto a 1.44M
  >floppy, eh?

    I don't have any occasion to do so.  I would copy such files to a
100 MB Zip diskette.  If you don't have a Zip Drive, there are "native
OS/2" utilities that will copy a large file to a spanned flock of
floppies.  IIRC, one such is a "freeware" IBM EWS program.  Also, there
is the latest version of PKZIP/PKUNZIP for OS/2 that will span a set of
floppies as it compresses the original files.

 ML>     Since the backups are records of current contents of my hard
 ML> drive, there is no problem in knowing which directory the original was
 ML> stored on, since it still exists.

KA>Unless, of course, you foolishly wipe out an entire 
  >directory and then wish to "restore" it. My experience with my one
  >time use was that until *I* remembered what the original path was
  >and specified it, all I got was errors that seemed to imply the
  >backup was bad.

    Since I use command-line utilities for most file maintenance, I
would find it very difficult to inadvertently wipe out both the contents
of a directory and the directory, in a single operation.  But if I were
to do so, I would probably realize what I had done after a very short
interval, so I would remember the name of the top directory.  One of the
virtues of RESTORE is that if you use the "/S" switch, you can restore
all the subdirectories of the named original directory in the same
operation that restores that directory.

    This interchange has been a good example of why one should not
generalize on one's own practices to apply to another person.  I
apologize for attempting to answering your original post to me.

    Regards,

        --Murray

___
 * MR/2 2.25 #120 * There, that will do until a REAL explanation comes along.

--- Maximus/2 2.02