========> [LT90A.AMBY]AAAREADME.TXT;1 <======== Don Amby's SYS$LOGIN Environment V1.0-7 --------------------------------------- Donald E. Amby Delco Systems Operations P.O. Box 471, M/S 1A21 Milwaukee, WI 53201 (414)768-2682 or (414)281-1296 Amby%Wizard.GM@Hac2Arpa.Hac.Com (Internet) AMBY (DECUServe) AMBY (DCS) This directory is the root of my (Don Amby) 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 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. ========> [LT90A.ANUNEWS]AAAREADME.TXT;2 <======== ANU NEWS This area contains compressed distributions of the latest ANU NEWS programs, plus the utilities to allow NNTP feeds over DECnet to interoperate correctly with some unix variants. Contributed by Glenn Everhart ========> [LT90A.BLACKBOARD]AAAREADME.TXT;2 <======== Preface Code in these directories implements a blackboard architecture as described in the paper "Implementing a Blackboard Architecture in a VAX/VMS Environment", presented at the 1990 DECUS Spring Symposium. The paper is included in the Spring 1990 DECUS PROCEDINGS and can also be obtained from the author: Frederick S. Schebor KMS Fusion Inc. 700 KMS Place P.O. Box 1567 Ann Arbor, MI 48106-1567 (313) 769-8500 The paper (minus figures, fancy fonts, etc.) is also included in the AAAREADME.DOC files as follows: [.SUBMISSION] - Abstract, Introduction, discussion, References [.BLACKBOARD] - VAX/VMS implementation [.BLACKBOARD_EXAMPLE] - Tic-Tac-Toe example Instructions on building the system, support routines, example and other implementation/execution notes can be found at the end of the AAAREADME.DOC files. Questions, concerns and/or comments from users is welcome at the above address. Abstract Artificial Intelligence research has produced a number of problem solving architectures. Although not as well known as expert systems or neural nets, the blackboard architecture continues to be an extremely useful and flexible tool for general purpose problem solving. This paper serves a twofold purpose: 1) to introduce the blackboard architecture and 2) to show how VMS features can be used in implementing a blackboard architecture. The first part of the paper includes a discussion of request-centered control and its application to the blackboard style of problem solving. The second part of the paper discusses the issues involved in implementing the blackboard architecture on a VAX computer under the VMS operating system. The emphasis is placed on using system utilities, functions and mechanisms, wherever possible. Doing this makes the implementation task easier. ========> [LT90A.BRIANJIM]AAAREADME.TXT;1 <======== BRIAN-JIM-MIKE These subdirectories contain BLISS programs that were used as examples in the DECUS pre-symposium seminar 'BLISS for Macro users'. They are very well documented, so there is no external documentation. [.HELLO] VERY remedial BLISS program. This just barely qualifies as a program. Displays the message 'Hello BLISS user' on the terminal [.CONVERT_VA] This program will convert a virtual address to it's corresponding physical address. The main routine isn't very useful, but the routine GET_PHY_ADDR is very generic, and can be incorporated into another program very easily. [.MANDELZOOM] This directory contains three programs: COMPUTE Which is used directly in the seminar, will compute the image of any region of the Mandelbrot set DISPLAY Provided here for completeness, reads the image output by COMPUTE, and the color table output by COLOR_TABLE, and displays the image on a graphics device COLOR_TABLE Provided here for completeness, creates the color table file used by DISPLAY. This color table is very striking, and can be used to create many beautiful pictures. [.CONSOLIO] This directory contains routines that allow the user to do I/O to the console when running at any IPL, and on any stack. These are ideal when writing standalone code, or drivers. [.NODUMP] This directory contains a program that will inhibit the system from writing a dump file when doing an operator requested shutdown. This will allow shutdowns, and reboots to be done in a fraction of the time it would normally take, since all of memory isn't being written out to the dump file. [.SSDRIVER] This directory contains a DR11-C driver completely written in BLISS. I haven't had time to go through it to make sure it will work on V5.x, or even compile under V5.x. However, it's here, and provides a good example of writing drivers in BLISS. [.USRLIB] This directory contains programs, and macro libraries for BLISS users to help make using BLISS easier. Brian Catlin Jim Gray 4-MAY-1990 ========> [LT90A.BRYANT]AAAREADME.TXT;1 <======== Geoff Bryant Schlumberger CAD/CAM 829 Middlesex Turnpike Billerica, MA 01821 This submission contains the latest version of APLTPU, a highly enhanced version of DEC's EDT Emulator. This version of APLTPU works under VMS V4.4-4.7 and VMS 5.x. Included are files to build APLTPU for whichever version of VMS you are using. This submission also includes APLEVE, which is APLTPU converted to be based on EVE rather then the EDT Emulator. APLEVE also contains enhancements over and above APLTPU. APLEVE is intended to replace APLTPU. APLEVE requires VMS version 5.0 or later. The following enhancements have been made to APLTPU since the submission to the Spring '89 (Atlanta) SIG tape: - Bug fixes The following enhancements were made in the conversion from APLTPU to APLEVE: - GOLD U supports capitalize in addition to upper/lower - PRINT has been added to line mode to print a "cheat sheet" - "Multi window" support for more than 2 windows - Setting of wildcard/normal FIND - GOLD R provides a mroe useful ruler - Unlimited number of saved positions - Of course EVE functions and keypads are also available Also included in this submission are two utilities, GBLSUBS and GBLSEARCH. GBLSUBS allows text substitution in multiple files with full support for wildcards in file names, and file and substitute confirmation. GBLSEARCH is used to search files for a given text string and to edit any files in which the string is found. More information follows about these utilities. If you have any suggestions, find a bug, or have a question, send it along. I can be reached either at the address above, or if you're on DECUServe, send mail to EISNER::BRYANT. APLEVE - Enhanced EVE APLEVE is an enhanced version of EVE. APLEVE includes home grown features, requests from users, and features gratefully borrowed from EVEPLUS, APLTPU, and DECUS. To use APLEVE you should define the following symbols: $ EVE :== @SYS$LIBRARY:APLEVE Page 2 $ EVER :== @SYS$LIBRARY:APLEVER and then type $ EVE filename or $ EVE to edit a file. If you don't specify a filename, the last file that you edited will be used. EVER will edit a file in read only mode. APLEVE will also allow wildcards in filenames. In addition to the keys defined by EVE, the following keys are defined by APLEVE: HELP - Give help on APLEVE and EVE keys GOLD I - Issue initialization commands GOLD $ - Issue DCL commands CTRL/B - Toggle one/two windows GOLD CTRL/B - Open a reference file in second window GOLD UP - Move to top window GOLD DOWN - Move to bottom window CTRL/N - "Nuke" a multi window GOLD W - Adjust window sizes GOLD C - Center a line of text GOLD U - Set case upper/lower GOLD J - Selected substitution GOLD S - Convert tabs/spaces GOLD E - Trim spaces/tabs at line end GOLD T - Convert non-printable chars CTRL/V - Enter control characters GOLD O - Toggle overstrike/insert mode GOLD B - Toggle box SELECT/CUT/PASTE GOLD X - Toggle word definition GOLD Y - Toggle graphics display CTRL/K - Start learn sequence CTRL/R - End learn sequence GOLD M - Save current position GOLD G - Go to saved position GOLD L - Go to specified line GOLD Q - Display current line/column GOLD R - Display a "ruler" GOLD F - Toggle margin support ON/OFF GOLD < - Set left margin GOLD > - Set right margin GOLD TAB - Set TAB size Page 3 GOLD V - Display APLEVE version number GOLD Z - Display the message buffer The following commands are available from APLEVE initialization files, as DO commands, as GOLD_I key commands, or as line mode commands: {ENABLE|DISABLE} BOX - Enables BOX mode SELECT/CUT/PASTE {ENABLE|DISABLE} DISPLAY DEFAULT_FILE - Enables display of default filename {ENABLE|DISABLE} MARGIN - Enables APLEVE margin support {ENABLE|DISABLE} MULTI WINDOWS - Enables APLEVE multi windows {ENABLE|DISABLE} WILDCARD FIND - Enables wildcard FINDs HELP - If interactive, provides help MESSAGE message - Displays user message PRINT HELP file - Writes help to file SET CURSOR top:bottom - Controls scrolling SET DCL {ERASE|NOERASE} - Erase DCL buffer between commands SET INSERT - Sets MAIN buffer to INSERT mode SET LEFT_MARGIN n - Left margin - APLEVE margin support SET OVERSTRIKE - Sets MAIN buffer to OVERSTRIKE mode SET QUIET - Disables APLEVE command verification SET RIGHT_MARGIN n - Right margin - APLEVE margin support SET SCREEN width - For 80/132 column screen width SET SEARCH {GENERAL|EXACT|EVE} - Set case sensitivity for search SET TAB EVERY number - Set tab sizes for APLEVE TABs SET VERIFY - Enables APLEVE command verification SET WORD {EDT|NON-ALPHANUMERIC|user} - Sets WORD definition SET WRAP number - Sets WRAP column for EDT wrapping TPU command - Executes the specified TPU command Documentation on APLEVE keys is provided through online HELP in APLEVE. A cheat sheet is provided the PRINT HELP command. BUILD.COM can be used to build and install APLEVE. APLTPU - Enhanced EDT Emulator for TPU APLTPU is an enhanced version of the EDT Emulator for TPU which was distributed with VMS V4.x. The DEC version of the emulator has been enhanced to include features from EVE, EVEPLUS, DECUS, and many in house enhancements. To use APLTPU you should define the following symbols: $ TPU :== @SYS$LIBRARY:APLTPU $ TPUR :== @SYS$LIBRARY:APLTPUR and then type $ TPU filename or Page 4 $ TPU to edit a file. If you don't specify a filename, the last file that you edited will be used. TPUR will edit a file in read only mode. TPU will also allow wildcards in filenames. In addition to the keys defined by the EDT Emulator from DEC, the following keys are defined by APLTPU: HELP - Give help on APLTPU keys and EDT emulator keys GOLD I - Issue initialization commands GOLD $ - Issue DCL commands CTRL/B - Toggle one/two windows GOLD CTRL/B - Open a reference file in second window GOLD UP - Move to top window GOLD DOWN - Move to bottom window GOLD W - Adjust window sizes GOLD C - Center a line of text GOLD U - Set case upper/lower GOLD J - Selected substitution GOLD S - Convert tabs/spaces GOLD E - Trim spaces/tabs at line end GOLD T - Convert non-printable chars CTRL/V - Enter control characters GOLD O - Toggle overstrike/insert mode GOLD B - Toggle box SELECT/CUT/PASTE GOLD X - Toggle word definition GOLD Y - Toggle graphics display CTRL/K - Start learn sequence CTRL/R - End learn sequence GOLD M - Save current position GOLD G - Go to saved position GOLD L - Go to specified line GOLD Q - Display current line/column GOLD R - Display a "ruler" GOLD F - Toggle margin support ON/OFF GOLD < - Set left margin GOLD > - Set right margin GOLD TAB - Set TAB size GOLD V - Display TPU version number GOLD Z - Display the message buffer With this version of APLTPU, the user can tailor many of the defaults for APLTPU by placing APLTPU commands in an APLTPU$INIT initialization file. Page 5 Documentation on APLTPU keys is provided through online HELP in APLTPU. A cheat sheet is provided as APLTPU.HLP. The source files included are: APLTPU.TPU - TPU source for APLTPU APLTPU.TXT - Source for the APLTPU help library APLTPU.HLP - A cheat sheet EDTSECINI.TPU - The source to DEC's EDT Emulator, included here with permission of Digital, since it is not distributed with VMS 5.0. APLTPU.COM - Procedures to invoke APLTPU with APLTPUR.COM filename recall and wildcards. BUILD.COM can be used to build and install APLTPU. Note that APLTPU has some minor conditional assemblies for VMS V5.0. If you want to give it a quick try, section files are included in this submission: APLEDTSECINI (VMS V4.X) and APLTPU$SECTION (VMS V5.x). GBLSUBS - Utility to substitute text in multiple files This utility allows you to replace all occurances of a string with another string in a list of files. GBLSUBS is invoked as follows: $ @TOOLS:GBLSUBS file(s) search_string replace_string You will be prompted for any unspecified parameters. Options are specified as switches for a file: /Confirm - will ask you to confirm each file /Exact - will do a case sensitive search /Query - will ask you to confirm each substitution GBLSEARCH - Utility search and edit/read files This utility allows you to SEARCH files for a string and to edit files containing the string. GBLSEARCH is invoked as follows: $ @TOOLS:GBLSEARCH file(s) search_string edit/read You will be prompted for any unspecified parameters. Options are specified as switches for a file: /Confirm - will ask you to confirm each file /Exact - will do a case sensitive search /Names - will display the names of all files searched Page 6 The default is to edit files read only. ========> [LT90A.CAP]AAAREADME.TXT;1 <======== CAP stands for the Columbia Appletalk Protocol. It is software that allows systems to talk Appletalk to Macintosh Computers. This directory contains various implementations of that software. ========> [LT90A.EPUBS]AAAREADME.TXT;1 <======== E PUBS Material (mostly TeX related) [.AMBY] TeXtools Work Area ------------------ This directory represents the work area that I use to build and install the tools that we have tailored for using TeX and LaTeX on our system. (From Don Amby) [.DVIOUT] DVIOUT is a program, written in C, that interprets a Device- Independent (DVI) file produced by programs such as TeX and produces output on a particular output device. It has a number of special features, accessible through command line options and through "special" commands. It is designed to handle more than one type of output device, and adding device protocols to its repertoir of devices is a relatively easy, but not trivial, task. It currently supports the Tektronix 4014 and standard PostScript output devices at 300, 400, 600 and 1200 dpi, with the Apple LaserWriter being a special case. It should work with the DEC LN03R printer. Additional information is contained in the file "dviout.txt". [.TEX_HELP_FILES] Help files for TeX [.XDVI] Program that allows viewing of DVI (TeX output) files on X windows (DECwindows) display. Many options. It is assumed the user of this software understands the TeX system and the requirements for pixel files, as well as the facilities of the VMS operating system. The TeX and METAFONT systems are quite complex, and successful integration of this software to a specific site requires an in-depth understanding of these systems, although most of the nitty-gritty details are not needed to successfully install this software. It is the author's hope that users of various high resolution graphics output devices being used with TeX will develop new drivers for specific output devices and provide a copy of the driver software so that it can be incorporated into the distribution of the DVIOUT software. The auxiliary program QUERYLW produces TFM files for the native Apple LaserWriter fonts. It conducts an "interactive" dialog with the LaserWriter, and converts the information thus obtained into font metric property list files. Because the metric information for the LaserWriter is proprietary to Apple (or Adobe), it cannot be supplied. However, the QUERYLW program can generate it for you. No documentation for this program is provided, other than that present or implied within the source files and example command files. The auxiliary program PSFONT generates PostScript fonts from the fonts generated by METAFONT and used by TeX. These fonts can then be sent Page 2 to the printer to remain permanently resident (or until the printer is turned off). DVIOUT can recognize whether these fonts are present through the site-modifiable options file for the printer. Using the downloaded TeX fonts speeds up DVIOUT and results in the print job completing quite a bit faster as well, although more memory is consumed in the printer. The ALWSMB program is a print symbiont specifically written for the Apple LaserWriter. It can send DVIOUT's output PostScript files to the LaserWriter, or any PostScript file from any source. It can handle downloading of permanently resident fonts by using a special "exitserver" mode. Additional information on the symbiont is in the files "smbreadme.1st" and "symbiont.txt". This software is furnished "as is". Although considerable effort has been expended to make this software correct and reliable, no warranty is implied; the author disclaims any obligation or liability for damages, including but not limited to special, indirect, or consequential damages arising out of or in connection with the use or performance of this software. Please address comments, criticism and bug reports to: Scott Campbell PAR Government Systems Corp. 7150 Campus Drive, Suite 215 Colorado Springs, CO 80920 PH: (719) 594-0095 (9am to 5pm MST) ========> [LT90A.GNUSOFTWARE]AAAREADME.TXT;3 <======== This area contains software from the Free Software Foundation. Included are Gnu Emacs, Gnu C, Gnu C++ and a variety of other items. The subdirectories [.VMS*...] contain Gnu C and Gnu C++ for VMS, plus the port of the LIBG++ runtime to VMS. These are a very high quality C and C++ compiler system for VMS. Most items' sources are in compressed TAR savesets with extensions like .TAZ or .TAR_Z or .TAR_LZW. All should be decompressed with COMPRESS (or lzdcmp in -b mode, as a less desirable option) and de-tarred with a tar reader. Several tar format readers for VMS are in the tools subdirectory of the index area. Some messages and files from the Gnu mailing lists are in ZOO archives here to save space. These are of interest also. Note that the VMS port of GAWK is in the [.gce90a...] tree on this set of tapes. The packing of the compressed savesets is done by the originators and has been simply left alone by the tape editors. Many of the VMS items are decompressed already. The VMS port of GCC was done by Angel Li (credit where credit is due). These files represent only FSF items which are new since the Fall 1989 tapes. Note: Also present are VMS ports of GCC, G++, LIBG++, and GAWK 2.11-1 in subdirectories [.vms*...]. The Gnu Emacs distribution will build correctly for VMS as is, using VAX11 C. Because of its size, it is not presented pre-built here. The [.translators] directory elsewhere on the tape also contains versions of f2c and p2c for VMS, allowing one to generate executables from sources in Fortran or Pascal as well as from C or C++, using free compilers. While there are license restrictions on use of LIBG++ in commercial software, note that InterViews has a c++ library that can be used instead. Interviews may be found on the X11 tapes or for ftp at interviews.stanford.edu on the Internet. Contributed by Glenn Everhart ========> [LT90A.GPLOT]AAAREADME.TXT;1 <======== PSCDOC:GPLOT.DOC 01 November 1989 GPLOT is a graphics utility program, designed for the processing of CGM metafiles produced by DI3000, DISSPLA10, DISSPLA11, DRAWCGM, NCARGKS1 and NCARGKS2. Source code for GPLOT will be released to other sites, so that graphics created at PSC can be processed locally. Graphics produced by GPLOT can be combined with TEX formatted text by the GTEX program. The version of GPLOT installed on the PSC machines includes drivers for PostScript, Tektronix 4010/4014/4207/4510, Cleartext CGM, and BinaryCGM output. Other device drivers are available for use at other sites, including DEC/GKS, Peritek, Silicon Graphics GL (IRIS), SUN, SUN monochrome, UIS, X Windows. GPLOT cannot handle CGM character-encoded files. The DrawCGM and CGMGen programs are included in this release also. See GPLOT.DOC for more documentation. ========> [LT90A.JMI]AAAREADME.TXT;1 <======== In support of the VAXNotes 103 session presented at the New Orleans DECUS Symposia the following files have been included: AAAREADME.1ST;1 - This file. NOTES$COMMAND.COY;1 - A NOTES$COMMAND procedure written by Dale Coy and made available on DECUServe. NOTES$COMMAND.MDCBBS;1 - A NOTES$COMMAND procedure using the 1.0 version of the above as the base, it was heavily modified by Barry W. Leung at MDC [M&SE in Cypress]. NOTES$COMMAND.MDC_DAC;1 - Yet another NOTES$COMMAND procedure. This one was a copy of the one modified by Barry and modified even some more. It is used at DAC. [in order to use any of the above, just change the extention to .tpu and then define the logical notes$command to point at the file before starting notes. Why are there three NOTES$COMMAND.TPU files? They are all included for example purposes. One of the best features of VAXNotes is the ability to modify the environment. These files should teach you how to do it. :-) ] NOTES$COMMAND_TEXT.COY;1 - A textual outline of what features are included in the NOTES$COMMAND.COY procedure NOTES_MAN.RNO;1 - As we all know, VAXNotes really requires that each user get a manual. No company wants to spend that kind of money so, at DAC we created our own. This .rno file is it. It contains some information that is DAC specific (like nodenames) and may require minor modification before use (it *will* require minor modification :-) ). PURGE_NOTES.COM;1 - Management wanted a method to purge notes from selected topics in selected conferences that are used as BBS's. This tool was written to allow them to do it [included so you can see a Notes/DCL interface]. PURGE_NOTES.RNO;1 - A help text for the above tool. UNSEEN.COM;1 - Most likely the most useful procedure in here and on the wishlist for enhancements as part of Notes, this tool is generaly run as a spwned process (spawn/nowait) at login. It updates a users notebook and then announces to the user which conferences have unseen notes, and how many unseen notes are in each conference. In this way the user will be advised what is unseen at login (sort of like the new mail messages). NOTEBOOK.DESCR;1 - This text file is Dale Coy's writtings on the format of a VAXNotes notebbok. It provides excellent insights to the inner workings of VAXNotes. [.VN101]*.* - Postscript files of the VAXNotes 101 session. This should allow you to develop a VAXNotes training class at your site. Page 2 If there are any questions or problems, please contact: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | J.M. Ivler | INTERNET: JMI@DAC.MDCBBS.COM | | McDonnell Douglas Corp. | UUCP: UUNET!DAC.MDCBBS.COM!JMI | | Douglas Aircraft Co. |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 3855 Lakewood Blvd | VOICE: (213) 497-5147 | | Mail-stop 36-49 |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Long Beach, CA 90846 | DECUServe and DCS available (IVLER) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ========> [LT90A.MAC_WATCH]AAAREADME.TXT;1 <======== MacWatch Watch is a networking debugging tool for use on a Macintosh on Localtalk or directly on Ethernet. It works with the Cayman GatorCard,3COM, and Apple Ethernet cards. It does not appear to work on either a Mac Plus or a Mac SE. It has been used most on Mac II's and the SE/30. There is no documentation for Watch nor is it a supported product. Use it at your own risk. It is freely distributed but Cayman Systems, Inc. still maintains a copyright on it. If you have any bugs to report, please feel free to send email to support@cayman.com. Changes in1.4.3 New Features: Display filtering - After packets are captured, they can be filtered before displaying on the screen. Capture filtering - The idea of capture filtering is to selectively pickup packets from the network, in order to cut down unnecessary packets. NOTE - Leading zeros are required for EtherNet address. Address range and format were not validated, therefore, any error in the address will have undetermined results. Bugs Fixed - Macintosh Plus, SE, & SE/30 crash - Phase 2 RTMP decode - Phase 2 ZIP decode - zone list in Chooser disappeared after quiting from Watch Known bugs - zone list in Chooser disappeared after quiting from Watch when using GatorCard. - sometimes one can not scroll to the first packet or a blank line will scroll to the top of the screen ========> [LT90A.MDRAW]AAAREADME.TXT;1 <======== Summary: MDRAW is an object oriented drawing package for ReGIS terminals. Objects may be cut, pasted, joined, unjoined, flipped and moved. An on-screen menu gives quick access to commands. Objects may be linked with other mdraw files, giving a tree of drawings which may be traversed. Text notes may be attached to objects, and edited during drawing with your favorite editor. Output goes to an LN03 laser printer, and may be included in TeX documents with the \special command. (This is taken care by the converter program 'vregis' which is included) You may also convert mdraw files into a CGM (computer graphics metafile) format for inclusion in Manuscript/Freelance. This is done with the mdr2cgm program (included). ========> [LT90A.MODULA3V14]AAAREADME.TXT;1 <======== This directory contains recent versions of SRC Modula-3, the implementation of the Modula-3 language by the System Research Center, a research laboratory of Digital Equipment Corporation. The Modula-3 language is described in the "Modula-3 Report (revised)", available as a technical report from: System Research Center Digital Equipment Corporation 130 Lytton Av Palo Alto, CA 94301 USA This report is present in PostScript format in this directory, either in one piece as Report.ps, or in three pieces are Report{1,2,3}.ps. The SRC implementation of Modula-3 is distributed in the form of a compressed tar file, m3-.tar.Z. From this file, you can build versions for the following machines: VAX VAX running Ultrix 3.1 DS3100 DECstation running Ultrix 3.1 SPARC Sparcstation running SunOS 4.0.3 You can also bootstrap the system to other machines/os from this distribution (see the release notes). The distribution contains all the sources of the compiler, runtime and libraries, mostly in Modula-3, for all the available architectures. In addition, it contains the C files resulting from the compilation of the Modula-3 files for the various architectures (most of the files are identical and not replicated). For ftp convenience, the distribution is also available in parts, in the files m3-.tar.Z-. Each file (except the last one) is 512Kb long. You can just cat these files (in the right order) to rebuild m3-.tar.Z. Release-.ps is the PostScript version of the release notes. These notes describe the differences with the previous versions, how to install the release and how to use it. They are also available in TeX format within the distribution, in doc/doc.tex. You can send mail to m3-request@src.dec.com if you have trouble to access/uncompress/untar these files. Enjoy ! [ Note: The M314.TAZ file here is the m3-v14.tar.Z file mentioned in the document, just renamed. Rename it to M314.tar_z and then use compress -d m314.tar (using compress in the tools subdirectory of the index area) to decompress it. - Tape editor.] ========> [LT90A.MUMPSSIG]AAAREADME.TXT;1 <======== Spring 1990 DECUS MUMPS Collection The collection contains the following packages: FILEMAN VA Fileman V17.32 UCDMUMPS Univeristy of California, Davis, MicroMUMPS V5.1 for PCs GAMES A collection of games from various sources TOOLS A collection of MUMPS tools from various sources I would be happy to answer questions about these packages and would like to encourage people to send software for the next release of the SIG Tape. Michael McIntyre PRx Inc. 43 Bradford St Concord,MA 01742 508-369-3566 ========> [LT90A.NCSATELNET]AAAREADME.TXT;1 <======== NCSA Telnet NCSA Telnet is an implementation of Telnet and FTP for PC or Macintosh computers. It is presented here essentially complete as obtained by FTP from zaphod.ncsa.uiuc.edu. A few files are compressed to reduce space demands, and I assume you have Binhex 4 and Stuffit available on macs to decompress the mac images. Contributed by Glenn Everhart ========> [LT90A.NOTES]AAAREADME.TXT;1 <======== VAX Notes Working Group - L&T SIG Abstract: NOTES$COMMAND.TPU and related procedures created for some relatively inexperienced users. This procedure was originally devised to assist captive users in navigating through VAX Notes conferences in addition, to permitting users to spawn VMS Mail and SET PASSWORD. Complexity is not evident in these files, however, they do demonstrate various aspects of VAX Notes tailoring for the users. Please see Dale Coy's One-Key Noting procedure for more elaborate NOTES$COMMAND.TPU magic. Also included is a an example of some VAX C code using Callable Notes and a description of the Notefile structure. The Notefile description was researched and written by Dale Coy and was originally posted on the DECUServe system. I received permission from Dale to include on the Spring tape. The "Callable" Notes example was developed by Jon Jones and was first posted on the PAGESWAPPER system. I received permission from Jon to include on the Spring tape. Submitted by: Mike Durkin Intracorp 1205 Westlakes Drive Berwyn, Pa 19312 (215) 889-2883 Please call if you require assistance in tailoring for your site. Please contact me if you are interested in becoming a member of the VAX Notes Working Group. This directory contains Command Procedures, Help Text and a User Help Library for VAX Notes which support the tailored NOTES$COMMAND.TPU as well as the Notefile description and Callable Notes example. FILES DESCRIPTION ----- ----------- AAAREADME.1ST This file KEYPAD.DISTRIBUTION The unaltered text for default Keypad help that was extracted from NOTES$HELP.HLB that provided the base for the modified KEYPAD.HLP KEYPAD.HLP Help Text file which describes all the user- defined keys present in NOTES$COMMAND.TPU KEYPAD.DISTRIBUTION was used as the base for the modifications. This file should be inserted in NOTES$HELP_USER.HLB Page 2 LOCAL_NOTE_PRINT.COM Command procedure which allows you to print a note or range of notes to the printer port of a VT series monitor. This procedure was developed by Mark Hyde of VAX Notes fame and is a most useful gap-filler. LOGIC.NOTES Various logicals required. LOGIN.COM Captive users LOGIN command procedure. Please note there may be other security measures you may want to include in your version. This was not designed to be a completely bullet proof procedure. MERGE_NOTES.C Example of using Callable Notes from VAX C as developed by Jon Jones. (This information was posted on the PAGESWAPPER system.) NOTEFILE.TXT Description of the structure of the Notefile as determined by Dale Coy. (This information was posted on the DECUServe system.) NOTES$COMMAND.TPU Self-explanatory. NOTES$HELP_USER.HLB Help library created to support user-defined keys. Contains KEYPAD.HLP which defines help for the user-defined keys in NOTES$COMMAND.TPU SETPASS.COM Command procedure which allows a user to set their password. ========> [LT90A.NOTES_AIT]AAAREADME.TXT;1 <======== This is a submission from DEC on behalf of the VAX Notes Working Group of the L&T SIG. The material presented here is based on a Notes Seminar given at New Orleans called "Problem Tracking using VAX NOTES". The slides from that presentation can be found in the file SLIDES.PS. This is a postscript file that can be printed on a postscript printer or viewed using a postscript previewer. The other files are the command procedures to do action item tracking using Notes, as explained in the slides. ========> [LT90A.PBMVMS]AAAREADME.TXT;3 <======== Extended Portable Bitmap Toolkit Distribution of 22nov89 Previous distribution 13sep89 Modified for VMS 19jun90 [Tape Editor's note: This material arrived JUST before the tapes went out. By compressing it and some executables elsewhere, I have been able to fit it onto the Spring '90 tapes. Check out AAAREADME.1ST for a list of all the (many!) formats this package converts between. Thanks to Ted Nieland for sending this off his Amiga VMSnet node. -Glenn Everhart, tapecopy editor] Included are a number of programs for converting various image formats to and from portable formats; plus some tools for manipulating the portable formats. The package is broken up into four parts (five parts if you count this one, the zeroth part). First is PBM, for bitmaps (1 bit per pixel). Then there is PGM, for grayscale images. Next is PPM, for full-color images. Last, there is PNM, which does content-independent manipulations on any of the three formats. These parts are semi-independent; if you're only going to deal with bitmaps, you don't have to install PGM and PPM, and this makes PNM run faster; if you want PGM, you must install PBM but can leave PPM out; but if you want PPM, you must install both PGM and PBM. PNM is optional but recommended. To install: (For VMS installation, see README.VMS) Unpack the files. Decide whether you want to use Imakefiles or Makefiles. If you want to use Makefiles: Edit the top-level Makefile, find each line with the string "CONFIGURE", and follow the directions for setting configuration options. Likewise edit pbmplus.h. Likewise edit pnm/Makefile. Make. When you're happy that things work ok, make install. If you want to use Imakefiles instead: Edit the top-level Imakefile, find each line with the string "CONFIGURE", and follow the directions for setting configuration options. Likewise edit pbmplus.h. Likewise edit pnm/Imakefile. Edit Makefile and */Makefile, look towards the end for the definition of TOP, and change it to point to your X11 tree. Save the original Makefiles, in case you later want to switch back to using them. Touch Imakefile, since you just editted Makefile. Make Makefile, make Makefiles, make depend, then make. Page 2 When you're happy that things work ok, make install. I've tested this stuff under 4.2 BSD, 4.3 BSD, on Sun 3's 4's and 386's and Sequents and Vaxen, with cc and gcc. Nevertheless, I'm sure bugs remain. Feedback is welcome; send bug reports, enhancements, checks, money orders, etc. to the addresses below. Be sure to mention what version you have when sending bug reports! Jef Poskanzer jef@well.sf.ca.us {ucbvax, lll-crg, sun!pacbell, apple, hplabs}!well!jef ========> [LT90A.TPUPLUS]AAAREADME.TXT;1 <======== TPUPlus This is a revised version of the TPUPlus package and is compatible with VMS V5.3. Many changes have been made to the TPUPlus source code because of the changes made by DEC in V5.3. A modified version of the TPU utility DIRED, as described in the VAX PROFESSIONAL magazine (October 1989), has been added along with a copy of Steve Graham's (British Telecom) line drawing utilities. Also included are several minor bug fixes and enhancements, including internal enhancements to the routines in TPUPLUS_PRNT.TPU. NOTICE This software is being provided free of charge and should remain as such, free to all who request it. A nominal fee may be charged for reproduction costs only. Please feel free to modify, enhance, or fix any/all bugs found (ABSOLUTELY NO GUARANTEE OR WARRANTY is expressed or implied.) I would appreciate being notified of any problem encountered or enhancements made to any of the programs so all who use this software may be notified. Thank you. Any and all questions or problems concerning this software should be directed to: Rickey H. (Rick) Stacks Sr. Programmer Analyst Arkansas Dept. of Pollution Control & Ecology 8001 National Drive / P.O. Box 9583 Little Rock, Ar. 72219 (501) 562-7444 ========> [LT90A.TRANSLATORS]AAAREADME.TXT;1 <======== These are language translators, not all converted for VMS. F2C - Fortran 77 to C (from research.att.com) P2C - Pascal to C PTC - Pascal to C ADA - Contains Cobol to Ada and Fortran to Ada translators (from Simtel20 repository.) ========> [LT90A.TRANSLATORS.VMS-F2C]AAAREADME.TXT;2 <======== Editor's Note: The Sources for F2C are in the ZOO archive VMS-F2C_SRC.ZOO. The objects were placed in the library F2C_OBJ.OLB. f2c for VAX/VMS This is an implementation of f2c for VAX/VMS systems with VAXC. F2c converts Fortran 77 source files to either C or C++ source files. F2c was written by AT&T. Only a few minor changes were necessary to get it to run under a VAX/VMS system. All of the source files for f2c as well as the support library are included in this backup saveset. The saveset also includes object files, object libraries, executable images, command files and documentation files as used on our system ( a cluster running VMS 5.3 with VAXC version 3.0 ). The command files used to build f2c and the support libraries presume a directory structure of the source files for f2c being in a directory or sub-directory of it's own with a sub-directory for the Fortran function library ( LIBF77.DIR in this saveset ) and a sub-directory for the I/O support library ( LIBI77.DIR in this saveset ). If you change the directory structure you will need to change the appropriate command files as well. Before using f2c you should read the documentation files and the installation instructions ( such as they are ) for a VMS system. These files are f2c.1 ( a ASCII version of the Unix man page provided by AT&T ), f2c.[DOC][PS] ( a modified version of the Unix man page for VMS systems ), and VMS_INSTALL.TXT. You should also read F2C_TECHNICAL_REPORT.PS if you have a PostScript compatible laser printer. It provides detailed information on how f2c works. You should be able to simply use the .EXE file and object libraries without recompiling. If you need to recompile for some reason, please see the appropriate instructions in VMS_INSTALL.TXT. Robert Schneider +-------------------------------------+-------------------------------------+ |Robert Schneider | Internet: robert@perv.pe.utexas.edu| |Department of Petroleum Engineering | BITNET: pefv673@utchpc | |University of Texas at Austin | THEnet: PERV::ROBERT | +-------------------------------------+-------------------------------------+ ========> [LT90A.UEMACS]AAAREADME.TXT;1 <======== This area contains micro-Emacs V3.10, built to work correctly on VMS. Submitted by R. Thomson. ========> [LT90A.XAW]AAAREADME.TXT;11 <======== MIT ATHENA WIDGETS ------------------ This directory contains the code for all the Athena widgets. I have converted all of them to VMS (except MAILBOX and VENDOR), but cannot guarantee that they all work correctly. There were three basic problems with the conversion: 1. Under VAX-C, extern references are not picked up from an object library. globalref and globaldef must be used instead. The mixture of private and public .H files makes these changes non-trivial. Without these changes, toolkit applications must be explicitly linked against each object module that they require. 2. Many of the Athena widget names conflict with the names of DECwindows widgets. This leads to the confusing situation where there are two variables with the same name, but different storage classes. This is easy to recognise, as you get a Toolkit error saying that you must have a non-null widget class when you try to run a program linked with the original Athena widgets. 3. The VMS C compiler gets upset if the same structure is declared extern and then initialised in the one module. The solution to the first problem is to change the way that the widget record and class structures are declared. There is an include file called EXTERNAL.H which was my first attempt at a work-around, but I abandoned this once I realised that it would not eliminate the need for #ifdefs in all the widgets anyway, because I had to change the widget names. NOTE: The file EXTERNAL.H #defines externalref and externaldef which are in the MIT Intrinsic.h, and also in the DECwindows version of Intrinsic.h. It may therefore be better to use these definitions for ALL widget record and class declarations rather than directly using globalref and globaldef. However, this would not solve the second problem, which is the class names. To eliminate the second problem, I added a prefix of "Xaw_" to all of the widgets. This has the unfortunate side effect that clients which use Athena widgets have to be modified to work on VMS. However, there is no other way around this. I have not changed the names of any of the external routines in the widgets. Most start with "Xt", but in R4 they should all be changed to "Xaw". However, MIT does not currently intend to add a prefix to the widget classes. The third problem was solved using #define to declare a symbol Page 2 inside each widget which indicates that it owns the widget records, and the include files therefore do not make any external references to them. This has no effect on clients who wish to include the relevant public header files. Finally, these widgets were designed for the R3 intrinsics, and DEC only provides R2 under VMS V5.1. I am not sure how much effect this has, if any. Known Problems -------------- GRAYPIXMAP, which is not a widget, contains a routine which is already in the DECwindows shareable image. This is probably an oversight. COMMAND was missing a parameter in two calls to HighlightRegion(). This caused some interesting behaviour because the widget worked when compiled with /nooptimise! Presumably these are "known" bugs, but I certainly did not know about them. The COMMAND widget does not correctly redraw the text label when it is resized, e.g. as in adjusting the grip in xcolors. It seems to rely on bit gravity, but in certain circumstances the text has been overwritten by the time that it is moved. The LOAD widget is a fudge. It will not work correctly on a multiprocessor system. FORM does not work properly on VMS. The problem seems to be that it assumes widgets will be properly placed (possibly by the CONSTRAINT widget). As an example of the problem, see xclipboard, where the command and text widgets all overlap one another. (It does work on a Sun 386i though, so DECwindows is probably at fault.) MAILBOX was not converted because it is specific to UNIX. VENDOR will compile, but I have not used it because DEC also provides a VENDOR widget. Trevor Taylor Oct-89 ========> [LT90A.XHP]AAAREADME.TXT;1 <======== ------------------------ HP X Widgets ---------------------------- The files on this tape contain source code and documentation source for Hewlett-Packard's X Widget set. Hewlett-Packard has contributed this code to the Massachussetts Institute of Technology for inclusion in the MIT distribution of public X Window software. It contains the appropriate public-use copyrights. The goal of this contribution is to help stimulate the development of commercial software products for the Unix (TM AT&T) workstation market by putting a flexible and powerful interface productivity library into public distribution. This directory contains the port by Art Stine of Clarkson University of the HP widgets to DECwindows for VMS. He reports it basically functional but not thoroughly tested. Some files are ZOOed by your tape librarian - Glenn Everhart, VAX SIG tape librarian