========> [VMSLT96B.AMIGAEMULATOR]AAAREADME.TXT;1 <======== This material comes from the net site: http://freeside.elte.hu/~dadus/homepage/amiga.html It consists of software emulators for the Amiga computer which run on other machines (notably Intel ones) with some sources. Also a listing of the site and considerable amounts of Amiga software is present. The major emulator is called UAE (Universal Amiga Emulator). It also runs on unix and probably can be made to run on any reasonable machine. ========> [VMSLT96B.DECUSERVE]AAAREADME.TXT;1 <======== This area contains the DECUSERVE journals released in 1996 which were obtained. These contain a variety of useful advice and tips. ========> [VMSLT96B.DECUSLIB]AAAREADME.TXT;1 <======== LOOPSCAN Searches a system - either a standalone VAX or a VMScluster - for processes that are looping uncontrollably. LOOPSCAN command is designed to be used primarily from within a detached process although it can be used interactively as well. It was obtained from the DECUS library site at www.decus.org. ========> [VMSLT96B.DICKEY]AAAREADME.TXT;1 <======== From: SMTP%"dickey@clark.net" 12-SEP-1996 I'm submitting more than one program; at this moment 2 are ready (I expect to be done testing/packaging the 3rd on Saturday - it's been a busy week): + vile 6.1 (I submitted vile 5.4 for the 2nd cdrom) + vttest 2.6 (a new program) and (the one I'm working on): + flist (there was some confusion last year, but it is a different program from Hunter Goatley's TPU utility). I've packaged each in a ".zip" file with the zip-file named by the directory in which I've put the source. (This is a source-only distribution, since I work on these programs strictly as a personal project - and I don't own a VAX). So: vile 6.1 is packaged in vile61.zip, which contains the directory "vile61". vttest 2.6 is packaged in vttest26.zip, which contains the directory vttest26 If you wish, I can package flist with a version number to distinguish it from Hunter Goatley's version. (By explanation: "flist" was originally an IBM program that I and other people used and emulated by writing our own versions on other systems. I wrote my version during 1984-1985, and revised it last year, converting to ANSI C and porting to the AXP. This year's version includes some bug fixes). In any case, I'll email you again when I'm done packaging flist. My files are available at ftp.clark.net:/pub/dickey/vms -- Thomas E. Dickey dickey@clark.net ========> [VMSLT96B.DPM]AAAREADME.TXT;1 <======== HER An unhandled VMS exception simply writes the condition, signal arguments, stack contents, and register dump to the standard output. This is seldom useful in production software, because: The user doesn't even notice the exception. Even if they do, they aren't aware of the implications. Even if they are, they don't know that they should copy the dump. Even if they do, they aren't quick enough. Even if they are, they don't remember to inform you. Even if they do . . . IT'S STILL NOT ENOUGH TO HELP YOU FIND THE BUG. So i wrote a relatively simple condition handler to solve all of the problems listed above. It traps any status desired, captures the data described below (some via $getjpi() and $getsyi() calls, some via a user-written system service named HOLMES), and logs it to a file named HARDWARE_EXCEPTION.RPT (in the login directory, if such is defined). The data written out includes: process information ========================================================================== the original condition which caused the exception names (user, process, account, terminal) times (login, cpu) image filespec default directory privileges (current, default, authorized, image) quotas (limit, count) working set (default, quota, extent, peak) system information ========================================================================== names (node, architecture, hardware, hardware model) times (boot, current) VMS version free global pages free global sections call stack ========================================================================== PC of each frame registers for each frame arguments in each frame [1] open file information [2] ========================================================================== channel number access (section, read, write, exclusive) resultant filespec or full device name activated image information [2] ========================================================================== channel number imagename (maybe filename, maybe logical name) Page 2 ident (from LINK command) creation date (from LINK command) current "installed" state (a.k.a. "known file" state) if applicable how linked (/debug, /traceback, /sysexe or sys.stb) global section major & minor idents virtual address range current patches if any (ECO numbers) [3] active timers information [2] ========================================================================== type (normal, system subroutine, wake entry) (repeat) (cpu-based) event flag number AST routine address request identification (also the AST parameter) expiration date/time active locks information [2] ========================================================================== lock id parent id (or zero) resource name (part printable, part binary . . . ugh) octal group number from UIC (or the word "system") access mode (user, super, exec, kernel) currently granted mode (nl, cr, pr, cw, pw, ex) currently requested mode (nl, cr, pr, cw, pw, ex) request state (granted, converting, waiting) value block contents (four unsigned longwords) [1] not very reliable on ALPHA machines [2] written to the file only if the HOLMES package (q.v.) is installed [3] not applicable on ALPHA machines, since there is no PATCH.EXE for them Examples for each architecture are provided in the SAMPLE_AXP_EXCEPTION.RPT and SAMPLE_VAX_EXCEPTION.RPT files. It would be nice to take advantage of any images linked /TRACEBACK to mimic that output --- including module names, function names, and line numbers --- but I just don't have time to decipher the TBK files in the [Vxx.TRACE.LIS] source listings. Sorry, I would very much like to do this, but not yet. Of course this makes life easier for the Technical Support employees; all of the information about which images, versions, and patches are all nicely written out for them to a single file automatically so that all they have to do is download that one .RPT back to me. I, too, find it incredibly useful when debugging an access violation or some similar exception during development, because I now have each image's virtual address range written down for me; a hex subtraction against the offending PC and a quick offset against the addresses listed in the .MAP file, and I've narrowed down the guilty instruction exactly, even in a dynamically-loaded shareable image. This directory contains the source code and option files for both images and a sample program demonstrating a call. There are two implementation methods available: a condition handler that you can establish directly named Page 3 HER_HandleException(), and a function your handler can call named HER_ReportException(). ok dpm --- David P. Murphy mailto:murphy@connor.datametrics.com (work) systems programmer mailto:dpm@access.digex.net (personal) http://www.access.digex.net/~dpm COGITO ERGO DISCLAIMUM ftp://ftp.access.digex.net/pub/access/dpm HOLMES Many VMS systems programmers have found the "SHOW PROCESS /CHANNEL" and "SHOW PROCESS /IMAGES" commands within the System Analyzer very useful at one time or another. Unfortunately, they can only be issued *by* a privileged process *for* an active process --- which is seldom practical. My company has many clients running many different programs, and when a problem occurs there is simply no time to dial up or even prompt a local supervisor through the steps; I wanted my handlers to capture this information for me. So I've written some C and MACRO32 code (the latter with assistance from Brian J. Schenkenberger, a.k.a. "vaxman") to create two shareable images which write the desired output to a disk file at any time from within my programs. The information about "open files" (actually channels) is displayed as chan flags filespec ---- ------ --------------------------------------------------- 10 ( ) DKA100: 20 ( r ) _CHRIS$DKA100:[PUBLIC.HER]HERTEST.EXE;1 30 (sr ) _CHRIS$DKA100:[SYSCOMMON.SYSLIB]UVMTHRTL.EXE;1 40 ( ) RTA1: 50 ( ) RTA1: 60 (sr ) _CHRIS$DKA100:[SYSCOMMON.SYSLIB]LIBRTL.EXE;1 70 (sr ) _CHRIS$DKA100:[SYSCOMMON.SYSLIB]VAXCRTL.EXE;1 80 ( ) RTA1: 90 ( rw ) _CHRIS$DKA100:[USER.MURPHY]HARDWARE_EXCEPTION.RPT;1 A0 (sr ) _CHRIS$DKA100:[SYSCOMMON.SYSMSG]VAXCMSG.EXE;1 B0 ( r ) _CHRIS$DKA100:[PUBLIC.HOLMES]SHERLOCK.EXE;1 C0 (sr ) _CHRIS$DKA100:[PUBLIC.HOLMES]MYCROFT.EXE;2 r = read access s = section file w = write access x = exclusive access the information about "images" is displayed (scrunched to fit 80 columns) as chan name version linked codes gs ident address patch ---- --------------- ------- ------------ ----- -------- ----------- ----- 20 HERTEST V1.0 23-JUL 13:31 0,0 200: 35FF 1,2 30 MTHRTL V05-005 12-OCT 04:24 IOHS 129,12 3600:2D5FF 60 LIBRTL V05-001 12-OCT 04:20 IOHS 1,14 2D600:46BFF 70 VAXCRTL V05-001 12-OCT 04:32 IOHS 4,3 46C00:5E7FF A0 VAXCMSG V04-007 12-OCT 04:57 IOHS 0,0 7F800:805FF B0 SHERLOCK_HOLMES V1.0 23-JUL 14:03 0,0 80600:817FF C0 MYCROFT_HOLMES V1.0 23-JUL 14:02 IOHSP 1,0 81800:829FF Page 4 and the information about "locks" is displayed (scrunched to fit 80 columns) as lockid parent resource grp access gr rq state valueblock -------- ------- ------------ --- ------ -- -- ------- ------------------- 5C0000B5 1000000 LMF$_VAX-VMS sys exec NL PW granted 0 0 0 0 2F0001BB 0 TEST_ONE sys user CR CR granted 0 0 0 0 200001F4 0 TEST_THREE 100 user EX EX granted 0 0 0 0 260001F6 0 TEST_TWO 100 user NL NL granted 0 0 0 0 10001FD 0 TEST_FOUR 100 user PW EX granted 1111 2222 3333 4444 30001FE 0 RMS$... sys exec EX NL granted 0 0 0 0 50001FF 30001FE APPENDER sys exec PW NL granted 0 0 0 0 2000202 30001FE .... sys exec NL EX granted 71 0 0 0 This package contains the source code and build procedure for both images and a sample program demonstrating a call. Since the open-files and activated-images information requires access, and access is required to find all of the existing-locks information, I decided to make two images: the more privileged image would be written in MACRO32 as a user-written system service which would gather the data, while the non-privileged image would be written in C as a dynamically-loaded shareable image for the simple reason that I did not want to link all of my programs against the privileged image. They are named MYCROFT and SHERLOCK respectively (Mycroft Holmes was Sherlock's smarter brother, which I found appropriate). The calling application invokes either of the two universal entry points in SHERLOCK, which in turn call several entry points in MYCROFT. +----------+ lib$find_image_symbol() +--------------+ | MAIN.EXE | ---------------------------> | SHERLOCK.EXE | +----------+ +--------------+ | linked V against +-------------+ | MYCROFT.EXE | installed /PROTECT +-------------+ The BUILD.COM procedure will attempt to compile any source modules whose matching object file is missing, then link the three images in "production" mode (i.e., no debug and no traceback). All necessary object files are included in the package for both VAX and AXP machines to avoid having to recompile. Images are also included in the package, but these should be avoided since the MYCROFT.EXE shareable is system-version dependent. After successfully building the images, the STARTUP.COM file must be run to define the logical names and install the images. Note that MYCROFT.EXE, as a protected shareable image, must be INSTALLed --- in fact, it must be INSTALLed with the /PROTECT qualifier. SHERLOCK.EXE, as a normal shareable image, does not have to be INSTALLed, unless of course the main executable which loads it is itself INSTALLed with privileges. Note that the logical names MYCROFT_HOLMES and SHERLOCK_HOLMES are defined by the STARTUP.COM procedure as executive-mode logicals in the system table; this is not *absolutely* necessary but is the canonical method. ok dpm Page 5 --- David P. Murphy mailto:murphy@connor.datametrics.com (work) systems programmer mailto:dpm@access.digex.net (personal) http://www.access.digex.net/~dpm COGITO ERGO DISCLAIMUM ftp://ftp.access.digex.net/pub/access/dpm ========> [VMSLT96B.DSTSRV]AAAREADME.TXT;3 <======== DST SCANNER Chris Chiesa (lvt-cfc@servtech.com) (formerly Chris_F_Chiesa@cup.portal.com) The collection of files accompanying this text, make up the "DST Scanner" utility: when built, they produce three executable images whose function is to scan an executable image and display, if the information is available, the names of the source files which were compiled/assembled and linked to form the image being scanned. The baseline utility scans a VAX or Alpha AXP VMS image and displays source file specifications only; a modified, "details" version scans a VAX image (no corresponding Alpha AXP "details" version currently exists) and displays source file specifications PLUS some RMS information (record/file organization, EOF position) associated with the source files. This utility does its job by reading the "target" executable image (.EXE) file, following the image's internal structure (Image Header, Debugger Symbol Table (DST), etc.), and extracting the desired information from one particular small subset of the information contained in the image's Debugger Symbol Table, or "DST," records. Note that an image will contain DST records _only_ for those contributing source files which were compiled (or assembled) with the /DEBUG qualifier, and only if the image itself was linked with the /DEBUG qualifier. Note that other software utilities exist which may interfere, or which you might worry MIGHT interfere, with the operation of the DST Scanner. The STABACCOP program used in creation of Standalone Backup sets on those systems which still support them, can be used to copy an executable image WITHOUT its Debug Symbol Table records; therefore, the DST Scanner will produce NO output upon scanning an image that was copied with STABACCOP. On the other hand, numerous public-domain utilities exist which clear the IHD$V_LNKDEBUG bit, and/or modify the transfer-vector array, in an image's header, in order to "disable" invocation of the VMS Debugger when executing an image which was compiled and linked with /DEBUG. Use of such utilities will NOT prevent the DST Scanner from finding, and emitting, the desired information if it was present in the "original" form of the image. The format of DST records is "undocumented" by Digital, in addition to being intricate and subject to change. It is, however, explained fairly thoroughly in the comments in the relevant section (DSTRECRDS.REQ) of the VMS Source Listing, allowing the intrepid programmer to write DST Scanners and such. Just don't expect Digital to help you fix it if it breaks at the next release of VMS! This particular DST Scanner is actually quite minimal, compared to what it could be "in theory." DST records embed a huge amount of information: routine names, other symbol names, sufficient information (file specification, RMS attributes, creation date, exact EOF position, and ODS-2 File ID) to uniquely identify each source file, and the complete source-line-to-instruc- tion-address table necessary for the VMS Debugger to support source-level Debugging -- just to name a few. There are at least a dozen (maybe more) types of DST record, and several subrecord types within most of those! From this wealth of information, this particular DST Scanner extracts *ONLY* the "source-file-specification strings" and, in the "details" version, RMS Page 2 file-and-record type and EOF-position values. It should be pretty clear from the source code for the "details" version, how to extend it to emit what YOU want it to emit -- at least from the "source-file correlation" type of DST record this code is designed to find-and-process There are a couple of other "limitations" -- if you want to call them that -- to this utility. First, the DST Scanner outputs to SYS$OUTPUT -only-. It would be fairly simple to add an /OUTPUT qualifier, but I've never gotten around to doing it; sorry again! Fortunately, you can easily get around this limitation by defining logical name SYS$OUTPUT to a file _before_ invoking the DST Scanner. This comes in very handy as you'll see. Second, my experience shows that an image contains a "source-file correllation" DST record for EVERY instance of a source file which contributed to a /DEBUG compilation at some point in the building of the image. For example, if you compiled several C source files, each of which included "hoohah.h," or included something else which included "hoohah.h," and then linked the resulting objects into a single executable image, then the DST Scanner would find, and display, "HOOHAH.H" several times, not just once. HOOHAH.H would appear at least once for each object whose compilation involved "hoohah.h" at ANY point. This can be a little annoying when trying to cross-reference the "raw" DST Scanner output stream to a minimal list of source files. On the plus side, the multiple-occurrence behavior makes it easy to notice, for instance, that two different C modules used two DIFFERENT versions of "hoohah.h" -- perhaps as a result of having been compiled at different times, across modifications of "hoohah.h" -- alerting you to a potential run-time problem without having to actually execute the image! Third, the DST Scanner emits source file specifications in the order it encounters source-file-correlation DST records in the image, which seems to be a combination of the order in which the compiler encountered the source files, and the order in which the linker encountered the objects. It is NOT alphabetical, and multiple appearances of a particular source file do NOT, as a rule, occur "in a row" but, rather, "scattered" throughout the image. This can make it tricky to find a particular source file you're looking for, but can be useful in determining the order in which the compilers and linker "put the image together," if you have reason to be concerned about it. Fourth -- and there's nothing I can do about this -- the DST Scanner can *only* find source file specifications if they're actually present, i.e. if DST records were generated at compilation/assembly time, and were preserved at link time. It is not necessary that all objects linked into an image be compiled with the same /DEBUG (or /NODEBUG) state. If any object contributing to the image was compiled without /DEBUG, no DST records were generated for that object, and thus the DST Scanner will NOT find any source-file information for that object. And of course if the image was LINKED without /DEBUG, you won't see ANY source file specifications AT ALL because all DST records have been omitted from the image! The second and third limitations can both be overcome by first directing SYS$OUTPUT to a file, then invoking the DST Scanner, and then sorting the Page 3 output file with SORT /NODUPLICATES. That will give you a nice, tidy, listing, in alphabetical order with each unique source file specification appearing exactly ONCE. But enough about that. How do you build it, and then how do you USE it? To build the DST Scanner, first make sure all the files supplied with this package reside in the same directory. Set your default directory to that directory and invoke the command procedure file BUILD_DST_SCANNERS.COM: $ @BUILD_DST_SCANNERS This procedure will perform three essential operations: 1) Define the logical name DSTDIR to point to the directory where the DST Scanner package's files reside; 2) Build a Macro library containing assembly-time macros necessary for step 3, below; 3) Assemble the Macro-32 source code for the DST Scanner, and link it to form the DST Scanner executable images; 4) Add a new DCL command, "DST", to the then-current process. Note several things. First, the logical name DSTDIR must point, at assembly time, to the directory where the Macro LIBRARY (created in step 2) resides. At run-time it must point to the directory where the DST Scanner executable images reside. These NEED NOT be the SAME directory, but things will probably go more smoothly if they ARE. Second, you'll note that I keep saying "DST Scanner executable IMAGES," plural. The DST Scanner package "as shipped" consists of three executable images: VAX_DST_SCANNER.EXE - reads a VAX image, emits source filespecs ONLY VAX_DST_SCANNER_DETAILS - reads a VAX image, emits source filespecs AND "other details" -- RMS attributes and EOF position, as shipped, but is easily modified to emit, say, source-file creation date... AXP_DST_SCANNER - reads an Alpha AXP image, emits source filespecs ONLY Which program gets run, depends on how you invoke the DST Scanner, which depends on how you issue the DST command. We'll get to that momentarily. Note that ALL THREE of these programs can be built, and will run and do what they're supposed to, under VAX/VMS (built/tested under V5.4-3) and OpenVMS AXP (built/tested under (cringe) V1.5-1H1). I -expect- them to be buildable, executable, and usable under "all" versions of VMS, but like any sane person I DON'T GUARANTEE it. Third, logical name DSTDIR gets defined, and the DST command verb added to your DCL environment, automatically, _only_ when you invoke Page 4 BUILD_DST_SCANNERS.COM. Thereafter it's up to YOU to define the logical and add the DST command verb. I'll discuss this further in a moment. So now that you've built the DST Scanner and have the command verb all ready to use, HOW do you USE it? Like this: $ DST [qualifiers] image_filespec Qualifiers: /VAX Scan a VAX/VMS (OpenVMS VAX) executable image /AXP Scan an OpenVMS Alpha (AXP) executable image /DETAILS Display source-file RMS attributes and EOF position in addition to file specifications. The /DETAILS qualifier is allowed only when scanning a VAX image. You can set up either /VAX or /AXP to be the default, as discussed below. The build-procedure BUILD_DST_SCANNERS.COM will define the logical name DSTDIR, and will add the DST command to your DCL environment. However, the next time you log in you will have to define the logical name, and add the command verb, yourself. Defining the logical name is done by using either the DEFINE or ASSIGN command, like so: $ DEFINE DSTDIR directory_where_DST_Scanner_executables_reside or $ ASSIGN directory_where_DST_Scanner_executables_reside DSTDIR Adding the DCL command verb is done by using either of the two .CLD files provided by this package, with the SET COMMAND command. Assuming the .CLD files reside in the directory pointed to by the DSTDIR logical name, the command is either: $ SET COMMAND DSTDIR:VAX_DST.CLD or $ SET COMMAND DSTDIR:AXP_DST.CLD The only difference is that VAX_DST.CLD defines the DST command so that when no qualifiers are specified the default is /VAX, and that AXP_DST.CLD defines the command so that the default is /AXP. Consult your system documentation for information on how to provide the Page 5 DST command on a system-wide basis, or to yourself automatically at login or in all processes. This should be enough information for you to build and use the DST Scanner. If it is not, you may contact me (at the time of this writing) on the Internet at lvt-cfc@servtech.com . If that address ever ceases to work, hopefully you'll still be able to search the Usenet newsgroups for "Chris Chiesa" and find me. :-) Chris Chiesa (lvt-cfc@servtech.com) September 19, 1996 ========> [VMSLT96B.DTK]AAAREADME.TXT;1 <======== This area contains a set of DECTalk support routines. They aren't well documented unfortunately but what we got is here. ========> [VMSLT96B.EMULATORS]AAAREADME.TXT;2 <======== This area contains some pdp11 emulators and a few other emulators for other machines. (.TAZ files are compressed TAR files). Sources are present when they were available. 6502.TAZ;1 AAAREADME.TXT;1 CPMDOS.ZIP;1 CPMSRC.TAZ;1 EMUL-SITE.POINTER;1 FMSX.Z;1 M2000.TGZ;1 M2000.TXT;1 M2000.ZIP;1 MG-DVR-MODS.TXT;1 MG.TAZ;1 PDP11.TAZ;1 SMS.DIFF;1 SMS2.DIFF;1 SUPNIK_EMULATORS.TAZ;1 VGB.TAZ;1 VGBZOOM.TAZ;1 Z80.TAZZ;1 ========> [VMSLT96B.ETAPE]AAAREADME.TXT;1 <======== ETAPE Rev. 2.26 28-Mar-1995 ETAPE is a general-purpose program for handling EBCDIC, ASCII, and Honeywell GCOS BCD tapes. It allows the user to move around at will within the tape, send output to different files, specify different blocksizes and record lengths for different files on the tape, and combine multiple tape files into a single output file. Special translation can be performed on tapes which have embedded packed decimal, floating-point, or binary fields. The capability of writing EBCDIC or ASCII tapes from VMS ASCII files is also included. EBCDIC tapes can be written in FB of VB mode, and may span several reels if necessary. ETAPE removes all trailing blanks from tape records after reading them. On output, records will be blank padded and blocked to create fixed length tape blocks. A switch can be set to turn off the EBCDIC translation and allow the translation (or writing) of ASCII tapes. Installation ============ ETAPE is comprised of the following files: AAAREADME.TXT This file ETAPE.CLD Command language for ETAPE ETAPE.FOR Source program & subroutines ETAPE.HLP Help file for the program ETAPE.OBJ Object from ETAPE (for re-linking) (Not distributed via MAILSERV) ETAPE_HELP_ENTRY.RNH UNH help file (not edited to be general) (This file is not up to date, but if anyone would like to fix it up, I'd love to have a copy -- Dale) ETAPE_INCLUDE.FOR Include file for fortran code SAMPLE.TRANS A sample directive file for special translation Note: in binary distributions (i.e. NOT Mailserv), the following files are also included for those folks that don't have a FORTRAN compiler. ETAPE.OBJ_VAX ETAPE.EXE_VAX ETAPE.OBJ_AXP ETAPE.EXE_AXP The following procedure is used to build ETAPE: $ FORT ETAPE (VAX) $ LINK ETAPE (AXP) $ LINK/NONATIVE ETAPE $ COPY ETAPE.EXE SYS$COMMON:[SYSEXE]ETAPE.EXE $ LIB/HELP/REPL/LOG SYS$HELP:HELPLIB ETAPE $ SET COMMAND ETAPE Page 2 Known Errors / Limitations ========================== To use ETAPE, a user must possess LOG_IO and PHY_IO privilege or ETAPE must be installed with those privileges. I'm sure there are bugs, but I don't know what they are. If you find one, please let me know. Special thanks for finding (and fixing) bugs go to: Bill Costa - University of New Hampshire John W. Miller - Indiana University of Pennsylvania Rollo Ross - University of South Australia Rick Millhollin - University of Oregon Don Vickers Please direct all comments, criticisms, and especially praise to: Dale Miller University of Arkansas at Little Rock Data Center NS204 2801 S. University Ave. Little Rock, AR 72204-1099 (501) 569-8714 DOMILLER@UALR.EDU ========> [VMSLT96B.ETEX]AAAREADME.TXT;1 <======== eTeX, an extended TeX, is now available here. It is backwards compatible to TeX, but contains several extensions. An example of the use of eTeX can be found on my page http://vzdmzi.zdv.uni-mainz.de/~knappen/jk006.html which demonstrates the usefullness of the new middle primitive. --J"org Knappen. ========> [VMSLT96B.FNAL_GOV]AAAREADME.TXT;2 <======== ******************************************************************************* **** CPS 2.9 README Documentation **** ******************************************************************************* CPS is a package of software tools that makes it easy to split a computational task, referred to as a job, among a set of processes distributed over one or more computers. Apart from considerations of speed, the set of processes will operate identically whether on a single computer or spread across multiple computers. Each process runs a program written by the user. These are called User Processes. The primary tools consist of a Job Manager program, a Shared Memory Manager program, and a set of subroutines, callable from either Fortran or C. The Job Manager (JM) starts the User Processes and Shared Memory Managers, provides common support services, handles errors that occur, and stops all processes when the job is over. The Shared Memory Manager (SHM) directs messages from User Processes to the JM or from User Processes to other User Processes residing on other computers. One SHM is started on each computer where there is at least one User Process. The subroutines provide mechanisms for interprocess communication, remote subroutine calls, and synchronization. These tools support a wide range of models of parallel programming, including remote subroutine calls and message passing. ***************************************************** DART Bootstrap Services (dbs) is the first component of run-control for the DART data acquisi- tion system, though it has potential usefulness as a tool in other applications. dbs is an rlogin session multiplexer. It allows a user, running a single program, to start up any num- ber of remote login sessions, feed shell commands to them, and collect the output from the sessions into one or more logfiles. From dbs, a user can issue commands to these rlogin sessions in one of two ways: either by issuing a dbs command with arguments indicating the session and the actual command, or by first attaching to a session and then issuing the command directly. In the latter case, a user is attached to the session interactively so it appears just like an rlogin session - dbs becomes transparent. When finished with this interactive mode, the user can escape back to dbs and attach to a different session if so desired. The basic commands allow for creating sessions on remote nodes, issuing commands within a session without attaching to it, attaching to a session, and stopping all processes within a session. The program can be driven by commands from a file. The DBS products consists of two parts, the dbs daemon, explained above and the dbs client which interfaces to the daemon, refered to as "dbsc". The bootstrap client communicates to the daemon in one of two modes: command mode or trans-parent (attached) mode. Commands issued in command mode are interpreted by the client and the daemon, while input and output in the transparent mode is passed between the client and the remote rlogin session with no interpretation. In this mode, output from the session is buffered in the daemon and optionally logged to a file. In transparent mode, the local terminal is placed in a "raw" mode so that the local terminal driver does not interpret control characters, etc. - they are passed on to the remote rlogin pseudo-terminal driver. Also, in this mode output from the remote session is copied to the local standard output. In other words, in Page 2 transparent mode the daemon and client are "invisible" to the rlogin session except for one exception: if the escape character is typed in, the session is detached, the client and daemon switch over to command mode, and output from the rlogin session is once again buffered by the daemon. Supported Platforms Daemon is supported on IRIX 5.3 Client is supported on IRIX 5.3 ****************************************** FRC Product Name: frc (bundle) Product Version: 1.0 Date: October 7, 1994 Contents: vx_frcv2.2, fb_frcv2.1, fbremv1.4 DESCRIPTION ----------- This is a "bundle", containing three separate but related products: vx_frc, fb_frc, and fbrem. The products are related in the following way: fbrem requires fb_frc, and fb_frc requires vx_frc. There are three archive files then, one for each product. See the README files in each archive for all pertinent information about a product, including its compatibility requirements regarding the product it depends upon, if any. A release of the "bundle" will contain compatible releases of each product which have been tested together. The bundle's version number will increment whenever ANY or ALL products within the bundle change. The FASTBUS Readout Controller (FRC) is an embedded processor FASTBUS board based on the LR33000 embedded CPU. It was developed by the Fermilab Computing Division's Data Acquisition Engineering Department. It is now sold commercially by Bi-Ra Systems, under the DOE Technology Transfer Program. This product is the software needed to take advantage of this board's capabilities. frc is a bundle of software with three components: vx_frc, fb_frc and fbrem. vx_frc is the VxWorks Board Support Package (BSP) which is the necessary basic operating software for the FRC board, under which everything else runs. VxWorks is a proprietary real-time operating system, and its use requires appropriate license from its producer, Wind River Systems, Inc. fb_frc is an implementation of the IEEE FASTBUS Standard Routines for the FRC board. fbrem is a client library which provides transparent access to fb_frc over a network via Sun's RPC (Remote Procedure Call) protocol, supported on most UNIX platforms. With an appropriate linking procedure, it should also run on VAX/VMS systems with appropriate third-party networking software. This may be supported in a future release. *********************************************** JUKE Product Name: juke Product Version: v5_0 Page 3 Abstract The "juke" product is an extensible software package for interfacing with tape, CD, and other media jukeboxes, (however since it currently is used only for tape, media is referred to as tape throughout) This makes it ideal for controlling tape jukeboxes for data analysis, backups, etc. where tape mounts are needed at times when it is inconvenient for human operators to perform them, or for automated labeling of batches of tapes etc. The "juke" package supports controlling multiple jukeboxes per host, multiple hosts per jukebox, etc. with control being shared over a network. "juke" controls only the jukebox media handling mechanism itself, and not any media drives, etc. contained within the jukebox. It deals with multiple jukebox types by treating them all as having simple, abstract components; the tapes themselves, slots to hold the tapes, drives which can play, read, or write the tapes, and "mailbox slots" which can be uncovered for people to take tapes in and out of the jukebox, or covered for the jukebox to be able to manipulate the tapes. A lookup table of tapes is maintained, by a small dbm(3) database, however only 3 short interface routines need to be written to add in interface to an existing tape database. "juke" consists of 5 main binary deliverables, an RPC daemon process which actually controlls the jukebox, an interactive RPC client which allows command line interface to the control of the jukebox, an API library which provides program callable access to jukebox control, and 2 SCSI pass-through drivers, one for Sun Microsystems Solaris systems, and one for AIX 3.* systems. It also comes with an extensive user guide with numerous examples, and an API reference describing the library calls. "juke" is currently being used to control Summus, Exabyte, and DEC DLT media changers at Fermilab. Documentation: User documentation is found in "doc/jukeuser.latex" in the distribution, or via WWW at: http://www.fnal.gov/docs/products/juke Contents: A file list is in the file Manifest. Platforms: juke can currently run Exabyte and DEC tape robots of various sizes on systems with SCSI pass-through devices, and Summus Carousels via serial ports. It provides a framework for adding other device types easily. This has been used on AIX, IRIX, and SunOS systems as an RPC client, and on SunOS 5.x, IRIX 4.x IRIX 5.x and AIX 3.2 systems as an RPC server. Server and client code for VMS exist, but haven't been Page 4 tested for several releases. Installation instructions can be found in the user documentation. Special installation instructions for the AIX pass-through driver are in the file jukedd/INSTALL in the distribution. Special installation instructions for the Solaris pass-through driver are in the file sst/INSTALL in the distribution. *********************************************** MXYZPTLK ("mix-yezz-pitel-ick") > Product name: MXYPTLK > Version: 3.1 > Documentation: mxyzptlk.ps > List of files: The primary file is a compressed tar file which can be installed under Unix. (See instructions below.) Upon installation, three subdirectories are created: ./demos, ./include, ./docs, and ./src The contained in these directories are as follows: docs: mxyzptlk.ps.Z demos: CMapTest.cc Hermite.cc Inverse_A_Test.cc Inverse_B_Test.cc Inverse_C_Test.cc Inverse_D_Test.cc Inverse_E_Test.cc Lie_A_Test.cc Lie_B_Test.cc Lie_C_Test.cc Lie_D_Test.cc Lie_E_Test.cc Lie_F_Test.cc Lie_G_Test.cc Lie_H_Test.cc Lie_I_Test.cc Lie_K_Test.cc Lie_L_Test.cc Limit_A_Test.cc Limit_B_Test.cc Limit_C_Test.cc Limit_D_Test.cc Limit_E_Test.cc Limit_F_Test.cc Limit_G_Test.cc Limit_H_Test.cc Page 5 Makefile SVDTest.cc concattest.cc coordTest.cc dfr.cc ev.cc evaltest.cc g5.cc hptest.cc lbtest.cc orthogonalTest.cc pbtest.cc survey.cc include: Barnacle.hxx CLieOperator.hxx Distribution.hxx JL.hxx JLC.hxx Jet.hxx JetC.hxx JetVector.h LieOperator.hxx ML.hxx Map.hxx MathConstants.hxx Matrix.hxx PhysicsConstants.hxx Vector.h c_erf.hxx cc_erf.hxx complexAddon.hxx dlist.hxx f2c.h menu.hxx mxyzptlk.hxx mxyzptlk.rsc slist.hxx src: Barnacle.cc CLieOperator.cc Distribution.cc JL.cc JLC.cc Jet.cc JetC.cc JetCFcns.cc JetFcns.cc JetVector.cc LieOperator.cc ML.cc Makefile Matrix.cc Matrix_SVD.cc Vector.cc Page 6 binomcoeff_recursive.c c_erf.cc cc_erf.cc cg.c cwerf64.c d_sign.c dlist.cc gcd.c menu.cc mod2pi.c mygaussj.cc nearint.c nexcom.cc normalForm.cc parsef.c rg.c slist.cc strequals.c > Platforms: Unix is the principal platform. The software has been used on DEC/VMS and DOS/Windows platforms with only minor modifications, prompted by the compilers. > Installation Under Unix, first uncompress mxyzptlk.tar.Z and > and build: then enter "tar xf mxyzptlk.tar". The subdirectories will be automatically created and files loaded into them. The Makefile can be used to create the library, libmxyzptlk.a, which is built from the files in the src subdirectory. The user can then build demo files by linking with libmxyzptlk.a. > Example programs: Are contained in the demos subdirectory. > Dependencies: None. > Acknowledgements: Thanks to James Holt for his contributions ****************************************************** NEDIT NEdit V4.0.1 3/21/96 NEdit is a GUI style plain-text editor for X/Motif systems. It is very easy to use, especially for those familiar with the Macintosh or MS Windows style of interface, combining full use of the mouse and window manager, with keystroke efficiency and a full complement of powerful editing commands. Features - Efficient, proven command set - Very complete functionality. NEdit is the primary editor for thousands of Unix and VMS programmers - Thorough consistency with Motif, MS Windows, and Macintosh Page 7 conventions - Designed for intensive use: fast response time, menu and dialog shortcuts, streamlined interaction - Multi-level undo - Learn/replay - 100% GUI from the ground up - True multi-window, fully graphical design - Mouse based editing - Cut and Paste with other X Windows/Motif programs, full compatibility with all X and Motif selection and text interchange styles - Secondary, quick-action, selections - Rectangular selection mode - Easy to learn - Just point and type - Capabilities are presented clearly in top level menus - Comprehensive on-line help - No special knowledge of X Windows required, all important options can be set from within the program - Features for programmers - Auto-indent - Block indentation adjustment - Parenthesis flashing and matching - Find lines directly from compiler error output - Emulated tabs - Unix ctags support - Client/Server mode for integration with software development tools - Easy installation - Self contained single executable file - Pre-built, tested executables available for Silicon Graphics, Sun (Solaris & SunOS), HP, OSF/1, DEC Ultrix, IBM AIX, Linux, and VMS systems Mark Edel, m/s 234 Fermi National Accelerator Laboratory P.O. Box 500 Batavia, IL 60148 (708)840-2496 edel@fnal.gov ========> [VMSLT96B.FREEWAREV3]AAAREADME.TXT;2 <======== These are a number of slightly late submissions that looked useful enough to include. ACC_CKPT010.BCK;1 Check point your accounting file BISON-1_22-19960713.ZIP;1 GNU BISON for VMS, latest vers. CALLMON.ZIP;1 Monitor calls to a shared image on Alpha VMS CRS.ZIP;1 VMS directory browser CRYDSK.ZIP;1 Remote disk and cryptodisk for VMS DFU024-RELEASE.TXT;1 Release for DFU, the disk utility pkg for DFU024SRC.BCK;1 ...VMS. Does many disk and file maintenance DFU_FREEWARE_024.A;1 ...operations. EMON021-3.BCK;1 Ethernet monitor program ERROR_WEDGE.ZIP;1 Retry disk operations if any errs occur w/src FASTLOGIN.BCK;1 Speed login by prog to do login.com things GZIP-1_2_4-19960226.TAR-GZ;1 Latest gzip compress/decompress HTTPD.ZIP;1 HTTP (WWW) server, many examples, utilities, and other bits to support hypertext in VMS JUMP022.BCK;1 Become another user KILL062.A;1 Kill other process (by user, name, etc.) KILL_NODE020A.BCK;1 Remotely crash another cluster member LASER011-26.BCK;1 Laser printer symbiont LYNX-CHANGES.TXT;1 Lynx, a text based web browser LYNX2-5FM.ZIP;1 ...latest VMS version PS2TEXTV11.ZIP;2 Convert Postscript to text PSICOPY040.BCK;1 Copy files over PSI (x.25) SAFETYSPD.TXT;3 SPD from the shadowing-vd author SCANPRINTER.BCK;1 Scan printers periodically, act if queues stall SD.BCK;1 Set default utility SHOCLUST-WEB.ZIP;1 Show cluster web based utility SYSPQL010B.BCK;1 Increase startup process quotas as user may want UCXTCPFILTER022A.BCK;1 Filter TCP/IP server requests, monitor them and insert additional checking if needed UNITOOLS.BCK;1 Selective delete accounting records, show image create date, change newmail counts, start DECterm as another user, search for text in any cmd's output, count file records, show workset, run prog on any X display, repeatedly do a cmd, etc. VDD64.ZIP;9 Virtual disk driver that works on Alpha, with support to use DEC volume shadowing to shadow the virtual disks. Use to shadow unlike size disks. w/src. VMSTARU4033.ZIP;1 Latest TAR utility for VMS VMS_INTERNAL_HACKS_SRC.ZIP;1 Many useful src examples for VMS WEBBOOK.1-OF-5;1 Bookreader access from the web WEBBOOK.2-OF-5;1 WEBBOOK.3-OF-5;1 WEBBOOK.4-OF-5;1 WEBBOOK.5-OF-5;1 ZLIB104.ZIP;1 Compress/decompress library ========> [VMSLT96B.FREEWAREV4]AAAREADME.TXT;2 <======== my port of gnu make 3.75 and a touch utility are available on ftp://ftp.progis.de/files/VMS/freeware for inclusion in the freeware cd for openVMS. Since backup isn't portable, I packed the files with vms-tar and gnu-zip. If either program isn't available to you, pleas mail me. Executables for vax (make.exe_vax, touch.exe_vax) and alpha (make.exe, touch.exe) are included. A short description of the program and its installation is in aaareadme.txt. I also added a short note about gnu c openvms/alpha in GNU_C_ALPHA.TXT. I hope the distribution format is acceptable. If any changes are required to match 'freeware cd standards', I'll be glad to help ! Regards, Klaus -- =20 proGIS Software E-Mail: kkaempf@progis.de Dipl.-Inform. Klaus K=E4mpf Fax: 0241-47067-29 Jakobstr. 117 Voice: 0241-47067-11 D-52064 Aachen WWW: http://www.progis.de Also present is an updated version of Art Ragosta's KRONOS scheduler package, fixing a bug in the freeware v3 version. ========> [VMSLT96B.FTP_HHS_DK]AAAREADME.TXT;1 <======== This area contains many of the utilities from the following FTP site. The index is appended. The following files are available via anonymous FTP from FTP.HHS.DK: Packages -------- Are placed in seperate diretories as zipped files. [.PASCAL_PPL]PASCAL_PPL.ZIP Description : easy to use PASCAL-interface to PPL$-routines The package includes: - PAR.MAR and MULTI.PAS which define and implements the interface - EX.* which shows how to use it - EXBIG*.* which shows how to use it with benefit (including timing results) Source : PASCAL and MACRO Binary : not available Notes : multiprocessor VAX necesarry to benefit (VAX only) Posted : INFO-VAX january 1993 [.SYMBIONT]SYMBIONT.ZIP Description : two symbionts The NULL symbiont does absolutely nothing. It can be used for making a blackhole queue (f.ex. if you want SYS$PRINT to point to an existing queue, but you do not want to see any print). The SERVER symbiont tests, if the files "language-type" matches that of the real queue, and creates a new printjob on the real queue with the same files. This can be very smart in an environment with both postscript and non-postscript printers, because postscript output on a non-postscript printer is a waste of paper. Theese functions is controlled via some logicals. Source : PASCAL and MACRO Binary : OBJ's and EXE's in SYMBIONT_BIN_VAX.ZIP (compiled with PASCAL 5.0 on VAX and linked on VMS VAX 5.5-2) OBJ's and EXE's in SYMBIONT_BIN_AXP.ZIP (compiled with PASCAL 5.0 on AXP and linked on VMS AXP 1.5) Notes : privs necesarry to initialize queue with symbiont Page 2 (VAX and AXP) Posted : INFO-VAX december 1991 [.MIRROR]MIRROR.ZIP Description : example of humor (try @DEMO) Source : PASCAL and FORTRAN Binary : not available Notes : (VAX only) Posted : INFO-VAX december 1990 [.PROF]PROF.ZIP Description : primitive profiler (also an example of how to read GST and DST) Source : FORTRAN and MACRO Binary : OBJ's + EXE's in PROF_BIN.ZIP (compiled with FORTRAN 6.1 on VAX and linked on VMS VAX 5.5-2) Notes : (VAX only) Posted : not [.MEM_EDIT]MEM_EDIT.ZIP Description : example of using callable EDT and callable TPU to edit memory-variable Source : MACRO Binary : not available Notes : (VAX only) Posted : INFO-TPU march 1993 [.SPI]SPI.ZIP Description : example of calling EXE$GETSPI Source : C Binary : not available Notes : not written by me (VAX only) Posted : MACRO32 february 1993 [.UTILITIES]UTILITIES.ZIP Description : examples of small utilities to help the system-manager with his daily work. The examples include: - Find information about all processes at node (pre-VMS5.2) - Find information about all processes at node (post-VMS5.2) - Find information about all processes in cluster - (post-VMS5.2 extended version 1) - Find all nodes in cluster and find information about all processes at nodes - (post-VMS5.2 extended version 2) Page 3 - Find information about one queue - Find information about all queues - Find information about one job - Find informatrion about all job in one queue - Find informatrion about all job in all queues - Find information about all usernames in SYSUAF (supported) - Find information about all usernames in SYSUAF (unsupported) - Find information about all disk-quotas on a disk (supported) - Find information about all disk-quotas on a disk (unsupported) Source : DCL, FORTRAN, PASCAL and C Binary : not available Notes : privs necesarry (VAX and AXP) Posted : presented at DECUS Denmark symposie june 1993 [.BM]BM.ZIP Description : this bechmark compares the efficiency of PASCAL, FORTRAN, C and MACRO for 3 basic numeric operations: matrix transpose, matrix copy and vector dot product. Results are included for different versions of PASCAL and FORTRAN. The results of PASCAL is very poor indeed. Source : PASCAL, FORTRAN, C and MACRO Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX june 1991 [.BM]RESULT.DAT Description : benchmark results from the program above. Source : - Binary : - Notes : none Posted : INFO-VAX march 1994 [.INST]INST_TEST.ZIP Description : this program tests the speed of various instructions in the VAX instruction-set Source : PASCAL and MACRO Binary : not available Notes : it takes approx. 100/VUPS CPU hours to run, so you may want to run it in the weekend (VAX only) Posted : INFO-VAX january 1992 [.INST]SUMMARY.TXT Description : a summary of results for the program above run on different VAX'es Page 4 Source : - Binary : - Notes : none Posted : INFO-VAX march 1992 [.INST]INST_RES.ZIP Description : a summary of results for the program above run on different VAX'es + the raw material on which the summary is based + a small program helping analyzing the results Source : PASCAL Binary : not available Notes : none Posted : not [.CPUTIME]CPUTIME.ZIP Description : demonstrates six different ways of getting CPU usage. Source : FORTRAN and MACRO Binary : not available Notes : (VAX only) Posted : INFO-VAX february 1994 [.FONTGEN]FONTGEN.ZIP Description : program that generates softfonts for VT220 terminals from an ascii-file + 2 example ascii-file fonts Source : PASCAL Binary : OBJ's and EXE's in FONTGEN_VAX.ZIP (compiled with PASCAL 5.0 on VAX and linked on VMS VAX 5.5-2) OBJ's and EXE's in FONTGEN_AXP.ZIP (compiled with PASCAL 5.0 on AXP and linked on VMS AXP 1.5) Notes : (VAX and AXP) Posted : not [.SETPMT]SETPMT.ZIP Description : changes the prompt to current directory whenever current directory is changed via DCL (and that is always the case unless some programs calls SYS$SETDDIR themselves). No privs required. Source : FORTRAN Binary : OBJ's and EXE's in SETPMT_BIN.ZIP (compiled with FORTRAN 6.1 and linked on VMS 5.5-2) Notes : needs VERB or VMS 5.5 (VAX only) Posted : not [.REDUCE]REDUCE.ZIP Description : performe expression reduction via TPU and a TPU$CALLUSER module using general RPS techniques Source : TPU, FORTRAN and MACRO Binary : OBJ's and EXE's in REDUCE_BIN.ZIP (compiled with FORTRAN 6.1 and linked on VMS 5.5-2) Notes : (VAX only) Posted : not Page 5 [.VAX2AXP]VAX2AXP_TXT.ZIP Description : a small guide to porting programs from VAX VMS to VMS AXP. Covers both FORTRAN,C,PASCAL and MACRO32 programs. Source : mostly text, but also small FORTRAN/C/MACRO32/MACRO64 demonstration programs Binary : - Notes : none Posted : presented at DECUS Denmark symposie june 1994 [.VAX2AXP]VAX2AXP_PS.ZIP (same as VAX2AXP_TXT.ZIP but a nicer postscript version genereated by WP 5.1/DOS) [.VAX2AXP]VAX2AXP_WP5.ZIP (same as VAX2AXP_TXT.ZIP but as a WP 5.1/DOS document) [.VAX2AXP]VAX2AXP_REVISED.TXT (revised version of the guide, text version only) [.GIVE_NAME]GIVE_NAME.ZIP Description : shows how to get the name of the calling routine Source : FORTRAN and MACRO Binary : OBJ's and EXE's in GIVE_NAME_BIN.ZIP (compiled with FORTRAN 6.1 and linked on VMS 5.5-2) Notes : (VAX only) Posted : INFO-VAX june 1994 [.SPAWN_MBX]SPAWN_MBX.ZIP Description : shows how to create a subprocess with input and output via mailboxes Source : FORTRAN and MACRO Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX july 1994 [.NICE]NICE_BASE_1.ZIP (zipped with VMS ZIP) [.NICE]NICE_BASE_2.ZIP (zipped with PKZIP) Description : Pascal beautifier (prettyprinter) with lots of features analysing code and helping porting between DEC PASCAL and TURBO PASCAL. This is the base kit for program modification. Source : C,YACC and LEX Binary : see below Notes : (all platforms) Posted : not Page 6 [.NICE]NICE_1.ZIP (zipped with VMS ZIP) [.NICE]NICE_2.ZIP (zipped with PKZIP) Description : Pascal beautifier (prettyprinter) with lots of features analysing code and helping porting between DEC PASCAL and TURBO PASCAL. This is a prepared kit for DEC PASCAL, TURBO PASCAL and STANDARD PASCAL. Source : C Binary : EXE's in NICE_BIN_GNUC.ZIP (compiled with GNU C 2.6.3 on VAX and linked on VMS VAX 6.2) EXE's in NICE_BIN_VAXC.ZIP (compiled with VAX C 3.2 on VAX and linked on VMS VAX 6.2) EXE's in NICE_BIN_DECC_VAX.ZIP (compiled with DEC C 5.3 on VAX and linked on VMS VAX 6.2) EXE's in NICE_BIN_DECC_AXP.ZIP (compiled with DEC C 5.3 on AXP and linked on VMS AXP 6.2) EXE's in NICE_BIN_MSC.ZIP (compiled and linked with MS C 7.0 on PC) EXE's in NICE_BIN_BC.ZIP (compiled and linked with Borland C 3.0 on PC) EXE's in NICE_BIN_DJG.ZIP (compiled and linked with DJ GPP 2.6.3 on PC) Notes : (all platforms) Posted : not [.MAILMANIP]MAILMANIP.ZIP Description : example of how to manipulate MAIL.MAI directly with 3 examples (list content, modify all FROM fields, give all messages in NEWMAIL folder the "New message" attribute) Source : FORTRAN Binary : OBJ's and EXE's in MAILMANIP_VAX.ZIP (compiled with FORTRAN 6.1 on VAX and linked on VMS VAX 5.5-2) OBJ's and EXE's in MAILMANIP_AXP.ZIP (compiled with FORTRAN 6.1 on AXP and linked on VMS AXP 1.5) Notes : (VAX and AXP) Posted : INFO-VAX january 1995 [.DCLEDIT]DCLEDIT.ZIP Description : utility for editing several commands retrieved from the recall buffer and execute them after editing Source : FORTRAN and MACRO Binary : OBJ's and EXE's in DCLEDIT_BIN_VAX.ZIP (compiled with FORTRAN 6.2 on VAX and linked on VMS VAX 6.1) OBJ's and EXE's in DCLEDIT_BIN_AXP.ZIP (compiled with FORTRAN 6.2 on AXP and linked on VMS AXP 6.1) Notes : (VAX and AXP) Posted : INFO-VAX august 1990 [.PTD]PTD.ZIP Description : example of usage of PTD$-routines (pseudo-terminals) Page 7 Source : C Binary : not available Notes : (VAX and AXP) Posted : not [.CORE]CORE.ZIP Description : very simple examples of MACRO-64 programming Source : FORTRAN and MACRO Binary : not available Notes : (AXP only) Posted : not [.XEVE]XEVE_SRC.ZIP [.XEVE]XEVE_SRC_ALPHAFIX.ZIP Description : eXtended EVE editor with lots of features for: - "system-manager editing" - programming - word-processing Source : TPU and FORTRAN Binary : TPU$SECTIONS's and EXE's in XEVE_BIN_VAX.ZIP (compiled with FORTRAN 6.3 on VAX and linked on VMS VAX 6.1) TPU$SECTION's and EXE's in XEVE_BIN_AXP.ZIP (compiled with FORTRAN 7.0 on AXP and linked on VMS AXP 6.2) Notes : (VAX and AXP) Posted : not [.XEVE.VMSVAX55]XEVE_SRC.ZIP Description : XEVE for VMS VAX 5.5 (probably all 5.x) Source : TPU and FORTRAN Binary : TPU$SECTIONS's and EXE's in XEVE_BIN_VAX.ZIP (compiled with FORTRAN 6.1 on VAX and linked on VMS VAX 5.5-2) Notes : (VAX and probably AXP) Posted : not Small programs -------------- Are placed in directory [.MISC] as single files. [.MISC]EXTTRNLNM.MAR Description : translates a logical in the context of another process. (particular usefull for translating logicals in another users LNM$PROCESS_TABLE) Source : MACRO Binary : not available Notes : privs necesarry (VAX only) Posted : not [.MISC]GETJIBADR.MAR Page 8 Description : get JIB-address from PID (used for getting actaul name of LNM$JOB) Source : MACRO Binary : not available Notes : privs necesarry (VAX only) Posted : not [.MISC]GETCH.C Description : example of implementing putch,kbhit and getch in C via $QIOW including CTRL/Y trapping Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX november 1991 [.MISC]GETCH_BCSTTRAP.C Description : example of implementing putch,kbhit and getch in C via $QIOW including CTRL/Y trapping and broadcast trapping Source : C Binary : not available Notes : (VAX and AXP) Posted : not [.MISC]CRC.C Description : example of emulating the CRC instruction Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX october 1990 and MACRO32 march 1993 [.MISC]FIND_FILE_%.C Description : Examples of calling LIB$FIND_FILE from C. Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX january 1991 [.MISC]EXTGETDDIR.MAR Description : get default directory in the context of another process. Source : MACRO Binary : not available Notes : privs necesarry (VAX only) Posted : not [.MISC]SYS$IMGACT.COM Description : it demonstrates what I know about the two Page 9 undocumented system-services SYS$IMGACT and SYS$IMGFIX and the documented user of them LIB$FIND_IMAGE_SYMBOL. Source : FORTRAN and MACRO Binary : not available Notes : (VAX only) Posted : MACRO32 december 1993 [.MISC]MIX_FORTRAN_C_IO.COM Description : it demonstrates how to use the same open files in both FORTRAN and C routines Source : FORTRAN and C Binary : not available Notes : (VAX only) Posted : INFO-VAX june 1994 [.MISC]FORTRAN_MACRO_CALL_%.COM Description : examples of calling MACRO routines from FORTRAN Source : FORTRAN and MACRO Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX april 1994 [.MISC]FORTRAN_VARARG.COM Description : examples of FORTRAN routines with varying number of arguments Source : FORTRAN and MACRO Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX april 1994 [.MISC]PASCAL_C_CALL.COM Description : examples of calling C routines from PASCAL Source : PASCAL and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1994 [.MISC]FORTRAN_C_CALL.COM Description : examples of calling C routines from FORTRAN Source : FORTRAN and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1994 [.MISC]BRKTHRUW.C Description : examples of calling SYS$BRKTHRUW from C Source : C Binary : not available Page 10 Notes : (VAX and AXP) Posted : INFO-VAX august 1994 [.MISC]LOGICAL_LOOKUP.MAR [.MISC]TEST_LOGICAL_LOOKUP.FOR Description : lookup of all logicals in logical name table Source : MACRO (test-program in FORTRAN) Binary : not available Notes : privs necesarry to lookup in non-private tables (VAX and AXP) Posted : INFO-VAX august 1994 [.MISC]CHNLST.MAR [.MISC]TEST_CHNLST.FOR Description : list all channels (with device-name and FID) for a given process Source : MACRO (test-program in FORTRAN) Binary : not available Notes : privs necesarry (VAX only) Posted : INFO-VAX august 1994 [.MISC]*_IMAGEINFO.MAR [.MISC]*_TEST_IMAGEINFO.COM Description : gets infor on current image Source : MACRO (test-program in FORTRAN) Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX october 1994 [.MISC]ENV.C Description : get/put from/to permanent DOS environment Source : C Binary : not available Notes : this is a DOS program Posted : not [.MISC]PORTABLE_INT2HEXSTR.PAS Description : portable code for converting an integer to a hex-string Source : PASCAL Binary : not available Notes : none Posted : COMP.LANG.PASCAL october 1994 [.MISC]QUEUE_CLEANUP.COM Description : deletes all entries in a queue Source : DCL Binary : - Notes : privs necesarry Page 11 Posted : INFO-VAX november 1994 [.MISC]WHO_IS_ON.COM Description : shows who is on the system Source : DCL Binary : - Notes : privs necesarry Posted : not [.MISC]UN_PW_CHECK.PAS Description : checks all usernames for if password=username Source : PASCAL Binary : not available Notes : privs necesarry (both VAX and AXP) Posted : not [.MISC]ACCOUNT.C Description : gets CPU usage for all process terminations from ACCOUNTNG.DAT file Source : C Binary : not available Notes : (both VAX and AXP) Posted : not [.MISC]RANDOM.PAS Description : density, accumulated and inverse accumulated function for the normal distribution Source : Pascal Binary : not available Notes : none Posted : not [.MISC]TEST_CIALST.FOR [.MISC]CIALST.MAR Description : list content of intrusion database Source : FORTRAN and MACRO Binary : not available Notes : privs necesarry (VAX and AXP) Posted : INFO-VAX november 1994 [.MISC]CHANGE_PROT.FOR [.MISC]CHANGE_PROT.PAS [.MISC]CHANGE_PROT.C Description : example of how to change protection (give Owner Delete access) Source : FORTRAN, PASCAL and C Binary : not available Page 12 Notes : (VAX and AXP) Posted : not [.MISC]FPUTEST.PAS Description : test for bad Pentium chips (FDIV bug) Source : PASCAL Binary : FPUTEST.EXE Notes : must be compiled with inline x87 instructions Posted : not [.MISC]FILE_SIZE.FOR [.MISC]FILE_SIZE.PAS [.MISC]FILE_SIZE.C Description : example of how to find size of file Source : FORTRAN, PASCAL and C Binary : not available Notes : (VAX and AXP) Posted : not [.MISC]EBCDIC.C [.MISC]TEST_EBCDIC.C Description : example of how to convert between EBCDIC and ASCII Source : C Binary : not available Notes : none Posted : comp.lang.c january 1995 [.MISC]LOAD_IMAGE_VAX.COM [.MISC]LOAD_IMAGE_AXP.COM Description : example of how to use LIB$FIND_IMAGE_SYMBOL to load shareable image Source : FORTRAN and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX march 1995 [.MISC]TERMSET.PAS [.MISC]TERMSET.C Description : example of how to use terminator-sets in SMG$-routines Source : PASCAL and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX december 1990/may 1995 [.MISC]READACL.FOR Description : example of how to read ACL from a file Source : FORTRAN Binary : not available Notes : (VAX and AXP) Page 13 Posted : INFO-VAX may 1995 [.MISC]TPU$CALLUSER.C Description : example of how create a TPU$CALLUSER routine (translation of logicals) Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-TPU march 1991 [.MISC]CLD.COM Description : example of how to use CLD-files and CLI$-routines Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX february 1992 [.MISC]LIST_LIBRARY.FOR [.MISC]LIST_LIBRARY.C Description : example of how to list content of text library with LBR$-routines Source : FORTRAN and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1993 [.MISC]TERM_SIZE.FOR Description : get terminal size (width and heigth) Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX april 1990 [.MISC]STRCVT.PAS Description : convert between "packed array of char" and "varying of char" Source : PASCAL Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX april 1992 [.MISC]ERR_HANDL.FOR Description : example of using an error-handler (via LIB$ESTABLISH) to handle certain floating point errors Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX february 1993 [.MISC]SEND_MAIL.PAS Page 14 Description : example of sending mail via callable mail (MAIL$-routines) Source : PASCAL Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX february 1991 [.MISC]OUTPUT_HELP.FOR Description : example of formating help output via LBR$OUTPUT_HELP Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX march 1993 [.MISC]PARSE.FOR Description : example of parsing file specification with SYS$PARSE Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1991 [.MISC]VERIFY.MAR [.MISC]TEST_VERIFY.FOR Description : test whether verify is set or not Source : MACRO (test-program in FORTRAN) Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX may 1991 [.MISC]RECALL.MAR [.MISC]TEST_RECALL.FOR Description : get copy of recall buffer Source : MACRO (test-program in FORTRAN) Binary : not available Notes : (VAX only) Posted : INFO-VAX september 1992 [.MISC]CPULOAD.MAR [.MISC]TEST_CPULOAD.PAS Description : get CPU load in various modes including idle time Source : MACRO (test-program in PASCAL) Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX september 1993 [.MISC]DELETE_CONFIRM.FOR Description : example of using LIB$DELETE_FILE to delete files with confirmation Source : FORTRAN Page 15 Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX april 1993 [.MISC]SHOW_QUOTA.FOR Description : example of getting disk-quota for user and getting the owner-field with SYS$GETUAI Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX june 1993 [.MISC]I8_VAX.COM [.MISC]I8_AXP.COM Description : example of how to use 64 bit integers Source : FORTRAN, C and C++ Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX november 1993 [.MISC]ACL.MAR [.MISC]TEST_ACL.FOR [.MISC]TEST_ACL.PAS Description : ACL manipulation Source : MACRO (test-program in FORTRAN and PASCAL) Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX february 1991 [.MISC]TERMINFO.C Description : get information about terminal Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1995 [.MISC]STMLF.C [.MISC]FIX512.C Description : example of how to set file attributes (change to STREAM_LF and FIXED 512) via SYS$MODIFY Source : C Binary : not available Notes : (VAX and AXP) Posted : not [.MISC]LNMLOOKUP.ZIP Description : user-written system-service to allow wildcard lookup of logicals Source : MACRO and C Page 16 Binary : not available Notes : written by Ferdinand Bolhár-Nordenkamp (VAX and AXP) Posted : not [.MISC]CHKPW.MAR [.MISC]CHKPW.C Description : check if username/password combination is valid Source : MACRO and C Binary : not available Notes : privs necesarry to check other usernames (VAX and AXP) Posted : INFO-VAX november 1995 [.MISC]CMPC3.COM Description : examples of getting CMPC3 functionality in FORTRAN Source : FORTRAN, MACRO and C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX december 1995 [.MISC]EXCVEC.MAR [.MISC]TEST_EXCVEC.FOR Description : example of how to get the exception vectors (can be used to tell whether an image is run under debugger) Source : MACRO (test program in FORTRAN) Binary : not available Notes : (VAX and AXP) Posted : VMSNET-INTERNALS february 1996 [.MISC]ID_BY_USER.C Description : example of how to find all identifiers held by user Source : C Binary : not available Notes : (VAX and AXP) Posted : VMS-WEB-DAEMON february 1996 [.MISC]DBF.PAS [.MISC]TEST_DBF.PAS Description : example of how to write an DBF-file Source : PASCAL Binary : not available Notes : (VAX and AXP) Posted : not [.MISC]MSG.COM Description : example of how to use "messages" Source : FORTRAN Binary : not available Notes : (VAX and AXP) Page 17 Posted : not [.MISC]IJOBCNT.C [.MISC]IJOBCNT_DCL.C Description : example of how to get number of current interactive users Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX may 1996 [.MISC]PASCAL_FORTRAN_CALL_CALL.COM [.MISC]FORTRAN_PASCAL_CALL_CALL.COM Description : example of how to call FORTRAN from PASCAL and PASCAL from FORTRAN Source : FORTRAN and PASCAL Binary : not available Notes : (VAX and AXP) Posted : not [.MISC]UAFCHK.PAS Description : check SYSUAF quotas for all usernames Source : PASCAL Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX july 1996 [.MISC]SHOWMEM.COM Description : show memory usage for all processes Source : DCL Binary : - Notes : (VAX and AXP) Posted : INFO-VAX august 1996 [.MISC]MAILQUOTE.TPU Description : quote mail and include signature automatically Source : TPU Binary : - Notes : (VAX and AXP) Posted : INFO-VAX july 1996 [.MISC]TRUNCATE.C Description : truncate a file at a specfied byte Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1996 [.MISC]FID2NAME.FOR Page 18 Description : translate from FID to filename with LIB$FID_TO_NAME Source : FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1996 [.MISC]PW_GEN.PAS Description : generate a lot of random passwords Source : PASCAL Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX august 1996 [.MISC]LIB$SET_LOGICAL.C Description : example of calling LIB$SET_LOGICAL Source : C Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX december 1996 [.MISC]MIX_C_CPLUSPLUS.COM Description : example of mixing C and C++ Source : C and C++ Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX december 1996 [.MISC]NULLCPU_VAX.COM [.MISC]NULLCPU_AXP.COM Description : get NULL CPU ticks Source : MACRO and FORTRAN Binary : not available Notes : (VAX and AXP) Posted : INFO-VAX june 1994 Various stuff ------------- Are placed in directory [.TMP] without any description. INFO-VAX collection ------------------- Are placed in directory [.COLLECTION]. A2PS.ZIP Ascii to PostScript converter ANIMATIONS.ZIP VT100 terminal animations via escape sequences BINHEX.ZIP BINHEX decoder for VMS BTOA.ZIP BTOA decoder for VMS CALLABLE_MAIL.ZIP documentation of callable mail CIA.ZIP testing and modififying the intrusion database Page 19 CLEAN_VMSMAIL.ZIP utility to cleanup VMSMAIL_PROFILE.DATA CURRENT_COMMAND.ZIP get name of current comamnd file DCL_MBX.ZIP create mailbox from DCL DCLTRACE.ZIP trace of DCL call stack DEFINE_KEY.ZIP equivalent of DCL DEFINE/KEY DEV_TO_FCB.ZIP emulation of the SHOW DEV/FILE command DISKACCT.ZIP get disk-usage summary without disk-qiota DYNLOADEXE.ZIP dynamic loading of EXE-file with SYS$IMGACT DYNLOADEXE2.ZIP variant DYNLOADEXE3.ZIP variant ETHERNET_ADDRESS.ZIP get ethernet-address EXPFILES.ZIP expand wildcard files like UNIX FIDDEL.ZIP delete file by FID FIX_SAVESET.ZIP set correct file-attributes on BACKUP saveset FOREIGNMAIL.ZIP documentation of VMS foreign mail protocol FORTRAN_BUGS.ZIP 3 small errors in FORTRAN easy to make FPARSE.ZIP equivalent of DCL lexical F$PARSE GET_IDENT.ZIP get identifiers held by PID GMT.ZIP get CPU usage in modes IEEE.ZIP conversion IEEE<->VAX float ISLOADED.ZIP test if devices is loaded KAST.ZIP documentation on how to queue KAST's LATSYM.ZIP modified symbiont that works like LATSYM LIST_VECTORS.ZIP list system service vectors LOGINOUT_CALLOUTS.ZIP usage of LOGINOUT callouts MAILUAF.ZIP utility to manage VMSMAIL_PROFILE.DATA MC.ZIP multi-column filter MODEM.ZIP how to setup modems on VMS NETLIB_DOC.ZIP NETLIB documentation NOTLIB_COPY.ZIP LIB$COPY implementation ODS2_READER.ZIP read ODS2-disk OPCOM.ZIP enabling OPCOM from a program PHONE.ZIP small tricks with PHONE PURGE.ZIP purge from program READDIR.ZIP opendir/readdir/closedir functions READDIR2.ZIP variant READDIR3.ZIP variant REBLOCK.ZIP set correct file-attributes on BACKUP saveset RTLHLP.ZIP help on RTL routines not in online help SET_PASSWORD.ZIP SET PASSWORD command SHOW_DISPLAY.ZIP get SHOW DISPLAY information from program SHOW_MEMORY.ZIP get SHOW MEMORY information from program SIXJET.ZIP sixel to HP laserjet bitmap conversion SMG_MENU.ZIP use SMG$CREATE_MENU SPRINFOR.ZIP gradual clock adjustment for VAX STRIPCC.ZIP strip terminal control characters SYS$CLI.ZIP examples of usage of SYS$CLI TOGGLE_DEBUG.ZIP toggle debug bit on and off UCX_IDENTD.ZIP IDENT server for UCX UNREADABLE_C.ZIP example of totally unreadable C USERS.ZIP how to treat users V2U_MAIL.ZIP convert VMS mail to UNIX mail VACATION.ZIP mail vacation program VAR_HUMOR.ZIP various humor VARIOUS_MACRO.ZIP various MACRO-32 code Page 20 VARIOUS_RMS.ZIP various code using RMS VAXCRTL-BUGS.ZIP VAXCRTL bug-list VMS 5.4-6.0 VMSFILES.ZIP description of VMS file formats VMSHIERARCHY.ZIP hierarchy of VMS users FORTRAN stuff ------------- Are placed in directory [.FTN] as zipped files. [.FTN]LZW.ZIP Description : implementation of LZW-algorithm in FORTRAN Source : FORTRAN and MACRO Binary : not available Notes : "almost standard" FORTRAN + some specific support routines Posted : not [.FTN]SFLZW.ZIP Description : port of package above to SALFORD FORTRAN on DOS made by Robert Hoschek Source : FORTRAN Binary : not available Notes : ported by Robert Hoschek Posted : not [.FTN]QS.ZIP Description : implementation of Quick-Sort in FORTRAN Source : FORTRAN Binary : not available Notes : "almost standard" FORTRAN Posted : comp.lang.fortran december 1994 [.FTN]NORMAL.ZIP Description : density, accumulated and inverse accumulated function for the normal distribution Source : FORTRAN Binary : not available Notes : standard FORTRAN Posted : comp.lang.fortran november 1994 C++ stuff --------- Are placed in directory [.CPLUSPLUS] as zipped files. [.PLUSPLUS]ECON.ZIP Description : classes for econometrical analysis with matrices and time-series + test-programs Source : C++ and FORTRAN Binary : not available Page 21 Notes : tested with GXX and CXX Posted : not CGI stuff --------- Are placed in directory [.CGI] as plain text files or zipped files. All scripts are for the OSU HTTP-server on VMS. [.CGI]SAS.ZIP Description : gateway script for browsing a SAS V5 database Source : C Binary : not available Notes : none Posted : not [.CGI]DBF.ZIP Description : gateway script for browsing a DBASE IV database Source : C Binary : not available Notes : none Posted : not [.CGI]QA.ZIP Description : script with simple question and answer test Source : C Binary : not available Notes : none Posted : not [.CGI]WKS.ZIP Description : gateway script for browsing a WKS or WK1 spreadsheet file Source : C Binary : not available Notes : none Posted : not [.CGI]SURVEY.ZIP Description : script with generic survey Source : C Binary : not available Notes : none Posted : not [.CGI]RANURL.ZIP Description : script for generic redirecting to random URL Source : C Binary : not available Page 22 Notes : none Posted : not [.CGI]GAB.ZIP Description : script for General Archive Browsing Source : C Binary : not available Notes : none Posted : not [.CGI]SHOWTIME.ZIP Description : script to display the time with small GIF-files Source : DCL Binary : not available Notes : none Posted : not [.CGI]DCLEX.ZIP Description : 7 very small demo-scripts Source : DCL Binary : not available Notes : none Posted : not [.CGI]DCLEX2.ZIP Description : 5 more small demo-scripts Source : DCL Binary : not available Notes : none Posted : not [.CGI]SHOWUSER.C Description : script for displaying the number if interactive and batch-jobs runnning on the server Source : C Binary : not available Notes : none Posted : VMS-WEB-DAEMON april 1995 [.CGI]BROWSER2.COM Description : script for redirecting to different HTML-files depending on browser type Source : DCL Binary : not available Notes : none Posted : VMS-WEB-DAEMON september 1995 [.CGI]NEW.COM Page 23 Description : script for displaying new documents Source : DCL Binary : not available Notes : none Posted : VMS-WEB-DAEMON october 1995 [.CGI]MGMT.ZIP Description : script for doing VMS system management via a WWW-browser Source : DCL Binary : not available Notes : none Posted : not [.CGI]FIG.ZIP Description : script for generating small figures as GIF-files on the fly Source : DCL and C Binary : not available Notes : none Posted : not [.CGI]URLSCAN.ZIP Description : utility-program (not a script) to check all HREF's in one or more HTML-files Source : C Binary : not available Notes : none Posted : VMS-WEB-DAEMON may 1995 [.CGI]HTMAIL.ZIP Description : utility-program (not a script) to convert mail to HTML and index it Source : DCL and PASCAL Binary : not available Notes : none Posted : not [.CGI]POSTACTION.C Description : utility-program (not a script) to make a POST request to a HTTP-server (intended for use by CGI scripts) Source : C Binary : OBJ's and EXE's in POSTACTION_BIN_VAX.ZIP (compiled with DEC C 5.0 on VAX and linked on VMS VAX 6.1 with UCX 3.3) OBJ's and EXE's in POSTACTION_BIN_AXP.ZIP (compiled with DEC C 5.0 on AXP and linked on VMS AXP 6.1 with UCX 3.3) Notes : none Posted : not [.CGI]INTCTYPE.ZIP Description : kit to make various Internet software treat 8 bit national Page 24 characters in the IsoLatin1 character-set proper regarding is/to upper/lower Source : C Binary : not available Notes : none Posted : not Fote Mirror ----------- Are placed in directory [.FOTE_MIRROR] as zipped files. This is a mirror of the Gopher client and Lynx WWW-browser available from Foteos Macrides's Gopher-server GOPHER.WFBR.EDU ! Important note: those kits is updated frequently ! [.FOTE_MIRROR]GOPHER2_1_3-CLIENT.ZIP Gopher client version 2.1.3 with latest modification by Foteos Macrides. [.FOTE_MIRROR]LYNX2-6.ZIP Lynx WWW-browser version 2.6. [.FOTE_MIRROR]LYNX2-6FM.ZIP Lynx WWW-browser version 2.6 with latest modification by Foteos Macrides. [.FOTE_MIRROR]WWWVMSINDEX.ZIP BUILD_INDEX program with search engines for HTTP-server with latest modifications by Foteos Macrides. [.FOTE_MIRROR]WWWVMSHELPGATE.ZIP VMS help gateway for HTTP-server with latest modifications by Foteos Macrides. [.FOTE_MIRROR]WWWVMSWHOISGATE.ZIP VMS whois gateway for HTTP-server with latest modifications by Foteos Macrides. [.FOTE_MIRROR]WWWVMSFINGERGATE.ZIP VMS finger gateway for HTTP-server with latest modifications by Foteos Macrides. [.FOTE_MIRROR]QUERYDT.ZIP VMS script for HTTP-server to generate report for POST FORM with latest modifications by Foteos Macrides. Page 25 [.FOTE_MIRROR]CGI-MAILTO.ZIP VMS script for HTTP-server to send mail from FORM's with latest modifications by Foteos Macrides. [.FOTE_MIRROR]WWWVMSPHGATE.ZIP VMS PH gateway for HTTP-server with latest modifications by Foteos Macrides. Jones Mirror ------------ Are placed in directory [.JONES_MIRROR] as zipped files. This is a mirror of the HTTP server available from David Jones's WWW server (URL http://www.eng.ohio-state.edu/soft/) ! Important note: this kit is updated frequently ! [.JONES_MIRROR]HTTP_SERVER_1-9C.ZIP DECthreads HTTP-server version 1.9C by David Jones. [.JONES_MIRROR]HTTP_SERVER_2-0.ZIP DECthreads HTTP-server version 2.0 by David Jones. [.JONES_MIRROR]HTTP_SERVER_2-0A.ZIP DECthreads HTTP-server version 2.0A by David Jones. [.JONES_MIRROR]HTTP_SERVER_2-1.ZIP DECthreads HTTP-server version 2.1 by David Jones. [.JONES_MIRROR]HTTP_SERVER_2-1A.ZIP DECthreads HTTP-server version 2.1A by David Jones. Cook Mirror ----------- Are placed in directories [.COOK_MIRROR] and [.COOK_MIRROR.TEST] as zipped files and individual files. This is a mirror of VMS MOSAIC available from George Cooks FTP server (URL ftp://wvnvms.wvnet.edu/mosaic/) ! Important note: The version in this directory is a relative stable "production"version. The version in the TEST sub-directory is a "test" version, which may have bugs and is updated frequently ! Page 26 [.COOK_MIRROR]*.* VMS Mosaic version 2.7 ported by George Cook. [.COOK_MIRROR.TEST]*.* Next version of VMS Mosaic. IFDL ---- [.IFDL]SDLIFDL.VMS_SHARE Kit in VMS_SHARE format. [.IFDL]*.* (excluding SDLIFDL.VMS_SHARE) Unpacked kit. IFDL backend for SDL. Written by Chris Sharman. ========> [VMSLT96B.GCE96B]AAAREADME.TXT;2 <======== Things from Glenn C. Everhart Fall 1996 ACORN_PHONE_NUMBER.TXT Correct phone number for Acorn Software. If you like FAVOID here, have a look at their site www.acornsw.com (and at safetyspd.txt) ASNDF.CLD;1 Latest virtual disk assign programs ASNDF.MAR;2 for DF: and VD: named virtual disks ASNDF_S264.MAR;2 (Ones with _s264 are designed for Alpha VMS V7.x) ASNVD_64.MAR;8 (Ditto _64 in this dir) ASNVD_CLD_64.CLD;1 ASNVD_S264.MAR;1 CMPHIGHC.ZIP;1 Compressing virtual disk, Vax or Alpha, with sources and docs. Also can present back/phys tapes as r/o disks. Works on any recent VMS. DFDRIVER_FAST.MAR;7 Test virtual disks, various source variations DFDRIVER_IOB.MAR;17 ditto DFDRIVER_S264.MAR;30 ditto DFDRIVER_VAX_SHADOK.MAR;1 ditto FAVOID.ZIP;3 Fragmentation avoider. PRevents much fragmentation. Build from source if you can...it's all included...and start it on disks that aren't active. JFCTLV2.MAR;1 Modified part of FAVOID that can be started on active disks. JFDRIVERV2.MAR;3 Modified part of FAVOID that can be started on active disks. JUKEBOX_CONTROL_SW_FOR_WNT.TXT;1 Note about jukeboxes on NT LOGGINGVD.ZIP;1 A virtual disk that logs all writes to a journal (so that it in effect is continuously backed up). Docs enclosed. SAFETYSPD.PS;2 SPD for my Safety product which does undelete (by changing VMS delete to use a wastebasket protocol), vastly expands system security and adds realtime prevention, filehiding, file passwords, privilege control, active Trojan horse prevention, etc., and also has some space management aids. SAFETYSPD.TXT;2 Ditto, Postscript. VDD64.ZIP;14 Virtual disk driver that works OK with DEC volume shadowing. Can be used to shadow unlike devices or parts of disks. Full sources supplied. VDDRIVER_64.MAR;44 Slightly updated (& probably faster) driver for vdd64 above. Glenn C. Everhart OVMS SIG Librarian & Tapecopy Coordinator Everhart@GCE.Com Total of 22 files. ========> [VMSLT96B.GNUSOFTWARE]AAAREADME.TXT;2 <======== GNU Software This area contains software obtained from the Free Software Foundation since the Spring 1996 sigtapes. The directory is: AAAREADME.TXT;1 ABOUT-NLS.TXT;1 AUTOCONF-2_12.TAR-GZ;1 BASH-2_0.TAR-GZ;1 BASH-DOC-2_0.TAR-GZ;1 BINUTILS-2_7.TAR-GZ;1 BUY-GNU-MANUALS-FROM-FSF.TXT;1 CALC-2_02F.TAR-GZ;1 CCCP.DIFFS;1 CFENGINE-1_3_15.TAR-GZ;2 CFENGINE-1_3_16.TAR-GZ;1 CVS-1_9.TAR-GZ;1 DESCRIPTIONS.TXT;1 ELISP-MANUAL-19-2_4_2.TAR-GZ;1 EMACS-19_34B.TAR-GZ;1 F2C.README;1 FILEUTILS-3_15.TAR-GZ;1 FLEX-2_5_4.TAR-GZ;1 G77-0_5_19.TAR-GZ;1 GAWD-3_01-DOC.TAR-GZ;1 GAWK-3_0_2.TAR-GZ;1 GCC-2_7_2_1.TAR-GZ;1 GFORTH-0_2_1.TAR-GZ;1 GHOSTSCRIPT-4_03.TAR-GZ;1 GHOSTSCRIPT403-GNU.TAR-GZ;2 GHOSTSCRIPTFONTS40STD.TAR-GZ;1 GIT-4_3_15.TAR-GZ;1 GNU-PASCAL.ANN;1 GNU-READMES.ZIP;1 GNUSSL_0_2_1.TAR-GZ;1 GPC-2_0.ZIP;1 GREP-2_0.TAR-GZ;1 GST115.TGZ;1 GUILE-1_0.TAR-GZ;1 GUILE.ANN;1 HURD-0-1.TAR-GZ;1 HYPERBOLE-4_01.TAR-GZ;1 ID-UTILS-3_2.TAR-GZ;1 JARG400.TXT-GZ;1 LYNX.README;1 MESA-2_1.TAR-GZ;1 METAHTML-5_01.TAR-GZ;1 METAHTMP.ANN;1 MTOOLS-3_0.TAR-GZ;1 OCTAVE-2_0_1.TAR-GZ;1 PERL-5_003.TAR-GZ;1 PIPS-1_01.TAR-GZ;1 PREP_PUB_GNU.TAR;1 PROGRAMINDEX.TXT;1 REMIND.GET;1 RX-1_3.TAR-GZ;1 RX-1_5.TAR-GZ;1 SCREEN-3_7_2.TAR-GZ;1 SH-UTILS-1_15.TAR-GZ;1 SMALLTALK-1_1_5.TAR-GZ;1 STOW-1_3_2.TAR-GZ;1 TAR-1_11_8.TAR-GZ;1 TEXINFO-3_9.TAR-GZ;1 TEXTUTILS-1_21.TAR-GZ;1 UCBLOGO-3_4.TAR-GZ;1 UNITS-1_53.TAR-GZ;1 WGET-1_4_2.TAR-GZ;1 WHAT_IS_CVS.TXT;1 ========> [VMSLT96B.GNUVMS]AAAREADME.TXT;2 <======== VMS GNU Things This area contains utilities advertised to be VMS ports of various Gnu utilities. They include CVS and RCA (a source management set of utilities along the lines of CMS, SCCS, etc.), GS (Ghostscript, a Postscript interpreter), make (something like unix make or DEC MMS), touch, Gnu Emacs (you need to build it; at the time of receipt there were still some TPU bugs that kept it from building; Release V7.1 fixed them.) and a bit more. 00_GNU_VMS_FTP_SITES.;1 00_HOW_TO.;1 00_HOW_TO.TXT;1 00_MAILINGLISTS.;1 00_UPDATES.;1 AAAREADME.TXT;1 BISON-1_22-19960713.ZIP;1 CVS-1_8_86.TAR-GZ;1 CVS-960925.TAR-GZ;1 CVS-VMS.ANN;1 CVS.README;1 CVSVMS.README;1 EMACS-19_28-19960529.TAR-GZ;1 EMACS-19_28.README;1 FIND-ERROR.EL;1 GS-VMS.README;1 GS-VMS.TAR-GZ;1 GS_312_EXE_AXP.ZIP;1 GS_312_EXE_VAX.ZIP;1 GS_351_AXP_EXE.ZIP;1 GS_351_VAXC_EXE.ZIP;1 GS_351_VAX_DECC_EXE.ZIP;1 GZIP-1_2_4-19960226.TAR-GZ;1 IP-VS-DECNET.TXT;1 MAKE-3_74-19951218.TAR-GZ;1 MAKE-3_74.README;1 MAKE_EXES.ZIP;1 OTHER_EXES.ZIP;1 RCS-5-6.TAR-GZ;1 TOUCH.AXP_EXE;1 TOUCH.TAR-GZ;1 TOUCH.VAX_EXE;1 VMSLIB.ZIP;1 VMSTAR.README;1 VMSTARU4033.ZIP;1 ========> [VMSLT96B.JED]AAAREADME.TXT;1 <======== This area contains: JED - text editor with EDT keypad abilities. runs on VMS, MSDOS, Unix, more. SLRN - News reader utility for various OSs SLSC - Spreadsheet utility for various OSs MOST - fullscreen file viewer. Has searches, binary/ascii mode, can do several files, many more options, faster, and cannot accidentally damage a file like an editor. From John Davis' area at space.mit.edu ========> [VMSLT96B.MATHOG]AAAREADME.TXT;1 <======== David Mathog's ftp site material. Most of the material described here is present. Questions about this FTP site should be directed to system@ftp.bio.caltech.edu. Anonymous uploads ("put") to this site are blocked. Directory contents as of 18-APR-1995: GIBBS.ZIP VMS port of the NCBI's Gibb's software. Contains .exe for VMS/AXP 6.1 + DECC 4.1, also source code, demo, build instructions, and porting notes. Use BINARY FTP to transfer. ICALCV.ZIP Slightly modified version of the ICALC program. On VMS systems it will put the results of up to 10 calculations, specified on the command line, into a symbol ICALC_OUT (comma separated, if more than one result). For the interactive mode, it will only put the LAST result into that symbol. MMAIL.COM Demo procedure demonstrating how to send MIME mail messages (as generated by mpack) via MULTINET. Use ASCII FTP to transfer. OPENVMS.DIR Directory containing a bunch of OpenVMS utilities in DCL. PESTFIND.ZIP ANSI C port of M. Rechsteiner's PESTFIND program. Test files. DCL procedures to wrap it for use with GCG package. PSCAL.ZIP VMS port of PCAL program - prints nice monthly calendars in POSTSCRIPT. PKZ204G.EXE MSDOS zip program, from Oak.Oakland.edu Simtel mirror site. Use BINARY FTP to transfer. RFINDPATTERNS.FOR,.TXT,.CMD Findpatterns variant - it extracts the pieces it finds into separate files. Only sites with valid GCG licenses should retrieve this program! Use ASCII FTP to transer. RTFTOHTML.ZIP VMS port of Chris Hector's RTFtoHTML software. Contains .exe for VMS/AXP 6.1 + DECC 4.1, also source code, docs, and build instructions. Use BINARY FTP to transfer. XBIN.ZIP Port to OpenVMS of a Unix (de)binhex program. Useful for extracting RTF files and others that don't have anything Page 2 important in the resource fork. Use BINARY FTP to transfer. Assorted OpenVMS utility procedures. Routines for moving around easily. These ALL keep track of the last directory visited, storing it in the logical LASTDIR. CD.COM "cd subdir" (=set def [.subdir]) DOWN.COM "down" (pick from list of subdirectories) HOME.COM "home" (return to sys$login) LAST_DIR.COM "last" (return to last directory) SET_DEF_DIR.COM "setdef disk:[dir]" (like set def) TO_DIR.COM "to dir" (like set def, but no [] needed) UP.COM "up 3" (like set def [-.-.-]) of last Miscellaneous routines CHANGEALL.COM Makes global substitutions across text files (has serious limitations - it cannot deal with "/" in substitutions!) DEFINE_UNIX.COM Put posix commands into DCL symbols FAKE_UNIX.COM Define a large subset of Unix commands, requires POSIX FIELDEXTRACTOR.COM Extract line/position/width fields and write to a file FIX_UNIXNAME.COM Fixes horrific Unix names, can also do very complex name substitutions and rearrangements. FULL_FAKE_UNIX.COM Like FAKE_UNIX, but defines more commands PAGEIT.COM Breaks a text file into fixed length pages and puts a header line on top. ========> [VMSLT96B.MOELLER]AAAREADME.TXT;1 <======== This area contains W. Moeller's remote tape on unix utility for VMS; use to make unix tapes look local at vms sites. ========> [VMSLT96B.MOREAU]AAAREADME.TXT;1 <======== o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o ada.cenaath.cena.dgac.fr VAX 6210 ------------------------------------------------------------------------------- ALTRIS-120.ZIP 4 tetris-like games (altetris, hextris, tertris & welltris) based on A. Alex Zaho's Generic Tetris 3.1.2 Author: bagleyd@perry.njit.edu VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- FLY8_111.ZIP Fly8 version 1.11 flight simulator Author: Eyal Lebedinsky (eyal@ise.canberra.edu.au) VAX AXP Language : DEC C (VAX & AXP) ------------------------------------------------------------------------------- GHOSTVIEW-VMS-276.ZIP Ghostview-VMS 2.7.6 + XMU + XAW3D Author: Johannes Plass VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- IMAGEMAGICK-377.ZIP Complete set of display, montage, tranform image utilities under X window - V 3.7.7 (Nov 1996) Author: John Cristy VAX Language: DEC C (C ANSI compiler required) AXP Language: DEC C ------------------------------------------------------------------------------- MOONCLOCK.ZIP Display time of day and moon phase Author: Keith Packard, MIT X Consortium moonclock extensions by Gunter Sprenger gunter@cs.tu-berlin.de VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- MOSAIC_275.ZIP NCSA Mosaic 2.7-5 Author: NCSA VMS mods by Bjorn Nilsson's and George Cook VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- MPEG_ENCODE_122.ZIP Mpeg encoder/decoder V 1.2.2 Author: Andy C. Hung VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- MXRN-DXRN-618-32.ZIP Motif or DECW news reader version 6.18-32 Authors: Ellen M. Sentovich and Rick L. Spickelmier VAX AXP Language: VAX C (VAX), DEC C (AXP) Requires: DECwindows (DXRN) DECW/MOTIF 1.0, 1.1 or 1.2 (MXRN) ------------------------------------------------------------------------------- ORLY_WORLD_31.ZIP Orly Airport world V 3.1 for Flight simulator with Paris, Orly, Melun, Le Bourget, Cerny, Roissy CDG and la Seine from Melun to Page 2 Conflans, Bretigny/Orge, Toussus-le-Noble and Velizy-Villacoublay, Toulouse Blagnac, la Garonne, Clermont-Ferrand-Aulnat, la chaine des Puys, Biarritz, Hendaye, St Jean-de-Luz harbour. Author: Patrick Moreau pmoreau@cena.dgac.fr moreau_p@decus.fr VAX Flight v 3.x AXP Flight v 3.x ------------------------------------------------------------------------------- PUZZLES.ZIP Collection of sliding blocks and rotational puzzles for X Window Author: David Albert Bagley, (bagleyd@source.asset.com) VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- SUB_HANGAR_10.ZIP Hangar with balloons, pilot and supercopter for Flight V 3 Author: Patrick Moreau (pmoreau@cena.dgac.fr) VAX AXP ------------------------------------------------------------------------------- VGP11.ZIP Vector Globe Projection V 1.1 Author: Rick Niles niles@axp745.gsfc.nasa.gov VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- X11R4_DECUS_LIB_AXP.ZIP X11R4 DECUS distribution (XAW & XMU headers and OLBs, XVMSUTILS sources, headers and OLBs) Author: MIT Patrick L. Mahan, TGV Inc AXP Language: DEC C ------------------------------------------------------------------------------- X11R4_DECUS_LIB_VAX.ZIP X11R4 DECUS distribution (XAW, XMU, XVMAUTILS sources, headers and OLBs) Author: MIT Patrick L. Mahan, TGV Inc VAX Language: VAX C ------------------------------------------------------------------------------- XBOING-24.ZIP XBOING version 2.4 (fine blockout type game) Author: Justin C. Kibell - jck@citri.edu.au VAX Language: GNU C 2.5.8 or DEC C 5.x AXP Language: DEC C 5.x Needs XPM 3.4 library (VAX & AXP.OLBs of XPM 3.4.G provided) ------------------------------------------------------------------------------- XDALICLOCK-208.ZIP Melting digital clock version 2.08 Author: Jamie Zawinski VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- XGAS.ZIP Animated simulation of an ideal gas Page 3 Author: Larry Medwin (MIT) VAX Language: VAX C or DEC C AXP Language: DEC C Needs DECUS X11R4 XAW & XMU libraries ------------------------------------------------------------------------------- XHTML-13_1.ZIP Html editor V 1.3-1 Author: John R. Punin VAX Language: DEC C, Motif AXP Language: DEC C, Motif ------------------------------------------------------------------------------- XLOCKMORE-313.ZIP Locks the local X display till a password is entered (with many graphic demos) V 3.13 New demos: flag & lissie Authors Patrick J. Naughton (naughton@eng.sun.com) David A. Bagley (bagleyd@hertz.njit.edu) VAX Language: DEC C AXP Language: DEC C ------------------------------------------------------------------------------- XMGR-3_01PL7.ZIP Plotting tool under X Window V 3.01pl7 Author: Paul J Turner (pturner@teleport.com) AXP Language: DEC C ------------------------------------------------------------------------------- XMORPH-02OCT96.ZIP Morphing under X Window Author: Michael J. Gourlay gourlay@ucsu.colorado.edu VAX AXP Language : VAX C or DECC (VAX), DEC C (AXP) ------------------------------------------------------------------------------- XPAINT-247.ZIP Paint program under X WINDOW v 2.4.7 Author: David Koblas, koblas@netcom.com Maintainer: Torsten Martinsen, bullestock@dk-online.dk VAX Language: DEC C AXP Language: DEC C Object libraries (JPEG, XAW3D, TIFF, PNG, ZLIB, XMU & XPM) provided for VAX & AXP ------------------------------------------------------------------------------- XPDF-06.ZIP X window PDF 1.1/1.2 viewer (version 0.6) Author: Derek B. Noonburg VAX Languages: GCC/G++, DEC C / DEC C++ AXP Languages: DEC C/DEC C++ ------------------------------------------------------------------------------- XPILOT-350.ZIP Multiplayer gravity war game client & server Authors: Bjørn Stabell Ken Ronny Schouten Bert Gsbers VAX Language: DEC C (may be GCC, but not tested) AXP Language: DEC C ------------------------------------------------------------------------------- XSTAR-110.ZIP Stars animation under X (simulation of n-body problem) V 2.20 Author: Wayne Schlitt (wayne@midwestcs.com) VAX Language: VAX C or DEC C AXP Language: DEC C ------------------------------------------------------------------------------- ========> [VMSLT96B.NET96B]AAAREADME.TXT;6 <======== Net Miscellany These are things picked up from Internet areas or newsgroups from all over (comp.os.vms heavily included) Titles are as descriptive as possible. Programs generally are of type .SRC and text files of type .TXT and other files names are hopefully descriptive. (.POINTER files are generally where to find out about something, generally on Internet.) Files included are: 40ERRS.HTML 40ERRS.TXT AAAREADME.TXT ACCOUNT.MAR ACTIVEX-SECURITY-IS-VS-VIRII-ONLY.TXT ALPHASERV1000_GRAPHICS.WORKAROUND ANDREW-V7.ANN ANON-POST.SRC ANOTHER-JAVA-SEC-HOLE.TXT ANOTHER_JAVA_VULNERABILITY.TXT ANTIZAP2.SRC ASN1PARSE.JAVA AST-IN-OTHER-PROCESS-ALPHA.ZIP BACKUP_VOLSET.HOWTO BEEP-IN-DECW.SRC BINHEX-VMS-FIXES.TXT BITPAD-FIRMWARE-DISCUSS.TXT BLISS11SRC.TAR-GZ BRIDGE-ASYNCH.HOWTO BUG-FREQS.TXT BXFORM-081.ZIP BXFORM.README BXFORMS-ALPHA-VMS.ANN C-TO-HTTP.POINTER CALC.ZIP CALCULATOR.ZIP CALLABLE_MAIL_CONTEXT.TXT CDC-TRIVIA-2.TXT CDC-TRIVIA-3.TXT CDC-TRIVIA-4.TXT CDC-TRIVIA-5.TXT CDC-TRIVIA.TXT CHEAP-MEM.WHERE CK-NOTE.TXT CLEAR_DEVICE_ERR_CNT.SRC COMPARE-IN-FTN.SRC COMPILE-FAVOID.HOWTO COMPILING_X_STUFF.HOWTO COMPILING_X_STUFF2.HOWTO COMPTOOL.ZIP CONSOLE.TAR_Z COPYFILE.SRC CPTX.ZIP CRACK-TUTORIALS.POINTER CREATE-PROCESSPRIVATE-SECTION.SRC CRP1201.UUE CRP1203.UUE CRP1204.UUE CRS.ANN CRS.ZIP CRYPTO-COURSES.POINTERS CRYPTOGRAPHY_AND_POLICY. CRYPTOPAPERS_MOSTLYPS.ZIP CSWING-INCLUDE-MODS.TXT C_OPEN_TUNING.HOWTO DCL-TO-FORTRAN-PRODUCT.POINTER DCL_DEBUGGING-TIP.TXT DCL_QUOTING_EXPLAINED.TXT DCL_SUBSTRING_ADRESSING.TXT DCL_TIP_RE_SYMS.TXT DEBUG-IN-ONE-PROC.HOW DEC-INTERNAL-BROWSE-HELPSITE.TXT DECODE_JAVA_CLASSES.POINTER DECTERM-REMOTE-START.COM DECTERM_MOTIF_HINTS.TXT DECTHREADS-EXAMPLE.SRC DECW-TIMEOUT-RESET.HOW DECW_CHAR_HOWTOFIND_IN_PROG.SRC DECW_CONSOLE_IN_WINDOW.HOWTO DECW_MENU_FONT_SIZE_SETUP.TXT DECW_MWM_PLACEMENT.TXT DEFINE-LOGICAL-FROM-C.SRC DIAGRAMC.SRC DIAGRAMF.SRC DIAGRAMI.SRC DIALBACKPROG.SRC DIFF-DIR.COM DIFF-TWO-DIRECTORIES.SRC DISKINFO.SRC DNEWS.ZIP DOING-LIMITED-STUFF-WITH-PRIVS.TXT DOUBLE-QUOTED-ADDRESSES-IN-MAIL.HOWTO DO_SOMETHING_AT_DATE.SRC DSSI-ALLOCLASS-SETUP.TXT DST-READ.ANN DUMP_RECALL_BUFFER.SRC ECL-ELAPSEDTIME.SRC EDITSYMBOL.SRC ED_LINES.SRC ED_SYMBOL.SRC ELABORATE-SCREEN-CLR.SRC ELM.POINTER ESILUG-CONTACTS.TXT EXPTAB.SRC EXTENSIONS.JAVA F97-DECUS-VMS-QNA.TXT FAST-C-IO.POINTER FETCH-HTTP.POINTER FETCH-POP-MESSAGES.SRC FILENAME-FROM-ID1.SRC FILENAME-FROM-ID2.SRC FILES_FTP2_KCL_AC_UK.TXT FILE_COMPRESSORS_COMPARED.TXT FIND_DISCONNECTED_PROCESSES.TXT FIND_MESSAGE_DEF.SRC FIND_PERSONAL_INFO_ON_ANYONE.HOWTO FIX_MESSAGE_HELP.HOWTO FLAME_REPLY_FORM.TXT FLIP_PROCESS_NODELETE_BIT.SRC FORTRAN_NAMING.TXT FORWARD_MESSAGE.B32 FREE-CONSOLE.POINTER GET-VERS.COM GETDVI-EXAMPLE.SRC GETDVI-EXAMPLE2.SRC GETTING-DEC-MANUALS.TXT GET_CMD_FILE_NAME.SRC GET_DAD_SERVICE_INFO.TXT GET_DAD_SERVICE_INFO_ALPHA.TXT GET_ELAPSED_TIME_IN_DCL.SRC GET_EXPIRY_DATE.SRC GET_LOCATION_TO_SYM.SRC GET_LOC_OF_TERM_TO_SYM.SRC GET_RID_OF_DECW_LOGICALS.HOWTO GIFMERGE.ANN GIFMERGE.ZIP GIFMRGE.HTML GOODSITE-NETSECURITYSTUFF.TXT GOPHER_EGREP_FIXES.TXT GRAYSOFT.LOOK GSPLIT.ZIP HBCAL.TAR_Z Page 2 HOW_TO_ORDER_PSECTS.TXT HP-PRINTER-AVOID-BLKPGS.HOWTO HPDAT-CONFIG.TXT HPFS_ON_NT.HOWTO ICE.ZIP IMAGEMAGICK-374.ZIP IMAP.ANN IMPERSONATE-USER.SRC INFO-SEC-TREE.TXT IO_DELETE_C_EXAMPLE.SRC IP-SPOOF-EXPLAINED.TXT IP-SPOOFING-EXPLAINED.TXT IP-VS-DECNET.TXT IP_SPOOF_EXPLAINED.TXT IRC2.ZIP ISP-KILL.SRC JAVA-SEC-HOLES.TXT JAVA-SECURITY-SITE-REF.TXT JAVA-SECURITY-STUDY.POINTER JAVA_EMAIL_FROM_APPLET.HOWTO JAVA_SECURITY_PROB2.TXT JAVA_SECURITY_SITES.TXT JAVA_SEC_HOLE_ANOTHER.TXT JAZ-DRIVE-SETUP.TXT JDK-BETA-LOC.POINTER JETDIRECT.TCPUSE-HOW LAT-PROTOCOL-INFO.REF LATSETUP-CORRECTION.TXT LAT_KERMIT_TIP.TXT LAT_TERM_USE.POINTER LD060-VIRT-DSK-KIT.ZIP LINEAR-SOLUTIONS-DOC.UUE LINK-COBOL.TIP LITECLUE.ZIP LOCKS-USAGE.TXT LOCK_MEMORY_IN_C_EXAMPLE.SRC LOGICAL-DEFINED-FROM-C.SRC LOTS-OF-MS-SECURITY-PROBS.TXT LOTS_OF_SECURITY-HOLES.TXT MAIL-LISTS.TXT MAIL-MOVER-TO-PINE.SRC MAIL-MULTIFILE-USE.TXT MAKE-MAIL-NEW.SRC MAP_FILE_TO_SECTION.SRC MENU-MASTER.SPD MENU.ZIP MICROSOFT-FORTRAN-LOW-QUALITY.TXT MIXED_CLUSTER_SETUP_LOGICALS.TXT MMG_SECT_FILLIN_DCL_TRICK.SRC MOCHA.POINTER MODE.C MORE-ON-ACTIVEX-INSECURITY.TXT MOSAIC2_7-5B3.ZIP MOTIF-SETTINGS.TXT MS-INTERNET-EXPLORER-BACKDOOR.TXT MULTIFILE_TAIL_PROG.PERL MULTITHREADING-HOWTO-IO.SRC MVAX_JUMPERS.TXT MVAX_JUMPERS.TXT2 NAME-ROUTER041.ZIP NET-JARGON.TXT NETBSD_FOR_VAX.POINTER NETCERTIFYORSIGNAPPS.ZIP NETSCAPECERTREQUEST.JAVA NETSCAPE_LOC.TXT NETSCAPE_RESOURCE_CONFIGS.SRC NETSCAPE_SECURITY_BREAKING.TXT NET_ACPCONTROL_EXAMPLE.SRC NET_THREAD_LIBRARY.POINTER NEW-NNTP.ANN NEW_ATTACK_ON_DES.SRC NFS_SRC.ZIP NODELETE_UNSET.TXT NT-WS-IS-NT-SERVER.TXT NTPDATE-CMU.ZIP NT_ALLOWS_CROSSPROC_MEM.USE NT_NETBIOS_DEFENSES.TXT NT_REGISTRY_EDIT_FROM_MSDOS.TXT NT_SECURITY.FAQ NT_V4_WARNING.TXT NT_WORKSTATION_SAMEAS_NT_SERVER.TXT OLD_MAIL_BEHAVIOR_GET.TXT OPCOM-TO-SYSLOG.1-OF-1 OS2-DRIVER-EXAMPLE.POINTER OTHER_MS_SEC_HOLES.TXT PATCH-DIFF.1-OF-7 PATCH-DIFF.2-OF-7 PATCH-DIFF.3-OF-7 PATCH-DIFF.4-OF-7 PATCH-DIFF.5-OF-7 PATCH-DIFF.6-OF-7 PATCH-DIFF.7-OF-7 PC-64BIT-ADDR-MAC.SRC PC-ADDR-M64-MACRO.SRC PCL_PRINT_VIA_MULTINET.TIP PDP-EMULATORS.TXT PERFORMANCE_HACKS2_WITH_RMS.TXT PERFORMANCE_HACKS_WITH_RMS.TXT PERSONA-IMPERSONATE.SRC PINE-POINTER.TXT PINE.GET PINEBETA9.GET PORTING-ADVICE.TXT PORTING-FORTRAN-VAX-ALPHA.TIPS POTENTIAL_GOPHER_MOD.TXT PPP-ANN.TXT PPP-GATE-AND-CMU.ANN PPP02.ZIP PPP02ETH.ZIP PRCNAME-HACK.SRC PRINT_TO_HP_PS_PRINTER.HOW PRIVS-AND-MAIL.TXT PROMPT_COLOR_SET.SRC PROTECTED_SUBSYSTEM.HOW PSEUDO_PHF_DEFENDER.SRC PUTR.GET QMAN-SIZE-SHRINK.HOWTO R2HALPHAVMS.Z R2HVAXVMS.Z R2HWIN.ZIP RAXTOOLB.ZIP RD53-JUMPERS.TXT READ-POLICE-DATA.SRCETC READ-RMS-FROM-MS.TXT RECOVERING_VOLSET_MEMBER.HOWTO REED-SOLOMON.SRC REMIND-3_0_15.TAR_Z REMIND-3_0_15.TGZ REMIND-README.1ST REMIND.GET REMOTE-CONTROL-NETSCAPE.SRC REMOTE-CTL-NETSCAPE.SRC REMOTE-SHADOW-CAUTION.TXT REMOTE_FTP_RELAY_VIA_GOPHER.TXT REMPRTSYMB.GET REMTAPTCPIP.ZIP;3 REVERSE_ENGINEER_SKIPJACK.TXT RJ45-CONN-MODEM-CTL.TXT RMS_ACCESS_FROM_PC.WHERE ROOT_VIRUS_INFECTS_SOLARIS.TXT RS423-CABLING.TXT RTF-1.TAZ RTF-SPEC-1.ZIP RTF2LATEX.READ RTFTOHTML.TXT RUN-NETSCAPE-REMOTELY.SRC RWAST_STATES_EXPLAINED.TXT SAMBA-NOTE.TXT SAMBA-POINTER-ANOTHER.TXT SAMBA-VMS.ANN SCO_UNIX_GIANT_SEC_HOLE_CHGRP_PRIV.SRC SCSI-FORMAT.C SCSI_FORMAT.C SEARCHPATHEXAMPLE.TXT SEC-TEMPLATES.TXT SECRETSERVICEINFO.ZIP SECURE_SOCKETS.TXT SECURE_UNIX_SERVER_SECURITY_HOLE.TXT SECURITY-DIGEST.TXT SECURITY-PATCHES.FAQ SECURITY-VENDOR-CONTACTS.FAQ SED-GREP-ETC.GET SENDOPR-EXAMPLE.SRC SEND_MIME_MAIL.SRC SEND_MSG_TO_USER.SRC SERT_VOLUME_OWNER.SRC SET-UP-LONG-DCL-SYM.HOW SETHOST-OLD.TXT Page 3 SETUSERNAME.SRC SHA1.TXT SHADOW-WARNING.TXT SHAR-IMG-BLD.SRC SHAREABLE-IMG-COOKBOOK.POINTER SHARED-GBL-SECT.HOWTOUSE SHARED-GBL-SECT.HOWTOUSE2 SHOW_CALLER_IN_DCL.SRC SHOW_OPEN_FILES_IN_DCL.SRC SHRINK_QMGR_JOURNAL.HOWTO SIGPRC-DOC.TXT SIGPRC_INTERPROC_COMM.TXT SKPLST1.SRC SKPLST2.SRC SKPLST3.SRC SNIFFERS.FAQ SNPRINTF.SRC SOX7-SRC.ZIP SPOOFING.TXT SPOOFING2.TXT SRC_FILE_FILTER.SRC SSH_SECURITY_HOLE.TXT SSL.FAQ SUBM-AS-SOMEONE.POINTER SUN-VT-KEYMAP.SRC SYMARK.LOOK S_MAIL.1-OF-5 S_MAIL.2-OF-5 S_MAIL.3-OF-5 S_MAIL.4-OF-5 S_MAIL.5-OF-5 TAIL.C TCPSEQPRED2.C TCSH_SECURITY-HOLE.TXT TELL-MAIL-CNT-IN-FOLDERS.SRC TELNET_QUEUES.TXT TEST_IF_DEVICE_LOADED.SRC TGD.ANN TGD1_2B.ZIP THREAD-SCHED.HOWTO TIME-BOOSTER.SRC TIME_BOOSTER.SRC TK_SECURITY-HOLE.TXT TSHIRT-W-PERL-RSA.TXT TURN_ON_COLOR.HOW UCX-NFS-STARTING.TIPS UCX-PATCH.SRC UCX-PING-SWITCHES.TXT UDPDENIAL.C UFCCPP.TXT UNDO-DVC-INIT.HOWTO2 UNDOC-VMS-STUFF.POINTER UNDOCD-VMS_INFO.ZIP UNIX_SENDMAIL_SECURITY_BREAK_TOOL.SRC UPSIDE-DOWN-VT-HACK.SRC USING-MX-WITH-UCX.HOWTO USING_A_MODEM_ON_VMS.TXT UTIL-TO-STEAL-SOLARIS-PASSWORDS.SRC UUTOOLS.ZIP VAUDENAY-PUB.HTML VAUDENAY-PUB.TXT VDD64.ZIP VIOC-CACHE.TXT VIOC-DEFAULT.TXT VMS-Q-AND-A-FALL96.TXT VMS-XEMACS.POINTER VMS-Y2000-1.TXT VMS-Y2000-2.TXT VMS.FAQ VMS.FAQ1 VMS.FAQ2 VMS.FAQ3 VMS1.FAQ VMS2.FAQ VMS3.FAQ VMSBACKUP.README VMSBACKUP.ZIP VMSTAR_SRC_FIX_NEEDED.TXT VMS_CALENDAR_UTILITY.ZIP VMS_FLOW_CTL_RTS.TXT VMS_GHOSTSCRIPT.POINTER VMS_INTERNAL_HACKS_SRC.ZIP VMS_IO_ADVICE.TXT VS3100-SCSI-JUMPERS.TXT VS3100_TT_SIGNALLING.TXT VT-SCRN-CLR.SRC WALLACH-JAVA-SECURITY.ZIP WARN_OF_ACCT_EXPIRY.SRC WEBBOOK.1-OF-5 WEBBOOK.2-OF-5 WEBBOOK.3-OF-5 WEBBOOK.4-OF-5 WEBBOOK.5-OF-5 WEBSITES.TXT WHY-CRYPTO-IS-HARDER.THAN-IT-LOOKS WHY_GOVT_RSTR.TXT WIN-SEC.STUFF WINDOWS_NT_SEC_PROBS.TXT WNT-SECURITY-ETC.TXT WNT-SECURITY.FAQ WNT_SECURITY.FAQ WSA_DEVICE_QIO_FORMAT.TXT WWW_SERVER_STUFF.TAR_Z X-HELP-BUBBLE.ANN X509CERTIFICATE.JAVA X509CERTREQUEST.JAVA XBIN.01-OF-31 XBIN.02-OF-31 XBIN.03-OF-31 XBIN.04-OF-31 XBIN.05-OF-31 XBIN.06-OF-31 XBIN.07-OF-31 XBIN.08-OF-31 XBIN.09-OF-31 XBIN.10-OF-31 XBIN.11-OF-31 XBIN.12-OF-31 XBIN.13-OF-31 XBIN.14-OF-31 XBIN.15-OF-31 XBIN.16-OF-31 XBIN.17-OF-31 XBIN.18-OF-31 XBIN.19-OF-31 XBIN.20-OF-31 XBIN.21-OF-31 XBIN.22-OF-31 XBIN.23-OF-31 XBIN.24-OF-31 XBIN.25-OF-31 XBIN.26-OF-31 XBIN.27-OF-31 XBIN.28-OF-31 XBIN.29-OF-31 XBIN.30-OF-31 XBIN.31-OF-31 XMCD-2.TGZ XPDF.POINTER XWPICK.ZIP ZIP2FLOP.UUE ZT-UNIX.ZIP ========> [VMSLT96B.NETPBM]AAAREADME.TXT;1 <======== NetPBM, GRAPHICS, Suite of graphic image format manipulation & conversion pgms Enhanced portable bitmap toolkit. The PBMPLUS toolkit allows conversions between image files of different format. By means of using common intermediate formats, only 2 * N conversion filters are required to support N distinct formats, instead of the N**2 which would be required to convert directly between any one format and any other. The package also includes simple tools for manipulating portable bitmaps. The package consists of four upwardly compatible sections: pbm Supports monochrome bitmaps (1 bit per pixel). pgm Supports grayscale images. Reads either PBM or PGM formats and writes PGM format. ppm Supports full-color images. Reads either PBM, PGM, or PPM formats, writes PPM format. pnm Supports content-independent manipulations on any of the three formats listed above, as well as external formats having multiple types. Reads either PBM, PGM, or PPM formats, and generally writes the same type as it read (whenever a PNM tool makes an exception and ``promotes'' a file to a higher format, it informs the user). -------------------------------------------------------------------------------- N E T P B M Netpbm is based on the widely spread Pbmplus package (release: 10 Dec 91). On top of that, a lot of improvements and additions have been made. After the latest release of Pbmplus, a lot of additional filters have been circulating on the net. The aim of Netpbm was, to collect these and to turn them into a package. This work has been performed by a group of program- mers all over the world. If *you* have some code to add, please contact us, and we will incorporate it. There is a mailing list for discussions about Netpbm. You post a message to the list by writing to "netpbm@fysik4.kth.se". If you want to be on the list, send a mail with the message "subscribe netpbm" to "majordomo@fysik4.kth.se". If you want to report a bug, please send your report to netpbm@fysik4.kth.se, and to the author of Pbmplus, jef@netcom.com. Please note, that this is not an official Pbmplus release. The code in this release is merely a collection of code from various sources around the world. Not all of the new code parts follow the high standard of programming of Pbmplus. We have tried to make the code portable to as many systems as possible, but we haven't cleaned up all routines. We hope that this release will help the many users of Pbmplus to upgrade their code all in one piece, instead of having to hunt down different code fragments at different sites around the world. We also hope, that our effort will help the author of Pbmplus, Jef Poskanzer, to make a new official release soon. Page 2 The file Netpbm lists all new featues and functions in netpbm. ========> [VMSLT96B.NETSRC]AAAREADME.TXT;2 <======== This material comes from comp.sources.unix and comp.sources.misc and is various programs in source form. AAAREADME.TXT;1 ADD-NOISE-TO-IMAGE.SRC;1 AUTOMARK-HTMS.SRC;1 CURSES-DEV-KIT.ZIP;1 IMAGE-MEDIAN-FILTER.SRC;1 PAD2PS00.SRC;1 PAD2PS01.SRC;1 PAD2PS02.SRC;1 PAD2PS03.SRC;1 PAD2PS04.SRC;1 PAD2PS05.SRC;1 PAD2PS06.SRC;1 PAD2PS07.SRC;1 PAD2PS08.SRC;1 PAD2PS09.SRC;1 PAD2PS10.SRC;1 PAD2PS11.SRC;1 PIDENTD01.SRC;1 PIDENTD02.SRC;1 PIDENTD03.SRC;1 PIDENTD04.SRC;1 PIDENTD05.SRC;1 PIDENTD06.SRC;1 PIDENTD07.SRC;1 PIDENTD08.SRC;1 PIDENTD09.SRC;1 WINLIKE_UNIX_INI.SRC;1 ========> [VMSLT96B.NTSEC]AAAREADME.TXT;1 <======== Subj: Re: [NTSEC] How to remove the Everyone Group On newly setup computers, you could use the NTSEC utilities to apply a set of saved permissions across a filesystem. The way to use it is to set up the permissions on files you want to restore later (such as on %SystemRoot%), run SAVEACL which will save those perms to a file. When you set up additional computers, just run RESTACL to reapply the default set of permissions from the file. For instance: saveacl -r c:\winnt35 winnt35.acl - save permissions to winnt35.acl restacl winnt35.acl - restore permissions This won't help with share permissions though, and I don't think there is a way to remove BUILTIN groups. You can get the NTSEC utilities on ftp://ftp.netcom.com/pub/wo/woodardk/. -Keith (This is for Windows NT, basically on Intel) ========> [VMSLT96B.PDP11]AAAREADME.TXT;2 <======== This area contains a pdp11 simulator (w/src) and a few systems that run with it, and some additional information about pdp10/20 simulators (but not the simulators). The software includes some OSs which are for noncommercial use and access & use is governed by licenses included with them. ========> [VMSLT96B.PERL]AAAREADME.TXT;1 <======== This contains a recent version of the PERL 5 language from genetics.upenn.edu in [.perl5], including improvements to its VMS operation. PERL is widely used in conjunction with web servers and many other needs, and can be used in place of AWK in some instances. ========> [VMSLT96B.PINE]AAAREADME.TXT;1 <======== Article 159787 of comp.os.vms: 22-NOV-1996 PINE 3.91 beta 10 A new beta of PINE for VMS is available (PINE 3.91 BETA 10) which contains a number of new things and changes to improve stability/reduce bugs. Details are enclosed below for those interested. Regards, Andy Harper Kings College London What is PINE ? -------------- Pine is a program that runs on a number of different platforms to provide a screen based mail and news reading facility. It originates at the University of Washington. Mail folders on remote systems can be read as easily as local mail folders, using standard POP and IMAP protocols. What is IMAP ? -------------- Several people asked 'what is IMAP' after my earlier message went around. Well it's a protocol that allows a client to access mailboxes on a server. It differs from the POP protocol in a number of key areas: * POP only accesses the NEWMAIL folder; IMAP can access any folder * POP downloads messages to the client; IMAP keeps them on the server (in either case, messages can be downloaded or left on the server if you wish but access to such messages with POP becomes tricky). POP is not good for people who move from PC to PC, whereas IMAP handles this neatly. * POP can only read a mailbox and delete items from it; IMAP can additionally search, rename and store (though these are not implemented in this VMS port). This allows suitable clients to move messages between folders on different systems. What Mail clients use IMAP? --------------------------- Most of the clients around still use POP (Eudora, pegasus, netscape mail etc.) but a number are starting to incorporate IMAP access to. The commercial one we use is called Simeon by ESYS Corporation (this is not a recommendation and I have no connection with the company!) and there is a freeware one called ATISMAIL around. There's also talk of adding IMAP to NETSCAPE mail and perhaps EUDORA. It IS an internet 'standard' and is therefore likely to become more prevalent over time. What about this IMAP server? ---------------------------- Page 2 We had a need for a functional IMAP server on our VMS systems, and a number of others seemed to be interested too, so I set about finding one. One such is the IMAPD server included with the PINE software from Univ. of Washington, which was ported to VMS by Yehavi Bourvine (based on the one included in the PINE 3.91 kit from U of Washington). This was known as 3.91 beta 5 for VMS. I've updated Yehavi's port with some additional bug fixes and features. Although there are later releases of pine (3.95 is current I believe) there are no working VMS ports (though 3.95 does include a partial port which is grossly incomplete). My improvements to 3.91 are primarily: * Fixing some problems with PINE sending mail out * Completing the port of the IMAPD server * Fully supporting the NETLIB TCP/IP interface * Adding a few new features, such as logging and decnet address mapping * Supporting builds with DEC C 5.3, GNU C 2.7.1 and VAXC 3.2, on both VAX and ALPHA RESTRICTIONS: ------------ The VMS port cannot current handle any operation which requires creating an empty mailbox or transferring a message from the network into a vms folder. This is due to major restrictions in the VMS callable mail interface. Several discussions with Digital have resulted in no viable workarounds as yet. I hesitate to say that I had some difficulty convincing them of the need for this but I did! AVAILABILITY: ------------- FTP: ftp://ftp2.kcl.ac.uk/zip/pine_3_91_beta_10.zip (ZIP format) ---- See the .ANN files for further information & build instructions. ========> [VMSLT96B.PPL]AAAREADME.TXT;1 <======== This area has some RTL components for the PPL directives in VMS. They came the way they are here...not well documented, but those familiar with PPL$ may find them useful. ========> [VMSLT96B.PRCS]AAAREADME.TXT;1 <======== PRCS -- Project Revision Control System Announcing version 1.0 of PRCS, the Project Revision Control System. PRCS is the front end to a set of tools that (like CVS) provide a way to deal with sets of files and directories as an entity, preserving coherent versions of the entire set. PRCS was designed primarily by Professor P. N. Hilfinger, with input and modifications by Luigi Semenzato and Josh MacDonald. PRCS is written and maintained by Josh MacDonald. Its purpose is similar to that of SCCS, RCS, and CVS, but (according to its authors, at least), it is much simpler than any of those systems. To compile and install PRCS, read the instructions in the INSTALL file. Once you have done this, you should at least read the first few sections of the documentation. It is available in info format. All documentation is located in the doc/ subdirectory. The current release, version 1.0, and future releases of PRCS can be found at ftp://XCF.Berkeley.EDU/pub/prcs. HTML documentation and recent developments are available online at http://www.XCF.Berkeley.EDU/~jmacd/prcs.html. PRCS is released under the GNU public license, see the file COPYING for details. A mailing list has been formed for announcements and discussion: prcs-list@XCF.Berkeley.EDU, you can subscribe by mailing majordomo@XCF.Berkeley.EDU with the single line subscribe prcs-list Comments about PRCS can be addressed to the following addresses: hilfinger@CS.Berkeley.EDU, jmacd@CS.Berkeley.EDU, prcs@XCF.Berkeley.EDU Bug reports can be addressed to the following address: prcs-bugs@XCF.Berkeley.EDU ---- This software is not specifically for VMS and may need some work to bring up on any particular system. ========> [VMSLT96B.SAFETY]AAAREADME.TXT;1 <======== SAFETY - Comprehensive undelete (changes delete to put files in a wastebasket and allows user undelete, and monitors space so it doesn't run out), very extensive security, and HSM style space protection features. This version will run on all your disks for 45 days, or on any one disk forever. The vendor sells the unlimited version, not too expensively. Glenn C. Everhart Everhart@Arisia.GCE.Com DELETE-PROTECT.DOC and EACF_USER_MAN.TXT are separate and slightly older descriptions of the security and deletion protection features. The SPD follows. ================================================================ Software Product Description Safety V1.2 Comprehensive Data Safety for your VMS systems. from General Cybernetic Engineering Executive Summary: There are many perils your data faces, and loss of data can cost time, money, and jobs. Intruders, disgruntled insiders, or hidden flaws in installed software can destroy records. What is more, mistaken losses occur constantly. Safety protects your system and your critical data in three ways: 1. A comprehensive security system adds extra checks for access to VMS files so that access by intruders or by people in non-job-required ways can be regulated or prevented. This allows your business - critical data to finally be protected against misuse, tampering, or abuse. Access from programs doing background dirty work (viruses, Trojans, worms, and the like, or even programs with security holes which can be exploited remotely (like Java browsers)) can also be blocked without damaging normal use. This active protection works three ways: by checking integrity of your files against tampering, by preventing of untrusted images from gaining privilege, and by regulating what other parts of the system an image may access. 2. A deletion protection system provides a way to undelete files which were deleted by mistake and to optionally copy deleted files to backup facilities before removal. Unlike all other VMS Page 2 "undelete" programs on the market, this facility does not rely on finding the disk storage that contained the file and reclaiming it before it is overwritten. Rather, it changes the semantics of the file system delete to use a "wastebasket" system and captures the file intact. Thus, this system works reliably. No others do. This facility is also useful where you have a requirement to keep all files of a certain set of types, since the backup function can be used to capture such files while permitting otherwise normal system function. The shelving or linking functions are also available for moving copies offline if this is desired. The Safety protection features are fully integrated with the DPS subsystem, so that deletion protection does not involve destroying file security. 3. When space runs out, hasty decisions about what to keep online often must be made, and the risk of accidentally losing something important is high. Safety protects you from running out of space. Space can be monitored and older items in the 1 wastebasket deleted if it is becoming low, without manual intervention. In addition, Safety is able to "shelve" files so that they are stored anywhere else desired on your system, and they are brought back automatically when accessed. Thus no manual arrangements need be made for reloading them. Safety can also keep the files on secondary storage, keeping a "soft link" to the files at their original site so they will be accessed on the secondary storage instead. Also, Safety can store files compressed, or can store them on secondary storage so that read access is done on the secondary storage, but write access causes the file to be copied back to its original site. Standard VMS utilities are used for all file movement, and moved files are also directly accessible in their swapped sites with standard VMS utilities. The VMS file system remains completely valid at all times. Safety gives you a full complement of tools for dealing with space issues automatically according to your site policy. These facilities are safe and easily understood. A comprehensive utility is provided by which you set your site policy to select which files are and are not eligible for automatic shelving. Also you are provided with screen oritented utilities for selecting files to shelve at any time. Access to the shelved files of course causes unshelving if the normal shelving-by-copy mode is used. Also, a simple set of rules permit locating Page 3 shelved or softlink target files at any time, even without Safety running. Safety at no time invalidates your file structures for normal VMS access...not even for an instant. In addition Safety contains functions to speed file access and inhibit disk fragmentation. The major subsystems of Safety will now be described. The Security Function System: Summary: Managing access to data critical to your business using ACL facilities in native VMS can be cumbersome and still is vulnerable to intruders or people acting in excess of their authority. Want to be sure your critical records can't be accessed save at authorized places, times, and with the programs that are supposed to access them (instead of, say, COPY.EXE)? Want to have protection against privileged users bypasssing access controls? Want to be able to password protect individual files? Want to be able to invisibly hide selected files from unauthorized intruders? 2 Have you read that attacks on machines can happen because a Java browser points at a web site that damages the system (as has been reported in the press)? Want to be able to protect your systems? The Safety security subsystem builds in facilities permitting all of these, and is not vulnerable to intruders who disable the AUDIT facility as all other commercial packages which purport to monitor access are. Description: When your business depends on critical files, or when you are obliged by law or contract to maintain confidentiality of data on your system, in most cases the options provided by VMS for securing this data can be cumbersome and far too coarse-grained. Page 4 The problem is that certain kinds of access to data are often needed by people in a shop, but other access should be prevented and audited. Moreover, the wide system access that can come as a result of having system privileges often does not mean that it should be used to browse or disclose data stored on the system. A system manager will in general not, for example, have any valid reason to browse the customer contact file, the payroll database, or a contract negotiation file, save in a few cases where these files need to be repaired or reloaded from backups. Likewise, a payroll clerk may need read and write access to the payroll file, but not in general with the COPY utility, nor from a modem, nor in most cases at 4AM. Finally, a person who must have privileges to design a driver and test it should ordinarily not have the run of the file system as well. Given examples like these, it is easy to see that simple authorization of user access to files is inadequate. While it is possible to build systems that grant identifiers to attempt some extra control, these can be circumvented by privilege, and create very long ACLs which become impossible to administer over a long period as users come and go. What is needed is a mechanism that is secure, cannot be circumvented by turning on privileges, and which provides a simple to administer and fine grained control that lets you specify who can get at your critical files, with what images, when, from where, and with what privileges. It is also desirable to be able to control what privileges the images ever see, and to be able to check critical command files or images for tampering before use, so that they cannot be used as back doors to your system. It should be possible to demand extra authentication for particular files as well, and to prevent a malicious user from even seeing a particularly critical file unless he can be permitted access. The Safety security subsystem is a VMS add-in security package which provides abilities to control security problems due to 3 intruders, to damage or loss by system "insiders" (users exceeding their authority), and to covert code (worms and viruses). It provides a much easier management interface to handle security permissions than bare VMS and provides facilities permitting control over even privileged file Page 5 accesses, for cases where there are privileged users whose access should be limited. Unlike systems which only intercept the AUDIT output, EACF can and does protect against ANY file accesses, and can protect files against deletion by unauthorized people or programs in real time as well as against access. The Safety security subsystem offers the following capabilities: * Files can be password protected individually. If a file open or delete is attempted for such a file and no password has been entered, the open or delete fails. * Access can be controlled by time of day. Added protections can be in place only some of the time, access can be denied some times of day, write accesses can be denied at certain times, or various other modalities of access can be allowed. * You can control who may access a file, where they may be (or may not be), with what images they may or may not access the file, and with what privileges the file may be accessed. Thus, for instance, it is trivial to allow a clerk access to the payroll file with the payroll programs, but not with COPY or BACKUP, not on dialup lines, and not if they have unexpected privileges. The privilege checks can be helpful where there are consultants working on a system who should be denied access to sensitive corporate information but who need privileges to develop programs, or in similar circumstances. You specify what privileges are permitted for opening the file, and a process with excess privileges is prevented from access. Vital business data access should not always be implied by someone having privilege. With this system you can be sure your proprietary plans or data stay in house, and are available only to those with business reasons to need them, not to everyone needing system privileges for unrelated reasons. Unlike packages using the VMS Audit facility's output (which can be silently turned off by public domain code), Safety cannot be circumvented by well known means. Its controls are designed to leave evidence of what was done with them as well. * You can hide files from unauthorized access. If someone not authorized to access a file tries to open it, they can be set to open instead some other file anywhere on the system. Meanwhile, Safety generates alarms and can execute site specific commands to react to the illegal access before it can happen. This can be helpful in gathering evidence of what a saboteur is up to without exposing real sensitive files to danger. Normal access goes through transparently. 4 Page 6 * You can arrange that opening a file grants identifiers to the process that opens it and that closing it revokes these identifiers. Set an interpretive file to do this and set it to be openable only by the interpreter and you have a protected subsystem capability that works for 4GLs which are interpretive. (Safety identifier granting, privilege modification, and base priority alteration is protected by a cryptographic authenticator preventing forging or duplication.) * You can actively prevent covert code ( viruses and worms) from running in two ways. First, Safety can attach a cryptographic checksum to a file such that the file will not open if it has been tampered with. Second, Safety can attach a privilege mask to a file which will replace all privilege masks for the process that opens it. By setting such a mask to minimal privileges, you can ensure that an untrusted image will never see a very privileged environment, and thus will be unable to perform privilege-based intrusions into your system even if run from a privileged user's account. * You can control base priority by image. Thus, a particularly CPU intensive image can be made to run at lower than normal base priority even if it is run interactively. * You can run a site-chosen script to further refine selection criteria. (Some facilities for doing additional checking while an image runs exist also.) * You can have "suspect" images set a "low-integrity-image" mode in which all file opens are checked with a site script which can report or veto access. This can be used to track or regulate what a Java applet can do, in case someone happens to browse a web site which exploits a Java hole to browse your system or damage it. Safety allows you to exempt certain images (e.g., disk defragmenters) from access checks, and it is possible to put a process into a temporary override mode also (leaving a record this was done) where this is needed. Safety facilities are controllable per disk, and impose generally negligible overhead. Safety will work with any VMS file structure using the normal driver interfaces. Also, Safety marking information resides sufficiently in kernel space that it cannot be removed from lower access modes, yet it uses a limited amount of memory regardless of volume size. Best of all, the Safety protection is provided within the file system and does not depend on the audit facility. Thus it prevents file access or loss before it happens, and does not have to react to it afterwards. Safety allows all of its Page 7 security provisions to be managed together in a simple screen-oriented display in which files, or groups of files, can be tagged with the desired security profiles or edited as 5 desired. Safety protections are in addition to normal VMS file protections, which are left completely intact. Therefore, no existing security is broken or even altered. Safety simply adds additional checking which finally provides a usable machine encoding of "need to know" for the files where it matters. The Safety Deletion Protection Subsystem. Description: The Safety Deletion Protection System is designed to provide protection against accidental deletion of file types chosen by the site, and to allow files to be routed by the system to backup media before they are finally removed from the system. This is accomplished by an add-in to the VMS file system so that security holes are not introduced by the system's action. The user interface is an UNDELETE command which permits one or more files to be restored to their original locations provided it is issued within the site-chosen time window after the undesired deletion took place. In addition, an EXPUNGE command is provided which allows files to be deleted at once, irretrievably, where space for such is required. Provision for automatic safe-storing of files prior to final deletion is present also in Safety DPS. Safety DPS is implemented as a VMS file system add-in which functions by intercepting the DELETE operation and allowing the file to be deleted to be copied or renamed to a "wastebasket" holding area pending final action, and to be disposed of by a disposal agent. The supplied agent will allow a site script to save the files if this is desired, and then finally deletes any files which have been deleted more than some number N seconds ago. If the UNDELETE command is given, the file(s) undeleted are replaced in their original sites. The supplied system can also be configured to rename files to a wastebasket area or to copy them directly, for undeletion by systems people only. (These Page 8 options are faster than the site command file option.) Safety DPS can be configured to omit certain file types from deletion protection (for example, *.LIS* or *.MAP* could be omitted), to include only certain files in the protected sets, or both. This can reduce the overhead of saving files which are likely to be easily recreated, or tailor the system for such actions as saving all mail files (by selecting *.MAI for inclusion). In addition, Safety DPS monitors free space on disks, and when a file create or extend would cause space exhaustion, Safety DPS runs a site script. By setting this script to perform final 6 deletions, Safety DPS can be run in a purely automatic mode in which deleted files are saved as long as possible, but never less than some minimum period (e.g., 5 or 10 minutes). Safety DPS files can be stored in any location accessible to VMS. If they are renamed, they must reside on the same disk they came from. Otherwise they can be stored in any desired place. Safety DPS is installed and configured using a screen oriented configuration utility to set it up, and basically runs unattended once installed. The Safety Storage Migration Subsystem Description: Safety has the ability to move files to secondary storage and automatically retrieve them when they are accessed. This backing can be similar to what HSM systems call "shelving", though it can be done in multiple levels, or it can be done in a way which permits files moved to secondary storage to be accessed there as though the files remained online. This resembles what are called "soft links" in Unix systems, in that file opens are transparently redirected to a file stored somewhere else reachable on the system, and the channel reset to the original device on close. A "readonly link" mode acts like a soft link Page 9 for readonly access, and like an unshelve operation where a file is opened read/write, should this be desired. Full control over this shelving and unshelving is provided. This provides a great deal of flexibility in reclaiming space when the Safety space monitoring function detects that space is needed. Not only can previously deleted files be finally moved to backup destinations and deleted, but the system can migrate seldom accessed files to nearline storage transparently. The site policy can drive this, or utilities provided can be used instead. Where it is chosen to run Safety in a lights-out fashion (with Safety reacting to low disk situations by emptying older deleted files from the wastebasket and/or file migration to backing store), the policy chosen for controlling such setting is handled by a full-screen, easily used, tool which sets the policy. Should still greater flexibility be needed, the scripts used for a number of operations are supplied together with a full description of the command line interface of the underlying software. This facilitates linking Safety file management functions with other packages should such be desired. 7 Safety can be run in a mode where there is essentially no overhead at all imposed (just a few instructions added along some paths and no disk access) for any files except those which need softlinks or possible unshelving. There is no limit to how many files may be so marked on a disk. A fullscreen setup script allows one to select the Safety run modes. Even if Safety is forced to examine all files for its markings, the overhead imposes no added disk access and costs only a tiny added time (typically a percent or two) in open intensive applications. In addition, Safety can be turned off or back on at any convenient point should this be desired. (This must be done using special tools provided for use by those specially authorized to do so.) Support: Safety runs on VAX VMS 5.5 or greater or AXP VMS 6.1 or greater. The same facilities exist across all systems. HSM must be installed on each cluster node of a VMScluster where it is to be used but imposes no restrictions on types of disk it works for. Safety will work with any file structure used by VMS, so long as Page 10 a disk class device is used to hold it. It is specifically NOT limited to use with ODS-2 disks. Safety is available for 45 day trial use licenses or can be licensed permanently. Safety is available for 45 day trial use licenses or can be licensed permanently. Safety is required on every node of a cluster using it, or its benefits will not be available on nodes not having the software running. Apart from this, there are no problems with having Safety available on only part of a VMS cluster. Safety is brought to you by General Cybernetic Engineering 18 Colburn Lane Hollis, NH 03049 603 465 9517 voice 603 465 9518 fax For orders, contact the above address or Sales@GCE.COM. For technical information contact Info@GCE.Com For support contact Support@GCE.Com Glenn C. Everhart Everhart@GCE.Com This copy of Safety will work on as many disks as you want for up to 45 days. Thereafter, it will work on one disk only, with full function, forever. If you want to get it to work for longer on many disks, you will need to license it; the cost is per CPU and allows ALL functions to be used (though you can select some and not others). Note that if you want Safety to work on a volume set, it needs to have an intercept enabled for each member, all pointing at the same data; a volume set counts as multiple volumes for the one-disk licensing purposes. The one-disk functions are not limited, and you can run the setup for many units, but after 45 days, only the first disk I/O intercept will work. The Safety setup menu (jt_setup) contains fairly extensive help built into it to guide installations. Complete manuals are in the kit, which installs with VMSINSTAL. To install, log in as SYSTEM and put SAFETY013.A somewhere (call it disk:[dir]safety013.a) and type $@sys$update:vmsinstal safety013 disk:[dir] and answer all questions. Defaults are usually OK. A few manuals may use the terms "SDH" or "Safety V1.2"; these just reflect their age Page 11 and don't change their validity. Safety runs on Vax or Alpha, any recent OpenVMS version. Pricing varies with CPU power (crudely); workstations are most inexpensive. Site licensing is available. ========> [VMSLT96B.SDL]AAAREADME.TXT;1 <======== SDL, LANGUAGE, Data Structure/Interface Definition Language SDL is both a data structure and interface definition language and a utility/compiler to convert those definitions into language output for a number of different languages. This allows a single source definition of a data structure, for example, while supporting multiple language representations of that data structure. SDL consists of a front-end and numerous language back-ends. The front-end generates an intermediate language which is interpreted by the back-ends. It is straightforward to create back-ends for new languages, following the example of an existing back end. When the SDL/LANGUAGE qualifier is used, the specified language name is used to search for the back-end image. Note that SDL sources are provided in the [.SRC] directory, including build and option files as well as needed include files. Since the OpenVMS operating system itself is written in multiple languages which share many of the same data structures, SDL is used to define the data structure once and then produce output for the respective languages which require access to that structure definition. The most recent "formal" documentation describes VAX SDL V3.2. That documentation is available on this kit. There have been a number of bug fixes made to SDL for Alpha which are included in this kit. To use this SDL, copy all the images into a particular directory, such as DAD$FREEWARE:[SDL], and create a local command file such as the following: To use the Alpha SDL images: $ AXP_NATIVE == 1 $ AXP_CROSS == 0 $ DEFINE EVMS$BUILD_TOOLS DAD$FREEWARE:[SDL.NATIVE], SYS$LIBRARY $ @EVMS$BUILD_TOOLS:SDL "" To use the VAX SDL images: $ AXP_NATIVE == 0 $ AXP_CROSS == 1 $ DEFINE EVMS$BUILD_TOOLS DAD$FREEWARE:[SDL.CROSS], SYS$LIBRARY $ @EVMS$BUILD_TOOLS:SDL "" ========> [VMSLT96B.SECURITY-THINGS]AAAREADME.TXT;2 <======== This area has a number of security extensions, many of them for unix, from the coast archive and has both papers and tools, many in ZIP form to save space. AAAREADME.TXT;1 MISCSECUR2.ZIP;1 MOCHA.HTML;1 README-FIX-OCT.1996;1 SATAN_EXTENSIONS.TAR_Z;1 SCAN-DETECTOR.TAR_Z;1 TRIPWIRE-1_2.TAR_Z;1 TRIPWIRE-SANS.PS_Z;1 WHAT_IS_COAST.PS;1 ========> [VMSLT96B.SECURITYSTUFF]AAAREADME.TXT;1 <======== This area is for security papers including papers on ActiveX security (and problems therewith) and Java security (and problems therewith). ========> [VMSLT96B.STL]AAAREADME.TXT;1 <======== The Standard Template Library Copyright (c) 1994 Rensselaer Polytechnic Institute This notice applies to all material accessible from this page except books, documents or source code bearing other copyright notices. ---------------------------------------------------------------------------- Much of the material accessible from this page is also available at ftp.cs.rpi.edu/pub/stl in compressed postscript files for hard copy printing and some of it in plain text (ASCII) files. Either follow the above link or ftp to ftp.cs.rpi.edu with username anonymous, do binary, then cd pub/stl. The main file is stl-info.ps.Z, which contains the STL Generic Algorithm Reference and most of the other material except papers and reports, which are in separate files (see the README file there). There are minor differences between the postscript and ASCII files and the material in these Web pages. ---------------------------------------------------------------------------- These pages contain detailed descriptions of STL generic algorithms, but only brief overviews of containers and iterators. (Not discussed at all are function objects, adaptors, and allocators.) For much more complete descriptions of all STL components, with many example programs, see D.R. Musser and Atul Saini, STL Tutorial and Reference Guide: C++ Programming with the Standard Template Library, Addison-Wesley, Reading, MA, 1996. (Available now.) In connection with the book, see also Source code resources and Errata list. ---------------------------------------------------------------------------- * STL, a new kind of library for C++ * How does STL differ from other C++ libraries? * STL-compatible compiler list (maintained by Warren Young) * How to compile programs that use STL---for RCS (Rensselaer Computing System) users * List of main STL include files * Simple example programs that use STL Some of these also use string handling facilities in mstring.h. * FTP sites for STL source code and related materials * Reference material o STL Generic Algorithm Reference, by Robert Cook, Jr., David R. Musser, and Kenneth J. Zalewski. Contains hypermedia data sheets describing all of the generic algorithms of STL, including source code and examples of use. The Page 2 examples can be executed directly from the data sheets. Based on the ANSI/ISO STL document (see below) and the Hewlett Packard implementation. o STL Container Classes o STL Iterator Categories o The Standard Template Library by Alexander Stepanov and Meng Lee (ANSI/ISO document) This is a formal document, not intended for mass consumption. In addition to generic algorithm and container class descriptions, it covers iterators, function objects, and adaptors. All components are described rigorously, but with few examples or much motivating discussion. It has been incorporated with few changes into the Draft Working Paper of the ANSI/ISO C++ Standards Committee, which is the final authority on all STL component specifications. o Algorithm-oriented Generic Libraries by David R. Musser and Alexander A. Stepanov This is a research paper describing some key design principles for building and documenting a software library based on generic algorithms. It does not describe STL per se, but has examples from a library that was STL's predecessor. A later version of this paper appeared in Software--Practice & Experience, Vol. 24(7), 623-642 (July 1994). This online version of the paper contains enhancements by Kenny Zalewski to allow running animations of some of the sorting examples and other sorting algorithms, using an animation program developed by David Musser, Nathan Schimke, Alex Stepanov, and Meng Lee. The animation program was implemented using Xlib and a predecessor of STL. o Additional references on generic programming ---------------------------------------------------------------------------- musser@cs.rpi.edu ========> [VMSLT96B.TECO]AAAREADME.TXT;1 <======== This area contains a few new TECO implementations to supplement those on the Spring 1996 sigtapes. Source is present where it was obtainable. ========> [VMSLT96B.TK]AAAREADME.TXT;2 <======== Materials from the FTP archives maintained by Hunter Goatley and Terry Kennedy (ftp.wku.edu or ftp.spc.edu) of OVMS utilities BOSS.ZIP;1 Multisession monitor...control several processes from one terminal BTRAN.TAR;2 Translate VAX Basic into C++ (initial version) BTRAN.ZIP;1 ditto BTRAN103.TGZ;1 BTRAN_STR_ANN.TXT;1 GAWK-DOC.ZIP;1 Docs for Gnu AWK GAWK.ZIP;1 Gnu AWK for VMS. A pattern matching oriented language GETCMD.ZIP;1 Show DCL command buffer for another process GLOGIN.ZIP;2 Log in as another users without a password ICALC.ZIP;2 Interactive calculator JUMP.ZIP;2 Become another user MGFTP.ZIP;1 FTP server, many improvements over others MGPCX.ANN;1 PCX, access MSDOS disk structures from VMS MGPCX.ZIP;1 ditto MG_FINGER.ZIP;1 Finger server for tcp/ip MMK.ZIP;1 Free version does most of what DEC MMS does (a "make") MPEG_PLAY.ZIP;3 MPEG movie player for VMS MX-PATCHES.ANN;1 MX042-PATCH.DIR;1 Patches for latest MX...small upgrades MX_DNSMTP.ALPHA_EXE;1 ditto MX_DNSMTP.EXE;2 MX_LOCAL.ALPHA_EXE;1 MX_LOCAL.EXE;2 PASLIB.ZIP;1 *unsupported* package of Pascal declarations for RTLs and system svcs PROBE.ZIP;1 VMS ethernet monitor PROBE22B.ZIP;1 ditto SMTP_SERVER.ALPHA_EXE;1 Upgraded SMTP (mail) server SMTP_SERVER.EXE;2 SPELL.ZIP;1 DECUS SPELL, updated STR.BUGFIX;1 STR.TAR;3 STR.ZIP;1 VMS strings routines, in portable C STR103.TGZ;1 TESTDEV.ZIP;2 VMS disk exerciser/perf test VMSBACKUP4-1.TAR;1 Read VMS Backup tapes on non-VMS systems ========> [VMSLT96B.TKTCL]AAAREADME.TXT;1 <======== This area contains TK and TCL (toolkit and command script language) for VMS. Included are a V7 and early V8 versions, together with a tip on building. This following describes the V8 kits here. This is my initial port of Tcl8.0 and Tk8.0 to VMS. I've only done very light testing of this port, I ran out of time before having to leave for vacation. Give it a try and let me know what's weird about it. Missing is support for some of the new "file" manipulation commands, mainly "file copy" and the directory removal logic for "file delete". I encourage contributions in this area. Implementing a "smart" copy, i.e. preserve RMS attributes, routine will take some coding effort. The Tk8.0 menus behave strangely, I don't know if it's the VMS port or a generic problem. Tk4.2 menus work fine. Run the widget demo to see for yourself. The function "tk_getOpenFile" mostly works but the display is ugly as one sees ".dir", semi-colons and mixed-case filenames. Haven't done a build on a Vax yet, again, I ran out of time. The file tcl8.tgz is a GNU gzip compressed tar file of my Tcl build directory and tk8.tgz is a GNU gzip compressed tar of the Tk build directory. All the objects and executables are included. I'm still using pmake. If someone contributes a MMS file, I'll include it with the distribution. ========> [VMSLT96B.TMESIS]AAAREADME.TXT;1 <======== This material comes from Brian Schenkenberger and is a template Alpha VMS system service intercept with source, and discussion on a system I/O speedup that may work with it. ========> [VMSLT96B.UNIXDCL]AAAREADME.TXT;1 <======== This area contains unix versions of many utilities of DCL type functions with sources. Many functions are supported. ========> [VMSLT96B.VMSGHOSTSCRIPT]AAAREADME.TXT;1 <======== This area contains Ghostscript for VMS, a Postscript interpreter which can be used to display Postscript documents or prepare them and process them into bitmaps for printing or faxing. ========> [VMSLT96B.VMS_ON_NT]AAAREADME.TXT;1 <======== This area contains a few bits of code which can implement VMS things on Windows NT. In the future more contributions of this sort would be most welcome. ========> [VMSLT96B.WNT]AAAREADME.TXT;1 <======== This area has an assortment of a few interesting-looking freely available utilities for Windows NT (mostly Intel flavor NT) including some which can be used to handle tape, edit disk raw, and similar activities. ========> [VMSLT96B.WWW]AAAREADME.TXT;2 <======== This area contains Web servers and browsers, an indexer (QI), and also the Mocha disassembler for Java (and a demo of the Crema obscurer for Java) and Lynx, a text-based web browser. The [.osupreview] directory has a few preview things including a preview of the OSU HTTP server (which supplements the current server HTTP_SERVER_2-1A.ZIP). The preview server has some code to allow logins and so on as well as normal serving. 0_4_2268_00.HTML;1 0_4_2268_00.TXT;1 AAAREADME.TXT;1 CREMA-E1.ZIP;1 CREMA.TXT;1 CREMADOWNLOAD.TXT;1 FORWARD_MESSAGE.B32;2 FREEWAIS-0_202.TAR_Z;1 GOPHER_SITE.POINTER;1 HTTP_SERVER_2-1A.ZIP;1 LYNX-CHANGES.TXT;1 LYNX.README;1 LYNX2-5FM.ZIP;1 LYNX2-6.ZIP;2 LYNX2HTML.TAR_Z;1 LYNX_HELP_FILES.ZIP;1 MOCHA-B1.ZIP;1 MOCHA.GET;1 MOCHA.HTML;2 MOCHA.TXT;1 MOCHABUGS.TXT;1 MOCHADOWNLOAD.TXT;1 MOCHAPROTECT.TXT;1 MOCHAREVIEWS.TXT;1 MOCHAUSES.TXT;1 MOSAIC275.ANN;1 MOSAIC2_7-5.ZIP;1 MOSAIC_EXE_VAX_V62.ZIP;1 OSUPREVIEW.DIR;1 QI310.ZIP;1 README.BUGS;1 README.VMS-2_7-5;1 SSBIO.ZIP;2 WHAT-IS-QI.TXT;1 ========> [VMSLT96B.XTOOLS-UNIX]AAAREADME.TXT;2 <======== This area contains a goodly collection of Unix utilities for X11 and readme files to describe them. Also many include source and should adapt easily to VMS X windows (at least on Alpha where the X kit is a direct use of the MIT code). AAAREADME.TXT;1 COLOR-XTERM-R6-PATCH.README;1 COLOREDIT-1_1.README;1 COLOR_XTERM.TAR-GZ;1 DDD-2_0.README;1 DISKTOOL-2.0$5N$README;1 DOCBOOK-TO-MAN.README;1 FILERUNNER_2_2.README;1 FILERUNNER_2_2.TAR-GZ;1 FTP_X_ORG_CONTRIB.LIS;1 INVALIDATE_TB.MAR;1 JPEG_5B.README;1 JPEG_5B.ZIP;1 KTERM-6-2-0.TAR-GZ;1 MFSM-1_3.README;1 MPDIST-3_3.TAR_Z;1 MPDIST.README;1 NEDIT.DOC;1 NEDIT_SOURCE.TAR-GZ;1 NETPBM-1MAR1994-P1.README;1 OLMOTD1_4.README;1 PIC2FIG.README;1 PIXY.README;1 PLAN-1-5-2.TAR-GZ;1 README.XAW3D;1 REPLAYXT-1-3.TAR-GZ;1 RXX-4_2_2.README;1 RXX-4_2_3.README;1 SCREENPRINTING.README;1 STRING2XMSTRINGCVT.README;1 TCL.TAR-GZ;1 TED3-0C.TGZ;1 TITRAX-1.98;1 TITRAX-1_98.README;1 TITRAX-1_98.TAR-GZ;1 TKPS2_0.README;1 UNCLUTTER-8.README;1 UPS-3_14-BETA-RGA-5.README;1 UWDIALER.README;1 WCL-2-7.TAR-GZ;1 WINTERP-2-03.TAR-GZ;1 XALARM-3_06.TAR-GZ;2 XALARM.README;3 XAUTOLOCK-PL10.TZ;1 XAW3D-1-3.TAR-GZ;1 XBENCH-0_2.README;1 XCB-2_2.TAR-GZ;1 XCB-2_3.README;1 XCB-2_3.TAR-GZ;1 XCRA-2_1.README;1 XCRA-2_1.TAR-GZ;1 XFSM-1_90.README;1 XINOUT-1_1.README;1 XINOUT-1_1.TAR_Z;1 XINPUT.README;1 XLOCKMORE-3-10.TAR-GZ;1 XLOCKMORE.README;1 XMADDRESSBOOK-1-5-3.TAR_Z;1 XMON-1-5-3.TAR-GZ;1 XMON.README;1 XPACMAN.README;1 XPACMAN.TAR-GZ;1 XPASTE-1_1.README;1 XPOST.TXT;1 XPOSTIT.LSM;1 XPOSTIT.TAZ;1 XPOSTITPLUS-2-2.TAR-GZ;1 XPOSTIT_PLUS-2_3.README;1 XPSEUDO_1_04.README;1 XPSEUDO_1_04.TAR_Z;1 XROUTE.README;1 XROUTE_11_9_94.TAR_Z;1 XRSH.README;1 XSCREENSAVER-1-26.TAR_Z;1 XSPACEWARS.README;1 XSPACEWARS_V0-0-2.TAR_Z;1 XTAR-1_4.README;1 XTAR-1_4.TAR-GZ;1 XTT-1-0-3.TAR-GZ;1 XVSET_0_90.README;1 XVTDL-5_2.README;1 XVTDL-5_2.TAR_Z;1 XWATCHWIN.TAR_Z;1 XWIT-3.2$5N$README;1 XWPICK-2-20.TAR-GZ;1 XWPICK.GET;1 XWPICK.README;1 XY_PLOT.TAR-GZ;1 ========> [VMSLT96B.XTOOLS]AAAREADME.TXT;2 <======== This area contains a number of X11 utilities, which claim to be able to run with VMS also in some fashion, plus description files for some of them and a couple other odds and ends. AAAREADME.TXT;1 COUNT.ANN;1 FTS012.SAV_Z;1 GD.TXT;1 GD1.TAR_Z;1 GDPM.ZIP;1 GIFMERGE.ZIP;1 INDEX.HTML;1 INDEX.TXT;1 KOBLAS.TXT;1 OP.TAR-GZ;1 PUBLIC_TGV_CISCO_COM_DIR.TXT;1 SOCKS.TAR-GZ;1 SOCKS_USENIX_PAPER.PS-GZ;1 TACACS.README;1 TGD1_2B.ZIP;1 TWM.ZIP;1 TXTRR.README;1 TXTRR.ZIP;1 VDD64.ZIP;12 WWWCOUNT2_3.ZIP;1 XFORECAST.ZIP;1 XMFM.ZIP;1 XPAINT-2_1_1.TAR-GZ;1 XTERM021.ZIP;1