========> DRC2:[LT90B2.AMBY]AAAREADME.TXT;1 <========





               Don Amby's SYS$LOGIN Environment V1.1-2
               ---------------------------------------

         Donald E. Amby

         Harnischfeger Engineers, Inc.
         P.O. Box 1512             or    13400 Bishops Lane
         Milwaukee, WI 53201             Brookfield, WI 53005

         414-797-6713, 414-797-6533 (FAX)

         DECUServe,DCS:  AMBY
         CompuServe:     73547,3256
         Internet:       amby@eisner.decus.org
         UUCP:           ...uunet!marque.mu.edu!amby!don
                         ...{decwrl,nosc,crash}!simpact!eisner!amby

This directory is the root of my login environment, which has a
LOGIN.COM file that is run at login time. There is also a SETUP.COM
file that defines all of my logical names, global symbols, keys, etc.
that define my working environment.

These were designed to function on the VAXcluster where I do all of my
real work, and these files expect certain things to be defined (in the
system logical name table).

1  Files

There following is a listing of some of the more important files that
can be found in my SYS$LOGIN directory.

      *  AAAREADME.TXT

         That's me that you are reading.

      *  LOGIN.COM

         Of course, this is my login procedure. It has been designed
         so that I can easily port it (as is) to any VMS system that I
         use.

      *  SETKEYS.COM

         This defines my favorite DCL keys.

      *  SETLOGS.COM

         This defines logical names that I require. Of course, it
         calls lots of other procedures.

      *  SETSYMBS.COM

                                                                Page 2


         This defines global symbols for running my tools. Of course,
         it calls lots of other procedures.

      *  SETUP.COM

         This is an overall setup which uses the other SET*.COM files.

      *  TOOLKITS.TXT

         This is a listing from running TOOLKITS tool which lists what
         tools I set up as part of my LOGIN.COM and what are the
         current versions. I update this each time I 'install' my
         SYS$LOGIN environment tools.


2  Backgound

Many years ago I adopted the convention of making software tools
available as part of a set of tools, which I refer to as a 'toolkit'.
Basically, a toolkit refers to a directory somewhere in the file
system where there is to be found a SETUP.COM file that you can run.

Running this SETUP.COM file will then define all that you need to make
the tools in the toolkit available. This typically means the
definition of logical names (in order to point to files, directories,
etc.) and global symbols (to run *.COM or *.EXE files that implement a
tool). In addition, sometimes it may use a Command Definition Utility
(CDU) to define new DCL command verbs (with the SET COMMAND and a
*.CLD file).

Much of this philosophy is the result of some of the good things that
I have seen on numerous DECUS SIG tapes.

A goal of mine has always been to make tools as portable as possible,
across VAX/VMS systems (running the same version of VMS). I currently
am running VMS V5.3-1, so I would expect everything to work on similar
systems.

3  Setting Up

In order to set up my environment and tools you need to run the
LOGIN.COM file, which will in turn run the SETUP.COM file (and all
other DCL command procedures).

         LOGIN.COM       My login command procedure.
           SETUP.COM       Overall setup for this set of tools.
             SETLOGS.COM     Defines logical names (AMBY$ROOT based).
             SETSYMBS.COM    Defines global symbols.
             SETKEYS.COM     Defines DCL keys.

The following is all that is necessary on the system where I work, and
have all of these files.

         $ @LOGIN

                                                                Page 3


If you are not running these from the system where I maintain this
stuff, then you will need to do something special. This is to
compensate for some logicals and symbols not being defined already for
you (like they are on my system).

         $ @LOGIN
         $ [.RUN]SETUP
         $ @LOGIN

4  Directories

