[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference kernel::csguk_systems

Title:CSGUK_SYSTEMS
Notice:No restrictions on keyword creation
Moderator:KERNEL::ADAMS
Created:Wed Mar 01 1989
Last Modified:Thu Nov 28 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:242
Total number of notes:1855

115.0. "V5.4" by KERNEL::WRIGHTON (odd numbered release = bug insert) Tue Oct 23 1990 16:19

    	
    	This topic is reserved for notes about V5.4 
T.RTitleUserPersonal
Name
DateLines
115.1V5.4 Filed test letterKERNEL::WRIGHTONodd numbered release = bug insertTue Oct 23 1990 16:19153
          <<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
                               -< CSGUK_SYSTEMS >-
================================================================================
Note 78.18                       VAX 9000 topic.                        18 of 78
KERNEL::WRIGHTON "No , it's meant to work like tha" 145 lines  31-JUL-1990 08:27
                         -< VMS 5.4 Field Test letter >-
--------------------------------------------------------------------------------





          DIGITAL


          VMS Version 5.4 Early Hardware Support
          Customer Letter

          AV-PCJPC-XE

          Digital is pleased to provide Field Test Version 5.4 of the VMS
          operating system. Because this is a field test kit, you will
          receive at least one media update and the complete Version 5.4
          documentation set at no charge, when they become available.
          Please apply any media updates shortly after you receive them.

                                        NOTE

             Use of this VMS media and documentation kit is subject
             to the terms and conditions of your field test agreement
             letter. You must sign that letter and return it to Digital
             before using this media and documentation kit.

          Contents of This Kit

          Enclosed are two TK50 tape cartridges or three magnetic tapes
          that contain VMS Field Test Version 5.4 software. Also included
          is the following field test documentation:

          o  VMS RTL Mathematics (MTH$) Manual

          o  VMS Volume Shadowing Manual

          o  VMS Debugger Manual Supplement

          o  VAX MACRO and Instruction Set Reference Manual Supplement

          o  VMS Version 5.4 Upgrade and Installation Manual

          o  VMS Version 5.4 Release Notes

          o  VMS Version 5.4 New Features Manual

          o  VMS Device Support Manual

          o  VMS Upgrade and Installation Supplement: VAX 6000 Series

 






          o  VMS Upgrade and Installation Supplement: VAX 9000 Series

          You might also receive VMS Version 5.3 documentation in your
          kit.

          Restrictions

          Digital recommends that you observe the following restrictions
          with VMS Field Test Version 5.4 software. Some of these restric-
          tions may be removed as you receive software updates.

          VAXft 3000 Systems

          The VAXft 3000 series is not supported in a VAXcluster environ-
          ment.

          VAX 6000 Model 400 Vector Systems

          o  One vector unit is allowed per system.

          o  The CIXCD adapter is not supported.

          o  VAXclusters are supported if the following conditions are
             met:

             -  The computers with vectors are running VMS Field Test
                Version 5.4 software.

             -  The other nodes in the VAXcluster environment are running
                VMS Version 5.3 or a subsequent dash release (5.3-n). For
                information on operating in mixed-version clusters, refer
                to VMS Version 5.4 Upgrade and Installation Manual.

          o  Standalone BACKUP might fail to boot, displaying the follow-
             ing error message:

                  VAX/VMS Version X4GE-A3A Major version id = 1 Minor version id = 0

                  %EXECINIT-F-Insufficient nonpaged pool

                                          2

 






             To avoid this problem, perform a conversational boot and
             increase nonpaged dynamic memory as follows:

                  >>> B/R5:1  CSA1:
                  SYSBOOT> SET NPAGEDYN 950000
                  SYSBOOT> CONTINUE
                     .
                     .
                     .

          VAX 9000 Systems

          Digital's VAX 9000 Program Office and your local account team
          (Sales and Customer Services) will provide a detailed plan and
          VMS Field Test Agreement that will include:

          o  Supported configurations

          o  Configuration or utilization restrictions

          o  Estimated schedule for lifting these restrictions

          Reporting Problems

          For VMS Field Test Version 5.4 support, consult your local Dig-
          ital Customer Support Center or your local Digital representa-
          tive.










              �Digital Equipment Corporation. 1990. All rights reserved.

                                          3
115.2V5.4 and the 9000KERNEL::WRIGHTONodd numbered release = bug insertTue Oct 23 1990 16:191144
          <<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
                               -< CSGUK_SYSTEMS >-
================================================================================
Note 78.37                       VAX 9000 topic.                        37 of 78
KERNEL::ODONNELLR                                  1136 lines   4-SEP-1990 18:29
                             -< 5.4 and the 9000 >-
--------------------------------------------------------------------------------

From:	CLADA::MEDLEY "PADDY MEDLEY, DTN: 784-3331, GAE, GALWAY  04-Sep-1990 1807"  4-SEP-1990 18:20:10.37
To:	@SYS_SUPPORT,@CSC_ENG
CC:	
Subj:	VMS 5.4 cover letter.

From:	MACNAS::JWAFER       "JOHN WAFER, ISBS QUALITY, 822-2243"  4-SEP-1990 15:02:23.65
To:	NOCONNOR,CLADA::ERROL,JHESNAN,CLADA::MEDLEY
CC:	
Subj:	VMS Letter and restrictions

From:	HYEND::ZAGAME "ISB Marketing DTN 297-5026  04-Sep-1990 0825"  4-SEP-1990 13:29:38.01
To:	@[.EUROPE.FIELD_TEST]UPDATE.DIS
CC:	
Subj:	Draft of VMS V5.4 cover letter - describes features and restrictions

     Attached is a draft of the letter that will go out with VMS V5.4.  It 
     describes  what  new features are in the release, plus it also covers 
     the  restrictions  which  may  apply  to  your VAX9000 system. I'm in 
     Cannes, but will try to read my mail as often  as  possible  in  case 
     you have any questions.

     best regards,

     - Steve

     ----------------------




          Cover Letter for VMS Version 5.4

          AV-LX-TE


          Digital is pleased to provide VMS operating system Version 5.4.
          This new version of VMS extends and enhances the VMS operating
          system by offering support for distributed transaction process-
          ing, enhanced data availability and integrity, and fault tol-
          erant computing. This version also provides support for vector
          processing and new VAX systems.

          For more information about these enhancements, see the VMS
          Version V5.4 New Features Manual.

          Upgrade and Installation

          The VMS Version V5.4 Upgrade and Installation Manual contains
          step-by-step instructions for upgrading and installing VMS
          Version 5.4 and VMS DECwindows.

          To support full VMS, a system disk of greater than 100 MB is
          recommended. When a smaller disk is used, tailoring is required
          prior to installing some VMS options. Refer to the VMS Ver-
          sion 5.4 Upgrade and Installation Manaul for information on
          tailoring.

          Please note that the VMS Version 5.4 upgrade procedure will
          restore your site specific files (e.g. SYSTARTUP_V5.COM) during
          the last phase of the upgrade. However, there are two files,
          SYSHUTDOWN.COM and SYSECURITY.COM, which are not restored. Your
          site specific version will be the next lower version of these
          files. Please take steps to preserve these files before starting
          the upgrade.

 






          Kit Contents: Media

          Enclosed is the VMS Version 5.4 media. For new customers, Ver-
          sion 5.4 is distributed on the following pieces of media:

          o  Nine-track, 1600 bpi magnetic tapes

          o  TK50 tape cartridges

          o  Compact Disc

          Kit Contents: Documentation

          The complete VMS Version 5.4 Documentation Set contains over
          100 manuals describing every aspect of using the VMS operating
          system for daily operations, system management, and programming.
          The documentation set is organized into several kits to provide
          a wide range of choices about the level of information desired.

          The Base Documentation Set provides users who do not require the
          complete documentation set with essential and frequently used
          reference information.

          For users who need complete information, the Extended Documen-
          tation Set provides introductory and reference information on
          every VMS resource. It contains three subkits-a subkit for each
          major type of user (general, system manager, programmer)-and an
          Obsolete Features Kit.

          The Release Notes Kit includes the cover letters, Software
          Product Descriptions, and release notes for VMS Version 5.0
          through VMS Version 5.4, the Overview of VMS Documentation, and
          the VMS Version 5.4 New Features Manual.

          The upgrade and installation supplements provide information
          on the features of VAX computers and step-by-step instructions
          for installing VMS software and for frequently performed system
          operations. The VMS Version 5.4 Upgrade and Installation Manual
          provides step-by-step installation and upgrade procedures for
          VMS Version 5.4 for all VAX computers. This manual must be used
          with the upgrade and installation supplement for individual VAX
          computers.

                                          2

 






          The VMS DECwindows Programming Kit is an optional kit which
          provides the information necessary to develop DECwindows appli-
          cations.

          The following manuals are new for VMS Version 5.4:

             VMS Device Support Reference Manual
             VMS Upgrade and Installation Supplement: VAX 9000 Series
             VMS Volume Shadowing Manual
             Display PostScript System Perspective for Software Developers
             Display PostScript System Client Library Reference Manual
             PostScript Language Extensions for the Display PostScript
             System
             PostScript Language Color Extensions
             Display PostScript System pswrap Reference Manual
             PostScript Document Structuring Conventions Specification
             Version 2.1
             VMS DECwindows Display PostScript System Programming Supple-
             ment
             Introduction to the CDA Toolkit
             Guide to Creating Compound Documents with CDA

          Complete documentation for VMS is also available on the VMS
          Online Documentation Library compact disc for use with the VMS
          DECwindows Bookreader.

          Documentation on the VMS Compact Disc  The VMS Version 5.4 com-
          pact disc includes the following two manuals along with the
          VMS Version 5.4 software: the VMS Version 5.4 Release Notes
          and the VMS Version 5.4 Upgrade and Installation Manual. Both
          manuals are in ASCII text format, readable on your terminal,
          and also in DECwindows Bookreader format, readable with the
          VMS DECwindows Bookreader. To read the VMS Version 5.4 Release
          Notes and the VMS Version 5.4 Upgrade and Installation Man-
          ual using the Bookreader, first copy the following files from
          the [DOCUMENTATION.V054] directory on the compact disc to the
          SYS$COMMON:[DECW$BOOK] directory on your system:

          o  VMS_V54_RELNOTES.DECW$BOOK

                                          3

 






          o  VMS_V54_INSTALL_UPGRADE.DECW$BOOK

          o  LIBRARY.DECW$BOOKSHELF

          Then, follow the directions for using the Bookreader in the VMS
          DECwindows Desktop Applications Guide.

          VMS Volume Shadowing Phase I and Phase II

          Digital provides a volume shadowing product with two methods
          for performing shadowing operations. VMS Volume Shadowing Phase
          I provides for centralized shadowing on VMS systems using Hi-
          erarchical Storage Controllers (HSCs) with compatible Digital
          Standard Architecture (DSA) disks.

          VMS Volume Shadowing Phase II allows shadowing on the same
          configurations as Phase I plus extends the benefits of volume
          shadowing to all DSA disks. Refer to the VMS Volume Shadowing
          Software Product Description 27.29.07.

          VMS Volume Shadowing Phase II is initially restricted in VMS
          Version 5.4 to VAXft 3000 standalone configurations, pending
          further qualification of the product. Digital Equipment Corpo-
          ration expects to significantly expand the range of supported
          configurations after successful qualification.

          CI Architecture Extensions

          Extensions to the computer interconnect (CI) architecture allow
          the application of multiple CI interfaces per CPU and multi-
          ple star couplers per VAXcluster system. These extensions make
          possible VAXcluster systems with many times the data through-
          out capacity of current VAXcluster systems with a single star
          coupler. VMS Version 5.4 will initially support up to four CI
          interfaces per CPU and two star couplers per VAXcluster system.

          DSF32 Support for the VAXft 3000 Computer

          Support for the DSF32 synchronous DDCMP communications option
          specifically for the VAXft 3000 has been added with DECnet-VAX
          and VMS Version 5.4.

                                          4

 






          DECnet-VAX Device Support Information

          In the next 6 to 12 months, VMS, DECnet-VAX, and VAXcluster
          software support for the DEQNA Ethernet adapter will be with-
          drawn. For 24 months after that, the DEQNA adapter will be ac-
          cessible only by user applications using the $QIO interface to
          the Q-bus Ethernet device driver (XQDRIVER). During that time,
          when the XQDRIVER recognizes the device as a DEQNA adapter, a
          console message will be printed specifying that the DEQNA is
          an unsupported device. However, these user applications will
          continue to work. At the end of the 24-month period, the DEQNA
          Ethernet adapter will no longer be accessible.

          Digital recommends that customer implementations that use the
          DEQNA upgrade as soon as possible to either the DELQA or the
          DESQA, whichever is appropriate for the system. Customer upgrade
          options currently are available from DECdirect. Contact your
          local Digital sales office for more information.

          Also, at the next major functional ("dot") release of VMS and
          DECnet-VAX, functional support for the DMV11 synch comm de-
          vice, and the KMV/KMS/K* custom synch comm devices also will be
          dropped.

          As of the next release, customers may continue to use customer
          developed drivers to access the above devices, however, DECnet-
          VAX and VMS will no longer use these devices for any native
          communication operations. Service contracts will be honored on
          the hardware for 12-24 months after the next release, however,
          at some point during the 12-24 month period, all support for the
          devices will be dropped. See the VAX Wide Area Device Drivers
          SPD (xx.xx) at the next release for more detailed information.

          Digital recommends that customer implementations that use these
          synch comm devices upgrade as soon as possible. Customer upgrade
          options currently are available from DECdirect. Contact your
          local Digital sales office for more information.

          DECnet-VAX V5.4 does not support the CIXCD adapter. Support for
          this adapter is planned for a followon release of DECnet-VAX.

                                          5

 






          Also, as of V5.4, CNDRIVER support for all other CI adapters is
          currently limited to single adapter operation. Multiport support
          is planned for a follow-on release of DECnet-VAX. This affects
          any operations which use CNDRIVER.

          PHONE Utility Update

          The VMS PHONE utility will be removed from the base VMS oper-
          ating system in a future major release, currently planned for
          12 to 15 months from the present time. Digital intends to pro-
          vide executable source code to the DECUS library at that time.
          Customers will be able to get support for the PHONE utility
          for the VMS version previous to this major release for up to 12
          months after FCS of that major release. Digital recommends that
          customers plan accordingly.

          SYSGEN Parameter Values and the VAX 9000 Series

          In order to maximize the performance of the VMS file system
          caches on the VAX 9000 series, Digital recommends the following
          minimum SYSGEN parameter values:

             ACP_HDRCACHE: 1500
             ACP_DIRCACHE: 1500
             ACP_DINDXCACHE: 300
             ACP_MAPCACHE: 300

          These caches are allocated from the system-wide paged pool.
          Therefore, in order to maintain the appropriate relationship
          among the various SYSGEN parameters, you should add the follow-
          ing records to SYS$SYSTEM:MODPARAMS.DAT:

             MIN_ACP_HDRCACHE = 1500
             MIN_ACP_DIRCACHE = 1500
             MIN_ACP_DINDXCACHE = 300
             MIN_ACP_MAPCACHE = 300

          Then, invoke AUTOGEN with feedback. For information on AUTOGEN,
          see Chapter 6 of the Guide to Setting Up a VMS System.

                                          6

 






          Layered Product Caution for Remote System Manager 2.2 Server

          VMS Version 5.4 corrects some previously inconsistent error re-
          turns to the AUTHORIZE facility. As a result, MANAGE> INSTALL
          OPERATING_SYSTEM commands fail when AUTHORIZE attempts to add
          a proxy account for the client a second time. The failure in-
          formation is returned when you use /NOTIFY. It will occur the
          second time an INSTALL OPERATING_SYSTEM command is issued for a
          new client.

          If you have the RSM Server installed and use this facility, you
          can work around the problem with the following command:

               MCR AUTHORIZE REMOVE /PROXY client-name::RSM$CMANAGER

          Use this command on the RSM server before performing INSTALL
          OPERATING_SYSTEM commands. For a patch to this problem, contact
          Digital Support channels.

          Correction to VMS V5.4 Release Note: ALL-IN-1 Shareable Images
          Requirement for CDA Support

          VMS Version 5.4 provides two new shareable images that are ac-
          tivated by the Compound Document Architecture (CDA) support for
          ALL-IN-1 Version 2.4. ALL-IN-1 is a privileged image; therefore,
          any images activated by ALL-IN-1 must also be installed as known
          images.

          The new shareable images for VMS Version 5.4 are not installed
          as known images. If you require CDA support for ALL-IN-1 Version
          2.4, you must install the two new shareable images as known im-
          ages. If you do not require CDA support, no action is required.

          To install the two shareable images for CDA support, add the
          following command lines to your ALL-IN-1 site startup file,
          OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM:

               $ CREATE SYS$SHARE:XDPS$DPSLIBSHR.EXE
               $ INSTALL CREATE SYS$SHARE:XDPS$DPSLIBSHR.EXE
               $ INSTALL CREATE SYS$SHARE:XDPS$DPSCLIENTSHR.EXE

                                          7

 






          Release Notes for the VAX 6000-500 Computer

          When booting (STABACKUP and VMS) a VAX 6000-500 system with 512
          MB of memory, you must perform a conversational boot and change
          the SYSGEN parameter PHYSICALPAGES to 1047552. For example:

               >>> B/R5:1 du0
               SYSBOOT> SET PHYSICALPAGES 1047552
               SYSBOOT> CONTINUE

          This problem will be fixed in the next maintance release of VMS.

          After your system is up and running you may wish to change the
          SYSGEN parameter PHYSICALPAGES to 1047552 to avoid stopping in
          SYSBOOT during each reboot. For example:

               $ RUN SYS$SYSTEM:SYSGEN
               SYSGEN> SET PHYSICALPAGES 1047552
               SYSGEN> WRITE CURRENT
               SYSGEN> EXIT

          Due to a problem in Version 5.4, primary switching on the 6000
          family of VAX computers will not work. When a STOP CPU command
          is issued on the primary CPU, the command will fail due to a
          lack of qualified CPUs to become the new primary one. This will
          be fixed in the next maintance release of VMS.

          Powerfail warm start functionality will not operate correctly
          under Version 5.4 for the VAX 6000-500 computer. This will be
          fixed in the next maintance release of VMS.

              �Digital Equipment Corporation. 1990. All rights reserved.

          ___________________
       [TM] The following are trademarks of Digital Equipment Corporation:
            DDCMP, DECnet-VAX, DELQA, DEQNA, MicroVAX, Q-bus, VAX, VAX-
            cluster, VAXft, VAXstation, VMS, VMS/ULTRIX Connection, XMI,

            and the DIGITAL Logo.

                                          8

 










                                     APPENDIX  A


                             INFOSERVER 100 INFORMATION


          An InfoServer 100 is a disk storage server that efficently
          transfers data between compact disc drives connected to the
          server and remote network client systems. A server consists
          of memory, an Ethernet interface, some number of compact disc
          drives and software to control the server.

          The VMS InfoServer Client software support, available in this
          release, allows a remote VMS network client to communicate with
          an InfoServer 100 storage server. The VMS InfoServer Client
          (VIC) enables shared access to any compact disc drive connected
          to an InfoServer 100.

          The VMS InfoServer Client software provides support for:

          o  Initial System Loading (ISL) via the Ethernet: This lets you
             install the VMS operating system from a compact disc via the
             Ethernet. You place a VMS compact disc distribution kit in
             an InfoServer 100 and then boot the CPU on which you want to
             install VMS.

          o  Compact Disc access via the Ethernet: This function allows an
             installed VMS system to access compact disc volumes available
             on an InfoServer 100.

          o  VMS Layered Product Installation: By placing a VMS Software
             Consolidation Compact Disc in an InfoServer 100, an installed
             VMS system can install VMS Layered Products via the Ethernet.


                            InfoServer 100 Information  9

 






          o  Online Documentation Access: By placing a VMS Online Doc-
             umentation Library Compact Disc in an InfoServer 100, an
             installed VMS workstation can display the VMS and VMS DECwin-
             dows documentation set.

          Each compact disc that you insert in an InfoServer drive is
          available to a remote client system as a service. Each InfoS-
          erver service has a service name. A VMS compact disc is identi-
          fied by its volume label. For example, the VMS V5.4 compact disc
          distribution kit has a volume label of VMS054. When you wish to
          access this compact disc, specify VMS054 as the service name.
          Service names are used by the InfoServer 100 to identify all
          disk volumes. For more information about changing service names,
          see the InfoServer 100 Installation and Owner's Guide and the
          VMS LAD Control Program (LADCP) Manual.

          A.1  Initial System Loading (ISL)

          Initial System Loading is a means of loading the operating
          system software onto your target system disk. The VMS InfoServer
          Client software supports the Initial System Loading of the
          following VAX computers:

          o  VAX 6200 with console rom version 5.0

          o  VAX 6300 with console rom version 6.0

          o  VAX 6000-400 with console rom version 2.0

          o  VAX 6000-500

          If you do not have the correct console rom version, see your
          Digital sales representative for an upgrade.






                           10  InfoServer 100 Information

 






          A.2  VMS InfoServer Client Installation: Startup and Use

          After installing an InfoServer 100 you will need to activate
          the VMS InfoServer Client software to allow a remote VMS client
          system to access the InfoServer 100 hardware.

          Once your system is up and running and you have logged into
          the SYSTEM account you can immediately start the InfoServer
          Client software or you may wish to modify the system startup
          command file to always start the InfoServer Client software. The
          InfoServer Client software shares access to the Ethernet port on
          your system.

                                        NOTE

             If DECnet is typically started on your system be sure the
             InfoServer startup procedure is executed after your DECnet
             startup procedure has completed.

          The InfoServer Client software requires a node name be defined
          for the system it runs on. The InfoServer Client software will
          attempt to obtain the system node name from two locations. The
          first is the logical name SYS$NODE which is defined by having
          DECnet started. The second is the SYSGEN parameter SCSNODE. If
          DECnet is not used on your system, define the SYSGEN parameter
          SCSNODE before executing the InfoServer Client startup command
          procedure. For more on SYSGEN, see the VMS System Generation
          Utility Manual.

                                        NOTE

             If the node name of you system cannot be found, the InfoS-
             erver Client software will not start.

          If you wish to have the InfoServer Client software started on
          your system after each reboot, be sure your system has a node
          name defined and that you have removed the comment character(!)
          from the command lines in SYS$MANAGER:SYSTARTUP_V5.COM which are
          used to call the ESS$STARTUP command procedure.

                           InfoServer 100 Information  11

 






          To manually start the InfoServer Client software, execute the
          InfoServer startup command procedure located in the SYS$STARTUP
          directory. This procedure can be executed only from a privileged
          account. Start the procedure by typing:

               $ @SYS$STARTUP:ESS$STARTUP CLIENT

          The InfoServer Client startup command procedure accepts one
          optional parameter, "CLIENT". This parameter enables the loading
          of the InfoServer client driver, ESS$DADDRIVER.EXE, and the
          InfoServer transport driver. If this parameter is ommited, the
          InfoServer transport driver, ESS$LASTDRIVER.EXE, is the only
          InfoServer driver loaded.

          Other VMS layered products can make use of the InfoServer trans-
          port driver and do not require the InfoServer client driver
          to be loaded. The startup command procedures for these layered
          products will call the InfoServer startup command procedure with
          the proper parameters specified for their product.

          As the startup procedure executes informational messages are
          displayed. The following sequence of messages result from a
          successful startup of the software. For more information about
          solving problems which may occur during ESS startup, see Sec-
          tion A.2.3

               %LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped
               %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER
               %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyyyyy
               %NIC$STARTUP-I-LOADED, DADDRIVER loaded









                           12  InfoServer 100 Information

 






          A.2.1  How to BIND to a Remote Disk

          After the startup procedure has successfully completed you may
          BIND to an InfoServer service. An InfoServer service is defined
          to be a drive and its volume connected to an InfoServer 100
          system. A InfoServer service name is used in a BIND command
          to specify a desired InfoServer volume. For ODS-2 volumes the
          InfoServer service name is defined to be the volume label of
          the volume. For example, the service name for a VMS Version 5.4
          compact disc distribution kit is VMS054. In order to BIND to the
          VMS Version 5.4 compact disc distribution kit the compact disc
          must be inserted into a compact disc drive which is connected to
          an InfoServer 100. To execute the BIND command for this volume
          you would type the following commands:

               $ RUN SYS$SYSTEM:ESS$LADCP
               LADCP> BIND VMS054
               %LADCP-I-BIND, service bound to logical unit DAD$VMS054 (_DADn:)
               LADCP> EXIT

          For more information about the BIND command, see the VMS LAD
          Control Program (LADCP) Manual.

          A.2.2  Mounting a Remote InfoServer Disk

          As a result of BINDing to a remote disk, a logical name and
          a local physical device name are displayed. The rule for the
          creation of the logical name is that the string "DAD$" is used
          as a prefix to the service name specified in a BIND command.

          The local physical device name is "DADn". Where n is the device
          unit number which is incremented with each successive BIND
          command.

          To mount the DAD device displayed by the BIND command, specify
          the logical name created by the BIND command. For example:

               $ MOUNT DAD$VMS054 VMS054

                           InfoServer 100 Information  13

 






          A.2.3  Problems During Startup

          If only the first informational message appears during the
          execution of the ESS$STARTUP command procedure, check to be
          sure that a node name is defined for your system.

          A log file is created or appended to each time the ESS$STARTUP
          command procedure is executed. This log file is located in the
          SYS$MANAGER directory with a filename of ESS$LAST_STARTUP.LOG.
          The information at the end of this file may help to determine
          why the ESS$STARTUP procedure is not successful starting the
          InfoServer.

          A.3  Release Notes for InfoServer 100 Software

          The following release notes pertain to the InfoServer 100 and
          VMS Version 5.4.

          A.3.1  Installing VMS from an InfoServer 100

          The VMS installation procedure asks you to enter the name of
          the device that holds the VMS distribution kit. If you are
          installing the VMS operating system from an InfoServer 100
          device, enter DAD1 in reponse to this prompt. For example:

               * Enter the name of the drive holding the VMS distribution media: DAD1

          A.3.2  Device Names

          The device code for the DEMNA Ethernet controller on the VAX
          6000-200, 6000-300, and 6000-400 series is ET. The device code
          for the DEMNA Ethernet controller on the VAX 6000-500 is EX.







                           14  InfoServer 100 Information

 






          A.3.3  Command Procedure to Test for DECnet Status Before
                 Starting the InfoServer 100 Software

          DECnet is not required for InfoServer 100 software usage. If
          you do not have DECnet, you can simply start the InfoServer 100
          software with the startup procedure ESS$STARTUP.COM.

          However, if DECnet is part of your system, you must make certain
          that DECnet is running before you start the InfoServer 100
          startup command procedure.

          The following is a sample command procedure that you can run to
          test whether DECnet is running. This type of command procedure
          is located in SYS$MANAGER. First, start DECnet. Then, run the
          command procedure from the site-specific startup file SYSTARTUP_
          V5.COM.

               $!    ESS$CHECK.COM
               $!    Sample Command Procedure to Check Status of DECnet
               $!
               $!  Check to see if the user has DECnet. DECnet is not necessary
               $!  for the InfoServer 100;  however, if the user has DECnet, the
               $!  InfoServer must be started AFTER DECnet.
               $!
               $!  If the user does not have DECnet running, but still wants to use
               $!  this command procedure, the user can indicate that DECnet is not
               $!  on the system by defining the logical name ESS$IGNORE_DECNET with
               $!  the following DCL command:
               $!
               $!  $ DEFINE ESS$IGNORE_DECNET TRUE
               $!
               $!  This logical name can be defined in the SYSTARTUP_V5.COM procedure
               $!  before the command line that invokes the InfoServer 100 startup file,
               $!  ESS$STARTUP.COM.
               $!
               $ IF F$TRNLNM("ESS$IGNORE_DECNET") THEN GOTO ESS_CONTINUE
               $!
               $!  Check to see if DECnet is running.  If DECnet is not running,
               $!  and the system is not running as a subprocess, loop for 10 minutes to

                           InfoServer 100 Information  15

 






               $!  give DECnet time to start up.
               $!
               $ decnet_cnt = 0
               $net_loop:
               $ IF .not. F$GETDVI("NET0","EXISTS") THEN GOTO wait_decnet
               $ IF F$GETDVI("NET0","MNT") THEN GOTO decnet_running
               $wait_decnet:
               $ IF DECNET_CNT .EQ. 0 THEN -
               WRITE sys$output "%ESS-I-WAITNET, InfoServer waiting for DECnet to start"
               $ WAIT 00:00:10
               $ decnet_cnt = decnet_cnt + 1
               $ IF DECNET_CNT .GE. 6*10 THEN GOTO give_up_on_decnet
               $ GOTO net_loop
               $give_up_on_decnet:
               $ WRITE sys$output "%ESS-F-NODECNET, InfoServer cannot start without DECnet"
               $ EXIT
               $!
               $decnet_running:
               $ WRITE sys$output "%ESS-I-INFO  DECnet detected as started"
               $!
               $ESS_CONTINUE:
               $! The user can now start the InfoServer 100 software with the command:
               $ @SYS$MANAGER:ESS$STARTUP.COM
               $ EXIT


          A.3.4  VMS Client Support for the InfoServer 100 Supports Only
                 Disk Access to Compact Disc Drives

          The Client InfoServer 100 software on the VMS operating system
          supports only disk access to compact disc drives. Using the VMS
          client InfoServer software to access any device other than a
          compact disc drive is unsupported.






                           16  InfoServer 100 Information

 






          A.3.5  Troubleshooting the LAN with MOP Down-line Load Systems

          When trouble shooting a LAN for failure of a down-line load
          from the InfoServer 100 box, it is not necessary to check for a
          MOP partition on the InfoServer box. A MOP partition is not
          necessary for a successful down-line loading of an Initial
          System Load image.

          A.3.6  Multiple Standalone BACKUP Operations from ISL is
                 Unsupported

          When you use the Initial System Load function to install the
          operating system, you can successfully issue only one backup
          command at the standalone backup prompt. A second backup command
          will be ignored and is unsupported for this release. For details
          on the Initial System Load Function, see the VMS Upgrade and
          Installation Supplement: VAX 6000 Series.

          A.3.7  PCSA and InfoServer 100 Interaction

          If you use both PCSA and the InfoServer 100 Client software on
          your system, you must obtain a new PCSA kit. Older PCSA releases
          and the InfoServer 100 Client software for VMS Version 5.4 are
          incompatible.


          A.3.8  RSM 2.2 and Infoserver 100 Interaction

          If you are installing RSM 2.2 on a system with a running Infos-
          erver 100 client or if you already have RSM 2.2 installed and
          you decide to run the Infoserver 100 Client software, you must
          perform the following steps to avoid a system crash during your
          installation:

          1. Always place the RSM$SERVER_STARTUP.COM file after the
             ESS$STARTUP.COM file in your system startup files.



                           InfoServer 100 Information  17

 






          2. Always replace your RSM$SERVER_STARTUP command file with
             the one provided for you in SYS$EXAMPLES. Use the following
             command:

                  $ COPY SYS$EXAMPLES:ESS$RSM$SERVER_STARTUP.COM -
                  _$ SYS$COMMON:[SYS$STARTUP]RSM$SERVER_STARTUP.COM

             Do this after an installation of RSM 2.2 before any RSM
             configuring or startup.

          3. If RSM 2.2 was already installed on your system, reboot your
             system before executing ESS$STARTUP.COM the first time.

          These precautions are designed to prevent the possibility of a
          system crash during your installation. After these three steps
          are done in the order specified, you can proceed normally.

                                        NOTE

             ESS$STARTUP.COM checks for the presence of old driver
             files used by RSM 2.2 and refuses to start up until those
             files are deleted. You will need to delete the following
             files:

                SYS$LOADABLE_IMAGES:LASTDRIVER.EXE
                SYS$LOADABLE_IMAGES:LADDRIVER.EXE
                SYS$LOADABLE_IMAGES:LASTCP.EXE

          A.3.9  Configuring Hardware for InfoServer 100 Usage

          All Ethernet Controllers within a VAX computer must be connected
          to the Ethernet and working. If two Ethernet Controller boards
          are in a machine but one is not connected to the wire, the
          ESS software may or may not work, depending on the hardware
          configuration.




                           18  InfoServer 100 Information

 






          A.3.10  ESS$LASTCP Quota Exceeded Message

          The SYSGEN parameter MAXBUF must be set to 2300 bytes for the
          SHOW SERVERS command to properly operate from the ESS$LASTCP
          utility. When the parameter is incorrectly set an error indicat-
          ing Quota Exceeded is displayed.

































                           InfoServer 100 Information  19

 










                                     APPENDIX  B


                    VAX 4000 MODEL 300 GENERAL INFORMATION GUIDE


          This appendix describes Digital's new computer, the VAX 4000
          Model 300 (VAX 4000-300) system. It also explains how the VAX
          4000-300 differs from the MicroVAX, VAXstation, and VAXserver
          3400, 3600, and 3900 Series of systems. Finally, this appendix
          describes some of the information needed to install the VMS
          operating system on the VAX 4000-300, if it was not factory-
          installed.

          B.1  General Information

          The VAX 4000 Model 300 system is the latest VAX computer in the
          MicroVAX, VAXstation, and VAXserver 3400, 3600, 3900 series of
          systems. Refer to the VMS Installation and Operations: MicroVAX,
          VAXstation, and VAXserver 3400, 3600, 3900 Series manual for
          basic system information. Keep this information with that manual
          for future reference.

          B.2  Features of the VAX 4000-300 System

          The differences between other members in the 3400, 3600, 3900
          series and the VAX 4000-300 are described in the following
          sections.







                  VAX 4000 Model 300 General Information Guide  21

 






          B.2.1  The Compact Disc Drive

          You can add an RRD40 compact disc drive to the VAX 4000-300
          system. This read-only drive reads data stored on removable
          compact discs.

          To determine the device name of an installed compact disc drive
          on your VAX 4000-300, enter the SHOW DEVICE command at the
          console-mode prompt (>>>). The device name appears on the line
          with RRD40.

          Refer to Chapters 2 and 4 of the VMS Installation and Opera-
          tions: MicroVAX, VAXstation, and VAXserver 3400, 3600, 3900
          Series manual for additional information.

          B.2.2  VAX 4000-300 Device Names

          The VAX 4000-300 system can have the device names listed in
          Chapter 4 of the VMS Installation and Operations: MicroVAX,
          VAXstation, and VAXserver 3400, 3600, 3900 Series manual. It can
          also have the following device names:

          ________________________________________________________________
                                                          Device Name
          Device_______________________Device_Name________for_Booting_____

          Integral Ethernet con-       EZA0               EZA0
          troller

          RRD40_on_a_KZQSA_____________DKAu_______________DKAu____________

          B.2.3  RF Drives

          Some VAX 4000-300 systems include RF30 or RF71 drives. Each
          drive uses an integrated controller to communicate through the
          Digital Storage Systems Interconnect (DSSI) bus. The device
          names for RF drives are determined by the configuration of the
          two integral DSSI adapters on the CPU module.

                  22  VAX 4000 Model 300 General Information Guide

 






          The following table shows the device name formats for the RF
          drives on the VAX 4000-300 system.

          ________________________________________________________________
          Device Name Formats          VMS
          for_Booting__________________Device_Name_Formats________________

          DIcu or x$DIcu               $n$DIAu or x$DIAu
          ________________________________________________________________

            where:
            c = controller designation

             A is the controller designation for the first DSSI bus
             B is the controller designation for the second DSSI bus

            u = unit number
            x = DSSI node name
          __n_=_allocation_class_value_(1_to_255)_________________________

          Example device names for booting:

               DIA0
               DIB1

          Example VMS device names:

               $1$DIA1
               BETTY$DIA0

          To determine the boot device name of an RF drive on your VAX
          4000-300, enter the SHOW DEVICE command at the console-mode
          prompt (>>>).






                  VAX 4000 Model 300 General Information Guide  23

 






          B.3  Installing the VMS Operating System on the VAX 4000-300

          If you have received a VAX 4000 Model 300 system with the VMS
          operating system already loaded (factory-installed) on the hard
          disk, you should not install this VMS operating system kit. Keep
          this media and documentation available, however, in case you
          encounter problems with the preinstalled software.

          If you encounter problems with the preinstalled software and
          need to reinstall the VMS operating system, follow the in-
          structions beginning in Chapter 1 of the VMS Installation and
          Operations: MicroVAX, VAXstation, and VAXserver 3400, 3600, 3900
          Series manual.

          Then refer to the VMS Version 5.4 Upgrade and Installation
          Manual for additional installation information.























                  24  VAX 4000 Model 300 General Information Guide
115.3V5.4-0A messgaeKERNEL::WRIGHTONodd numbered release = bug insertTue Oct 23 1990 16:2187
          <<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
                               -< CSGUK_SYSTEMS >-
================================================================================
Note 78.52                       VAX 9000 topic.                        52 of 78
KERNEL::WRIGHTON "odd numbered release = bug insert" 79 lines   1-OCT-1990 23:44
                            -< VMS 5.4-0A message >-
--------------------------------------------------------------------------------


	Info on Special V5.4-0A Patch Kit (compliments Ellen Barden)


+++++++++++++++++++++++++
+  D  I  G  I  T  A  L  +                 INTEROFFICE MEMORANDUM
+++++++++++++++++++++++++
                                          DATE:  September 28, 1990

TO:  Distribution                         FROM:  Ellen Barden
                                          DEPT:  CSSE/32-Bit BSSG
CC:                                       LOC:   ZKO1-1/D19
                                          EXT:   381-2801
                                          ENET:  CSSE32::BARDEN

SUBJECT:  Special VMS V5.4-0A Patch Kit 

-------------------------------------------------------------------------------
                      DIGITAL INTERNAL USE ONLY
-------------------------------------------------------------------------------


Since VMS V5.4 submitted to the SSB in early September, some VMS software 
problems have been discovered that may potentially affect the new VAX 9000 
and VAX 6000-5xx systems.  VMS engineering has decided that a patch kit is 
needed for the customers of those new processors only, in order to ensure 
their stability.  Please note that the VAX 6000 5xx system has not been
announced yet.

This patch kit will be distributed with VAX 9000 and VAX 6000-5xx systems 
until VMS V5.4-1 ships (expected date December 1990).  All fixes contained
in this patch kit will be part of this VMS release, so all customers will
receive the fixes at that time.  The patch kit will also be sent 
to all customers worldwide who have already received a VAX 9000 system, and 
to any CSC contacts who received a VMS V5.4 pre-release kit(these shipments 
should be completed by October 5, 1990).
 

KIT DESCRIPTION:

The patch kit will be available on TK50, magnetic tape, and CDROM media.
It will update the VMS version number on the system from VMS V5.4 to VMS 
V5.4-0A for support reasons.  The kit will also include a cover letter 
explaining the installation instructions.  A postscript file of the cover 
letter is being sent to you in a separate mail message.

The VMS V5.4-0A special patch kit contains fixes for the following areas:

  o  DUDRIVER (Potential data corruption problem - QAR #1482)
  o  F11BXQP (QAR #1328)
  o  MARIAH Lurt Table 
  o  MARIAH warm start 
  o  VAX-9000 console security 
  o  VAX-9000 DEMNA driver selfstart 
  o  VAX-9000 SMP Stop/CPU
  o  VAX-9000 SMP powerfail restart


SSB MANUFACTURING/SHIPMENT PLANS:

The magnetic tape patch kit(part #QA-001AA-TM) will ship on the QA-001AA-HM 
kit (VMS V5.4 H kit for VAX 9000 customers) beginning on October 5, 1990. 
It will also be incorporated into any VMS V5.4 pre-release kits for the VAX 
9000 systems until VMS V5.4 FRS (October 5th).

The TK50 patch kit (part #QA-001AA-T5) or CDROM patch kit (part #QA-001AA-T8) 
will be added to the VAX 6000-5xx H/W information kit (Part #QZ-K33AA-EW).  

All three media kits will be available in the U.S. via the SSB Fastship program.
Part numbers of these kits are:

   o  QA-001AA-TM (magnetic tape and cover letter)    available Oct. 5, 1990
   o  QA-001AA-T5 (TK50 cartridge and cover letter)   available Oct. 5, 1990
   o  QA-001AA-T8 (CDROM and cover letter)            available Oct. 10, 1990

The SSB will use the Colorado Patch Kit process to log/track/ship the patch
to U.S. customers as necessary. Europe will set up a similar delivery 
mechanism with the European CSCs, and GIA CSCs will ensure that the patch 
kit is available in their regions. 
115.4Cover letter, postscript formatKERNEL::WRIGHTONodd numbered release = bug insertTue Oct 23 1990 16:211263
          <<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
                               -< CSGUK_SYSTEMS >-
================================================================================
Note 78.53                       VAX 9000 topic.                        53 of 78
KERNEL::WRIGHTON "odd numbered release = bug inse" 1255 lines   1-OCT-1990 23:48
              -< Covering letter for V5.4-0A (postscript format) >-
--------------------------------------------------------------------------------


%!PS-Adobe-2.0
%%Creator: VAX DOCUMENT V1.2B
%%+(+1 PSEUDOCONDENSE)
%%+Copyright 1986,1987,1988,1989,1990 DIGITAL EQUIPMENT CORPORATION.  
%%+All Rights Reserved.
%%DocumentFonts: (atend)
%%Pages: (atend)
%%EndComments
/DEC_DVC$dict where {					%FIND DICTIONARY
  pop
}{ %else
  /DEC_DVC$dict 300 dict def
} ifelse 
/BeginDVC$PSDoc {					%BEGIN DOCUMENT
  vmstatus pop pop 0 eq {
    DEC_DVC$dict begin  InitializeState
  }{ %else
    /DVC$PSJob save def  DEC_DVC$dict begin  InitializeState
    /DVC$PSFonts save def
  } ifelse
} def
/EndDVC$PSDoc {						%END DOCUMENT
% --- Preserving current page count ---
  vmstatus pop pop 0 eq {
    end
  }{ %else
    DVC$PSFonts restore  end  DVC$PSJob restore
  } ifelse
} def
%
DEC_DVC$dict begin
%
mark					% CREATE ISOLatin1 ENCODING
/ISOLatin1
  8#000 1 8#054 {StandardEncoding exch get} for 
  /minus
  8#056 1 8#217 {StandardEncoding exch get} for 
  /dotlessi 
  8#301 1 8#317 {StandardEncoding exch get} for 
  /space /exclamdown /cent /sterling /currency /yen /brokenbar /section 
  /dieresis /copyright /ordfeminine /guillemotleft /logicalnot /hyphen 
  /registered /macron /degree /plusminus /twosuperior /threesuperior /acute 
  /mu /paragraph /periodcentered /cedilla /onesuperior /ordmasculine 
  /guillemotright /onequarter /onehalf /threequarters /questiondown /Agrave 
  /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla /Egrave /Eacute 
  /Ecircumflex /Edieresis /Igrave /Iacute /Icircumflex /Idieresis /Eth /Ntilde 
  /Ograve /Oacute /Ocircumflex /Otilde /Odieresis /multiply /Oslash /Ugrave 
  /Uacute /Ucircumflex /Udieresis /Yacute /Thorn /germandbls /agrave /aacute 
  /acircumflex /atilde /adieresis /aring /ae /ccedilla /egrave /eacute 
  /ecircumflex /edieresis /igrave /iacute /icircumflex /idieresis /eth /ntilde
  /ograve /oacute /ocircumflex /otilde /odieresis /divide /oslash /ugrave 
  /uacute /ucircumflex /udieresis /yacute /thorn /ydieresis 
  /ISOLatin1 where not {256 array astore def} if 
cleartomark
%
/DECMCS ISOLatin1 256 array copy def
mark						% CREATE DECMCS ENCODING
  8#240 8#244 8#246 8#254 8#255 8#256 8#257 8#264 
  8#270 8#276 8#320 8#336 8#360 8#376 8#377
  counttomark
  {DECMCS exch /.notdef put} repeat		% STACK NOW CONTAINS MARK
  8#250 /currency   8#327 /OE   8#335 /Ydieresis   8#367 /oe   8#375 /ydieresis
  counttomark -1 bitshift			% DIVIDE BY 2
  {DECMCS 3 1 roll put} repeat			% STACK NOW CONTAINS MARK
cleartomark
%
/DOCPSE DECMCS 256 array copy def 
mark						% CREATE DOCPSE ENCODING
  8#055 /hyphen
  8#201 /bullet    8#202 /emdash     8#203 /endash    8#204 /dagger
  8#205 /daggerdbl 8#206 /registered 8#207 /trademark %8#210 /Delta
  8#211 /fi        8#212 /fl
  counttomark -1 bitshift			% DIVIDE BY 2
  {DOCPSE 3 1 roll put} repeat			% STACK NOW CONTAINS MARK
cleartomark
%
/reencodedict 10 dict def			%Local storage for "ReENCODE"
/ReENCODE {		% /basefont /newfont encoding ReENCODE
    /newencoding exch def	%ARG: NAME OF ENCODING VECTOR
    /newfontname exch def	%ARG: NEW NAME FOR FONT AFTER RE-ENCODING
    findfont
    /basefontdict exch def	%ARG: NAME OF FONT TO BE RE-ENCODED
    basefontdict maxlength dict begin	%CREATE AND OPEN NEW DICT
	basefontdict {		%COPY ENTRIES FROM BASE FONT DICT TO NEW ONE
	    1 index /FID ne {
		def		%IF NOT THE ONE WE'RE ENCODING, JUST COPY PTRS
	    } { %else
		pop pop		%IGNORE FID AND ENCODING FOR ONE WE'RE ENCODING
	    } ifelse
	} forall
	/FontName newfontname def	%DEFINE NEW NAME 
	/Encoding newencoding def	%DEFINE NEW ENCODING VECTOR
	newfontname currentdict definefont	%TURN IT INTO A PS FONT
	pop			%IGNORE MODIFIED DICT RETURNED BY DEFINEFONT
    end
} def
%
/cvsstr 64 string def
/tempmatrix matrix def
%
/BP {							% BEGIN PAGE
  /Magnification exch def
  /Colorsused 0 def
  /RVmatrix matrix def
  /DVC$PSPage save def
} def
%
/EP {DVC$PSPage restore} def				% END PAGE
%
/XP {				% EXIT PAGE (TEMPORARILY) TO ADD FONTS/CHARS
  % SAVE CURRENT POINT AND COLOR INFORMATION SO IT CAN BE RESET LATER
  matrix currentmatrix aload pop currentrgbcolor Colorsused
  /Xpos where {pop Xpos} {0} ifelse
  /Ypos where {pop Ypos} {0} ifelse
  /currentpoint cvx stopped {0 0 moveto currentpoint} if 
  /DVC$PSPage where {pop DVC$PSPage restore} if
  moveto
  /Ypos exch def  /Xpos exch def
  /Colorsused exch def setrgbcolor
  matrix astore setmatrix
} def
%
/RP {/DVC$PSPage save def} def		% RESUME PAGE
%
/PF {GlobalMode  LocalMode} def			% PURGE FONTS TO RECLAIM MEMORY
%
/GlobalMode {		% SWITCH TO BASE SAVE/RESTORE LEVEL, SAVING STATE
  RVmatrix aload pop
  PortraitMode  PaperWidth  PaperHeight  PxlResolution  Resolution 
  Magnification Ymax        Xorigin      Yorigin        RasterScaleFactor
  % SAVE CURRENTPOINT INFORMATION TO RESET LATER
  /currentpoint cvx stopped {0 0 moveto currentpoint} if 
  /DVC$PSPage where {pop DVC$PSPage restore} if
  DVC$PSFonts restore  RecoverState
} def
%
/RecoverState {					% PRESERVE STATE AT BASE LEVEL
  18 copy
  /Ypos exch def           /Xpos exch def        /RasterScaleFactor exch def
  /Yorigin exch def        /Xorigin exch def     /Ymax exch def
  /Magnification exch def  /Resolution exch def  /PxlResolution exch def
  /PaperHeight exch def    /PaperWidth exch def  /PortraitMode exch def
  matrix astore /RVmatrix exch def
  DoInitialScaling
  RVmatrix concat
  PortraitMode not {PaperWidth 0 SetupLandscape} if
  Xpos Ypos moveto
} def
%
/InitializeState {		% INITIALIZE STATE VARIABLES TO DEFAULT VALUES
  /Resolution 3600 def  /PxlResolution 300 def
  /RasterScaleFactor PxlResolution Resolution div def
  /PortraitMode true def
  /Magnification 1000 def  /Xorigin 0 def  /Yorigin 0 def
  /Xpos 0 def  /Ypos 0 def  /InitialMatrix matrix currentmatrix def
  /Colorsused 0 def /RVmatrix matrix def
} def
%
/LocalMode {		% SWITCH FROM BASE SAVE/RESTORE LEVEL, RESTORING STATE
  /Ypos exch def  /Xpos exch def  /RasterScaleFactor exch def
  /Yorigin exch def  /Xorigin exch def  /Ymax exch def
  /Magnification exch def  /Resolution exch def  /PxlResolution exch def
  /PaperHeight exch def  /PaperWidth exch def  /PortraitMode exch def
  matrix astore /RVmatrix exch def
  DoInitialScaling
  RVmatrix concat
  PortraitMode not {PaperWidth 0 SetupLandscape} if
  Xpos Ypos moveto
  /DVC$PSFonts save def  /DVC$PSPage save def
} def
%							% ABBREVIATIONS 
/S /show load def
/SV /save load def
/RST /restore load def
/Yadjust {Ymax exch sub} def
%
/SXY {		% (x,y) POSITION ABSOLUTE, JUST SET Xpos & Ypos, DON'T MOVE
  Yadjust  /Ypos exch def /Xpos exch def
} def
%
/XY {						% (x,y) POSITION ABSOLUTE
  Yadjust  2 copy /Ypos exch def /Xpos exch def  moveto
} def
%
/X {						% (x,0) POSITION ABSOLUTE
  currentpoint exch pop   2 copy /Ypos exch def /Xpos exch def  moveto
} def
%
/Y {						% (0,y) POSITION ABSOLUTE 
  currentpoint pop exch Yadjust  2 copy
  /Ypos exch def /Xpos exch def  moveto
} def
%
/xy {						% (x,y) POSITION RELATIVE
  neg rmoveto  currentpoint /Ypos exch def /Xpos exch def
} def
%
/x {						% (x,0) POSITION RELATIVE
  0 rmoveto  currentpoint /Ypos exch def /Xpos exch def
} def
%
/y {						% (0,y) POSITION RELATIVE
  0 exch neg rmoveto  currentpoint /Ypos exch def /Xpos exch def
} def
%
/R {						% DRAW A RULE
  /ht exch def  /wd exch def   gsave
% 0 setgray
  currentpoint  newpath  moveto
  0 ht rlineto  wd 0 rlineto
  0 ht neg rlineto  wd neg 0 rlineto
  closepath fill  grestore  wd 0 rmoveto
  currentpoint /Ypos exch def /Xpos exch def
} def
%
/RES {		% <PXL-file resolution(pix/inch)> <resolution(pix/inch)> RES
  /Resolution exch def  /PxlResolution exch def
  /RasterScaleFactor PxlResolution Resolution div def
  DoInitialScaling
} def
%
/DoInitialScaling {					% DO INITIAL SCALING
  InitialMatrix setmatrix  72 Resolution div dup scale
} def
%
/PM {		% <paper-height(pix)> <paper-width(pix)> PM
  XP
    /PaperWidth exch def  /PaperHeight exch def
    /Ymax PaperHeight def /PortraitMode true def
    DoInitialScaling
  RP
} def  
%
/SetupLandscape {translate  90 rotate} def
/LM {		% <paper-height(pix)> <paper-width(pix)> LM 
  XP
    /PaperWidth exch def  /PaperHeight exch def
    /Ymax PaperWidth def  /PortraitMode false def
    DoInitialScaling PaperWidth 0 SetupLandscape
  RP
} def  
%
/MAG {						% CHANGE MAGNIFICATION SETTING
  XP  /Magnification exch def  RP
} def
%
/SPB {		%  <xoffset><yoffset>SPB - BEGIN "\SPECIAL" MODE
  Yadjust /Yorigin exch def /Xorigin exch def
  currentrgbcolor Colorsused
  GlobalMode Xorigin Yorigin translate
  Resolution 72 div dup scale			% RESTORE DEFAULT SCALING
  Magnification 1000 div dup scale		% ADJUST FOR ANY MAGNIFICATION
  /Xpos Xpos 72 Resolution div mul 1000 Magnification div mul def
  /Ypos Ypos 72 Resolution div mul 1000 Magnification div mul def
  /spsavobj save def	%SAVE STATE & STACK DEPTH FOR CLEANUP AFTER FIGURE
  /showpage {} def	%DISABLE DURING FIGURE; `RESTORE' WILL BLOW DEF AWAY
  /DEC$EDMS_setrgbcolor /setrgbcolor load def	% save standard definition
  /setrgbcolor {				% create new definition
    /DEC$EDMS_SEPARATE_COLORS where		% if separating colors
    { pop DEC$EDMS_SEPARATE_COLORS 0 ne		% and not on color pass 0
      { pop pop pop 1 1 1 } if			% ...then write white
     } if
    DEC$EDMS_setrgbcolor			% set color as now specified
  } def
  /DEC$EDMS_image /image load def		% save standard definition
  /image {					% create new definition
    /DEC$EDMS_SEPARATE_COLORS where		% if separating colors
    { pop DEC$EDMS_SEPARATE_COLORS 0 ne		% and not on color pass 0
      { gsave					% ...save current device state
        nulldevice				% ...make no marks
        DEC$EDMS_image				% ...process the image
        grestore				% ...restore old device state
      }
      { DEC$EDMS_image } ifelse			% if on color pass 0 - image
    }
    { DEC$EDMS_image } ifelse			% if not separating colors - image
  } def  mark
} def
%
/SPE {		% SPE - END "\SPECIAL" MODE
  cleartomark
  spsavobj restore 
  1000 Magnification div dup scale	% UN-ADJUST FOR ANY MAGNIFICATION
  72 Resolution div dup scale		% RESTORE DEFAULT INTERNAL SCALING
  LocalMode
  /Colorsused exch def setrgbcolor
} def
%
/PP
%
% If DEC$EDMS_MAKE_FILM is defined, it will add the crop & alignment marks,
% and the document name, page number, & ink color identifiers to the page.
%
% Formal Arguments:	None
%
% Referenced Variables: DocumentName
%			Colorsused
%			Currentpagecount
% 			DEC$EDMS_MAKE_FILM
%
% Referenced Procedures: AlignMark
%
% Side Effects: Leaves the current font as Helvetica 8 point.
%		Creates the variable "junkstr".
%
{ /PageNumber exch def
  /DEC$EDMS_MAKE_FILM where					% if making film...
  { pop 2 DEC$EDMS_SEPARATE_COLORS exp cvi Colorsused and 0 ne	% and if the correct separation
    { /Helvetica findfont 400 scalefont setfont
      20 setlinewidth 0 setgray
      PaperWidth 150 add PaperHeight 100 add moveto		% show the ink color
      (Ink: ) show DEC$EDMS_COLOR_NAMES DEC$EDMS_SEPARATE_COLORS get show
      PaperWidth 150 add PaperHeight 600 add moveto
      (Page: ) show						% show the page number
      /junkstr 4 string def PageNumber junkstr cvs show
      ( of ) show DEC$EDMS_TOTAL_PAGES junkstr cvs show
      150 PaperHeight 100 add moveto				% show the document name
      (Document: ) show DEC$EDMS_DOCUMENT_ID show
      150 -500 moveto 						% show ownership text
      (This film is the property of Digital Equipment Corporation) show stroke

      /mask 15							% all crop marks on by default
      /DEC$EDMS_SUPPRESS_CROPMARKS where				% if defined, xor in the suppression mask
          { pop DEC$EDMS_SUPPRESS_CROPMARKS xor } if def

      mask 1 and 1 eq
        { PaperWidth PaperHeight moveto				% Upper Right
          450 0 rmoveto 1350 0 rlineto -1800 1800 rmoveto 0 -1350 rlineto } if

      mask 2 and 2 eq
        { PaperWidth 0 moveto					% Lower Right
          450 0 rmoveto 1350 0 rlineto -1800 -1800 rmoveto 0 1350 rlineto } if

      mask 4 and 4 eq
        { 0 0 moveto						% Lower Left
          -450 0 rmoveto -1350 0 rlineto 1800 -1800 rmoveto 0 1350 rlineto } if

      mask 8 and 8 eq
        { 0 PaperHeight moveto					% Upper Left
          -450 0 rmoveto -1350 0 rlineto 1800 1800 rmoveto 0 -1350 rlineto } if
      stroke

      /mask 15							% all registration marks on by default
      /DEC$EDMS_SUPPRESS_REGMARKS where				% if defined, xor in the suppression mask
          { pop DEC$EDMS_SUPPRESS_REGMARKS xor } if def

      mask 1 and 1 eq						% Top Center
         { gsave PaperWidth 2 div PaperHeight
	   /DEC$EDMS_POSITION_REGMARKS where
	     { pop DEC$EDMS_POSITION_REGMARKS -50 mul add } if
	   translate AlignMark grestore } if

      mask 2 and 2 eq						% Right Center
        { gsave PaperWidth
	 /DEC$EDMS_POSITION_REGMARKS where
	  { pop DEC$EDMS_POSITION_REGMARKS -50 mul add } if
	  PaperHeight 2 div translate AlignMark grestore } if

      mask 4 and 4 eq						% Bottom Center
        { gsave PaperWidth 2 div 0
	 /DEC$EDMS_POSITION_REGMARKS where
	  { pop DEC$EDMS_POSITION_REGMARKS 50 mul add } if
	 translate AlignMark grestore } if

      mask 8 and 8 eq						% Left Center
        { gsave 0
	 /DEC$EDMS_POSITION_REGMARKS where
	  { pop DEC$EDMS_POSITION_REGMARKS 50 mul add } if
	 PaperHeight 2 div translate AlignMark grestore } if
      showpage
    }
    { erasepage } ifelse
  }
  { showpage } ifelse
} def
/CLRP {erasepage} def
%
/DMF {		%  /font-name <point-size(pix)> DMF
  /psz exch def  /nam exch def  nam findfont psz scalefont setfont
} def
%
/concatnam {	%  /abcd (xxx) concatnam  ==> /abcdxxx
  /xxx exch def  /nam exch def
  /namstr nam cvsstr cvs def
  /newnam namstr length xxx length add string def
  newnam 0 namstr putinterval
  newnam namstr length xxx putinterval
  newnam cvn 
} def
%
/strip {	%  /abcdef 2 strip ==> /cdef
  /num exch def  /nam exch def
  /namstr nam cvsstr cvs def
  /newlen namstr length num sub def
  namstr num newlen getinterval  cvn
} def
%		ROUTINES TO HANDLE PACKING/UNPACKING NUMBERS
/PackHW {	% <target> <pos> <num> PackHW --> <new target>
  /num exch def  /pos exch def  /target exch def
  num 16#0000FFFF and 1 pos sub 16 mul bitshift  target or
} def
/PackByte {	% <target> <pos> <num> PackByte --> <new target>
  /num exch def  /pos exch def  /target exch def
  num 16#000000FF and 3 pos sub 8 mul bitshift   target or
} def
/UnpkHW {	%  <pos> <num> UnpkHW --> <unpacked value>
  /num exch def  /pos exch def
  num 1 pos sub -16 mul bitshift 16#0000FFFF and
  dup 16#00007FFF gt {16#00010000 sub} if
} def
/UnpkByte {	%  <pos> <num> UnpkByte --> <unpacked value>
  /num exch def  /pos exch def
  num 3 pos sub -8 mul bitshift 16#000000FF and
  dup 16#0000007F gt {16#00000100 sub} if
} def
%
% FOR POSTSCRIPT FONTS, LOOK AT SIZE REQUESTED.  IF IT HAS A DECIMAL REMAINDER
% EQUIVALENT TO .001-.009 POINTS (I.E., .050-.450 VAXDOC UNITS), THAT'S A FLAG 
% TO STRETCH IT VERTICALLY BY ADDING 1-9 EXTRA POINTS TO THE VERTICAL SCALING.
%
/TESTING false def
%
/ps-scalefont {
		% save requested size - as entered and as integer
    dup /x-size exch def cvi /x-int exch def
		% calc decimal remainder, mul x 1000, round
    x-size x-int sub 1000 mul round cvi /remainder exch def
		% see how we scale...
    remainder 50 lt remainder 450 gt or {
		% scale isomorphically
	/ystretch 0 def
	x-size scalefont
    } {
		% scale anamorphically
	/ystretch remainder def
	x-int ystretch add /y-size exch def
	[x-int 0 0 y-size 0 0] makefont
    } ifelse
		%
    TESTING {
	(\nSIZE ) print x-size 12 string cvs print 
	(\tINT ) print x-int 12 string cvs print 
	( REM ) print remainder 12 string cvs print
	( +Y ) print ystretch 12 string cvs print
	( =\t) print
	ystretch 0 eq {
	    x-size 12 string cvs print
	    ( scalefont) print
	} {
	    ([) print x-int 12 string cvs print 
	    ( 0 0 ) print y-size 12 string cvs print
	    ( 0 0] makefont) print
	} ifelse
    } if
} def
%
/DPSF {		% /procname size /fontname DPSF
    findfont exch ps-scalefont [ exch /setfont cvx ] cvx def
} def
%
/PXLBuildCharDict 17 dict def
/CMEncodingArray 256 array def
0 1 255 {CMEncodingArray exch dup cvsstr cvs cvn put} for
/RasterConvert {RasterScaleFactor div} def
/TransformBBox {
  aload pop
  /BB-ury exch def  /BB-urx exch def  /BB-lly exch def  /BB-llx exch def
  [ BB-llx RasterConvert BB-lly RasterConvert 
    BB-urx RasterConvert BB-ury RasterConvert ]
} def
/RunLengthToRasters {
  % none yet
} def
/GenerateRasters {			% GENERATE RASTERS FOR "IMAGEMASK"
  rasters  runlength 1 eq {RunLengthToRasters} if
} def
%
/int-dict-name {int (-dict) concatnam} def
/int-dict {int (-dict) concatnam cvx load} def
%
/DefinePXLFont {
	%  <int-font-name><ext-font-name><pt-sz(pix)><PXL mag><num-chars>...
	%  ...[llx lly urx ury]<newfont-fg>DefinePXLFont
  /newfont exch def  /bb exch def      /num exch def  /psz exch def
  /dsz exch def      /pxlmag exch def  /ext exch def  /int exch def
  /fnam ext (-) concatnam pxlmag cvsstr cvs concatnam def
  newfont not {
    int-dict-name 13 dict def
    int-dict begin
      /FontType 3 def  /FontMatrix [ 1 dsz div 0 0 1 dsz div 0 0 ] def
      /FontBBox bb TransformBBox def  /Encoding CMEncodingArray def
      /CharDict 1 dict def  CharDict begin  /Char-Info num array def  end
      /BuildChar {
        PXLBuildCharDict begin
          /char exch def  /fontdict exch def
          fontdict /CharDict get /Char-Info get char get aload pop
          /rasters exch def  /PackedWord1 exch def
          0 PackedWord1 UnpkHW 16#7FFF ne {
	    /PackedWord2 exch def  /wx 0 PackedWord1 UnpkHW def
            /rows 2 PackedWord1 UnpkByte def  /cols 3 PackedWord1 UnpkByte def
            /llx 0 PackedWord2 UnpkByte def   /lly 1 PackedWord2 UnpkByte def
            /urx 2 PackedWord2 UnpkByte def   /ury 3 PackedWord2 UnpkByte def
	  }{ %else
	    /PackedWord2 exch def  /PackedWord3 exch def  /PackedWord4 exch def
            /wx 1 PackedWord1 UnpkHW def    /rows 0 PackedWord2 UnpkHW def
            /cols 1 PackedWord2 UnpkHW def  /llx 0 PackedWord3 UnpkHW def
            /lly 1 PackedWord3 UnpkHW def   /urx 0 PackedWord4 UnpkHW def
            /ury 1 PackedWord4 UnpkHW def
          } ifelse
          rows 0 lt {
	    /rows rows neg def /runlength 1 def
	  }{ %else
	    /runlength 0 def
	  } ifelse
          wx 0
          llx RasterConvert lly RasterConvert 
          urx RasterConvert ury RasterConvert setcachedevice
          rows 0 ne {
	    gsave
	      cols rows true  RasterScaleFactor 
              0 0 RasterScaleFactor neg llx .5 add neg ury .5 add 
              tempmatrix astore  GenerateRasters imagemask
            grestore
          } if
        end
      } def
    end
    fnam int-dict definefont pop 
  } if 
  int-dict-name fnam findfont psz scalefont def
  currentdict int [ int-dict /setfont cvx ] cvx put
} def 
/PXLF { true  DefinePXLFont} def	% SIGNAL THAT FONT IS ALREADY LOADED
/PXLNF {false  DefinePXLFont} def	% SIGNAL THAT FONT IS NOT ALREADY LOADED
%
/PXLC {	% <int-font-name><code><wx><llx><lly><urx><ury>...
	% ...<rows><cols><runlength><rasters>PXLC
  /rasters exch def  /runlength exch def  /cols exch def  /rows exch def
  /ury exch def      /urx exch def        /lly exch def   /llx exch def
  /wx exch def       /code exch def       /int exch def
  % SEE IF LONG OR SHORT FORMAT IS REQUIRED
  true cols CKSZ rows CKSZ ury CKSZ urx CKSZ lly CKSZ llx CKSZ 
  TackRunLengthToRows {
    int-dict /CharDict get /Char-Info get code 
    [ 0 0 llx PackByte 1 lly PackByte 2 urx PackByte 3 ury PackByte
      0 0 wx PackHW 2 rows PackByte 3 cols PackByte rasters ] put
  }{ %else
    int-dict /CharDict get /Char-Info get code 
    [ 0 0 urx PackHW 1 ury PackHW   0 0 llx PackHW 1 lly PackHW
      0 0 rows PackHW 1 cols PackHW 0 0 16#7FFF PackHW 1 wx PackHW rasters ] put
  } ifelse
} def
%
/CKSZ {abs 127 le and} def
/TackRunLengthToRows {runlength 0 ne {/rows rows neg def} if} def
%
/PLOTC {
  % <wx><dsz><psz><llx><lly><urx><ury><rows><cols><runlength><rasters>PLOTC
  /rasters exch def  /runlength exch def  /cols exch def  /rows exch def
  /ury exch def      /urx exch def        /lly exch def   /llx exch def
  /psz exch def      /dsz exch def        /wx exch def
  % "PLOT" A CHARACTER'S RASTER PATTERN
  rows 0 ne {
    gsave
      currentpoint translate  psz dsz div dup scale
      cols rows true  RasterScaleFactor 0 0 RasterScaleFactor 
      neg llx .5 add neg ury .5 add  tempmatrix astore
      GenerateRasters imagemask
    grestore
  } if
  wx x
} def
%
/AlignMark
%
% This procedure draws an alignment mark centered on the coordinate system
% origin. If the variable DEC$EDMS_SEPARATE_COLORS = 0 then a "positive"
% alignment mark is drawn. If DEC$EDMS_SEPARATE_COLORS <> 0 then a "negative"
% alignment mark is drawn. 
%
% Formal Arguments: NONE
%
% Referenced Variables: DEC$EDMS_SEPARATE_COLORS
%
% Referenced Procedures: NONE
%
% Side Effects: NONE
%
{ DEC$EDMS_SEPARATE_COLORS 0 eq
  { 0 0 300 0 360 arc
    0 -450 moveto 0 450 lineto -450 0 moveto 450 0 lineto stroke }
  { 0 0 450 0 360 arc fill 1 setgray 0 0 300 0 360 arc 
    0 -450 moveto 0 450 lineto -450 0 moveto 450 0 lineto stroke 0 setgray }
  ifelse
} def


/SC
% If not making film, the following procedure sets the current color using the
% RGB color model. If making film, the procedure notes the "color pass" and,
% if the specified color index matches the color pass, subsequent marks are
% written in black. If the specified color index does not match the color pass,
% marks are written in white. Use of colors on individual pages is also tracked
% to allow pages that don't use a particular color to be suppressed on that
% color pass (by the code in the /PP routine).
%
% Formal Arguments: color index (on stack)
%
% Referenced Variables: Colorsused
%			DEC$EDMS_SEPARATE_COLORS
%			DEC$EDMS_SUPPRESS_COLOR
%
% Referenced Procedures: NONE
%
% Side Effects: Modifies the variable Colorsused to record use of the color.
%
{ /DEC$EDMS_SUPPRESS_COLOR where		% if suppressing color
  { pop 0 setgray pop }				% .then set "color" to Black 
  { /DEC$EDMS_SEPARATE_COLORS where		% .else if separating colors
    { pop dup DEC$EDMS_SEPARATE_COLORS eq	% ..and if on this color pass
      { 0 setgray /Colorsused Colorsused	% ...then write black (do write)
        2 3 index exp cvi or def }		% ...and note use of the "color"
      { 1 setgray } ifelse pop }		% ...else write white (don't write)
    { dup (  ) cvs dup length 15 add string     % ..using the color index,
      /tstr exch def                            % ..build up the name of the
      tstr 0 (DEC$EDMS_COLOR_) putinterval      % ..potential external color
      tstr exch 15 exch putinterval             % ..name procedure
      tstr cvn where                            % ..and see if it is defined
      { pop pop tstr cvn cvx exec }             % ...if it is, execute it
      { DEC$EDMS_COLOR_ARRAY exch get		% ..else execute the internal
        exec } ifelse				% ..color setting procedure
    } ifelse
  } ifelse
} def

/RV                                          % .. gross recto/verso translate
{ /DEC$EDMS_ENABLE_RECTOVERSO where
      { pop
	/RVmatrix DEC$EDMS_ENABLE_RECTOVERSO 50 mul 0 matrix translate def
	RVmatrix concat
      } if
} def

end  %DEC_DVC$dict
%%EndProlog
%%BeginSetup
/DEC$EDMS_MAKE_FILM where	% if we are making film...
 { pop				% ..clean up the stack
   54 dup translate		% ..make room for the film info
 } if
BeginDVC$PSDoc
/PaperWidth 8.500 Resolution mul def
/PaperHeight 11.000 Resolution mul def
/Ymax PaperHeight def
CLRP 300 3600 RES
%>  Postamble of file WORK1:[GEBURA.EATME]MUP-COVER.DVI_PS.
% DefineFont:F171 Category:15 Pointsize:14
% DownloadPSFont
%!PS-Adobe-2.0
%%Title: PostScript Digital Logo Font, v1.1
%%Creator: Ned Batchelder
%%CreationDate: 9-Nov-87
%%DocumentFonts: Symbol
%%DocumentSuppliedFonts: DigitalLogo
%%EndComments
%
%		    DIGITAL INTERNAL USE ONLY
% 
% INTRODUCTION:
% This rendition of the Digital logo was prepared by Ned Batchelder using 
% Adobe Illustrator and hand manipulation of the resulting PostScript code.
% Photographic masters of the logo were obtained from David Comberg in the
% Graphic Design Group. Additional consultation was provided by Elliot
% Hendrickson, one of the original designers of the logo.
% 
% USE:
% This file defines a new PostScript font, called /DigitalLogo. It consists
% of three characters. (d) is the entire Digital logo, (t) is a small
% trademark symbol, and (T) is a large trademark symbol. The font is designed
% so that the argument to scalefont is the height of the logo. There is no
% extra white space around the logo at all. The trademarks are designed to be
% shown right after the logo, and they align themselves. The only correct
% strings to show with this font are (d), (dt), and (dT). There is an entry
% (named GapWidth) in the font dictionary which gives the unscaled width of
% the gap between the blocks. This distance is given because it is used as a
% unit to determine how much space to leave around the logo.
% 
% HISTORY:
% The logo was designed in 1957 by Elliot Hendrickson, who was then working
% as an independent designer. He was contracted by DEC to do a brochure, and
% DEC wanted a logo to accompany it. The logo up to then had been the letters
% DEC in blocks the shape of the plug-in cards that DEC had been producing.
% Elliot re-worked the logo, incorporating letters which were hand-drawn for 
% the purpose by Arthur Hover(?). The logo has been maintained since then in 
% conventional technology, ie, film masters. There was at least one reworking 
% of the logo at some point.
% 
% The masters I received had a number of interesting features. The boxes were
% not all the same width, and there seemed to be no logic to which boxes were
% wider. The 'g' was the narrowest, and the 'i' and 'l' were second widest.
% Also, the two 'i's were not exactly the same shape. On ten-inch masters,
% (one box to an 8�x11 sheet), the boxes were not rectangles, but were very
% slightly tapered in wierd ways. I assume that the tapering is the result of
% too many reproductions, but the difference in widths may have been
% deliberate at some time. Elliot reports that when he drew it, all boxes
% were the same width. I have retained the different widths in my version,
% since the experts I had at hand did not seem to think I should make them
% uniform.
% 
% Please feel free to use this logo, but keep in mind the following:
% 
% 1. This code is for INTERNAL USE ONLY.
% 2. I am not entirely happy with the final shapes of the letters, and am
% hoping to improve them. Please allow for future updates to this code.
% 3. Only use this logo within the guidelines of the Corporate Identity
% program. If you use this font precisely as is, you can't get in much
% trouble. Don't take the shapes and do strange things with them. 
% In particular, the Identity states that the logo is a one-color logo: The
% letters are actually holes in the blocks, through which the background can
% be seen. Do not modify this code so that the letters are always white.
% 
% Edit history:
% 
% 21-Sep-87 nmb	    Created as a standalone file with demo.
%  6-Nov-87 nmb	    Converted to font form.
%  9-Nov-87 nmb	    Removed // uses for compatibility with LW Classics
%

%%BeginFont: DigitalLogo
10 dict begin

/FontInfo 3 dict def
FontInfo begin
    /Notice
(The Digital logo is a registered trademark of Digital Equipment Corporation.)
    def
    /FullName (Digital logo) def
    /version (1.1) def
    end

/FontType 3 def				% This is a user-defined font
/FontMatrix matrix def			% Use an identity transform
/FontBBox [ 0 0 3.383 1 ] def		% Logo itself is biggest
/GapWidth .070 def			% The width of the gap between boxes

/Encoding 256 array def
0 1 255 { Encoding exch /.notdef put } bind for

Encoding
dup (d) 0 get /DEC-logo put		% (d) gives logo
dup (t) 0 get /smalltrademark put	% (t) gives small trademark
    (T) 0 get /largetrademark put	% (T) gives large trademark

/Work 15 dict def			% for doing work in font.

/BuildChar {
    exch begin				% Use the font dictionary
	Work begin
	    Encoding exch get		% Look up the character name
	    load			% Pull out the procedure
	    exec			% Run it.
	    end				% Work
	end				% fontdict
    } bind def

Work begin

/.notdef {} def

%
% - `DEC-logo' -
%
% Images a DEC logo with the lower left corner at the current origin, with a
% height of one unit, in the current color.
% 

/m /moveto load def
/l /lineto load def
/c /curveto load def

/DEC-logo {
    3.383 0 0 0 3.383 1 setcachedevice
    {	% D
	% d counter
	.2930 .3513 m
	.2932 .3217 .2587 .2758 .2167 .2757 c
	.1719 .2759 .1280 .3165 .1280 .3977 c
	.1280 .4801 .1718 .5225 .2153 .5227 c
	.2587 .5225 .2932 .4760 .2930 .4407 c
	closepath
	% d outside
	.2953 .5787 m
	.2953 .7600 l
	.3843 .7600 l
	.3843 .1960 l
	.2923 .1960 l
	.2923 .2220 l
	.2848 .2144 .2531 .1813 .1990 .1813 c
	.1426 .1812 .0417 .2282 .0417 .3977 c
	.0417 .5414 .1171 .6157 .2067 .6157 c
	.2399 .6157 .2725 .6039 .2953 .5787 c
	closepath
	% d box
	.432 0.0 m
	.432 1.0 l
	.000 1.0 l
	.000 0.0 l
	closepath
	} exec
    {	% I
	% i box
	.927 0.0 m
	.927 1.0 l
	.502 1.0 l
	.502 0.0 l
	closepath
	% i body
	.6695 .196 m
	.6695 .600 l
	.7595 .600 l
	.7595 .196 l
	closepath
	% i dot
	.6695 .655 m
	.6695 .755 l
	.7595 .755 l
	.7595 .655 l
	closepath
	} exec
    {	% G
	% g counter
	1.2813 .4478 m
	1.2813 .4837 1.2409 .5208 1.2035 .5208 c
	1.1713 .5208 1.1215 .5003 1.1215 .4084 c
	1.1215 .3105 1.1827 .2962 1.2030 .2962 c
	1.2433 .2962 1.2813 .3239 1.2813 .3667 c
	closepath
	% g box
	0.997 1.0 m
	1.415 1.0 l
	1.415 0.0 l
	0.997 0.0 l
	closepath
	% g outside
	1.2822 .5609 m
	1.2729 .5742 1.2424 .6044 1.1988 .6044 c
	1.1311 .6043 1.0367 .5652 1.0367 .3955 c
	1.0368 .2617 1.1437 .2168 1.1876 .2168 c
	1.2350 .2167 1.2702 .2443 1.2798 .2547 c
	1.2798 .2126 l
	1.2798 .1815 1.2479 .1511 1.1945 .1511 c
	1.1485 .1512 1.1437 .1807 1.1437 .1953 c
	1.0497 .1953 l
	1.0497 .1486 1.0798 .0804 1.1888 .0803 c
	1.2864 .0803 1.3186 .1176 1.3325 .1316 c
	1.3442 .1434 1.3617 .1758 1.3617 .2017 c
	1.3617 .6 l
	1.2823 .6 l
	closepath
	} exec
    {	% I
	% i box
	1.910 0.0 m
	1.910 1.0 l
	1.485 1.0 l
	1.485 0.0 l
	closepath
	% i body
	1.6525 .196 m
	1.6525 .6 l
	1.7425 .6 l
	1.7425 .196 l
	closepath
	% i dot
	1.6525 .655 m
	1.6525 .755 l
	1.7425 .755 l
	1.7425 .655 l
	closepath
	} exec
    {	% T
	% t
	2.2128 .7525 m
	2.1305 .7525 l
	2.1305 .6071 l
	2.0874 .6071 l
	2.0874 .5396 l
	2.1305 .5396 l
	2.1305 .2852 l
	2.1305 .2367 2.1554 .1986 2.2248 .1987 c
	2.2573 .1987 2.2560 .1985 2.2842 .2034 c
	2.2842 .2874 l
	2.2658 .2842 2.2601 .2829 2.2511 .2832 c
	2.2338 .2837 2.2128 .2898 2.2128 .3206 c
	2.2128 .5395 l
	2.2780 .5395 l
	2.2780 .6071 l
	2.2128 .6071 l
	closepath
	% t box
	2.404 0.0 m
	1.980 0.0 l
	1.980 1.0 l
	2.404 1.0 l
	closepath
	} exec
    {	% A
	% a box
	2.474 0.0 m
	2.474 1.0 l
	2.888 1.0 l
	2.888 0.0 l
	closepath
	% a outside
	2.5439 .4728 m
	2.6210 .4728 l
	2.6210 .5138 2.6422 .5353 2.6826 .5353 c
	2.7470 .5354 2.7449 .5067 2.7448 .4708 c
	2.7050 .4553 2.7087 .4557 2.6480 .4419 c
	2.5709 .4241 2.5237 .3911 2.5236 .3112 c
	2.5237 .2331 2.5793 .1914 2.6420 .1915 c
	2.7048 .1914 2.7178 .2117 2.7438 .2290 c
	2.7438 .1978 l
	2.8422 .1978 l
	2.8190 .2352 2.8251 .2425 2.8249 .2706 c
	2.8250 .2926 2.8249 .5080 2.8249 .5080 c
	2.8250 .5507 2.8028 .5768 2.7883 .5855 c
	2.7521 .6071 2.7074 .6097 2.6826 .6098 c
	2.5945 .6096 2.5438 .5653 2.5439 .4728 c
	closepath
	% a counter
	2.7448 .3946 m
	2.7448 .3401 l
	2.7448 .3152 2.7145 .2670 2.6550 .2669 c
	2.6260 .2668 2.6098 .2883 2.6097 .3162 c
	2.6098 .3442 2.6335 .3657 2.6536 .3697 c
	2.6745 .3739 2.7226 .3862 2.7448 .3946 c
	closepath
	} exec
    {	% L
	% l box
	3.383 0.0 m
	3.383 1.0 l
	2.958 1.0 l
	2.958 0.0 l
	closepath
	% l
	3.1255 .196 m
	3.1255 .765 l
	3.2155 .765 l
	3.2155 .196 l
	closepath
	} exec
    fill
    } bind def

%
% % pct `trademark' --
%
% Borrow the sans-serif trademark symbol from /Symbol. AFM file says:
%	C 228 ; WX 786 ; N trademarksans ; B 5 293 725 673 ;
% We scale it down to pct percent of the height of the logo and superscript 
% it some, and voila!
%

/trademark {
    /s exch .380 div def
    /w s .725 mul .070 add def
    /u 1 .673 s mul sub def
    w 0 0 u w 1 setcachedevice
    /Symbol findfont s scalefont setfont
    .070 u m					% Superscript it
    (\344) show
    } bind def

% 
% These are two different trademarks (just different sizes).
%

/smalltrademark { .15 trademark } def
/largetrademark { .25 trademark } def

end						% Work dictionary

currentdict					% Get the font dict
end						% Close it up
/DigitalLogo exch definefont pop		% Define the font.

%%EndFont
% EndDownloadPSFont
/F171 700.0 /DigitalLogo DPSF
% DefineFont:F159 Category:10 Pointsize:8
/NewCenturySchlbk-Roman /NewCenturySchlbk-Roman@DOCPSE DOCPSE ReENCODE
/F159 400.0 /NewCenturySchlbk-Roman@DOCPSE DPSF
% DefineFont:F153 Category:10 Pointsize:10
/NewCenturySchlbk-Bold /NewCenturySchlbk-Bold@DOCPSE DOCPSE ReENCODE
/F153 500.0 /NewCenturySchlbk-Bold@DOCPSE DPSF
% DefineFont:F152 Category:10 Pointsize:10
/NewCenturySchlbk-Italic /NewCenturySchlbk-Italic@DOCPSE DOCPSE ReENCODE
/F152 500.0 /NewCenturySchlbk-Italic@DOCPSE DPSF
% DefineFont:F151 Category:10 Pointsize:10
/F151 500.0 /NewCenturySchlbk-Roman@DOCPSE DPSF
% DefineFont:F98 Category:10 Pointsize:9
/Courier /Courier@DOCPSE DOCPSE ReENCODE
/F98 450.0 /Courier@DOCPSE DPSF
% DefineFont:F36 Category:10 Pointsize:10
/Helvetica-Bold /Helvetica-Bold@DOCPSE DOCPSE ReENCODE
/F36 500.0 /Helvetica-Bold@DOCPSE DPSF
% DefineFont:F34 Category:10 Pointsize:10
/Helvetica /Helvetica@DOCPSE DOCPSE ReENCODE
/F34 500.0 /Helvetica@DOCPSE DPSF
% DefineFont:F32 Category:10 Pointsize:11
/F32 550.0 /Helvetica-Bold@DOCPSE DPSF
% DefineFont:F29 Category:10 Pointsize:12
/Helvetica-BoldOblique /Helvetica-BoldOblique@DOCPSE DOCPSE ReENCODE
/F29 600.0 /Helvetica-BoldOblique@DOCPSE DPSF
%%BeginDEC$EDMSInfo
/DEC$EDMS_DOCUMENT_ID () def
/DEC$EDMS_COLOR_NAMES [ (BLACK) (BLACK) (BLACK) (BLACK) ] def
/DEC$EDMS_COLOR_ARRAY [
  { 0 setgray }         %color 0 procedure
  { 0 setgray }         %color 1 procedure
  { 0 setgray }         %color 2 procedure
  { 0 setgray }         %color 3 procedure
] def
/DEC$EDMS_TOTAL_PAGES 0 def
%%EndDEC$EDMSInfo
/DEC$EDMS_MAKE_FILM where
{ pop /DEC$EDMS_SEPARATE_COLORS where
  { pop }
  { (ERROR - DEC$EDMS_MAKE_FILM requires DEC$EDMS_SEPARATE_COLORS be defined) = quit } ifelse
} if
/DEC$EDMS_SEPARATE_COLORS where
{ pop /DEC$EDMS_SUPPRESS_COLOR where
  { pop (ERROR - DEC$EDMS_SEPARATE_COLORS and DEC$EDMS_SUPPRESS_COLOR are mutually exclusive) = quit } if
  DEC$EDMS_SEPARATE_COLORS 1 gt { (ERROR - No such color used in this file) = quit } if
} if
/DVC$PSFonts save def
%%EndSetup
%
%%Page: 1 1
%%BeginPageSetup
%%EndPageSetup
%%PageFonts: (atend)
%%PageCustomColors: (atend)
1000 BP PaperHeight PaperWidth PM 0 0 XY 
%%BeginCustomColor: 0 
0 SC 3899 4297 XY F171(dt)S 3899 5792 XY F29(Cover)S 199 x(Letter)S
200 x(for)S 199 x(VMS)S 199 x(V)S -23 x(ersion)S 200 x(5.4-0)S 2 x(A)S
198 x(Update)S 3899 X 896 y F36(A)S -37 x(V)S -27 x(\203PEW3A\203TE)S
3899 9279 XY F151(The)S 193 x(VMS)S 192 x(V)S -46 x(ersion)S 192 x(5.4-0A)S
193 x(Update)S 192 x(contains)S 192 x(necessary)S 193 x(software)S 192 x
(enhancements)S 193 x(for)S 192 x(the)S 193 x(V)S -56 x(AX)S 192 x(9000)S
192 x(and)S 3899 X 597 y(the)S 141 x(V)S -55 x(AX)S 141 x(6000\203500)S
141 x(series)S 140 x(of)S 142 x(computers.)S 213 x(If)S 141 x(you)S
143 x(have)S 142 x(a)S 141 x(V)S -55 x(AX)S 140 x(9000)S 142 x(or)S
141 x(V)S -55 x(AX)S 140 x(6000\203500)S 141 x(computer)S -36 x(,)S
147 x(you)S 142 x(need)S 3899 X 598 y(to)S 164 x(apply)S 165 x(the)S
164 x(VMS)S 164 x(V5.4-0A)S 164 x(Update)S 164 x(after)S 164 x(installing)S
165 x(or)S 165 x(upgrading)S 165 x(to)S 165 x(V)S -47 x(ersion)S 165 x
(5.4)S 165 x(of)S 164 x(the)S 165 x(VMS)S 164 x(operating)S 3899 X 598 y
(system.)S 221 x(Follow)S 166 x(these)S 166 x(instructions:)S 3899 X
897 y F36(1.)S 631 x F151(If)S 183 x(you)S 183 x(are)S 184 x(installing)S
183 x(VMS)S 182 x(V)S -46 x(ersion)S 183 x(5.4,)S 188 x(follow)S 183 x
(the)S 183 x(instructions)S 183 x(in)S 183 x(Chapter)S 183 x(3)S 183 x
(of)S 183 x(the)S 183 x F152(VMS)S 183 x(V)S -64 x(ersion)S 4945 X 597 y
(5.4)S 166 x(Upgrade)S 167 x(and)S 167 x(Installation)S 167 x(Manual)S
F151(.)S 4945 X 897 y(If)S 117 x(you)S 118 x(are)S 117 x(upgrading)S
119 x(to)S 117 x(VMS)S 116 x(V)S -46 x(ersion)S 118 x(5.4,)S 127 x(follow)S
117 x(the)S 117 x(instructions)S 117 x(in)S 118 x(Chapter)S 117 x(8)S
117 x(of)S 117 x(the)S 117 x F152(VMS)S 117 x(Upgrade)S 4945 X 598 y
(and)S 167 x(Installation)S 167 x(Manual)S F151(.)S 3899 X 896 y F36
(2.)S 631 x F151(After)S 173 x(the)S 173 x(installation)S 173 x(or)S
173 x(upgrade,)S 177 x(boot)S 173 x(the)S 173 x(system)S 173 x(\(if)S
173 x(it)S 173 x(did)S 173 x(not)S 173 x(boot)S 173 x(automatically\))S
173 x(and)S 174 x(log)S 173 x(into)S 4945 X 598 y(the)S 166 x(SYSTEM)S
166 x(account.)S 222 x(For)S 167 x(example:)S 7336 X 747 y F98(Welcome)S
269 x(to)S 269 x(VAX/VMS)S 269 x(V5.4)S 5991 17299 XY(Username:)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 468 x(SYSTEM)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 5991 X 498 y(Password:)S 3899 X 896 y F36(3.)S 631 x F151(Place)S
238 x(the)S 238 x(tape)S 238 x(cartridge,)S 256 x(compact)S 238 x(disc,)S
256 x(or)S 238 x(magnetic)S 238 x(tape)S 238 x(labeled)S 237 x(`)S -9 x
(`)S(V)S -51 x(AX/VMS)S 238 x(V5.4-0A')S -10 x(')S 237 x(in)S 238 x
(the)S 4945 X 598 y(appropriate)S 194 x(drive.)S 307 x(Substituting)S
194 x(the)S 194 x(name)S 195 x(of)S 194 x(the)S 194 x(drive)S 195 x
(that)S 194 x(contains)S 194 x(the)S 194 x(VMS)S 194 x(V5.4-0A)S 194 x
(Update)S 4945 X 598 y(for)S 166 x F152(device-name)S F151(,)S 167 x
(type)S 166 x(the)S 167 x(following)S 166 x(and)S 166 x(press)S 166 x
(Return:)S 5991 X 747 y F98($)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(@SYS$UPDATE:VMSINSTAL)S 269 x(VMSMUPA054)S 269 x(device-name:)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 3899 X 897 y F36(4.)S 631 x F151(The)S 167 x(procedure)S 167 x
(displays)S 165 x(a)S 166 x(series)S 166 x(of)S 166 x(messages)S 165 x
(and)S 166 x(asks)S 166 x(you)S 167 x(some)S 166 x(questions.)S 221 x
(For)S 167 x(example:)S 7336 X 747 y F98(VAX/VMS)S 269 x(Software)S
269 x(Product)S 269 x(Installation)S 269 x(Procedure)S 269 x(V5.4)S
5991 23276 XY(It)S 269 x(is)S 269 x(1-OCT-1990)S 269 x(at)S 269 x(9:00)S
5991 X 498 y(Enter)S 269 x(a)S 269 x(question)S 269 x(mark)S 269 x(\(?\))S
269 x(at)S 269 x(any)S 269 x(time)S 269 x(for)S 269 x(help.)S 5991 X
498 y(*)S 269 x(Are)S 269 x(you)S 269 x(satisfied)S 269 x(with)S 269 x
(the)S 269 x(backup)S 269 x(of)S 269 x(your)S 269 x(system)S 269 x(disk)S
269 x([YES]?)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(Y)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 5991 25269 XY(Please)S 269 x(mount)S 269 x(the)S 269 x(first)S
269 x(volume)S 269 x(of)S 269 x(the)S 269 x(set)S 269 x(on)S 269 x(MUA0:.)S
5991 X 498 y(*Are)S 269 x(you)S 269 x(ready?)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 468 x(Y)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 5991 X 498 y(%MOUNT-I-MOUNTED,)S 269 x(VMSMUP)S 269 x(mounted)S
269 x(on)S 269 x(_MUA0:)S 5991 X 797 y(The)S 269 x(following)S 269 x
(products)S 269 x(will)S 269 x(be)S 269 x(processed:)S 6798 X 797 y
(VMSMUPA)S 269 x(V5.4)S 8143 X 797 y(Beginning)S 269 x(installation)S
269 x(of)S 269 x(VMSMUPA)S 269 x(V5.4)S 269 x(at)S 269 x(9:00)S 5991 X
797 y(%VMSINSTAL-I-RESTORE,)S 269 x(Restoring)S 269 x(product)S 269 x
(save)S 269 x(set)S 269 x(A)S 269 x(...)S 8143 X 797 y(.)S -269 x 498 y
(.)S -269 x 498 y(.)S -269 x 498 y(Now)S 269 x(applying)S 269 x(the)S
269 x(VMS)S 269 x(V5.4-0A)S 269 x(updates...)S 8143 X 499 y(.)S -269 x
498 y(.)S -269 x 498 y(.)S -269 x 498 y(Installation)S 269 x(of)S 269 x
(VMSMUPA)S 269 x(V5.4)S 269 x(completed)S 269 x(at)S 269 x(9:05)S 5991 X
797 y(%VMSINSTAL-I-SHUTDOWN,)S 269 x(This)S 269 x(product)S 269 x(requires)S
269 x(that)S 269 x(the)S 269 x(system)S 268 x(be)S 269 x(rebooted.)S
%%EndCustomColor: 0
1 PP EP
%%PageTrailer
%%PageFonts: DigitalLogo Helvetica-BoldOblique
%%+ Helvetica-Bold NewCenturySchlbk-Roman
%%+ NewCenturySchlbk-Italic Courier
%%PageCustomColors: 0 1
%
%%Page: 2 2
%%BeginPageSetup
%%EndPageSetup
%%PageFonts: (atend)
%%PageCustomColors: (atend)
1000 BP PaperHeight PaperWidth PM 0 0 XY 
%%BeginCustomColor: 0 
0 SC 3899 3969 XY F36(5.)S 631 x F151(After)S 153 x(you)S 154 x(apply)S
153 x(the)S 154 x(VMS)S 152 x(V5.4-0A)S 153 x(Update,)S 156 x(complete)S
153 x(your)S 154 x(upgrade)S 154 x(or)S 154 x(installation)S 152 x(as)S
153 x(described)S 153 x(in)S 4945 X 598 y(the)S 166 x F152(VMS)S 166 x
(V)S -64 x(ersion)S 167 x(5.4)S 166 x(Upgrade)S 167 x(and)S 167 x(Installation)S
167 x(Manual)S F151(.)S 3899 5763 XY F32(Releas)S -2 x(e)S 183 x(Notes)S
3899 X 797 y F151(When)S 186 x(you)S 186 x(boot)S 186 x(standalone)S
185 x(BACKUP)S 185 x(on)S 186 x(a)S 185 x(V)S -55 x(AX)S 185 x(6000)S
185 x(or)S 186 x(9000)S 185 x(series)S 185 x(system)S 185 x(with)S 186 x
(512Mb)S 185 x(of)S 186 x(memory)S -55 x(,)S 3899 X 597 y(you)S 190 x
(must)S 189 x(perform)S 189 x(a)S 189 x(conversational)S 190 x(boot)S
189 x(and)S 190 x(change)S 190 x(the)S 190 x(SYSGE)S -2 x(N)S 189 x
(parameter)S 189 x(PHYSICALP)S -37 x(AGES)S 188 x(to)S 3899 X 598 y
(1047552)S 166 x(\(less)S 165 x(than)S 166 x(512Mb\).)S 222 x(For)S
167 x(example:)S 4945 X 747 y F98(>>>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(B/R5:1)S 269 x(du0)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 498 y(SYSBOOT>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(SET)S 269 x(PHYSICALPAGES)S 269 x(1047552)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 499 y(SYSBOOT>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(CONTINUE)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 3899 10495 XY F151(This)S 166 x(will)S 165 x(be)S 166 x(\211xed)S
167 x(in)S 167 x(a)S 166 x(future)S 166 x(release)S 166 x(of)S 166 x
(VMS.)S 3899 11491 XY(After)S 149 x(your)S 151 x(system)S 150 x(is)S
149 x(up)S 150 x(and)S 150 x(runnin)S 2 x(g,)S 154 x(you)S 151 x(can)S
150 x(use)S 150 x(SYSGE)S -2 x(N)S 150 x(to)S 150 x(change)S 151 x(PHYSICALP)S
-37 x(AGE)S -2 x(S)S 150 x(to)S 150 x(1047552)S 3899 X 598 y(to)S 166 x
(avoid)S 166 x(stopping)S 166 x(in)S 167 x(SYSBO)S -2 x(OT)S 166 x(during)S
167 x(each)S 167 x(reboot.)S 222 x(For)S 166 x(example:)S 4945 X 747 y
F98($)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(RUN)S 269 x(SYS$SYSTEM:SYSGEN)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 498 y(SYSGEN>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(USE)S 269 x(CURRENT)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 498 y(SYSGEN>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(SET)S 269 x(PHYSICALPAGES)S 269 x(1047552)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 499 y(SYSGEN>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(WRITE)S 269 x(CURRENT)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 4945 X 498 y(SYSGEN>)S
%%EndCustomColor: 0
%%BeginCustomColor: 1
1 SC 418 x(EXIT)S
%%EndCustomColor: 1
%%BeginCustomColor: 0
0 SC 3899 15825 XY F151(T)S -46 x(o)S 162 x(make)S 162 x(this)S 161 x
(permanent,)S 163 x(add)S 162 x(this)S 161 x(value)S 162 x(to)S 161 x
(your)S 163 x(\211le,)S 163 x(SYS$SYSTEM:MODP)S -38 x(ARAMS.DA)S -29 x
(T)S -45 x(.)S 162 x(AUTOGE)S -2 x(N)S 3899 X 598 y(refers)S 166 x(to)S
166 x(this)S 166 x(\211le)S 166 x(to)S 166 x(con\211gu)S 2 x(re)S 166 x
(the)S 166 x(system.)S 14771 17419 XY F153(NOTE)S 4796 X 897 y(Please)S
166 x(note)S 167 x(that)S 167 x(the)S 166 x(V)S -45 x(AX)S 165 x(6000-500)S
166 x(series)S 166 x(does)S 166 x(not)S 167 x(support)S 167 x(the)S
167 x(CIBC)S -2 x(A-A.)S 8543 34745 XY F36(\251)S 150 x(Digital)S 167 x
(Equip)S 2 x(ment)S 166 x(Corporation.)S 223 x(1990.)S 222 x(All)S 166 x
(rights)S 167 x(reserved.)S 3899 X 577 y 6996 24 R 3899 35857 XY F159
(\207)S 199 x(The)S 133 x(following)S 132 x(are)S 133 x(trademarks)S
132 x(of)S 133 x(Digita)S -2 x(l)S 133 x(Equipment)S 132 x(Corporation:)S
177 x(V)S -44 x(AX,)S 131 x(VMS,)S 133 x(and)S 133 x(the)S 133 x(DIGIT)S
-21 x(AL)S 132 x(Logo.)S 15417 37573 XY F34(2)S
%%EndCustomColor: 0
2 PP EP
%%PageTrailer
%%PageFonts: Helvetica-Bold NewCenturySchlbk-Roman
%%+ NewCenturySchlbk-Italic Courier NewCenturySchlbk-Bold
%%+ Helvetica
%%PageCustomColors: 0 1
%
%%Trailer
EndDVC$PSDoc
/DEC$EDMS_MAKE_FILM where	% if we are making film...
 { pop				% ..clean up the stack
   -54 dup translate		% ..undo the film translation
 } if
%%Pages: 2
%%DocumentFonts: DigitalLogo NewCenturySchlbk-Roman
%%+ NewCenturySchlbk-Bold NewCenturySchlbk-Italic
%%+ Courier Helvetica-Bold Helvetica Helvetica-BoldOblique
%%DocumentCustomColors: 0 1
115.5KERNEL::WRIGHTONodd numbered release = bug insertTue Oct 23 1990 16:2270
          <<< KERNEL::DISK$APD1:[NOTES$LIBRARY]CSGUK_SYSTEMS.NOTE;1 >>>
                               -< CSGUK_SYSTEMS >-
================================================================================
Note 78.73                       VAX 9000 topic.                        73 of 78
KERNEL::WRIGHTON "odd numbered release = bug insert" 62 lines  19-OCT-1990 09:19
                      -< problems with V5.4 MUP install >-
--------------------------------------------------------------------------------


SUBJECT:  VMS 5.4 Install On 9xxx Systems Hangs during 5.4 MUP install phase.   
 

DESCRIPTION: 

          After the initial install of 5.4, the MUP tape is requested to be
          installed.   The installation appears to be going okay until such
          time as UPDATE_CONSOLE.COM is  invoked to  copy  VMB9AQ.EXE  from
          SYSDISK down to CSA1.  The following error message is printed out
          on the console:

               %COPY-E-WRITEERR, Error Writing CSA1:[USERFILES]VMB9AQ.EXE;2
               -RMS-F-SYS, QIO System Service Request Failed
               -SYS-F-TIMEOUT, Device Timeout
               %COPY-W-NOTCOMPLT, SYS$COMMON:[SYSEXE]VMB9AQ.EXE 
                        Not Completely Copied

          VMS remains hung at this time and will not continue with the
          install.  A reboot of VMS at this point brings us back to 
          INSTALL requesting that the MUP tape be installed and the
          same failure.

WORKAROUNDS:
               >>>I/K
               >>>BOOT/NOSTART "bootfile"
               >>>DEPOSIT R5 1
               SYSBOOT> SET/STARTUP SYS$SYSTEM:STARTUP.COM
               SYSBOOT> CONTINUE

          At this point the install is complete except for needing
          to @SYS$UPDATE:UPDATE_CONSOLE.COM to update the console RD54 
          with VMB9AQ.EXE,  installing licenses and running AUTOGEN.

        To avoid this problem all together. Do the following:

          On the initial boot after you have restored the "B" saveset.

               >>>I/K
               >>>BOOT/NOSTART "bootfile"
               >>>DEPOSIT R1 1
               SYSBOOT>SET ERRORLOGBUFFERS 64
	       SYSBOOT>SET ERLBUFFERPAGES 32
	       SYSBOOT>CONTINUE

	Proceed with the installation normally.


\\%VAX 9000 9210 9410 9420 9430 9440 AQUARIUS SOFTWARE NONE VMS 5.4      

To Distribution List:

Rory O'DONNELL@UVO,
Dave WRIGHTON@UVO,
Andreas KAEMPFE@SUF,
Thomas RATSCH@MGO,
Gerd GABRYS@COO,
Roberto VERCELLI@TNO,
Maurizio MORRONE@RIO,
Walter GROSSI@MIO,
Daniel GONON@GVO,
MEIR ALON@ISO