************************************************************************
* ##     ##    ###    ##     ##       ## ##     ## ##     ##  ######   *
* ##     ##   ## ##    ##   ##       ##  ##     ## ###   ### ##    ##  *
* ##     ##  ##   ##    ## ##       ##   ##     ## #### #### ##        *
* ##     ## ##     ##    ###       ##    ##     ## ## ### ##  ######   *
*  ##   ##  #########   ## ##     ##      ##   ##  ##     ##       ##  *
*   ## ##   ##     ##  ##   ##   ##        ## ##   ##     ## ##    ##  *
*    ###    ##     ## ##     ## ##          ###    ##     ##  ######   *
*                                                                      *
*                     Version 4.7 "Turnkey" System                     *
*                                                                      *
*                      +-+-+-+-+-+-+-+                                 *
*                      |d|i|g|i|t|a|l|   VAX 8650                      *
*                      +-+-+-+-+-+-+-+                                 *
*                                                                      *
************************************************************************


Thanks and Contributions
========================
    We would like to extend thanks to Al Kossow of the CHM and BitSavers
archives, Johnny Bilquist, David Bolen, Lars Brinkhoff, Matt Burke, Alon
Gendel, Hans-Ulrich Hölscher, Supratim Sanyal, Matt Wilson , and finally
Brewster Kahle of the Internet Archive. All of the above contributed
directly, or indirectly to the assembly of this kit.


VAX-11 Simulation
=================
    The SIMH v4.x simulation of the VAX-11/780 or VAX 8650 is required
for this kit to function, full stop. We prefer to use the "open-simh"
distribution, however it requires one be able to build the package from
source. It may be found here:
        <https://github.com/open-simh/simh>
The preference for the VAX-11/780 ir VAX 8650 simulation is multi-fold:
    1. System support and system requirements: the microVAX I, microVAX
II, VAX-11/730, and VAX-11/750 do not meet the memory requirements of
the complete turnkey system setup.
    2. (Future) Cluster Interconnect support: Keith Halewood (possibly)
and Matt Burke are working on an implemention of Cluster Interconnect,
which requires a VAX-11/750, VAX-11/780, or VAX 8600.
    3. VAXstation 100 Graphics support: Lars Brinkhoff produced an
implementation of the VAXstation 100 graphical workstation hardware,
which requires a UNIBUS system (e.g. a VAX-11/730, VAX-11/750,
VAX-11/780, or VAX 8600).


Networking
==========
    The maximum usefulness of this turnkey distribution is one where the
