Google
 

Trailing-Edge - PDP-10 Archives - BB-H138D-BM - 5-1-documentation/boot.doc
There are 22 other files named boot.doc in the archive. Click here to see a list.


BOOT.DOC -- Changes from V7(134) to V10(151)
October 1981






























COPYRIGHT (C) 1976,1979,1982 BY
DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.


THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND  COPIED
ONLY  IN  ACCORDANCE  WITH  THE  TERMS  OF  SUCH  LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE OR  ANY  OTHER
COPIES  THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON.  NO TITLE TO AND OWNERSHIP OF  THE  SOFTWARE  IS  HEREBY
TRANSFERRED.

THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE  WITHOUT  NOTICE
AND  SHOULD  NOT  BE  CONSTRUED  AS  A COMMITMENT BY DIGITAL EQUIPMENT
CORPORATION.

DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR  RELIABILITY  OF  ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
BOT10.DOC                                                       Page 2


BOOT.DOC -- Changes from V7(134) to V10(151)
October 1981



1.0  SUMMARY

BOOT is used to load the TOPS-20  Monitor  from  disk  into  KL10/KS10
memory.   On  normal  system startup, BOOT is automatically loaded and
started by RSX20F, and will load the TOPS-20 Monitor without  operator
intervention.

BOOT is also responsible for dumping  KL10/KS10  memory  after  system
malfunction, for later analysis.

BOOT version 10(151) runs only with TOPS-20 Release 5.

BOOT is documented in the following documents:

     TOPS-20 Software Installation Guide

     TOPS-20 Operator's Guide



2.0  EXTERNAL CHANGES

There are two new switches:  (1) /E loads  the  resident  monitor  and
transfers control to EDDT.  (2) /I prints the version of BOOT, and the
type and version of any DX20 microcode modules that  are  embedded  in
BOOT.

BOOT's  error  messages  have   been   rewritten   in   ASCII/English;
applicable  messages  will  also  include  relevant  structure  and/or
filenames.  The messages are listed and documented in  the  Operator's
Guide.  It is important to realize that some investigation is required
in determining the circumstances that caused the message to be output.
For example, "Stucture not found" can be caused by:

     1.  NO pack mounted

     2.  INCORRECT pack mounted

     3.  Pack not spinning

     4.  Drive door not closed completely

     5.  Any hardware problem that prevents BOOT from finding the pack

When dumping, BOOT no  longer  writes  its  own  image  (or  the  DX20
microcode)  to DUMP.EXE.  Thus there will be a file hole in any dumps,
ranging from pages 16 to 51 for non-RP20 sites and pages 16 to 56  for
RP20  sites.   These  file holes occur in the resident monitor area of
the dump.
BOT10.DOC                                                       Page 3


When searching for a bootable structure, BOOT  first  searches  for  a
pack whose APR serial number matches the CPU being booted.  If no such
structure is found, BOOT searches for structure "PS:".   If  strucutre
"PS:"  is  not  found,  BOOT  prints  an  error message and returns to
command level.

BOOT is more communicative about its 4  major  operations,  describing
the  activity  it  is  attempting,  and  responding  with "[OK]" if it
succeeds.  These activities are:

     1.  Loading the resident monitor.

     2.  Loading the swappable monitor.  Note:  physical  memory  size
         and  monitor  configuration  may require BOOT to perform more
         than one pass while loading the swappable monitor.

     3.  Loading any DX20 microcode.   Note  that  "DX20A"  refers  to
         TU7x-DX20's while "DX20B" refers to RP20-DX20's.

     4.  Dumping.

During an auto-reload, DX20B's are reloaded;  DX20A's are not.

If BOOT suffers an error while loading  the  swappable  monitor,  BOOT
will  print  out its own error message before returning control to the
monitor (which will then BUGHLT).



3.0  KNOWN BUGS AND DEFICIENCIES

BOOT will load the TOPS-20 Monitor from disk only.

This version of BOOT can not load monitors prior to version 4.



4.0  INSTALLATION INSTRUCTIONS


4.1  Files Needed to Run BOOT

BOOT requires the file to be loaded, usually PS:<SYSTEM>MONITR.EXE, be
present on the disk.  The default file is PS:<SYSTEM>MONITR.EXE.


4.2  Instructions for Loading and Installing BOOT

BOOT is distributed on the floppy diskettes containing  the  front-end
software.   It  is  installed  in  the  front-end  area  during system
installation, (see TOPS-20 Software Installation Guide).
BOT10.DOC                                                       Page 4


4.3  Files Needed to Build BOOT

BOOT is built from the following files:

     BOOT.MAC
     KLPRE.MAC
     PMT.MAC
     KSPRE.MAC
     DXMCA.RMC
     DXMCE.RMC (RP20 sites only)
     RP2.MAC (RP20 sites only)


4.4  Instructions for Building BOOT

The procedure for building BOOT is complex.  It is suggested that BOOT
only be built by submitting the Batch file BOOT.CTL.


4.5  Special Considerations

None.



5.0  INTERNAL CHANGES

TU78/RP20/RP07 support has been added.  (Note that an RP20  is  not  a
bootable device.)

Maximum dumpable core has been increased to 3 megawords.

Directory entries in DUMP.EXE are now section-aligned.

VBOOT now runs in the section it is called from.  For  TOPS-20  V4  it
will always run in section 0.  For TOPS-20 V5 it runs first in section
0 and then (after being called by the monitor) runs in section 1.



6.0  SUGGESTIONS

None.



[End of BOT10.DOC]