SC1041_SAIL_PDP-6_hardware_log_1968-01

20-JAN-67 18:00-19:30 or so

[full page printout attached to Logbook]

CORE PARITY ERROR, LOCATION INDETERMINATE PC=340000004506 INSTR=402000001134 DATE=000641123071 TIME=1652:17

CORE PARITY ERROR, LOCATION INDETERMINATE PC=340000004506 INSTR=402000001134 DATE=000641123071 TIME=1652:42

CORE PARITY ERROR, LOCATION INDETERMINATE PC=340000004506 INSTR=402000001134 DATE=000641123072 TIME=1653:25

F ? .C 56 JOB 2 STANFORD 2.8/09A

.K

.C 56 JOB 2 STANFORD 2.8/09A

.K

.RUN DTA 1 BLTST 120 JOB 1 STANDORD 2.8/09A

BLOCK TRANSFER ERROR. FROM TO "E" EA DRES COR. WORD ERR. WORD C (BLTAC)

256503 212357 313653 233654 720000300000 520000100000 156062311736 256503 212357 313653 233655 720001300001 520001100001 156062311736 256503 212357 313653 233656 720002300002 520002100002 156062311736

↑C

.RUNT 151:26.88

43

Any body who can pull tape 910 off DTA 3 Can have it !!! Reg Reddy

I and Samson PJV

21 Jan 68 THE DEC SCOPE IS RATHER BADLY ARAM

22 janvier 68 Printer is skipping line PJV?

1130 22 Jan 68 System died on parity error Had trouble reloading system Decdump hung up in UUO's . Finally tried everything again and it worked.

[START printout inserted into logbook page]

? CORE PARITY ERROR, LOCATION 000000000275. OPND=00000000007 SYSTEM REINITIALIZED AT SYSTEM RESTARTED AT

RAN VINS4, VINS5, MULDIV, BLTST. 112 FOR 10 min SRR

[END printout]

44

4⁰⁵ Jan. 22, 1968

Printer ribbon rolled up off the left side of the upper mandril. Apparently is [sic] was not started in its guide. Installed a new ribbon, cleaned the character drum, and emptied the dust cup. J. Gleason

17⁵⁰ Ran 6 pages of test print on the printer. All characters appeared to be printed correctly. Also no line skipping occurred! (Use PRDIAG on CUSP2 for the test. J. Gleason

18⁴⁵ We have been watching the -10V output line on the 1562 Ref. Supply board in the type 30 display for most of the day to determine the reason for the "rippling display". The ripple was less than 10mv so we decided to disconnect the scope and wait for the "rippling display" to re-occur. It did re-occur ~ 1/2 hr after we disconnected the scope. I put the scope on pinE of the 1562 (-10V Ref) and saw 0.5V pK-pK 120 ~ ripple. I also saw 0.5V PK-PK ripple on the -15V line (PinC). After banging on the table top the ripple disappeared! *! *! Will have to wait until it re-appears again. J. Gleason

45

at pins on 1 L14, & 13 no problems Ran checkerboard in core 1 for 10 min No errors. Put up system SRR

Jan 23 [START printout attached to logbook page] CORE PARITY ERROR, LOCATION 000000200000 OPND=000000000000 PC=30000006274 INSTR=251042000000 DATE=00641136531 TIME=1318:39 [ENG printout] MHH

TTY1 Changing characters ("S" only)

[START printout inserted onto logbook page] EXIT ↑C .S TVBUF CONTAINS 07102 WORD : PLTBUF CONTAINS 16206 WORDT ↑C .A DTA5,DATA DTAS ASSIGNED .S TVBUF CONTAINS 07102 WORDS PLTBUF CONTAINS 16206 WORDS [END printout]

1830 23 Jan 68 SCOPE got wavy. Tired wiggling connectors on 1814E no change Tried wiggling the 1562 in 2814. Fixed problem. The 1562 and its socket want a close inspector. SRR

[Lab page no] 46

1730 24 JAN 68 Bill Pitts reports random results from MACROX assembling checkers. Investigation shows 1) the results are not repeatable and should be. 2) the symbol table search in MACROX seems to be effected 3) the probability of it striking is less than 1 in 4.

We tried twice with no other users but running in AMPEX core. There were no errors. SRR

1605 24 JAN 68 UIN55 complains that MULM Failed once in 5 min. Several times between 1605 & 2000 in all cases simulation didn't give same results twice. Will investigate tomorrow morn. SRR