[comp.archives] [comp.os.vms] Free 326 page VAX BOOK available via Anonymous FTP

JOE@oregon.uoregon.edu (Joe St Sauver) (02/14/90)

Archive-name: oregon-vaxbook/13-Feb-90
Original-posting-by: JOE@oregon.uoregon.edu (Joe St Sauver)
Original-subject: Free 326 page VAX BOOK available via Anonymous FTP
Archive-site: decoy.uoregon.edu [128.223.32.19]
Archive-directory: pub/vaxbook
Archive-files: README
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

I've prepared a 326 page VAX BOOK that attempts to answer most of the questions
University of Oregon users have had about using VMS, EDT, the networks, stat
and graphics packages, etc. Most of the concepts presented are illustrated by 
means of annotated examples. A detailed table of contents and index are 
included.

The book is available in either Digital Standard Runoff output format suitable
for printing on a line printer, or in PostScript form suitable for printing on
an Apple LaserWriter or other 300 DPI PostScript printer. I am also making the
raw .RNO files (and the code used to convert the guide into TeX) available for
those of you who are interested in customizing the VAX BOOK for your own site.

To get a free PostScript copy of the guide via anonymous FTP try:

    $ FTP DECOY.UOREGON.EDU         <-- (DECOY.UOREGON.EDU=128.223.32.19)
    Name: anonymous                 <-- login as "anonymous"
    Password: blah                  <-- use whatever you want for a password
    *cd pub/vaxbook                 <-- change to the pub/vaxbook directory
    *dir                            <-- look at the directory, if you want to
    *get README                     <-- check out the README file for help...
    *binary                         <-- switch to binary mode
    *get vms.ps                     <-- get the postscript version of the book
    *quit

Note that your FTP commands might be somewhat different from those shown...

If you like the guide, have any suggestions for additions, or catch any errors
please drop me a note... I'm going to be working on a few other projects for
a while, but eventually I'll probably do a revision of it and comments are 
always helpful.

Also, please feel free to mention the guide to anyone else who might be 
interested in a copy of it.

Joe St Sauver (JOE@OREGON.UOREGON.EDU or JOE@OREGON)
Statistical Programmer and Consultant
University of Oregon Computing Center