|STAT 5.4 Distribution March 1989 Installation Instructions for DOS Note: These installation instructions are substantially different from previous versions of |STAT. The package is still distributed on three diskettes but there is no assumed directory structure; all programs and files are at the same level. Files are distinguished by their extensions. The first three diskettes contain executable files, in alphabetical order. The third diskette contains documentation files and other information. See the README file on the last distribution diskette. EXTENSION DESCRIPTION EXE Executable files MAN Manual Entries (displayed with MANSTAT.BAT) BAT Batch Files with DOS Commands DAT Data Files COM KEYDO.COM is a command line editor with history Setting Up the |STAT Directory Make a directory on a hard disk called STAT with a command like: MKDIR C:\STAT For each floppy, copy all the files on all the disks to that directory: COPY A:*.* C:\STAT Place your |STAT directory on your execution PATH. Setting Up the Online Manual You should update the MANSTAT.BAT file with the directory name where it will find manual entries (those files that end with MAN). Rather than use the TYPE command in MANSTAT.BAT, a command that displays one screen at a time might be used instead. Most of the programs have online help with the -L (limits), -O (options), and -V (version), options. Problems? If a floppy does not work, it may have been damaged in transit. Return it to me for a replacement. If the programs do not run on your machine, your machine might not be IBM compatible. To learn how to use the programs, look at the examples in the online manual entries, or read the |STAT Handbook (which must be ordered separately). With several thousand users, I cannot deal with individuals with questions about how to use the programs. If you think you have found a bug in the programs, I want to hear from you. Send me a copy of the input data, and the command you used, and a description of the problem and/or the output. Since 1980 when distribution started, no serious bugs have been found. Usually, a problem is due to compatibility problems that I can adapt to, so if I fix a problem for you, future users can avoid it completely. Gary Perlman Department of Computer and Information Science The Ohio State University Columbus, OH 43210 perlman@cis.ohio-state.edu 614-292-2566 form printed 3/14/89