system has networking available. On Linux this is effectively "out of
the box" when you build the SIMH emulator - although it is highly
recommended to use VDE2 and an isolated virtual network switch (i.e. a
vde-switch) as opposed to connecting the system to a "real" network
directly. The supplied "comms.ini" file is preconfigured to attach the
simulator to the default configuration of a vde-switch -- more on that
file will follow. On a Windows system, the Windows Packet Caputre
Library library (WinPcap; <https://www.winpcap.org/>) is required for
SIMH for network function; whilst there is no version of VDE2 for
Windows (unfortunately), one can approach the isolated network segment
idea if one has VirtualBox installed and connects SIMH to the
"VirtualBox Host-Only Network" network adapter, if one has been defined.

    In either case -- Windows or Linux -- the "comms.ini" file *MUST* be
changed, to reflect your networking setup. To determine which changes
are to be made, run any SIMH simulator which supports Ethernet -- given
that this kit requires the VAX-11/780 or VAX 8650 simulator, it should
be readily available -- and query the Ethernet device for available
network interfaces. Some examples:
	VAX 8600 simulator Open SIMH V4.1-0 Current
	sim> show XU eth

	MicroVAX II (KA630) simulator Open SIMH V4.1-0 Current
	sim> show XQ eth

	VAXstation 3100 M76 (KA43-A) simulator Open SIMH V4.1-0 Current
	sim> show XS eth
Further, the connection ports and peering information of the DMC11/DMR11
synchronous serial/DDCMP links may be adjusted as well. If you want to
change tthe number of DMC11/DMR11 links, you must edit the "vax8600.ini"
configuration file.

    Prior to the installation you should collect the networking details
so that you can proceed through the installation questionnaire with a
minimum of fuss.


The Installation Process
========================
    The turnkey installation is very simple, and fully automated after
the initial configuration dialogue has been completed. To perform the
installation perform the following:
    1. Start the SIMH VAX-11/780 or VAX 8650 simulator from the "vms47"
       directory, such that it reads and performs the configuration
       within the "vax780.ini" or "vax8600.ini" file. You will know you
       have done it correctly as a banner similar to the one at the
       beginning of this file is printed. You will also notice a second
       banner saying to run the installation script.
    2. At the SIMH simulator prompt, which has been configured to give
       a modicum of verisimilitude to the real VAX console prompt (the
       "dead sergeant" prompt, in other words), issue the command
           >>> do install
       Which will run the installation script.
    3. Follow the prompts given by the installation script.
Please note that when prompted for the DECnet node name, you *MUST*
capitalize it, otherwise the installation script will hang. This is an
unavoidable requirement -- unless and until such time as the SIMH
scripting language is extended.

Installation Options of Particular Note
---------------------------------------
    The turnkey installation questionnaire is rather self-explanatory in
terms of the options. However, to give a better understanding of some of
the more easily confused options, please note the following:
    1. Passwords: If one does not desire the default turnkey password
       (that is, "Digital1977"), the SYSTEM password will become the new
       default password choice.
    2. Demonstration Users: An additional eleven (11) non-privileged
       user accounts are added to the system; these accounts are:
           ACG     CGP     DAR     DHG     DNC     HML     JAK
           KDM     LFL     RIH     TJP
    3. 
---+++---1---+++---2---+++---3---+++---4---+++---5---+++---6---+++---7--


Post-Installation Tasks
=======================
    There are some post-installation tasks that can/should be undertaken
once the turnkey kit has completed its installation process.

ALL-IN-1 User Setup
-------------------
    The first task is setting up an ALL-IN-1 user account for the
account that was created during the system setup. You *WILL* need a
VT-100 compatible terminal emulator, thus you *WILL* need to connect via
the simulated DZ11 terminal multiplexer, via telnet over TCP/IP, or via
CTERM/RTREM over DECnet Phase IV. Whichever of the three methods are
chosen, login as user "ALLIN1" with the password you provided in the
installation questionnaire.

    Once you have logged in, ensure the terminal characteristics are
correct, by issuing the command:
  $ SET TERMINAL/INQUIRE
You may then issue the command to start ALL-IN-1 as the ALL-IN-1 System
Manager:
  $ ALLIN1/USER=MANAGER
You will now have a "graphical" display; enter the command "SM" to get
to the System Manager Functions menu. Enter "SEL" to select master file,
then press F1, followed by "L" to get a list of master files; enter the
option that matches "PROFILE" and press Enter. Press Enter once again to
set the master file.
    Now create the new ALL-IN-1 user; enter the command "C" then the
command "UP" at the "Create Options" menu to add a user profile. At the
"User Profile" screen, fill out the fields (using tab and
the arrow keys to navigate between them); the "VMS Name" field should be
the same as the "Username" (so that invoking ALL-IN-1 requires only
entering the command without need to request a specific user), and both
should be the same as the username of the account created during the
system installation - the default being "DNC". The "Directory" filed
should be filled in with the user's VMS directory; assuming the default
username was used then the directory field would be "DRA0:[DNC]" (less
the quotation marks). Once the user profile information has been
entered - note there is a second page, accessible by tabbing past the
end of the first - press enter to return to the "Create Options" menu.
    Use the *KEYPAD* zero to exit the "Create Options" menu, again use
the keypad zero to return to the main menu. And issue command "EX" to
exit ALL-IN-1.

TEAMDATA User Setup
-------------------
    To make use of TEAMDATA you will have to create a database file for
the user. Luckily TEAMDATA automatically handles this; once you have run
TEAMDATA for the first time, you will need to ensure the "TEAMDB"
logical is set on login. If one uses the "login.com" file supplied by
the kit, this is already done for you. If you are not, please add the
following to your user's "login.com" file:
	$ ! Setup the TEAMDATA logical, if the database exists
	$ IF F$SEARCH("SYS$LOGIN:TEAMDB.RDB") .NES. "" THEN -
	$       DEFINE/JOB TEAMDB SYS$LOGIN:TEAMDB.RDB


Miscellaneous Notes
===================
    The "superseded" folder includes old, superseded parts of turnkey
kit. Mostly for those curious to see.
    The "testing" folder includes some software distribution tapes that
are in a testing phase for eventual integreation into the turnkey, once
they are integrated -- if they can be -- they will be moved to the
"media" distribution kit.
    The observant will note that there are two configuration files in
the kit's main "vms47" directory -- one for the VAX 8650 and one for a
VAX-11/780 -- both configurations can be run simultaneously. Further the
installation script allows for one to configure the systems such that
they will cooperate (namely, the VAX-11/780 will make use of the DECdns
clearinghouse on the VAX 8650; note that the systems are not being
clustered). In the case of running both the '780 and '8650 simulators on
the same host, attaching to the same Ethernet device, you may wish to
modify the configurations of the two simulators to add a dedicated DDCMP
link between them; the configuration modifications would be as such:
        'vax8600.ini':
    --- vax8600.old
    +++ vax8600.ini
    @@ -71 +71 @@
    -set DMC enable, LINES=4
    +set DMC enable, LINES=5
    @@ -75,0 +76 @@
    +set DMC4 MICRODIAG=enable, TYPE=DMR

        'vax780.ini':
    --- vax780.old
    +++ vax780.ini
    @@ -51 +51 @@
    -set DMC enable, LINES=4
    +set DMC enable, LINES=5
    @@ -55,0 +56 @@
    +set DMC4 MICRODIAG=enable, TYPE=DMR

        'comms.ini':
    --- comms.old
    +++ comms.ini
    @@ -12,0 +13 @@
    +;     DMR-11 #3: VAX/VMS 4.7 Turnkey “795VAX::”
    @@ -16,0 +18 @@
    +set ENV CPR4=11795
    @@ -26,0 +29 @@
    +;     DMR-11 #3: VAX/VMS 4.7 Turnkey “780VAX::”
    @@ -30,0 +34 @@
    +set ENV CPR4=11785
    @@ -51,0 +56,4 @@
    +
    +; DMR-11 № 3
    +set DMC4 PEER=127.0.0.1:%CPR4%
    +attach DMC3 %CPFX%5

The above are diff patches which may be fed into patch as desired to
produce the requierd configuration modifications. As stated above, these
modifications are not strictly necessary, if the two simulators' DELUA
interfaces are able to communicate. For example, if the simulators have
their Ethernet interfaces connected to a VDE2 virtual switch, the DDCNP
connection is unnecesary.
