Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

^LTOPS20 Change Order Number 5.1044

Written by: ZIMA		24-May-80 18:35:48

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

Program: MONITOR
   Routines Affected:	BOOT

Related TCO's:
Related SPR's: 


Problem: The attempt to zero 20-23 to fend against CCW word parity errors
is not doing it.

Diagnosis: Typo in literal.

Solution: Fix typo.


^LTOPS20 Change Order Number 5.1045

Written by: ZIMA		24-May-80 18:37:40

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

Program: MONITOR
   Routines Affected:	BOOT

Related TCO's:
Related SPR's: 


Problem: The MTBOOT prompt is coming out as MTBOOT > (extra space).

Diagnosis: Typo in BYTE pseudo-op.

Solution: Fix typo.


^LTOPS20 Change Order Number 5.1046

Written by: ZIMA		24-May-80 18:44:41

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

Program: MONITOR
   Routines Affected:	BOOT

Related TCO's:
Related SPR's: 


Problem: BOOT hangs on KS-10s.

Diagnosis: 
     Non-zero contents in location 35 (KLINIK output word) when BOOT
tries to output its prompt induces the 8080 to think that KLINIK output
is desired.  The microprocessor tries to output the spurious KLINIK byte
and forgets about the CTY output (checks KLINIK first).  This leaves
BOOT looping waiting for the CTY communication word to be cleared.

Solution: 
     Final solution will be in a future revision to the microporcessor
ROM; in the interim, put in code (SMFLG conditional) to clear the
KLINIK communication words.


^LTOPS20 Change Order Number 5.1095

Written by: ZIMA		 5-Jul-80 22:12:32

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

Program: MONITOR
   Routines Affected:	BOOT

Related TCO's:	5.1257
Related SPR's: 


Problem: BOOT HANGS

Diagnosis: 
     BOOT is totally unprepared for the case of uninitialized memory,
especially in the area of the BOOT self-relocation code.  It takes
page faults on each word of the exchange and winds up looping at zero.
A KS10 cannot be booted after powerup until a ZM is done.

Solution: 
     Move the initial EPT to the CODEND page, where it will remain fixed
until BOOT has moved itself.  Change the sense of the exchange loop so it
will be microcode invariant against the destructive page faults from any
uninitialized memory.


^LTOPS20 Change Order Number 5.1095

Written by: ZIMA		 5-Jul-80 22:12:32

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

Program: MONITOR
   Routines Affected:	BOOT

Related TCO's:	5.1257
Related SPR's: 


Problem: BOOT HANGS

Diagnosis: 
     BOOT is totally unprepared for the case of uninitialized memory,
especially in the area of the BOOT self-relocation code.  It takes
page faults on each word of the exchange and winds up looping at zero.
A KS10 cannot be booted after powerup until a ZM is done.

Solution: 
     Move the initial EPT to the CODEND page, where it will remain fixed
until BOOT has moved itself.  Change the sense of the exchange loop so it
will be microcode invariant against the destructive page faults from any
uninitialized memory.


^LTOPS20 Change Order Number 5.1257

Written by: ZIMA		 4-Feb-81 10:20:40

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

Program: boot

Related TCO's:	5.1095
Related SPR's: 	 14573


Problem: 
     Various problems relating to power-fail on 2020 systems.  For instance,
BOOT hangs, first page of ROOT-DIRECTORY may be trashed, SWPPTP BUGHLTs on
reload, etc.

Diagnosis: 
     Uninitialized MOS memory can cause a wide range of problems that BOOT
and the monitor are not prepared to handle.  Memory initialization is done
by the front-end for the KL processor.

Solution: 
     Add code to BOOT under SMFLG conditional to initialize memory for
the KS-10.