The following is a list of the important subdirectories which can be
found below my SYS$LOGIN directory.

         [.CDD]          My CDD dictionary (for DATATRIEVE stuff).
         [.DATA]         Data files used to drive the environment.
         [.DECUS]        DECUS related stuff.
         [.DEV]          Development areas for collections of tools.
         [.DOC]          Documentation related to tools, etc.
         [.EXE]          Executables (*.COM,*.EXE,*.OBJ,*.OLB) for tools.
         [.HELP]         Help library (and help sources) for tools.
         [.ISEE]         ISEE tools personal working area.
         [.NOTES]        VAX Notes related files and tools.
         [.RUN]          Run-time area for my toolkits.
         [.SITE]         Site specific definitions.
         [.TEMP]         Temporary files directory (my SYS$SCRATCH).
         [.TOOLKITS]     Various collections of older tools that I am
                         in the process of replacing.

5  Getting Help

After you have run the SETUP.COM file you can get help on my personal
tools and environment with the AMBYHELP command.

     $ AMBYHELP

6  SIG Tape Submission

This section is a discussion of what is contained in the LZW
compressed saveset that is in this directory along with this file. As
such you will need to decompress it using the LZDCMP tool, in order to
recover the backup saveset. Then you will need to use BACKUP in order
to get at the individual files.

6.1  Saveset Directories

