Google
 

Trailing-Edge - PDP-10 Archives - BB-H138B-BM - 4-documentation/boot.tco
There are 25 other files named boot.tco in the archive. Click here to see a list.
TOPS20 Change Order Number 4.2154

Written by: DBELL		 6-Jan-79 19:09:37

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: YES

Program: BOOT

Related TCO's:
Related SPR's: 


Problem: 
BOOT has to be changed whenever the resident monitor changes its
size too much.

Diagnosis: 
Last page to be read in is assembled into BOOT as a constant.

Solution: 
Change the algorithm which BOOT reads in EXE files.  The algorithm for
reading in files is now the following:

1.	If the old syntax of (first,last) was used, which specifies
	the first and last pages to be read in, use them.

2.	If the new switch "A" is specified, then read in all of the
	EXE file from page 0 to page 377.  This upper limit is the
	limit which BOOT knows how to read in.  This will supercede
	the (first,last) specification.

3.	If neither of the above has been used, then obtain the upper
	limit from the symbol table pointer in .JBSYM.  The end of
	the symbol table is assumed to be the end of the resident
	monitor (or whatever program is being read in).

4.	If page 0 does not exist, or .JBSYM is zero, then use the
	old style default upper limit assembled into BOOTS.

These changes allow the end of the resident monitor to be moved around
easily since the last page read by BOOT can also vary.  Running
diagnostics will not be ripped off as long as the "A" switch is used.
TOPS20 Change Order Number 4.2454

Written by: ENGEL		11-Sep-79 14:31:23

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: NO

Program: BOOT

Related TCO's:
Related SPR's: 


Problem: BOOT CLOBBERS MEMORY WHEN IT LOADS ITSELF INTO CORE.  MANY PAGES
IN DUMPS ARE CLOBBERED BECAUSE OF THIS.

Diagnosis: HAVE BOOT BE MORE CLEVER

Solution: BOOT WILL DROP IN OVER THE RESIDENT MONITOR.  WHEN IT MOVES ITSELF
IT WILL SAVE THE AREA IT IS MOVING INTO.  DUMP FILES WILL HAVE A LARGE WHOLE
IN LOW CORE AND THE REST OF MEMORY SHOULD BE AS IT WAS BEFORE BOOT RAN.  

THE DELETE COMMAND WAS IMPLEMENTED IN BOOT.
TOPS20 Change Order Number 4.2534

Written by: DBELL		18-Oct-79 16:48:50

Edit checked: NO			   Document: NO
  TCO Tested: NO		Maintenance Release: NO
Hardware-related: YES

Program: BOOT

Related TCO's:
Related SPR's: 


Problem: 
If the DX20 microcode is loaded, and tape unit 0 is not on line, the
DX20 will halt.  This situation comes up once you share tapes between
two systems, and have to reload one of them.  The operator has to
manually enable unit 0 for the system being reloaded.  However, on an
auto-reload, no operator is there to enable unit 0, thus the microcode
will fall over.

Diagnosis: 
BOOT always loads the DX20 microcode, even in cases where it doesn't
have to.  Once such case is on an automatic reboot, where we have
previously loaded the DX20 when the system originally came up.

Solution: 
Have BOOT only load the DX20 microcode when the operator is involved.
On an automatic reboot, BOOT will now just leave the microcode that
was running alone.