I suspect you have a bunch of files for the program roff, an old Unix
text formatter. Its descendents include troff, groff, and xroff; and it
inspired systems such as TeX. All of the files are plain text, but some
of them include commands for a macro processor. In general, each file
is piped through a sequence of programs, and the output is then
concatenated together before printing (or saving to postscript). The
file extension often indicates which processor should be used; for
example, *.txt indicates plain text, and *.tbl would be run by the
program tbl to create formatted tables.
RUN2.COM might have contained the commands to generate this document;
open it with a text editor to see if it contains Unix file commands.
You might ask over at
if anyone there recognizes these files. The website
a few examples of how roff works.
In the mean time, reading the .txt files will probably give you most of
the information. Opening the other files in a text editor may fill in
Are you running Linux or Windows?
If Linux, find a terminal, mount the disk, run MC (Midnight Commander)
and press F3 or F4. F3(View) will allow you to look at the bare file
when you change it to Hex(F4) mode. F4(Edit) is a standard text editor.
Most of the files will probably be able to be read as text files. The
fact that you were able to provide a file listing says that you can
access the disk, so the files are only a step away.
In Lieu of Linux, try an older version of DOS and the DOS text editor.
It will mangle any of the filenames not in 8.3 format, but if it will
read the disk format, you'll be able to edit the files. Don't save them,
even if it recommends it.
Some of those look like old INFO files, but the RUN2.COM file could
prove interesting. It could be an executable.
That is a VMS directory listing.
It's unclear from the OP's wording (as well as the unexpected addition of
a CMS change history) if he executed a DIR command on a VMS system in order
to display the directory listing, or if he has been given a file 1.txt and
told that is what is on the floppy.
If it's the former, then he can try asking the question on comp.os.vms and
somebody might recognise the files. If it's the latter and he needs to
actually find a method of accessing the contents of the floppy, then what
he is looking for is a ODS-2 reader as the floppy is likely to be in ODS-2
In this case, it's almost certainly a DCL command procedure (VMS version
of a Unix shell script).