The following is a complete listing of every directory that is in the
LZW compressed saveset file that is part of this submission. Some of
the directories are empty, and can be ignored. These inadvertently
made it into the submission.

    [AMBY]                              Top directory, that is my actual SYS$LOGIN.
    [AMBY.CDD]                          My CDD dictionary (for DATATRIEVE stuff).
    [AMBY.DATA]                         Data files used to drive the environment.
    [AMBY.DECUS]                        DECUS related stuff.
                                                                Page 4


    [AMBY.DECUS.LT_SIG]                 Languages & Tools SIG development area.
    [AMBY.DECUS.LT_SIG.CMS]                 DEC/CMS library for L&T SIG Folder, etc.
    [AMBY.DECUS.LT_SIG.WRK]                 Work directory for building the L&T SIG Folder, etc.
    [AMBY.DEV]                          Development areas for collections of tools.
    [AMBY.DEV.AMBY]                         AMBY product development area (for my personal set of tools).
    [AMBY.DEV.AMBY.CMS]                         DEC/CMS library
    [AMBY.DEV.AMBY.WRK]                          Work directory where I build my personal tools.
    [AMBY.DEV.BASETOOLS]                    BASETOOLS product development area.
    [AMBY.DEV.BASETOOLS.CMS]                    DEC/CMS library.
    [AMBY.DEV.BASETOOLS.WRK]                     Work directory for building BASETOOLS.
    [AMBY.DEV.CMTOOLS]                      Configuration Management toolkit development area.
    [AMBY.DEV.CMTOLS.CMS]                       DEC/CMS library.
    [AMBY.DEV.CMTOOLS.WRK]                      Work directory for building CMTOOLS.
    [AMBY.DEV.COMMON]                       Common modules, tools, libraries development area.
    [AMBY.DEV.COMMON.CMS]                       DEC/CMS library.
    [AMBY.DEV.COMMON.WRK]                        Work directory for building COMMON tools.
    [AMBY.DEV.COMMON2]                      Another library for COMMON stuff.
    [AMBY.DEV.COMMON2.CMS]                     DEC/CMS library.
    [AMBY.DEV.DCS]                          DCS site specific development area.
    [AMBY.DEV.DCS.CMS]                          DEC/CMS library.
    [AMBY.DEV.DCS.WRK]                           Work directory for building DCS product.
    [AMBY.DEV.DECUSERVE]                    DECUServe site specific development area.
    [AMBY.DEV.DECUSERVE.CMS]                     DEC/CMS library.
    [AMBY.DEV.DECUSERVE.WRK]                    Work directory for building DECUSERVE product.
    [AMBY.DEV.DECUSTOOLS]                   DECUS toolkit developement area (how I package DECUS tools into a toolkit).
    [AMBY.DEV.DECUSTOOLS.WRK]                   Work directory for building DECUSTOOLS product.
    [AMBY.DEV.DOCTOOLS]                     Documentation toolkit development area.
    [AMBY.DEV.DOCTOOLS.CMS]                      DEC/CMS library.
    [AMBY.DEV.DOCTOOLS.WRK]                     Work directory for building DOCTOOLS product.
    [AMBY.DEV.EDIT]                         My personal editing environment development area.
    [AMBY.DEV.EDIT.CMS]                          DEC/CMS library.
    [AMBY.DEV.EDIT.WRK]                          Work directory for building EDIT product.
    [AMBY.DEV.SITE]                         Template for site specific stuff.
    [AMBY.DEV.SITE.CMS]                          DEC/CMS library.
    [AMBY.DEV.SITE.WRK]                          Work directory for building SITE product.
    [AMBY.DEV.TESTTOOLS]                    Beta test tools toolkit development area.
    [AMBY.DEV.TESTTOOLS.CMS]                     DEC/CMS library.
    [AMBY.DEV.TESTTOOLS.WRK]                    Work directory for building TESTTOOLS product.
    [AMBY.DEV.TEXTOOLS]                     TeX/LaTeX toolkit development area.
    [AMBY.DEV.TEXTOOLS.WRK]                     Work directory for building TEXTOOLS product.
    [AMBY.EXE]                          Executables (*.COM,*.EXE,*.OBJ,*.OLB) for my own personal tools.
    [AMBY.HELP]                         Help library (and help sources) for my personal tools.
    [AMBY.NOTES]                        VAX Notes related files and tools.
    [AMBY.RUN]                          Run-time area for my toolkits.
    [AMBY.RUN.BASETOOLS]                    Basic toolkit of tools that are used by lots of other tools
    [AMBY.RUN.BASETOOLS.DATA]                    Toolkit data files.
    [AMBY.RUN.BASETOOLS.DOC]             Toolkit documentation files.
    [AMBY.RUN.BASETOOLS.EXE]             Toolkit executable files.
    [AMBY.RUN.BASETOOLS.HELP]            Toolkit help library and related help files.
    [AMBY.RUN.CMTOOLS]                      Configuration Management toolkit.
    [AMBY.RUN.CMTOOLS.DATA]              Toolkit data files.
    [AMBY.RUN.CMTOOLS.DOC]               Toolkit documentation files.
    [AMBY.RUN.CMTOOLS.EXE]               Toolkit executable files.
    [AMBY.RUN.CMTOOLS.HELP]              Toolkit help library and related help files.
    [AMBY.RUN.DECUSTOOLS]                   DECUS toolkit, which is how I make tools from DECUS SIG tapes available.
                                                                Page 5


    [AMBY.RUN.DECUSTOOLS.DATA]           Toolkit data files.
    [AMBY.RUN.DECUSTOOLS.DOC]            Toolkit documentation files.
    [AMBY.RUN.DECUSTOOLS.EXE]            Toolkit executable files.
    [AMBY.RUN.DECUSTOOLS.HELP]           Toolkit help library and related help files.
    [AMBY.RUN.DOCTOOLS]                     Documentation development toolkit, to help in building complex RUNOFF documents.
    [AMBY.RUN.DOCTOOLS.DATA]             Toolkit data files.
    [AMBY.RUN.DOCTOOLS.DID]                      Toolkit data item descriptions (document templates).
    [AMBY.RUN.DOCTOOLS.DOC]              Toolkit documentation files.
    [AMBY.RUN.DOCTOOLS.EXAMPLES]         Toolkit example files.
    [AMBY.RUN.DOCTOOLS.EXE]              Toolkit executable files.
    [AMBY.RUN.DOCTOOLS.HELP]             Toolkit help library and related help files.
    [AMBY.RUN.EDIT]                         My editing environment toolkit, that sets up my LSEDIT environment and other TPU stuff.
    [AMBY.RUN.EDIT.DATA]                 Toolkit data files.
    [AMBY.RUN.EDIT.DOC]                  Toolkit documentation files.
    [AMBY.RUN.EDIT.EXE]                  Toolkit executable files.
    [AMBY.RUN.EDIT.HELP]                 Toolkit help library and related help files.
    [AMBY.RUN.NOTES]                        VAX Notes enhancement tools (mostly from DECUServe members).
    [AMBY.RUN.NOTES.DATA]                        Toolkit data files.
    [AMBY.RUN.NOTES.DOC]                         Toolkit documentation files.
    [AMBY.RUN.NOTES.EXE]                         Toolkit executable files.
    [AMBY.RUN.NOTES.HELP]                        Toolkit help library and related help files.
    [AMBY.RUN.SITE]                         Site specific toolkit, that is where I can tailor the environment to run my tools.
    [AMBY.RUN.SITE.DATA]                 Toolkit data files.
    [AMBY.RUN.SITE.DOC]                  Toolkit documentation files.
    [AMBY.RUN.SITE.EXE]                  Toolkit executable files.
    [AMBY.RUN.SITE.HELP]                 Toolkit help library and related help files.
    [AMBY.RUN.SITE.MAIL]                 Site specific common mail distribution list area.
    [AMBY.RUN.TESTTOOLS]                    Beta test toolkit, which is where most tools are initially released for use.
    [AMBY.RUN.TESTTOOLS.DATA]            Toolkit data files.
    [AMBY.RUN.TESTTOOLS.DOC]             Toolkit documentation files.
    [AMBY.RUN.TESTTOOLS.EXAMPLES]                Toolkit example files.
    [AMBY.RUN.TESTTOOLS.EXE]             Toolkit executable files.
    [AMBY.RUN.TESTTOOLS.HELP]            Toolkit help library and related help files.
    [AMBY.RUN.TESTTOOLS.INCLUDE]                Toolkit include files.
    [AMBY.RUN.TESTTOOLS.TEMPLATE]               Toolkit template files.
    [AMBY.RUN.TESTTOOLS.TEST]                   Toolkit test area.
    [AMBY.RUN.TEXTOOLS]                     TeX and LaTeX toolkit, which contains stuff used to access TeX on our system.
    [AMBY.RUN.TEXTOOLS.DATA]             Toolkit data files.
    [AMBY.RUN.TEXTOOLS.DOC]              Toolkit documentation files.
    [AMBY.RUN.TEXTOOLS.EXE]              Toolkit executable files.
    [AMBY.RUN.TEXTOOLS.HELP]             Toolkit help library and related help files.
    [AMBY.RUN.TEXTOOLS.LOCAL]                    Local version of TEX_INPUTS files.
    [AMBY.SITE]                         Site specific definitions.
    [AMBY.SITE.DCS]                     Site specific stuff that I use to tailor my tools to use on DCS system. 
    [AMBY.SITE.DECUSERVE]               Site specific stuff that I use to tailor my tools to use on DECUServe system. 
    [AMBY.TEMP]                         Temporary files directory (my SYS$SCRATCH).
    [AMBY.TOOLKITS]                     Various collections of older tools that I am in the process of replacing.
    [AMBY.TOOLKITS.FILETOOLS]               Software tools related to file manipulations.
    [AMBY.TOOLKITS.FILETOOLS.DATA]               Toolkit data files.
    [AMBY.TOOLKITS.FILETOOLS.EXE]                Toolkit executable files.
    [AMBY.TOOLKITS.FILETOOLS.HELP]               Toolkit help related files.
    [AMBY.TOOLKITS.MISCTOOLS]               Miscellaneous software tools collection.
    [AMBY.TOOLKITS.MISCTOOLS.DATA]               Toolkit data files.
    [AMBY.TOOLKITS.MISCTOOLS.DOC]                Toolkit documentation files.
    [AMBY.TOOLKITS.MISCTOOLS.EXE]                Toolkit executable files.
                                                                Page 6


    [AMBY.TOOLKITS.MYTOOLS]                 This is an old collection of tools that were originally for my private use.
    [AMBY.TOOLKITS.MYTOOLS.DATA]         Toolkit data files.
    [AMBY.TOOLKITS.MYTOOLS.EXE]                  Toolkit executable files.
    [AMBY.TOOLKITS.MYTOOLS.HELP]         Toolkit help library and help related files.
    [AMBY.TOOLKITS.MYTOOLS.UTILS]                Toolkit executables (this was used before I got in the habit of [.EXE] directories).
========> DRC2:[LT90B2.EPOCH]AAAREADME.TXT;1 <========


Subj:   Epoch 3.2

Version 3.2 of Epoch, GNU Emacs for the X windowing system has been formally
released.

Epoch is a modified version of GNU Emacs 18.55 with several major enhancements:

        o Multiple X-Window support
        o Marked and Attributed regions of text
        o Support for multiple fonts (fixed size), underlining, and
          stipple patterns.
        o Asynchronous communication with other X-Clients (usually the
          window manager)
        o Mouse-dragging with highlighting to support mouse-based cut-and-
          paste.
        o Access to raw X-Window objects

        
README for Epoch version 3.2 

Major changes:

+ Epoch elisp code is now dumped when Epoch is built.  See loadup.el in
lisp directory for which files are dumped.  dot.emacs should load any 
elisp files which are not dumped.  (Or if memory prohibits dumping files)

+ Epoch now relies on some of the standard lisp files being different
from the standard distribution. These are
        @ version.el : Changed to have "Epoch" in messages
        @ startup.el : If running Epoch, forces screens 0,1 to be mapped
                       (unless inhibit-initial-screen-mapping is non-nil)
        @ time.el : display-time-filter now supports hooks in variable
                    display-time-hook.
        @ loadup.el : Dumps under the name "epoch" instead of "emacs"
        @ loaddefs.el : Changed to have "Epoch" in the mode line
        @ backquote.el : Fixed bug with '(@, )'.

Only version.el, loaddefs.el, and loadup.el are incompatible with
GNU-Emacs 18.55, and these only in that certain messages/displays will
say "Epoch" instead of "Emacs".

+ epoch::create-screen no longer maps screens upon creation. This is a
critical difference. This is necessary so that property manipulations can be
performed on the screen before it is mapped. The changes in startup.el are
primarily to make sure that the first edit screen is mapped if for some
reason the init file gets an error. Notice also that for some of the
advertised features to work, you must use create-screen, so that the correct
properties are set (or take care of them yourself).

+ Event handling is completely different. Read the manual, look at the code.

+ Mouse handling is completely different. You can still use the standard
Emacs code if you want, but the new version is really a _lot_ better. Read
the manual.

                                                                Page 2


+ Handling of attributes is completely different.  The complete context for
displaying text (i.e. foreground/background color, stipple pattern, font, 
underline color, etc.) is now specified in a "style" structure.  Attribute
tables are now references to styles.  Read the manual for further details.

+ Buttons are completely different. Read the manual. There is code in
fix3-2.el in the distribution to change (most of the) vector button code to
the new format. The new style is based on Denys Duchier's version. Also,
read-only buttons are supported now.

+ The Epoch manual is now in Info format.
u
+ X Properties work better (more general). In particular, X resources
can be used, and also properties can be set to lists/arrays of values
(c.f. WM_PROTOCOLS).
========> DRC2:[LT90B2.M2VAX]AAAREADME.TXT;1 <========


This is a Modula-2 compiler for VAX/Ultrix obtained from Gatekeeper.dec.com
via anonymous FTP. Full sources are present.
========> DRC2:[LT90B2.M3]AAAREADME.TXT;1 <========


This is release 1.5 of SRC Modula-3. 

Print the documentation doc/doc.ps; the TeX sources are also there
in case you cannot print this PostScript file. You will find detailled 
installation directives in this documentation.


This release is known to work on the following systems:

     <system>        Requirements       Hardware           Operating
                disk (Mb)   time (min)                       sytem
     -----------------------------------------------------------------
     VAX           30           50      VAX 8800           Ultrix 3.1
     DS3100        35           13      DECstation 5100    Ultrix 3.1
     SPARC                              Sparcstation-1     SunOS 4.0.3
     AP3000                             Apollo DN4500      Domain/OS 10.2
     AIX386                                                AIX/PS2
     IBMR2                              IBM R6000          AIX 3.1
     IBMRT                              IBM RT             IBM/4.3 (AOS 4.3)
     HP300                              HP 9000/300        HP-UX 7.0

