Trailing-Edge
-
PDP-10 Archives
-
6.1_emacs_manuals_1er
-
manuals/klad20.mem
There are no other files named klad20.mem in the archive.
PRODUCT CODE: AC-F502K-DD
PRODUCT NAME: HOW TO BUILD KLAD20-F.S.
CAUTION
-------
SUPPORTS KLAD20-Z-6.0-PRE-C
MODEL B PROCESSORS ONLY!
THIS DOCUMENT IS NOT INTENDED TO BE APPLICABLE TO EARLIER VERSIONS
OF KLAD20. IT IS ADVISABLE THAT THE USER REFER TO KLAD20 SPECIFIC REVISIONS
IN ORDER TO PERFORM ANY REQUIRED UPDATES.!!!
COPYRIGHT 1982 DIGITAL EQUIPMENT CORPORATION, MARLBOROUGH, MASS.
SUPPORTS KLAD20 VERSION KLAD20-Z-6.0-A
*** WARNING *** WARNING ***
THE CONTENTS OF THIS AND ALL KLAD10 OR KLAD20 MEDIA ARE CONFIDENTIAL IN
NATURE, AND ARE THE SOLE PROPERTY OF DIGITAL EQUIPMENT CORPORATION. ITS
USE IS INTENDED FOR D.E.C. PERSONNEL ONLY!
IT IS NOT PERMITTED TO DISTRIBUTE, RELEASE, OR OTHERWISE MAKE AVAILABLE ANY
OF THE SOFTWARE, DOCUMENTATION, OR ANY OTHER FILES FROM THESE MEDIA TO
PERSONS NOT CONSIDERED BONA-FIDE, AUTHORIZED EMPLOYEES OF DIGITAL EQUIPMENT
CORPORATION.
INDIVIDUALS WHO VIOLATE OR OTHERWISE DISREGARD THIS WARNING WITHOUT
PREVIOUS WRITTEN CONSENT FROM LCG PRODUCT SUPPORT, AND FIELD SERVICE
MARKETING, MAY BE SUBJECT TO DISCPLINARY ACTION.
IT IS SUGGESTED THAT THE USER OF THIS DOCUMENT READ THESE INSTRUCTIONS AT
LEAST ONCE, BEFORE ATTEMPTING TO PERFORM ANY OF THE INDICATED PROCEDURES.
EDITED 6-NOV-84
PAGE 1
KLAD20 VERSION 6.0 (COOK-BOOK)
SUPPORT FOR TOPS-20 REL. 6.0
EDITED 6 NOVEMBER 84
SUPPORTS KLAD20 VERSION KLAD20-Z-6.0-A
C o n t e n t s
---------------
A. Introduction PAGE 2
B. Usage of KLAD-20 PAGE 3-5
Appendix A. Creating a KLAD-20 PACK from DUMPER-tapes. PAGE 6-16
Appendix B. Tailoring TOPS-20 for YOUR system. PAGE 17
Appendix C. Creating DUMPER tapes for KLAD-20. PAGE 18-19
Appendix D. GOODIES, which are new on KLAD-20. PAGE 20
Appendix E. The PTYCON-control-file for FRONT-END saving. PAGE 21-23
Appendix F. The PTYCON-control-file to restore the FRONT-END. PAGE 24
Appendix G. HELP file for USING the UETP TEST PACKAGE PAGE 25
Appendix H. Procedure to update DIAGNOSTIC floppies. PAGE 26
Appendix I. Procedure to update KLAD-20 from magtape. PAGE 27-31
Appendix J. How MARLBORO manufactures KLAD-20 packs. PAGE 32-33
Appendix K. Update- (patching) technique for .A11 files. PAGE 34-39
Appendix K1. Update- (patching) technique for .A10 files. PAGE 40-46
PAGE 2
A. WHAT IS KLAD-20?
KLAD-20 (KL ADVANCED DIAGNOSIS FOR TOPS-20) IS A SINGLE DISK-PACK ,
WHICH CONTAINS ALL CURRENTLY AVAILABLE SOFTWARE TO RUN AND DIAGNOSE
A TOPS-20 SYSTEM.
SPECIFIC CONTENTS:
1. A COMPLETE VERSION OF THE OPERATING SYSTEM (RUNNABLE MONMED MONITOR
IN <SYSTEM> MONITOR.EXE). ALL OTHER MONITORS IN <NEW-SYSTEM>
THIS MONITOR WILL WORK FOR MOST ALL -20 BASED HARDWARE VERSIONS.
2. THE CONTENTS OF THE CURRENT DIAGNOSTIC-TAPES, AND THE
DIAGNOSTICS TO DOWN-LINE LOAD AND TEST SECONDARY PDP-11'S
LOCATED IN THE FRONT-END AREA [6,11], AND IN <3-DIAGNOSTICS>
ON THE -20 SIDE.
3. THE CONTENTS OF THE CURRENT DIAGNOSTIC-TAPES IN THE FRONT-
END FILE-SYSTEM UIC [6,11].
4. A FIELD-SERVICE WORK AREA <F-S> (PASSWORD FS)
NOTE: AN ACCOUNT NUMBER IS NOT REQUIRED!
5. AN AREA <UETP.LIB>, WHICH CONTAINS THE CURRENT VERSION OF THE
24 HOUR RELIABILITY TEST, USED BY F A & T.
NOTE: THE "RELIAB.CMD" FILE MAY HAVE TO BE MODIFIED TO SUIT
YOUR INDIVIDUAL SYSTEM CONFIGURATION.
6. A FULL DIRECTORY OF THE 20-SIDE IN <OPERATOR>KLAD20.DIR ,
A DIRECTORY OF THE 11-SIDE IN <OPERATOR>FE11.DIR.
7. CURRENT MANUALS IN <MANUALS>.
BEWARE , THESE MANUALS ARE ONLY FOR INTERNAL USE ...
NOT FOR CUSTOMERS.
WITH THE EXCEPTION OF <OPERATOR> AND <F-S> , WHICH HAVE "WHEEL"
CAPABILITIES , ALL OTHER AREAS ARE "FILES ONLY" AND CAN ONLY BE
MODIFIED FROM ONE OF THE ABOVE AREAS.
IT IS RECOMMENDED TO LOG IN AND WORK UNDER <F-S> TO GET AUTOMATIC
READ-ACCESS TO THE DIAGNOSTICS AND THE BATCH-FILES FOR THE F A & T
24 HOUR RELIABILITY TEST IN <UETP.LIB>.
READ APPENDIX G:, IF YOU WANT TO USE THE UETP TEST PACKAGE
PAGE 3
B. HOW CAN KLAD-20 BE USED?
------------------------
B1: STAND-ALONE DIAGNOSTIC USAGE WITH KLDCP .
---------------------------------------
USING THE LATEST RELEASE OF KLDCP , YOU CAN RUN ALL DIAGNOSTICS
IN NORMAL MANNER ( PACK MODIFYING DIAGNOSTICS OF COURSE EXCLUDED!)
EXAMPLE: FAST CHECK IF KL IS ALIVE AND RH11-ACCESS WORKS.
------------------------------------------------
1. MOUNT KLAD-20 PACK ON UNIT 0 ( DUAL PORTED)
2. SET PDP-11 SWITCHES TO OCTAL 203 ( BIT 7 SAYS "BOOT FROM DISK",
BITS 0,1 SAY "DONT'T START KLI UP")
BITS 8,9 AND 10 ARE THE UNIT-NUMBER OF THE DISK AS SEEN FROM THE RH11
;IN THIS CASE UNIT 0.
3. PUSH "ENABLE" AND "SWITCH REGISTER".
4. WAIT TILL CTY PRINTS "[DB0 MOUNTED]".
5. TYPE CONTROL/BACKSLASH TO CALL THE PARSER.
6. IF PARSER ECHOES PAR% OR PAR# SKIP TO STEP 8.
7. IF PARSER ECHOES PAR> , TYPE "SET CON MAI <CARR. RET.>" AND
TYPE "SHUT < CARR. RET.>" TO STOP RUNNING 20.
... NOW YOU SHOULD SEE PAR% OR PAR# !!
8. TYPE "MC BOO <CARR. RET.>" TO PARSER.
9. AFTER YOU SEE BOO> , TYPE "DBOOT <CARR. RET.>"
10.AFTER SOME CLICKING ( RESET'S) YOU ARE IN KLDCP.
*************************************************************
11. SET KLAD-20 PACK WRITE-PROTECT !!!!!!!!!!!!!!!!!!!!!!!!!!
*************************************************************
NOW YOU WANT TO RESET THE 11-SWITCHES TO THE STATE , DIAGNOSTICS NEED ,
IN CASE OF THE "B-COMMAND" , YOU RUN WITH SWITCHES SET TO ZERO.
YOU ARE NOW IN KLDCP AND CAN RUN DIAGNOSTICS. THE FAST ( ROUGHLY 20 MIN.)
CHECKOUT CAN BE CALLED BY TYPING "B <CARR. RET.> TO KLDCP.
AFTER YOU HAVE CHECKED THE SYSTEM ,YOU CAN GET BACK TO RSX20 IN THE
FOLLOWING WAY:
PAGE 4
IF YOU HAVE BEEN RUNNING ANY DIAGNOSTIC , WHICH MIGHT HAVE LEFT BAD
PARITY IN CORE , YOU HAVE TO ZERO MEMORY BEFORE STARTING UP TOPS-20,
SINCE BOOT DOES NOT ZERO 20-MEMORY.
KLDCP ALLOWS YOU TO ZERO CORE IN 64K CHUNKS
MZ 0,-1 ;ZEROES THE FIRST 64K
MZ 200000,-1 ;ZEROES THE NEXT CHUNK .. AND SO ON TILL YOU
;HAVE ZEROED ALL CORE!
THERE IS ALSO A PARSER COMMAND , WHICH WILL WORK MUCH SLOWER;
FOR A 128K SYSTEM THIS COMMAND WOULD BE: ZERO 0>177777 <CARR. RET.>
12. SET KLAD-20 PACK WRITE-ENABLED
RESET PDP-11 SWITCHES TO OCTAL 203
... OR AS YOU HAD THEM IN STEP 2 ...
********************************************************
IF STEP 12 IS NOT DONE , THE FOLLOWING STEPS WILL FAIL !
THE CORRECT PROCEDURE IN THIS CASE IS:
1. STOP THE 11 (HALT SWITCH)
2. WRITE-ENABLE PACK
3. RELOAD AND RESTART 11 FROM SWITCHES
********************************************************
13.TYPE TO KLDCP "SE 173000 <CARR. RET.>" -- ( TRIGGER ELECTRONIC FINGER)
14.AFTER YOU SEE "[DB0 MOUNTED]", TYPE "CONTROL/BACKSLASH"
15.TYPE TO PARSER "RU KLI <CARR. RET.>"
16....AND FOLLOW NORMAL MONITOR-STARTUP PROCEDURES.
B2: USING KLAD-20 WITH TOPS-20 IN TIMESHARING PAGE 5
---------------------------------------------
ASSUMING THAT YOU HAVE TAILORED KLAD-20 FOR YOUR SYSTEM (SEE APPENDIX B:)
YOU PRESS THE DISK AND ENABLE BUTTONS SIMULTANEOUSLY , ANSWER "TIME AND
DATE"-,"WHY RELOAD"- AND "RUN CHECKD"-QUESTIONS ON THE CTY AND LOG
IN UNDER <F-S> FS . YOU ARE NOW ALL SET TO RUN USER-MODE DIAGNODTICS.
TO RUN THE UETP TEST PACKAGE, YOU HAVE TO SUBMIT THE JOBS FROM THE
PTYCON SUB-JOB "UETP". FOLLOW THE INSTRUCTIONS OUTLINED IN
APPENDIX G:
TO GET RID OF UNWANTED LPT-OUTPUT AND TO STOP ALL THE BATCH JOBS
THAT YOU SUBMITTED, YOU HAVE TO TYPE:
CANCEL PRINT */USER:F-S
CANCEL BATCH */USER:F-S
...AFTER SOME TIME OF CLEANUP , THE COMMAND "I O < CARR.RET.>" SHOULD
SHOW THAT THERE IS NO OUTPUT PENDING , AND "I B <CARR. RET.>
SHOULD SAY THAT NOTHING IS IN THE BATCH-QUEUES.
IT IS ALSO GOOD PRACTICE TO DELETE THE LOG-FILES , IF THEY ARE NOT
NEEDED ANYMORE BY DOING AN:
"ENABLE <CARR. RET.>" ; TO PULL DOWN THE FENCES
"DELETE <*>*.LOG < CARR. RET.>" ; TO DELETE THE LOG-FILES
"EXP <*> < CARR. RET.>" ;TO REALLY GET THESE FILES OUT
BEWARE: STARTUP OF KLAD-20 IN TS-MODE REQUIRES THE PACK TO BE WRITE-
ENABLED!
IF YOU WANT TO TURN THE SYSTEM BACK TO THE CUSTOMER , DO A "CONTROL-
BACKSLASH" ON THE CTY , WHICH CALLS IN THE PARSER, TYPE TO THE
PARSER:
"SHUT <CAR.RET.>"...YOU SHOULD SEE A
********KL HALTED***********
NOW YOU CAN SAFELY REMOVE THE KLAD-20 PACK FROM THE DRIVE!
APPENDIX A: CREATING A KLAD-PACK FROM DUMPER TAPES PAGE 6
--------------------------------------
THE CONTENTS OF THIS AND ALL KLAD10 OR KLAD20 MEDIA ARE CONFIDENTIAL IN
NATURE, AND ARE THE SOLE PROPERTY OF DIGITAL EQUIPMENT CORPORATION. ITS
USE IS INTENDED FOR D.E.C. PERSONNEL ONLY!
IT IS NOT PERMITTED TO DISTRIBUTE, RELEASE, OR OTHERWISE MAKE AVAILABLE ANY
OF THE SOFTWARE, DOCUMENTATION, OR ANY OTHER FILES FROM THESE MEDIA TO
PERSONS NOT CONSIDERED BONA-FIDE, AUTHORIZED EMPLOYEES OF DIGITAL EQUIPMENT
CORPORATION.
INDIVIDUALS WHO VIOLATE OR OTHERWISE DISREGARD THIS WARNING WITHOUT
PREVIOUS WRITTEN CONSENT FROM LCG PRODUCT SUPPORT, AND FIELD SERVICE
MARKETING, MAY BE SUBJECT TO DISCPLINARY ACTION.
IT IS SUGGESTED THAT THE USER OF THIS DOCUMENT READ THESE INSTRUCTIONS
AT LEAST ONCE, BEFORE ATTEMPTING TO PERFORM ANY OF THE INDICATED
PROCEDURES.
CONVENTIONS USED IN THIS DOCUMENT:
THE WORD "PROMPT:"
INDICATES AN OUTPUT FROM THE SYSTEM TO THE USER ON THE
USERS' TERMINAL, INDICATING THAT THE SYSTEM IS WAITING
FOR AN INPUT FROM THE OPERATOR (USER).
THE EXPRESSION(S) "CARR.RET" OR <CR>
INDICATES THAT THE USER IS DIRECTED TO INSERT (TERMINATE)
HIS KEYBOARD ENTRY WITH A CARRIAGE RETURN. IN THE MAJORITY
OF CASES, IT IS ASSUMED THAT THE USER WILL TERMINATE ALL
KEYBOARD ENTRIES WITH A "CARR. RET", UNLESS SPECIFICALLY
DIRECTED TO DO OTHERWISE.
THE CHARACTER "$" (DOLLAR SIGN)
THIS IS A VISUAL INDICATION THAT THE "ESC" OR "ALT-MODE"
KEY HAS BEEN USED. WHEN THIS CHARACTER IS USED IN THE
BODY OF A PORTION OF TEXT, OR COMMAND SEQUENCE, IT INDICATES
THAT THE USER IS DIRECTED TO TYPE THE "ESC", OR "ALT-MODE"
KEY WHICHEVER IS AVAILABLE ON HIS KEYBOARD.
*** WARNING *** WARNING *** WARNING *** WARNING ***
BEFORE BEGINNING ANY PORTION OF THIS OPERATION, REMOVE ALL CUSTOMER
DISK PACKS, MAGNETIC TAPES, AND SYSTEM FLOPPY MEDIA, AND PLACE THEM
IN A SECURE AREA AWAY FROM THE SYSTEM
PREREQUISITES: PAGE 7
1. A SOLID KL (DECSYSTEM-20) WITH ONE MAGTAPE, ONE DUAL-PORTED
DISK DRIVE, AND CONSOLE TERMINAL.
2. A FORMATTED AND VERIFIED DISK-PACK (SEE SPECS PRINTED FROM
DDRPI/PAKINT OUTPUT).
****** BEWARE ******
D O N O T M A P O U T S O F T E R R O R S !!
____________________________________________________
3. SYSTEM VERIFICATION BY RUNNING THE 'B' STRING BEFORE
IMPLEMENTING THESE PROCEDURES.
4. The KLAD-20 BACK-UP tapes and system FLoppies.
THE FLOPPIES THAT YOU ARE USING WITH THIS PROCEDURE MUST HAVE
THE FOLLOWING SOFTWARE WITH THE INDICATED SOFTWARE VERSIONS:
RSX-20F VB15-21
KLI.TSK VB15-15
KLX.MCB VER 2.0[400] (MODEL B)
4. This document .. and roughly 90 minutes time !
S T E P S
---------
Mount formatted pack on a dual-ported drive (unit 0), write-enabled
------------------------------------------------------------------------
MOUNT floppy A into left-hand (0) UNIT and floppy B into right-hand (1) UNIT
-------------------------------------------------------------------------
mount first magtape (1 OF 3) on UNIT 0 ( write-protected).
--------------------------------------------------
Set PDP-11 switches to 000003 and PRESS "ENABLE" and "SW-REG" simultaneously.
------------------------------------------------------------------------
!!!***** NOTE *****!!!
FOR THE PURPOSES OF DEMONSTRATION, THIS DOCUMENT WILL ASSUME THAT
THE SYSTEM YOU ARE USING IS A 2060 MODEL B, WITH MOS MEMORY.
IF THE SYSTEM YOU ARE USING IS AN OLDER 2040/2050 MODEL A, OR
A MODEL B, THE COMMAND INTERFACE TO KLI WILL NOT VARY TO ANY
GREAT DEGREE FROM PREVIOUS KLAD20 BUILD PROCEDURES.
IT IS THE INTENTION OF THIS DOCUMENT TO ILLUSTRATE THE DIFFERENCES
IN THE KLI INTERFACE THAT HAVE BEEN INTRODUCED SINCE THE ADVENT
OF MOS MEMORY.
...After some CLICKING YOU will See: PAGE 8
[SY0: REDIRECTED TO DX0:]
[DX0: MOUNTED]
[DX1: MOUNTED]
OPERATOR ACTIONS
-----------------
BEGIN THE PROCESS BY TYPING A CONTROL-BACKSLASH (^\).
THIS WILL ACTIVATE THE PARSER, AND CAUSE THE PROMPT OF:
PAR%> OR PAR>
1. "^\"
PAR>
THE USER WANTS TO ENTER THE PROGRAM 'KLI', SO HE TYPES THE
COMMAND MC KLI <CR> (THIS MEANS A CARRIAGE RETURN)
2. PAR>"MC KLI"<CR>
AFTER SOME SECONDS, AND HEAVY FLOPPY TRAFFIC, THE PROGRAM
KLI WILL START AND PROMPT WILL QUESTIONS REGARDING OPERATIONS
COMMANDS. FOLLOW THIS COMMAND STRING, AND ENTER ALL EXPRESSIONS
CONTAINED BY QUOTES (" "). DO NOT TYPE THE QUOTE (" ") SIGNS!!
KLI -- VERSION VB15-12 RUNNING
KLI -- ENTER DIALOG [NO, YES, EXIT, BOOT]?
3. KLI> "YES"<CR>
KLI -- KL10 S/N: XXXX., MODEL B, 60 HERTZ
KLI -- KL10 HARDWARE CONFIGRUATION:
MOS MASTER OSCILLATOR
EXTENDED ADDRESSING
INTERNAL CHANNELS
CACHE
IF YOU HAVE MCA25 ON YOUR MACHINE, YOU WILL GET THIS QUESTION:
KLI -- SELECT PAGE TABLE [FILE,BOTH,0,1]?
KLI>"BOTH"
* NOTE * XXXX IN THIS INSTANCE IS YOUR SYSTEM S/N:
KLI -- RELOAD MICROCODE [YES, VERIFY, NO]?
4. KLI>"YES"<CR>
KLI -- MICROCODE VERSION 352 LOADED
THIS NEXT QUESTION DEALS WITH ENABLING CACHE. OBVIOUSLY, IF
YOUR SYSTEM DOES NOT HAVE CACHE, YOU WILL NOT SEE THIS PROMPT.
THEREFORE, GO DIRECTLY TO STEP 6.
KLI -- RECONFIGURE CACHE [FILE, ALL, YES, NO]?
5. KLI>"ALL"<CR>
KLI -- ALL CACHES ENABLED
KLI -- CONFIGURE KL MEMORY [FILE,ALL,REVERSE,FORCE,YES,NO]?
PAGE 9
6. KLI>"FORCE"<CR>
STARTING MF20 DBE SCAN. WAIT 25 SEC/256K.
MEMORY RESOURCES:
CONTROLLER ADDRESS TYPE MODULES/GROUPS
7 6 5 4 3 2 1 0
10 MF20 0 0 0 0 0 0 0 4
KLI -- CONFIGURE MOS MEMORY [ALL,YES,NO]?
7. KLI> "ALL"<CR>
****** NOTE ******
IN ALL PROBABILITY, YOUR SITE MAY NOT HAVE THE SAME TYPE OF
MEMORY AS IN THE EXAMPLE ILLUSTRATED IN THIS DOCUMENT. AS
A RESULT, THIS PORTION MAY NOT BE EXACTLY THE SAME AS THE
PRINT-OUT ON YOUR CTY. IF YOUR PARTICULAR SYSTEM HAS CORE
MEMORY, KLI WILL ASK ABOUT CONFIGUATION. YOUR RESPONSE SHOULD
BE "ALL";
U N L E S S
YOU ARE RE-CONFIGURING MEMORY BECAUSE OF A STORAGE MODULE
FAILURE, OR SUSPECT ERRORS IN A GIVEN SECTION OF MEMORY.
LOGICAL MEMORY CONFIGURATION,
ADDRESS SIZE INT TYPE CONTROLLER
00000000 256K 4 MF20 0 10
KLI -- LOAD KL BOOTSTRAP [YES, NO, FILENAME]?
8. KLI>"MTBOOT"<CR>
KLI -- WRITE CONFIGURATION FILE [YES,NO]?
9. KLI --"NO"<CR>
10. KLI -- BOOTSTRAP LOADED AND STARTED
11. MTBOOT>"/E"<CR>
TAPE SHOULD BE LOADING MONITOR INTO -20 MEMORY.
AFTER SOME SHORT PERIOD OF TIME, YOU WILL SEE THE PROMPT
EDDT. NOW, START AT THE 'REFRESH' ENTRY POINT.
12. EDDT
"143<ESC>G"
DO YOU WANT TO REPLACE THE FILE SYSTEM ON THE SYSTEM STRUCTURE?
13. "YES"<CR>
DO YOU WANT TO DEFINE THE SYSTEM STRUCTURE?
PAGE 10
14. "YES"<CR>
HOW MANY PACKS ARE IN THIS STRUCTURE?
15. "1"<CR>
NOTE: KLAD IS ALWAYS A ONE (1) PACK STRUCTURE !!!
ON WHICH "CHANNEL,UNIT" IS LOGICAL PACK # 0 MOUNTED:
16. "?"
WE HAVE ASKED YOU TO TYPE A ? BECAUSE IT IS POSSIBLE THAT YOUR
SYSTEM MAY NOT BE USING CHANNEL 1 FOR LOGICAL DISK UNIT 0.
IN THIS EXAMPLE, WE ARE USING CHANNEL 1, LOGICAL DISK UNIT 0.
BY TYPING A "?" THE SYSTEM WILL TELL YOU WHAT CHANNELS,
UNITS IT BELIEVES THAT IT HAS, AS WELL AS DISK TYPE, AND STATUS.
[ENTER A PAIR OF NUMBERS SEPERATED BY A COMMA THAT SPECIFY THE
CHANNEL AND UNIT UPON WHICH THE APPROPRIATE PACK IS MOUNTED.
THE FOLLOWING IS A LIST OF VALID CHANNEL, UNIT PAIRS:
EXAMPLE:
0,-1,0 ;TYPE=RP06,DUAL PORT
ON WHICH CHANNEL, UNIT IS LOGICAL UNIT 0 MOUNTED :?
17. "0,-1,0"<CR>
DO YOU WANT THE DEFAULT SWAPPING SPACE?
18. "NO"<CR>
HOW MANY PAGES FOR SWAPPING?
******** NOTE ********
IF THE DISK PACK THAT YOU ARE USING IS AN RP04, THEN THE
AMOUNT OF SWAPPING SPACE THAT YOU MUST USE IS 8500 PAGES.
IF THE DISK PACK THAT YOU ARE USING IS AN RP06, THEN THE
AMOUNT OF SWAPPING SPACE THAT YOU MUST USE IS 10000 PAGES.
19. "10000"<CR>
DO YOU WANT THE DEFAULT SIZE FRONT-END FILE SYSTEM?
20. "NO"<CR>
HOW MANY PAGES FOR THE FRONT-END FILE SYSTEM?
21. "8700"<CR>
PAGE 11
DO YOU WANT THE DEFAULT SIZE BOOTSTRAP AREA?
22. "YES"<CR>
WHAT IS THE NAME OF THIS STRUCTURE?
22A. "PS:"<CR>
******** NOTE ********
IF YOUR DISK PACK WAS NOT FORMATTED USING THE "PAKINT" COMMAND
YOU MAY BE ASKED THE FOLLOWING QUESTION:
... WANT TO WRITE A PROTO-TYPE SET OF BAT BLOCKS?
IF THIS MESSAGE DOES NOT APPEAR, GO TO STEP 23.
22B. "YES"<CR>
[STRUCTURE "PS" SUCCESSFULLY DEFINED]
[PS MOUNTED]
NOTE: IF YOU SEE THE FOLLOWING MESSAGE:
%%NO SETSPD --- CONTINUE, THIS IS NORMAL!
ENTER TODAYS' DATE AND TIME AS DD-MM-YY HHMM<CR>
23. 6-NOV-84 1431 (EXAMPLE)
PROMPT: YOU HAVE ENTERED 6 NOVEMBER 1984 2:31 PM
IS THIS CORRECT (Y,N)
24. "YES"<CR> (IF DATE IS CORRECT)
THE NEXT RESPONSE MAY TAKE SOME TIME.
WHY RELOAD?
******************
*BUGCHK "NOLODF" AT 13-NOV-84 14:32:00
*COULD NOT FIND CI-20 MICROCODE LOAD PROGRAM
*JOB: 0, USER: OPERATOR
******************
25. "OT KLAD-BUILD"<CR>
YOU MAY SEE THE FOLLOWING MESSAGE:
<SYSTEM>ACCOUNTS-TABLE.BIN NOT FOUND - ACCOUNT VALIDATION DISABLED
THIS IS NOT AN ERROR ! CONTINUE OPERATIONS !
NO SYSJOB (EXPECTED PRINT-OUT)
26. "^C" (TYPE CONTROL -C TO GET MONITOR ATTENTION)
NO EXEC
MX>
PAGE 12
NOW, WE WANT TO GET THE SYSTEM EXEC FROM MAGTAPE. WHEN YOU
COMPLETE THE FOLLOWING COMMAND STRING, NOTE THAT THE SYSTEM
WILL 'FILL IN' THE MISSING LETTERS.
27. MX>"GMTA0:"<CR> (ECHOES AS: GET FILE MTA0:)
?
MX>
THIS WAS EXPECTED, BECAUSE THE TAPE IS NOT CORRECTLY POSITIONED.
SO, WE TYPE THE STRING AGAIN.
28. MX>"GMTA0:"<CR> (ECHOES THE SAME AS STEP #25)
29. MX>"S"<CR> (ECHOES AS START)
TOPS-20 COMMAND PROCESSOR 6.0(1030)
@
30. @"ENABLE"<CR>
31. $"RUN MTA0:"<CR>
THIS RUNS THE NEXT SEQUENTIAL FILE ON MAGTAPE.
PROMPT: DLUSER>
32. DLUSER> "LOAD MTA0:"<CR>
THIS WILL CREATE THE DIRECTORIES AND THEIR QUOTAS ON YOUR
DISK STRUCTURE. IT MAY TAKE ABOUT A MINUTE OR SO.
YOU MAY SEE THE MESSAGE:
CANNOT FIND ERROR MESSAGE FILEESTR: UNDEFINED ERROR NUMBER PS:<ROOT-D
IRECTORY>
THIS IS NOT A REAL ERROR CONDITION. CONTINUE WITH OPERATIONS.
PROMPT: DONE!
33. DLUSER> "EXIT"<CR>
NOW THAT THE DIRECTORIES ARE CREATED, WE MUST BEGIN THE ACTUAL
RESTORATION PROCESS. THE FIRST PART MUST BE DONE MANUALLY.
34. "RUN MTA0:"<CR>
THIS CALLS IN AND RUNS THE NEXT SEQUENTIAL PROGRAM ON MAGTAPE.
PROMPT: DUMPER>
35. DUMPER>"TAPE MTA0:"<CR>
NOTE THAT IN THE FOLLOWING COMMAND, THE DOLLAR SIGN ($) IS AN
INDICATION THAT THE 'ESC' OR 'ALT-MODE' KEY ON YOUR KEYBOARD
IS TO BE USED. PLEASE REMEMBER THAT ANY TIME YOU SEE THIS
SIGN ($) TYPE THE 'ESC' OR 'ALT-MODE' KEY.
PAGE 13
36. DUMPER>"ACC$SYS$"<CR>
WE WILL BE REPEATING THE NEXT COMMAND SEQUENCE TWICE.
*** NOTE *** IF YOU SHOULD SEE THE MESSAGE:
? SEQUENCE ERROR, RECORD 1, CONTINUING
NO ERROR ! CONTINUE OPERATIONS!
37. DUMPER>"RESTORE <*>*.*.* PS:<*>*.*.*"<CR>
DUMPER TAPE #1, KLAD20-Z-6.0-A EXEC,ERRMES.BIN, TUESDAY 6-NOV-84
LOADING FILES INTO PS:<SYSTEM>
?SEQUENCE ERROR, RECORD 1, CONTINUING
END OF SAVESET
PROMPT: DUMPER>
38. DUMPER>"RESTORE <*>*.*.* PS:<*>*.*.*"<CR>
DUMPER TAPE #1, KLAD20-Z-6.0-A <UTILITIES>, TUESDAY 6-NOV-84
LOADING FILES INTO PS:<UTILITIES>
?SEQUENCE ERROR, RECORD 1, CONTINUING
END OF SAVESET
PROMPT: DUMPER>
39. DUMPER>"EXIT"<CR>
NOW THAT THE 'MANUAL' OPERATIONS ARE NEARLY COMPLETED, WE ARE
GOING TO ENTER THE 'AUTOMATED' MODE.
40. $"DO <UTILITIES>RESTOR.MIC"<CR>
PAGE 14
FOLLOW THE INSTRUCTIONS TYPED BY THE MIC FILE
TO RESTOR ALL TAPES.
YOU HAVE COMPLETED THE BUILD PROCEDURES. TO OBTAIN ADDITIONAL INFORMATION
ABOUT YOUR NEW KLAD-PACK, READ THE ENTIRE DOCUMENT KLAD20.MEM IN
THE <MANUALS> AREA.
IT IS SUGGESTED THAT YOU USE THE "COPY" COMMAND TO THE LINE PRINTER,
OR USE A HARD COPY TERMINAL DEVICE, AND "TYPE" THESE FILES. BE ADVISED,
THEY ARE EXTREMELY LONG . . . . .
EXAMPLES: COPY <MANUALS>KLAD20.MEM$PLPT0:
THIS ECHOES AS: COPY <MANUALS>KLAD20.MEM (TO) PLPT0:
OR IF USING A TERMINAL DEVICE,
TYPE <MANUALS>KLAD20.UPD
PAGE 15
FOLLOW PROCEDURES OF APPENDIX B (TOGETHER WITH HELP FROM THE INSTALLATION-
GUIDE ; ON <MANUALS> ;) TO TAILOR THE SYSTEM ACCORDING TO YOUR PERIPHERALS.
1. CONTROL-BACKSLASH ;PRESS CTRL AND BACKSLASH
;TO GET THE PARSER
;PROMPT: PAR>
2. SHUT ;STOP TIME-SHARING, FORCE KL
;INTO HALT-LOOP
;PROMPT: ***KL HALTED***
SET THE SWITCHES ON THE PDP-11 TO 0207
--------------------------------------
PRESS ENABLE AND DISK BUTTONS ON PDP-11 SIMULTANEOUSLY.
-------------------------------------------------------
YOU WILL NOW SEE THE KL LOADING MICRO-CODE, CONFIGURING MEMORY (ENABLING CACHE
... IF ITS A 2050) AND LOADING BOOTS. A <CARR.RET.> WILL LOAD THE DEFAULT
MONITOR OUT OF <SYSTEM>MONITOR.EXE.
;PROMPT: ENTER TIME AND DATE
3. ......AFTER ENTERING THE TIME AND DATE AND ANSWERING "Y" , IF YOU DID
IT CORRECT ,RUN CHECKD , TO MAKE SURE ,THAT YOUR FILE-SYSTEM IS CLEAN
(ANY ERRORS PREFIXED WITH A "?" NEED INTERVENTION - THE ONES WITH
A "%" SIGN GET FIXED AUTOMATICALLY )-LET PTYCON START THE OPERATOR JOBS
UP , AND FINALLY, LOG IN AS OPERATOR. (PASSWORD IS KLAD, ACCOUNT #
IS NOT REQUIRED.) "ENABLE YOUR PRIVLEDGES, AND CONNECT TO THE DIRECTORY
<SYSTEM>. NOW, YOU MUST CHANGE THE SERIAL NUMBER ON THE KLAD-PACK
TO REFLECT YOUR SYSTEMS' SERIAL NUMBER.
1. LOG OPERATOR KLAD
2. ENABLE ;ENABLE PRIVLEDGES
3. CONNECT <SYSTEM> ;THIS IS WHERE THE FILE RESIDES
4. TV MONNAM.TXT ;THIS FILE CONTAINS THE SERIAL #
5. R1234$XXXX$$ ;WHERE XXXX = YOUR SYSTEMS' SERIAL #
6. ;X$$ ;A $ SIGN INDICATES THE ESC OR ALT-MODE
;KEY. THIS CLOSES THE FILE.
PAGE 16
7. OUTPUT FILE? MONNAM.TXT.1
;WE WANT TO KEEP THE GENERATION
;NUMBER AT .1
8. EXPUNGE ;RELEASES OLD DISK SPACE
9. CONNECT <OPERATOR> ;GET BACK TO YOUR OWN DIRECTORY
10. DEL *.TV ;DELETES UNNECESSARY FILE
11. EXPUNGE ;FREES NEEDED DISK SPACE
NOTE: IT IS GOOD PRACTICE TO CHANGE AT THIS TIME THE PASSWORDS FOR THE TWO
DIRECTORIES , WHICH CAN LOG-IN <OPERATOR> AND <F-S>.
IT IS RECOMMENDED TO CHANGE <OPERATOR>'S PASSWORD (KLAD ) AND <F-S>'S
PASSWORD (FS) TO THE COST-CENTER NR., WHICH SERVICES THIS SYSTEM...
AND TO MAKE THIS CHANGE KNOWN TO THE DDC (COLORADO SPRINGS).
EXAMPLE:COST-CENTER 70W SERVICES YOUR SYSTEM, IN THIS CASE THE PASSWORDS
FOR <OPERATOR> AND <F-S> WOULD BE CC70W.
THIS WILL ALLOW YOU TO KEEP TIGHTER CONTROL OVER KLAD AND ALSO WILL ALLOW
THE DDC (COLORADO) AND OTHER DEC-INTERNAL SUPPORT TO GET ONTO KLAD
AT "WEIRD TIMES OF SORROW".
PAGE 17
APPENDIX B: TAILORING THE KLAD-20 FOR YOUR SYSTEM
-------------------------------------
TO TAILOR YOUR SYSTEM, REFER TO THE TOPS-20 MANUAL SET. YOU
COULD ALSO REFER TO THE KLAD20-USER-GUIDE.DOC FILE IN THE
<MANUALS> AREA OF THE KLAD PACK. NOTE THAT THE PROCEDURE IN
<MANUALS> IS THE PROCEDURE USED BY MANUFACTURING ACCEPTANCE
FOR THE KLAD20.
PAGE 18
APPENDIX C: CREATING A BACK-UP FOR THE KLAD-20 CONTENTS.
--------------------------------------------
EXPERIENCE TELLS, THAT THE GUY WHO HAS BACKUP, NEVER GETS "DONE IN";
BEING SUPERSTITIOUS ( OR EXPERIENCED ) IT IS GOOD PRACTICE TO BE
PREPARED FOR THE WORST.
YOU NEED:
1. KLAD-20 ONLINE AND RUNNING TOPS-20
2. AT LEAST 3 MAGTAPES AND AT LEAST ONE WORKING MAGTAPE-DRIVE.
PROCEDURES (TIME REQUIREMENT ROUGHLY 1 HOUR)
LOG IN AS <F-S>
MOUNT MAGTAPE 1 (FRONT-END TAPE) ON UNIT 0
(WRITE ENABLED 2400 FOOT TAPE REQUIRED)
@LOG F-S FS
@ENA
$CONN <UTILITIES>
$DO SAVE PS,0 ;WHERE PS IS THE STRUCTURE NAME AND 0 IS THE
;MAGTAPE SPECIFIER.
THEN FOLLOW THE INSTRUCTIONS IN THE .MIC FILE.
After mounting a fresh tape type "^P" to start saving
the 20 side of the pack.
...AFTER DUMPER REQUEST A NEW TAPE, DISMOUNT THE
OLD ONE , MOUNT A NEW ONE AND GIVE NEW UNIT-NR.
FOR DUMPER.
LABEL TAPES AS Follows:
;____________________________________________________
;:KLAD20-Z-6.0-PRE-C DEC-PROPERTY :
; TAPE x of y :
;:SAVE BY: :
;: _______________ :
;____________________________________________________
PAGE 19
THE "FRONT-END"TAPE LOOKS IN THE BEGINNING FAIRLY MUCH LIKE
THE INSTALLATION TAPE. ASIDE FROM SPECIALS , THE END OF THIS TAPE
HOLDS A SAVE-SET OF OUR FRONT-END , WHICH CAN BE ROLLED ONTO KLAD
AS LONG AS KLAD HAS MORE THAN 11000 PAGES FREE , WITHOUT USING THE
SLOW AND TEDIOUS RH11. SAFETY FEATURES BUILD INTO OUR SPECIALS CHECK
THE DISK-SPACE ON LOGICAL CONTINGENCY AND (POSSIBLE) HARDWARE ERRORS.
********************************************************************
THE RESTORATION PROCEDURE WILL ONLY WORK, IF YOU HAVE AT
MONITOR-STARTUP DECLARED A FRONT-END AREA OF 8700 PAGES!!!!
********************************************************************
THE FULL-DUMP TAPES CAN BE USED TO ROLL BACK ANY LOST OR DELETED
FILES ON THE 20-SIDE.
PAGE 20
APPENDIX D: GOODIES WHICH YOU MIGHT HAVE TO USE ON KLAD:
--------------------------------------------
1. READ ALLOWS YOU TO CHECK ANY FILES FOR ERRORS , AS LONG AS YOU
ARE ENABLED.SINCE THE RSX-20 VERSION, WE ARE RUNNING, DOES NOT
HANDLE ECC CORRECTION, IT IS GOOD PRACTICE IN THIS CASE TO CHECK
THE INVOLVED FILES FOR PROBLEMS USING READ!
2. FE ALLOWS YOU TO UPDATE FILES ON THE RSX-20 SIDE.
---SO YOU CAN UPDATE DIAGNOSTICS, IF YOU ROLL THEM IN VIA
MAGTAP ONTO THE 20-SIDE!!! READ USEFE.* FOR MORE INFO!!!
****************************************************************
BEWARE!!!!!
KLDCP DOES NOT FULLY UNDERSTAND RSX-20, IT WILL TRY TO RUN THE
FIRST VERSION OF ANY PROGRAM IT FINDS UNDER RSX-20...SO YOU
HAVE TO DELETE THE OLD DIAGNOSTIC VERSION BEFORE YOU SHIP THE
NEW ONE OVER....OTHERWISE RSX-20 WILL TELL YOU THAT THE NEW ONE
IS THERE, BUT KLDCP WILL STILL USE THE OLD ONE...
****************************************************************
3. LPLOAD ALLOWS YOU TO CHECK THE STATE OF THE RAM AND VFU AND
TO JAM-LOAD THESE GUYS BACK INTO THE LPT'S
BEWARE: THE TOPS-20 SYSTEM DOES NOT RELOAD THE LPT-RAM DURING TIME-
SHARING, IF THERE ARE NO ERROR-CONDITIONS, THE ONLY WAY TO FORCE
A NEW RAM-FILE OUT IS LPLOAD.
4. THERE IS AN UPDATED (AND MORE OR LESS WORKING) VERSION OF
FILDDT ON KLAD!!!
5. STRTST ALLOWS YOU TO MOUNT STRUCTURES WITHOUT USING THE
STANDARD CUSPS.
6. DIRTST ALLOWS YOU TO CHECK DIRECTORIES IN DETAIL.
7. .SEQ FILES ARE INCLUDED FOR THE NEW CI AND NI DIAGNOSTICS
IN THE <2-DIAGNOSTICS> AREA.
8. ANOTHER GOOD-NEWS-ITEM!!! KLDCP VERSIONS 17 (AND LATER)
ARE NOW HANDLING ECC !!!!!!!
9. DDRPI NOW IS A LITTLE BIT MORE CLEVER, IT HAS A NEW COMMAND
CALLED PAKINT WHICH ALLOWS YOU TO GO THRU ALL STEPS OF
FORMATTING!! IT ALSO ALLOWS READING AND WRITING ON THE DISK
DURING TIME-SHARING (BE CAREFUL WITH WRITING ON THE CUSTOMERS
PACKS!!!!)
PAGE 21
APPENDIX E: SAVE.MIC
@ENABLE
; Mic file to save KLAD on Magtapes.
;
; Parameters:
; A = Master Structure = 'A:
; B = Magtape = MTA'B:
;
; Type "^P" to continue. Type "^A" to abort.
;
@DEF MTA: MTA0:
=^B
;
@NOERROR
@DEF DSK:
@CONN <UTILITIES>
@DEL SAVE.LOG
;
@ERROR
;
@PHOTO
*SAVE.LOG
*
@
@ENABLE
@DAYTIME
;
@DEF DIS: 'A:
@MOU STR DIS:
;
ASSMAG::
@DEF MAG: MTA'B:
@ASSIGN MAG:
@IF (NOERROR) @GOTO REWMAG
;
; ? Can't assign MTA'B:
; Repair problem and type "^P".
=^B
@BACKTO ASSMAG
;
REWMAG::
@REWIND MAG:
@IF (NOERROR) @GOTO PRIME
;
; Put MTA'B: online. Type "^P" when ready.
;
=^B
@BACKTO REWMAG
;
PRIME::
;
@NOERROR
@SET FILE INVISIBLE DIS:<SPOOL>*.*
@SET FILE INVISIBLE DIS:<SYSTEM>DUMP.*
@DEL DIS:<6-DIAGNOSTICS>*.*.*
@EXP DIS:<6-DIAGNOSTICS>
@ERROR
;
@COPY DIS:<SYSTEM>2060-MONBIG.EXE.* DIS:<6-DIAGNOSTICS>
@COPY DIS:<SYSTEM>EXEC.EXE.* DIS:<6-DIAGNOSTICS>
@COPY DIS:<SYSTEM>ERRMES.BIN.* DIS:<6-DIAGNOSTICS>
;
;**********************************************************
; *
; The following steps create KLAD-20 BACKUP-TAPE 1 *
; *
; CONTENTS: <SYSTEM>2060-MONBIG.EXE *
; <SYSTEM>EXEC.EXE *
; <SUBSYS>DLUSER.EXE *
; DLUSER-FILE to recreate KLAD-DIRECTORIES *
; <SUBSYS>DUMPER.EXE *
; <SYSTEM>EXEC.EXE,ERRMES.BIN *
; <UTILITIES> *
; <ROOT-DIRECTORY>FRONT-END-SYSTEM-*.BIN *
; *
; Assumptions: 2400 feet MAGTAPE on UNIT 0 *
; *
; Time requirements: Roughly 12-15 min WALL-CLOCK time *
; *
;**********************************************************
;
@GET DIS:<SYSTEM>2060-MONBIG.EXE
@SAV MAG:
@GET DIS:<SYSTEM>EXEC.EXE
@SAV MAG:
@GET DIS:<SUBSYS>DLUSER.EXE
@SAV MAG:
;
@START
*STRUCTURE DIS:
*DUMP MAG:
*EXIT
;
@RESET
@GET DIS:<SUBSYS>DUMPER.EXE
@SAV MAG:
;
@CONN DIS:<SYSTEM>
@DISABLE
@START
*TAPE MAG:
*SSNAME KLAD20-Z-6.0-PRE-C
*SAVE DIS:<6-DIAGNOSTICS>*.*.* PS:<SYSTEM>*.*.*
*EXIT
;
@ENABLE
@DEL DIS:<6-DIAGNOSTICS>*.*.*
@EXP DIS:<6-DIAGNOSTICS>
@CONN <UTILITIES>
@DISABLE
;
@START
*TAPE MAG:
*SSNAME KLAD20-Z-6.0-PRE-C <UTILITIES>
*SAVE DIS:<UTILITIES>*.*.* PS:<UTILITIES>*.*.*
*EXIT
@ENABLE
@CONN DIS:<ROOT-DIRECTORY>
;
;*******************************************************************
;This step checks the FE-SYSTEM on DISK-ERRORS ,it takes some time !
;*******************************************************************
;
@RU DIS:<UTILITIES>READFE
*DIS:<ROOT-DIRECTORY>FRONT-END-FILE-SYSTEM.BIN
*COPY FRONT-END-BOOT.BIN DIS:<FE-COPY>FRONT-END-BOOT.BIN
@DISABLE
;
@DIS:<SUBSYS>DUMPER
*TAPE MAG:
*SSNAME KLAD20-Z-6.0-PRE-C Front-end-system copy
*SAV DIS:<ROOT-DIRECTORY>FRONT-END-*.*.* PS:<FE-COPY>
*EXIT
;
@ENA
@RU DIS:<UTILITIES>READFE
*DIS:<ROOT-DIRECTORY>FRONT-END-FILE-SYSTEM.BIN
*REN DIS:<ROOT-DIRECTORY>FRONT-END-BOOT.BIN DIS:<5-DIAGNOSTICS>*.*.*
@RESET
@CONN <SYSTEM>
@UNLOAD MAG:
;
;
TAPE2::
;*******************************************************************
;
; Now to save the entire -20 side with DUMPER.
;
; Note: To continue at this point with a differnt tape unit
; redefine MAG: (i.e. @"DEF MAG: MTA1:")
;
TAPCHK::
;
; Mount tape 2 on tape drive write enabled and online.
; Type "^P" when ready
;
;*******************************************************************
;
;
=^B
;
; Begin saving entire pack
;
@DUMPER
*TAPE MAG:
*ACCSYS
*REWIND
@IF (ERROR) @BACKTO TAPCHK
*
*SSNAME KLAD20-Z-6.0-PRE-C SYSTEM-COPY
*SAVE DIS:<*>*.*.* PS:<*>*.*.*
;
;
; After the first tape (tape 2) is finished mount next
; tape (write enabled) and reissue tape-drive spec
; to DUMPER.
;
; If a second tape drive is available you can
; get it ready and online while the first is
; is still writing and issue the new tape-drive spec
; to DUMPER.
;
; When all areas have been saved type "^P" to
; finish.
;
;***********************************************************
;
=^B
;
@NOERROR
@SET FILE VISIBLE DIS:<SPOOL>*.*
@SET FILE VISIBLE DIS:<SYSTEM>DUMP.*
@ERROR
;
@GOTO END
%ERR::
;
; ERROR in SAVE.MIC
;
END::
@DAY
@POP
@KMIC
APPENDIX F: RESTOR.MIC
;****************************************************************
;* Mic file to start the second phase of a FULL KLAD-20 RESTORE. *
;* *
;* ASSUMPTIONS: EXEC.EXE and ERRMES.BIN in PS:<SYSTEM> *
;* DIRECTORY <UTILITIES> restored *
;* *
;* FRONT-END-AREA previously defined as *
;* length of 8700 pages *
;* *
;****************************************************************
;
MAGTAP::
;
;
@DEFINE MAG: MTA0:
;
; Type "^P" when ready.
=^B
;
@RUN <UTILITIES>PHOTO
*RESTOR.LOG
*
@
@ERROR
@ENABLE
;
@DAYTIME
@TERMINAL NO PAGE
@TERMINAL LENGTH 0
@DAYTIME
;
@RU <UTILITIES>DUMPER
*TAPE MAG:
*ACCSYS
*RESTORE <*>*.*.*PS:<FE-COPY>*.*.*
*EXIT
;
@CONN PS:<FE-COPY>
@RUN PS:<UTILITIES>COPYFE
*<FE-COPY>FRONT-END-FILE-SYSTEM.BIN
*<ROOT-DIRECTORY>FRONT-END-FILE-SYSTEM.BIN
@DELETE <FE-COPY>*.*
@EXPUNGE <FE-COPY>
@RESET
;
@ENABLE
@BUILD <OPERATOR>
*PASS KLAD
*ACC F-S
*
@
@CONN <SYSTEM>
@RU PS:<UTILITIES>MAKDMP
*CREATE PS:<SYSTEM>DUMP.EXE 2048
*EXIT
@
@UNLOAD MAG:
;
; Mount tape 2 on tape drive.
; Type "^P" when ready.
;
;NOTE: To use magtape other than MTA0: redefine MAG:
;
=^B
;
@RU PS:<UTILITIES>DUMPER
*TAPE MAG:
*ACCSYS
*RESTORE <*>*.*.* <*>*.*.*
;*****************************************************************
;* WHEN TAPE #1 HAS FINISHED, DUMPER WILL UNLOAD THE TAPE *
;* FROM UNIT 0 & DEMAND A NEW TAPE FILESPEC. *
;* *
;* WHEN THE TAPE HAS BEEN UNLOADED, MOUNT TAPE #2 *
;* & TYPE "MTA?:", ? IS THE # OF THE UNIT YOU ARE USING. *
;* CONTINUE UNTIL ALL TAPES ARE RESTORED.
;* *
;* WHEN ALL TAPES HAVE BEEN RESTORED
;* TYPE "^P" TO FINISH
;* *
;*****************************************************************
;
=^B
;
;
@GOTO END
%ERR::
;
; ERROR in RESTOR.MIC
;
END::
@DAY
@POP
@KMIC
PAGE 25
APPENDIX G: HELP FILE FOR USING THE UETP TEST PACKAGE
-----------------------------------------------------
MANUFACTURING ENGINEERING
MARLBORO
OCT 1980
MOUNT KLAD PACK ON DRIVE 0 (DUAL PORTED)
BOOT UP THE SYSTEM IN THE MANNER YOU ARE ACCUSTOMED
SWITCH REGISTER LOAD,DISK LOAD,ETC.
ANSWER ALL THE NECESSARY QUESTIONS,AND TYPE DATE & TIME
WHEN ASKED FOR IT. RUN CHECKD ON YOUR INITIAL START-UP
AND WHENEVER YOU BRING THE SYSTEM UP FROM A CRASH.
WHEN 6-PTYCON.ATO IS FINISHED PRINTING,
YOU MAY EITHER LOGIN AS FIELD SERVICE,OR ATTACH TO JOB 1.
IF YOU LOGIN AS FIELD SERVICE, ENABLE CAPABILITIES, & USING
CONFIG.EXE CONFIGURE YOUR KLAD TO THE SYSTEM
(I.E. 6-CONFIG.CMD, 6-PTYCON.ATO,...ETC.) TO YOUR HARDWARE.
IF YOU DO AN ATTACH TO OPERATOR JOB 1, CONN UETP, ENABLE
CAPABILITIES, & USING CONFIG.EXE CONFIGURE YOUR KLAD.
EXAMPLE:
LOG <F-S> FS
ENA
CONN <MFG>
RU CONFIG
--------
OR:
ATT OPERATOR 1 <CR>
[ATTACH CONFIRM] <CR>
PASSWORD (ENTER PASSWORD FOR OPERATOR)
^X
PTYCON>CONN UETP
ENA
CONFIG
AFTER RUNNING CONFIG YOU SHOULD RELOAD THE SYSTEM TO GUARRANTEE
THAT ALL CONFIGURATION CHANGES ARE MADE.
READ KLAD20-USER-GUIDE.DOC IN THE <MANUALS> AREA FOR MORE
INFORMATION.
PAGE 26
APPENDIX H: PROCEDURE TO UPDATE DIAGNOSTIC FLOPPIES.
----------------------------------------
IT IS RECOMMENDED TO UPDATE YOUR DIAGNOSTICS ON YOUR FLOPPIES,
AFTER YOU HAVE BUILT YOUR KLAD-PACK. MOST OF THE
DIAGNOSTICS HAVE GONE THRU UPDATES AND REVISIONS.
THE FOLLOWING PROCEDURE SHOULD BE USED:
(THE EXAMPLE ASSUMES THAT YOU HAVE THE FLOPPY MOUNTED ON DRIVE 0
AND ARE ALREADY IN KLDCPU COMING FROM THE KLAD-PACK ON UNIT 0)
DIR DX0: ;FIND OUT, WHAT IS ON THIS FLOPPY
[IF YOU WANT TO REPLACE EVERYTHING, ZERO THE FLOPPY BY SAYING]
[ZERO DX0: ;THIS ZEROES THE FLOPPY]
DATE 6-NOV-84 ;SET DATE IN FORM DD-MMM-YY
FILE DX0:<RP0:KLDCP.HLP ;TRANSFERS KLDCP.HLP TO FLOPPY FROM DISK.
PAGE 27
APPENDIX I: HOW TO UPDATE YOUR KLAD20 PACK WITH NEW DIAGNOSTIC MAGTAPES.
------------------------------------------------------------
THE FOLLOWING PROCEDURE ASSUMES, THAT YOU HAVE THE SYSTEM STAND-ALONE.
I.E.THE MONITOR HAS BEEN STARTED FROM KLAD, & IS THE PUBLIC STRUCTURE
(PS) ON A DUAL-PORTED DRIVE.
1. LOG IN UNDER <F-S> ON THE CTY (YOU NEED TO TALK TO THE 11 LATER!)
2. MOUNT DIAGNOSTIC MAGTAPE ON MTA0:
NOTE: "$" DENOTES PRESSING OF ESCAPE-KEY.
-----
3. ASS MTA0:<CR> ASSIGNS MAGTAPE DRIVE
--- -----
4. SKIP MTA0: 1 FILE<CR> SKIPS FIRST FILE
---- ----- - ----
5. RU MTA0:<CR> STARTS MAGTAP FROM MTA0
-- -----
6. MTA0:<CR> DRIVE WE USE
-----
7. 1600<CR> DENSITY
----
8. GET MAGTAP.DIR<CR> MOVES DIR ONTO DISK
--- ----------
9. RENAME MAGTAP.DIR$DDXLA.DIR<CR>
------ --------------------
OR
10. RENAME MAGTAP.DIR$DFXLK.DIR<CR>
------ --------------------
11. GET BEWARE.TXT<CR> MOVES TXT FILE ONTO DISK
--- ----------
NOTE: THIS FILE CONTAINS A LIST OF THE DIAGNOSTICS THAT
-----
HAS CHANGED OR BEEN ADDED.
NOW YOU CAN LOOK AT THE DIRECTORY & BEWARE.TXT FILE & DECIDE
WHICH OF THE DIAGNOSTICS THAT YOU WANT TO PUT ONTO THE KLAD.
12. PRESS "CTRL C" "CTRL C" INTERRUPTS MAGTAP & BRINGS
---- - ---- - YOU BACK TO EXEC-LEVEL
13. ENABLE<CR> GIVES YOU PRIVILEDGES
------
14. CONN <4-DIAG$<CR> CONNECTS YOU TO AN EMPTY AREA.
---- --------
15. CONT$<CR> CONTINUES MAGTAP
-----
16. GET X.Y<CR> GETS (X=NAME .Y=EXTENSION) INTO
--- --- <4-DIAGNOSTICS> FROM MAGTAPE.
REPEAT THIS STEP UNTIL YOU
HAVE ALL OF THE DIAGNOSTICS
MOVED OVER INTO <4-DIAGNOS-
TICS> AREA.
NOTE: IT IS ADVISABLE TO GET THE DIAGNOSTICS IN THE ORDER IN
-----
WHICH THEY APPEAR ON THE DIRECTORY, TO AVOID UNNECESSARY
REWINDS.
17. EXIT<CR> GETS YOU BACK TO EXEC-LEVEL
----
18. DIR<CR> SHOWS YOU FILES TRANSFERRED.
---
19. DIR <*-DIAGNOSTICS>X.Y<CR> SHOWS YOU IF ANY OF THE ABOVE
--- ------------------ DIAGNOSTICS IS ALSO ON THE 20
-SIDE OF KLAD. REPEAT THIS
STEP FOR ALL OF YOUR NEW DIAGS
& MARK THEM.
EXAMPLE: DIR <*-DIAGNOSTICS>DDLPA.A10
<2-DIAGNOSTICS>
DDLPA.A10.1
<4-DIAGNOSTICS>
DDLPA.A10.1
IN THIS CASE WE HAVE TO UPDATE THE 20-SIDE IN
<2-DIAGNOSTICS>!!!!!!!!!!
NOTE: FOR EVERY DIAGNOSTIC FOUND ON THE 20-SIDE, ISSUE THE
-----
FOLLOWING COMMAND, WITH THE RIGHT <DIRECTORY>, & THE RIGHT
NAME.EXT. IN OUR EXAMPLE THIS COMMAND WOULD HAVE BEEN:
20. COPY DDLPA.A10$<2-DIAGNOSTICS>$<CR>
---- --------------------------
21. APPEND$DFXLK.DIR$DDXLA.DIR<CR> COMBINING THE DIR FILES
--------------------------
22. RENAME$DDXLA.DIR$<F-S>DIAGS.DIR<CR> COPYING FILES TO F-S AREA
------------------------------
23. DIR <F-S>*.DIR<CR> CHECKING THE DIR
--- ----------
24. DELETE <4-DIAGNOSTICS>*.DIR<CR>
------ --------------------
25. EXPUNGE <4-DIAGNOSTICS><CR>
------- ---------------
26. FE<CR> RUNS PROGRAM ESTABLISHING THE
-- 20 TO 11 CONNECTION FOR FILE-
TRANSFER.
27. PRESS "CTRL C" "CTRL C"
---- - ---- -
28. DET$CONT$<CR> YOU WANT FE TO RUN IN A DE-
--------- TACHED STATE.
29. PRESS "CTRL BACKSLASH" TO GET TO PARSER
---- ---------
30. MC MOU<CR> STARTS RSX20F MOUNT TASK FILE
-- ---
31. FE0:<CR> MOUNTS "FE" DEVICE
----
32. PRESS "CTRL Z"
---- -
33. PRESS "CTRL BACKSLASH"
---- ---------
34. MC PIP<CR> STARTING "PIP" TASK FILE
-- ---
35. TT:=DB0:[6,11]X.Y;*/LI<CR> GET DIRECTORY OF OLD VERSIONS
---------------------- TO BE DELETED.
36. DB0:[6,11]X.Y;*/DEL<CR> YOU HAVE TO DO THIS FOR ALL OF
------------------- THE OLD DIAGNOSTICS.
37. DB0:[6,11]*.*;*=FE0:[340,33]*.*<CR> GETS FILES FROM <4-DIAGNOSTICS>
------------------------------- INTO 11-AREA [6,11]. THIS IS A
SLOW PROCESS.
38. TT:=DB0:[6,11]X.Y;*/LI<CR> THIS WILL GIVE YOU A LIST OF THE
---------------------- DIAGNOSTIC & SHOULD HAVE TODAYS
DATE & TIME.
39. DB0:[5,5]FE11.DIR=DB0:[*,*]*.*;*/DIR<CR> CREATES A DIR FILE OF ALL THE
------------------------------------ FILES CONTAINED IN THE [5,5] &
[6,11] DIRECTORIES.
40. FE0:[340,33]*.*;*=DB0:[5,5]FE11.DIR;*<CR> THIS WILL TRANSFER THE DIR
------------------------------------- FILE TO THE 20-SIDE IN <4-
DIAGNOSTICS> AREA
41. PRESS "CTRL Z" BRINGING IN PARSER
---- -
42. PRESS "CTRL BACKSLASH" PARSER
---- ---------
43. MC DMO<CR> GETTING DISMOUNT PROGRAM
-- ---
44. FE0:<CR> DISMOUNTS THE "FE" DEVICE
----
45. PRESS "CTRL Z" BRINGING IN PARSER
---- -
46. PRESS "CTRL BACKSLASH" PARSER
---- ---------
47. PRESS "CTRL Z"
---- -
48. PRESS "CTRL C" "CTRL C"
---- - ---- -
49. ATTACH <F-S> JOB #<CR> YOUR ATTACHING BACK TO THE JOB
------ ----- --- - YOU DETACHED FROM EARLIER.
50. RSXFMT<CR> STARTING A PROGRAM TO TRANSLATE
------ RSX-ASCII TO 7-BIT-ASCII
51. CONVERT$FE11.DIR$FE11.DIR.1<CR> DOING THE CONVERSION
---------------------------
52. PRESS "CTRL C" "CTRL C"
---- - ---- -
53. CONN <4-DIAG$<CR> GO TO <4-DIAGNOSTICS> AREA
---- --------
54. RENAM$FE11.DIR$<OPERATOR>FE11.DIR$<CR> MOVING FE11.DIR TO <OPERATOR>
----------------------------------
55. DELETE <4-DIAGNOSTICS>*.*<CR> YOU ARE DELETING THE FILES THAT
------ ------------------ YOU HAVE ALREADY PUT ONTO THE
56. EXPUNGE <4-DIAGNOSTICS><CR> FRONT-END AREA
------- ---------------
57. CONN <OPERATOR><CR>
---- ----------
58. VDIR <*>*.*.*,<CR> DOING A DIRECTORY OF THE
---- --------- COMPLETE PACK
59. OUTPUT$KLAD20.DIR<CR>
-----------------
60. <CR>
----
61. DIR<CR> CHECKING TO SEE IF FE11.DIR &
--- KLAD20.DIR ARE IN THIS AREA
BASICALLY YOU ARE NOW DONE, BUT....
IF YOU WANT TO BE PROFESSIONAL, YOU SHOULD APPEND WITH AN EDITOR THE
ASCII-FILE "KLAD20.UPD". THIS FILE IS USED BY MARLBORO TO SHOW YOU THE
CURRENT CHANGES MADE TO THE PACKS, TILL THEY LEAVE THE FACTORY. THE
FILE IS IN <F-S>.
AND...BEWARE, YOUR ORIGINAL BACKUP-TAPES FOR KLAD ARE NOW OUTDATED!!!
FOLLOW THE PROCEDURES OF APPENDIX C TO CREATE YOUR NEW 3 BACKUP-TAPES
TO BE PREPARED FOR THE WORST!!!!
PAGE 32
APPENDIX J. HOW MARLBORO MANUFACTURES KLAD-20 PACKS.
----------------------------------------
REQUIREMENTS:
-------------
1. THE KLAD-20 MASTER-PACK.
2. A SOLID 20-SYSTEM.
3. AT LEAST 2 DISK-DRIVES (ONE DUAL-PORTED FOR THE MASTER
AND ONE FOR THE COPY (NOT DUAL-PORTED)
4. 33 MINUTES PER COPY, IF THE PACK HAS ALREADY BEEN FORMATTED.
OVERVIEW:
---------
THE COPYING PROCESS HAS BEEN STREAMLINED TO MAKE THE PROCESS AS
FOOL-PROOF AS POSSIBLE, TO CUT DOWN ON HUMAN ERRORS. SINCE IN-HOUSE
CONDITIONS ARE SLIGHTLY MORE GENEROUS THAN FIELD-CONDITIONS, THE
PROCESS WAS SPED UP.
BASICALLY A MIC-FILE DOES THE COPY-ING PROCESS.
TO CREATE A NEW PACK YOU MUST FOLLOW THE PROCEDURE BELOW:
1. BRING THE KLAD MASTER SYSTEM UP IN THE WAY YOU NORMALLY
WOULD DO.
2. IF THE UETP JOBS START UP, EITHER CANCEL THE BATCH STREAMS
OR TYPE, "DO <MFG>CANCEL$<RET>".
3. LOG IN AS F-S (PASSWORD FS)
4. TYPE "ENA" TO ENABLE PRIVILEGES.
5. TYPE "CONN <5-DIAGNOSTICS>"
6. CYCLE UP A FORMATTED PACK ON AN AVAILABLE DRIVE. MAKE NOTE
OF THE RH20 # (VARIABLE X IN STEP NUMBER 7) AND THE DRIVE
# (VARIABLE Y IN THE STEP NUMBER 7).
7. TYPE "DO MAKPAK X,Y<RET>", WHERE X AND Y ARE THE RH20 # AND
THE DRIVE # RESPECTIVELY.
8. THE MIC FILE WILL RUN UNITS AND ASK YOU TO CHECK THE RH20 #
AND UNIT # AND TYPE <CTRL>P TO CONTINUE.
9. WATCH THE CONSOLE TERMINAL FOR ERRORS.
10.REMOVE COPY-PACK AND ATTACH LOG-FILES TO PACK.
11.IF THIS WAS THE ONLY PACK TO COPY, GO TO STEP 16
OTHERWISE GO BACK TO STEP 6.
12.TYPE "CONTROL-BACKSLASH" TO GET TO THE PARSER AND TYPE
"SHUT", YOU WILL SEE "DEC-20 NOT RUNNING".
13.REMOVE THE MASTER-KLAD PACK FROM THE DRIVE.
PAGE 34
APPENDIX K: KLAD-20 PATCHING PROCEDURE FOR .A11 FILES
-----------------------------------------
OVERVIEW:
---------
ALL MAJOR DIAGNOSTIC FILES ON KLAD20 ARE PATCHABLE (ALL *.A10 AND ALL
*.A11 FILES, *.BIC AND *.BIN FILES CAN ONLY BE PATCHED VIA UPD2 ON
FLOPPIES.)
THE PATCHING FOLLOWS 3 MAJOR STEPS:
1. GET FILE TO BE PATCHED INTO WORK-AREA AND FIND OUT, WHERE IT IS
KEPT ON KLAD-20.
2. PUT FILE BACK INTO AREA(S) IT IS KEPT ON KLAD-20.
3. UPDATE FILE <MFG>KLAD20.UPD TO KEEP TAB ON CHANGES MADE TO THIS
KLAD-20.
TO MINIMIZE THE WORKING WITH THE DIFFERENT "SAVE"-FORMATS CREATED
ON THE 10/20 BY OUR ASSEMBLERS/LOADERS (MACRO/LINK MACY11, PAL10 ETC)
THE "ASCIIZED" FORMAT WAS INVENTED. CONVRT ALLOWS YOU TO "ASCIIZE"
THE OUTPUT FILES OF THE ABOVE MENTIONED ASSEMBLER/LOADERS AND CROSS-
ASSEMBLERS.
BASICALLY AN *.A11 FILE CONSISTS OF LOAD-LINES AND A TRANSFER-
LINE.
CONVRT TRANSLATES 6-BIT OCTAL VALUES INTO 7-BIT ASCII, STARTING WITH THE
LEAST SIGNIFICANT BITS. PDP11 WORDS ARE THEREFORE REPRESENTED BY 3
ASCII CHARACTERS (6+6+2=16) THIS IS THE BASIC STORAGE UNIT IN ASCIIZED
FILES. PDP10 WORDS ARE TRANSLATED INTO THREE UNITS (16+16+4=36)
6-BIT VALUES BETWEEN 0 AND 74 ARE TRANSLATED INTO 100 TO 154, VALUES
75 TO 77 ARE LEFT UNCHANGED.
THE GENERAL LINE FORMAT IS:
M T C , A , W1 , W2 , ... S <CARRIAGE RETURN>
M = E - PDP11 FILE, T - PDP10 FILE, ; - COMMENT LINE (TITLE)
T = "SPACE" - ASCIIZED LINE , O - OCTAL PATCHING LINE
C = COUNT OF CONCURRENT WORD-UNITS (TIMES 3 FOR PDP10 WORDS)
A = ADDRESS OF FIRST OF THE C CONCURRENT WORDS
WX = CONTENTS OF WORDS
S = CHECKSUM-WORD (SUM OF A AND ALL W'S PLUS S GIVES 16-BIT ZEROES)
PAGE 35
SPECIAL CONDITIONS:
1. IF TYPE-FIELD IS O (OCTAL), THE ADDRESS AND WORD-FIELDS ARE TRANS-
LATED FROM 6 OCTAL NUMBERS INSTEAD OF FROM 3 ASCIIZED CHARACTERS
AND NO CHECKSUM IS EXPECTED.
2. IF THE COUNT-FIELD IS LEFT OUT, THE FOLLOWING ADDRESS-FIELD IS
TAKEN AS THE "START-ADDRESS" OF THE PROGRAM ---TRANSFER-LINE AND
END OF FILE IS ASSUMED.
THE BASIC EDITING SEQUENCE THEREFORE BREAKS DOWN TO:
1. SEARCH FOR TRANSFER-LINE AND INSERT LOAD-LINE IN FRONT OF IT.
EXAMPLE (PDP11-DIAGNOSTIC-A11 FILES; 1 WORD PATCH)
15000/107
LOAD-LINE HAS 1 WORD AND LOOKS LIKE
EO1,15000,107
EXAMPLE (A11-FILES, 2 WORD PATCH)
15002/107
15004/110
LOAD-LINE WILL LOOK LIKE:
EO2,15002,107,110
EXAMPLE:
PUT YOUR KLAD-PACK ON UNIT 0, AND PUT UP BITS 0,1,2,7 ON THE
11 FRONT-END. PRESS "ENABLE" AND "SWITCH REGISTER", THIS WILL
GET YOU RSX-20F.
RSX-20F V15-12 00:03 7-NOV-84
[SY0: REDIRECTED TO DB0:]
[DB0: MOUNTED]
KLI -- VERSION V15-12 RUNNING
KLI -- ENTER DIALOG [NO,YES,EXIT,BOOT]?
1. KLI>YE
--
KLI -- RELOAD MICROCODE [YES,VERIFY,NO]?
2. KLI>YE
--
KLI -- MICROCODE VERSION 352 LOADED
KLI -- RECONFIGURE CACHE [FILE,ALL,YES,NO]?
3. KLI>ALL
---
KLI -- ALL CACHES ENABLED
KLI -- CONFIGURE KL MEMORY [FILE,ALL,YES,NO]?
4. KLI>ALL
---
PAGE 36
LOGICAL MEMORY CONFIGURATION:
CONTROLLER
ADDRESS SIZE RQ0 RQ1 RQ2 RQ3 CONTYPE INT
00000000 128K 01 00 01 00 MA20 4
00400000 128K 03 02 02 02 MA20 4
KLI -- LOAD KL BOOTSTRAP [YES,NO,FILENAME]?
5. KLI>YE
--
KLI -- CONFIGURATION FILE ALTERED
KLI -- BOOTSTRAP LOADED AND STARTED
6. BOOT> <CR> (IF MONITOR.EXE WILL NOT BOOT USE:
2060-MONBIG or 2060-MONMAX AFTER THIS BOOT> COMMAND)
[PS MOUNTED]
SYSTEM RESTARTING, WAIT...
7. ENTER CURRENT DATE AND TIME: 7 NOV 1984 1829
YOU HAVE ENTERED SUNDAY, 7-NOVEMBER-1984 6:29PM,
8. IS THIS CORRECT (Y,N) Y
--
9. WHY RELOAD? <CR>
10. RUN CHECKED? N
--
RUNNING DDMP
SYSJOB 2(6) STARTED AT 7-NOVEMBER-1984 6:29
RUN SYS:CHKPNT
RUN SYS:INFO
RUN SYS:MAILER
RUN SYS:QUASAR
JOB 0 /LOG OPERATOR XX 220100
ENA
^ESET LOGINS ANY
^ESEND * SYSTEM IN OPERATION
^ESET OPERATOR
PTYCON
11. HERE YOU HAVE TO TYPE IN 2 CTRL C'S AND 1 CTRL O
[FROM OPERATOR: SYSTEM IN OPERATION]
12. @LOG F-S (PASSWORD) FS 1
--- --- -- -
13. @ENA ;PULL FENCES DOWN
---
14. $DIR <*>DGMMA
------------
<2-DIAGNOSTICS>
DGMMA.A11.1 ;FIND IF FILE IS ALREADY ON 20-SIDE
15. $I DIS <5-DIAGNOSTICS> ;TO CHECK FOR FREE AREA
- --- ---------------
0 PAGES ASSIGNED
1000 WORKING, 1000 PERMANENT ALLOWED
7540 SYSTEM PAGES FREE
PAGE 37
16. $CONN <5-DIAGNOSTICS> (PASSWORD)
---- --------------- ;CONNECT TO WORK-DIRECTORY <5-DIAG>
;I.E. [340,34] FOR FE.
15. $FE ;START FE-PROGRAM ON CTY
--
18. CTRL "\" ;TO CALL IN PARSER
--
19. PAR>RU MOU ;MOUNT FE-DEVICE
-- ---
20. MOU>FE:
---
MOU -- MOUNT COMPLETE
21. MOU>^Z
--
22. CTRL "\"
---
23. PAR>RU PIP ;START PIP
-- ---
24. PIP>TT:=DB0:[6,11]DGMMA.*/LI
----------------------------
DIRECTORY DB0:[6,11] ;CHECK IF ORIGINAL FILE IS THERE
7-NOV-84 6:31
DGMMA.A11;1
25. PIP>FE:[340,34]*.*=DB0:[6,11]DGMMA.A11
----------------------------------
;TRANSFER FILES TO <5-DIAGNOSTICS>
26. PIP>^Z ;GET OUT OF PIP
--
27. CTRL "\"
--
28. PAR>MC DMO ;DISMOUNT THE FE DEVICE
-- ---
29. DMO>FE0:
----
DISMOUNT COMPLETE
30. CTRL "Z"
--
31. 2 CTRL "C"S ;STOP FE-PROGRAM
-
32. $DIR
---
<5-DIAGNOSTICS>
DGMMA.A11.1 ;IS FILE ON 20?
33. $TV DGMMA.A11
-- ---------
34. *;Y$$
----
INPUT FILE: DGMMA.A11.1
46990 CHARS
PAGE 38
35. *ZL$$ ;GO TO LAST LINE
----
36. *0LT$$ ;TYPE IT OUT
-----
37. *-LT$$ ;TYPE NEXT BUT LAST LINE
-----
;EOF
38. *-LT$$ ;TYPE PREVIOUS LINE
-----
E ,X@,OH@ ;WE ARE AT BEGINNING OF TRANSFER LINE
39. *IEO1,35036,107 ;INSERT PATCH LINE
--------------
40. $$
--
41. *-LT$$ ;CHECK IT
-----
EO1,35036,107
42. *;X$$ ;WRITE FILE BACK
----
OUTPUT FILE: DGMMA.A11.2 !NEW GENERATION!
43. $FE ;START FE(FE STILL MOUNTED)
--
44. CTRL "\" ;GET PARSER
---
45. RU MOU ;STARTS RSX20F MOUNT TASK FILE
-- ---
46. MOU>FE0: ;MOUNTS "FE" DEVICE
----
MOU -- MOUNT COMPLETE
47. MOU>CTRL "Z"
--
48. CTRL "\" ;GETS YOU TO PARSER
--
49. PAR>RU PIP ;START PIP
-- ---
50. PIP>DB0:[6,11]DGMMA.A11;1/DEL ;DELETE OLD VERSION, SO THAT
------------------------- ;KLDCP FINDS THE RIGHT ONE
;OUT OF PIP
51. PIP>DB0:[6,11]*.*=FE:[340,34]DGMMA.A11;2
------------------------------------
;TRANSFER FILES TO 11
52. PIP>TT:=DB0:[6,11]DGMMA.*/LI
------------------------
;CHECK IF FILES GOT OVER
DIRECTORY DB0:[6,11]
14-AUG-77 18:38
DGMMA.A11;2 92. 15-AUGUST-77 18:38
PAGE 39
53. PIP>CTRL "Z"
--
54. CTRL "\" ;GETS YOU TO PARSER
--
55. PAR>MC DMO ;GETTING DISMOUNT PROGRAM
-- ---
56. DMO>FE0: ;DISMOUNTS THE "FE" DEVICE
----
DISMOUNT COMPLETE
57. CTRL "Z"
--
58. 2 CTRL "C"S ;TO STOP FE-PROGRAM
-
59. $DEL *.* ;CLEAN UP <5-DIAG> FOR THE
-------
60. $EXP ;NEXT TIME YOU USE IT
---
61. $I DIS ;CHECK TO SEE IF THE AREA
- ---
;IS DELETED
0 PAGES ASSIGNED
1000 WORKING, 1000 PERMANENT ALLOWED
7536 SYSTEM PAGES FREE
62. CTRL "\" ;GET PARSER
---
63. PAR>SHUT
----
**HALTED**
%DECSYSTEM-20 NOT RUNNING
64. PAR%M BOO
- ---
65. BOO>DBOOT
-----
DECSYSTEM DIAGNOSTIC CONSOLE
VERSION 0.15
SWR = 001207 DTE # 0
CMD:
66. >.RP0
67. >.P DGMMA
68. >.EE 35036
035036 /000107
>.
NOTE: BEWARE!! YOU HAVE JUST CHANGED (IN THIS EXAMPLE) THE CONTENTS
OF THE 11-SIDE OF KLAD. IF YOU HAVE A LITTLE TIME LEFT, YOU
SHOULD ALSO RE-SAVE YOUR KLAD20 UPDATE TAPES. SEE THE
PROCEDURE IN (KLAD20.MEM-APPENDIX C).
PAGE 40
APPENDIX K1: KLAD-20 PATCHING PROCEDURE FOR .A10 FILES
-----------------------------------------
PUT YOUR KLAD-PACK ON UNIT 0, AND PUT UP BITS 0,1,2,7 ON THE
11 FRONT-END. PRESS "ENABLE" AND "SWITCH REGISTER", THIS WILL
GETS YOU RSX-20F.
RSX-20F V15-12 0:03 28-MAR-77
[SY0: REDIRECTED TO DB0:]
[DB0: MOUNTED]
KLI -- VERSION V15-12 RUNNING
KLI -- ENTER DIALOG [NO,YES,EXIT,BOOT]?
1. KLI>YE
--
KLI -- RELOAD MICROCODE [YES,VERIFY,NO]?
2. KLI>YE
--
KLI -- MICROCODE VERSION 352 LOADED
KLI -- RECONFIGURE CACHE [FILE,ALL,YES,NO]?
3. KLI>ALL
---
KLI -- ALL CACHES ENABLED
KLI -- CONFIGURE KL MEMORY [FILE,ALL,YES,NO]?
4. KLI>ALL
---
LOGICAL MEMORY CONFIGURATION:
CONTROLLER
ADDRESS SIZE RQ0 RQ1 RQ2 RQ3 CONTYPE INT
00000000 128K 01 00 01 00 MA20 4
00400000 128K 03 02 02 02 MA20 4
KLI -- LOAD KL BOOTSTRAP [YES,NO,FILENAME]?
5. KLI>YE
--
KLI -- CONFIGURATION FILE ALTERED
KLI -- BOOTSTRAP LOADED AND STARTED
6. BOOT> <CR>
[PS MOUNTED]
SYSTEM RESTARTING, WAIT...
7. ENTER CURRENT DATE AND TIME: 14 AUG 1977 1829
YOU HAVE ENTERED SUNDAY, 14-AUGUST-1977 6:29PM,
8. IS THIS CORRECT (Y,N) Y
--
9. WHY RELOAD? <CR>
10. RUN CHECKED? N
--
PAGE 41
RUNNING DDMP
SYSJOB 2(6) STARTED AT 14-AUG-1977 1829
RUN SYS:CHKPNT
RUN SYS:INFO
RUN SYS:MAILER
RUN SYS:QUASAR
JOB 0 /LOG OPERATOR XX 220100
ENA
^ESET LOGINS ANY
^ESEND * SYSTEM IN OPERATION
^ESET OPERATOR
PTYCON
11. HERE YOU HAVE TO TYPE IN 2 CTRL C'S AND 1 CTRL O
[FROM OPERATOR: SYSTEM IN OPERATION]
12. @LOG F-S (PASSWORD) FS 1
--- --- -- -
13. @ENA ;PULL FENCES DOWN
---
14. $DIR <*>DFDXC
------------
<2-DIAGNOSTICS>
DFDXC.A10.1 ;FIND IF FILE IS ALREADY ON 20-SIDE
15. $I DIS <5-DIAGNOSTICS> ;to check for free area
- --- ---------------
0 PAGES ASSIGNED
1000 WORKING, 1000 PERMANENT ALLOWED
7540 SYSTEM PAGES FREE
16. $CONN <5-DIAGNOSTICS> (PASSWORD)
---- --------------- ;CONNECT TO WORK-DIRECTORY <5-DIAG>
;I.E. [340,34] FOR FE.
*************************************************************
NOTE: IF THE PROGRAM THAT YOU ARE GOING TO PATCH, ONLY EXISTS
ON THE FRONT-END AREA, CONTINUE ON, OTHERWISE SKIP
STEPS 15. THROUGH STEP 32.
*************************************************************
15. $FE ;START FE-PROGRAM ON CTY
--
18. CTRL "\" ;TO CALL IN PARSER
--
19. PAR>RU MOU ;MOUNT FE-DEVICE
-- ---
20. MOU>FE:
---
MOU -- MOUNT COMPLETE
PAGE 42
21. MOU>^Z
--
22. CTRL "\"
---
23. PAR>RU PIP ;START PIP
-- ---
24. PIP>TT:=DB0:[6,11]DFDXC.*/LI
----------------------------
DIRECTORY DB0:[6,11] ;CHECK IF ORIGINAL FILE IS THERE
14-AUG-77 18:34
DFDXC.A10;1
25. PIP>FE:[340,34]*.*=DB0:[6,11]DFDXC.A10
----------------------------------
;TRANSFER FILES TO <5-DIAGNOSTICS>
26. PIP>^Z ;GET OUT OF PIP
--
27. CTRL "\"
--
28. PAR>MC DMO ;DISMOUNT THE FE DEVICE
-- ---
29. DMO>FE0:
----
DISMOUNT COMPLETE
30. CTRL "Z"
--
31. 2 CTRL "C"S ;STOP FE-PROGRAM
-
32. $DIR
---
<5-DIAGNOSTICS>
DFDXC.A10.1 ;IS FILE ON 20?
33. RUN CONVRT.SAV
CONVRT - DECSYSTEM DIAGNOSTIC ASCIIZER CONVERSION PROGRAM [DDQDG]
VERSION 000.014
TYPE /H<CR> FOR HELP
34. FILE:/H
--
COMMANDS TERMINATE WITH <CR>
COMMAND IS FILE.EXT/SWITCH
PDP-10 'EXT' DEFAULT IS 'SAV'
PDP-11 'EXT' DEFAULT IS 'BIN'
PDP-8 'EXT' DEFAULT IS 'BIN'
DX20 'EXT' DEFAULT IS 'BIN'
KMC11 'EXT' DEFAULT IS 'BIN'
MICRO 'EXT' DEFAULT IS 'MCR'
PAGE 43
COMMAND FUNCTION
------- --------
FILE PDP-10 SAVE FILE TO ASCII '.A10' CONVERSION
FILE/T " DEFAULT
FILE/A PDP-10 SAVE FILE TO "SUPER" '.A10' CONVERSION
FILE/S PDP-10 '.A10' FILE BACK TO '.SAV' CONVERSION
FILE/E PDP-11 BINARY FILE TO ASCII '.A11' CONVERSION
FILE/8 PDP-8 BINARY FILE TO ASCII '.A8' CONVERSION
FILE/X DX20 BINARY FILE TO ASCII '.ADX' CONVERSION
FILE/C KMC11 BINARY FILE TO ASCII '.KMC' CONVERSION
FILE/F MINNOW DEBUG MICRO-CODE LISTING TO '.RAM' CONVERSION
FILE/K KS-10 MICRO-CODE LISTING TO '.RAM' CONVERSION
FILE/M MICRO-CODE LISTING TO ASCII '.RAM' CONVERSION
FILE/R MICRO RAM FILE ONLY, NO LISTING
/N DON'T PRINT MICRO CODE ERRORS
/H THIS MESSAGE
YOU HAVE TO CONVERT THE .A10 PROGRAM TO .SAV FORMAT SO YOU CAN
PATCH THE PROGRAM.
35. FILE:DFDXC.A10/S
-----------
CONVERTING COMPLETED, INPUT BLOCKS = 281, OUTPUT BLOCKS = 157
EXIT
36. .GET DFDXC.SAV
--- ---------
JOB SETUP
YOU CAN USE DDT TO FIGURE OUT THE NUMERICAL VALUE OF THE PATCH.
--------------------------------------------------------------
37. .DDT
---
38. 30725/ CAIN 2,10051=306100,,10051
------ -
39. 30741/ MOVEI 10051=201000,,10051
------ -
40. 43254/ CAIN 1,10051=306040,,10051
------ -
41. PRESS CTRL 'C'
-
YOU NOW HAVE THE NUMERICAL NOTATIONS FOR THE PATCH. DELETE
DFDXC.SAV THEN EXPUNGE.
RUN THE CONVRT PROGRAM AS BEFORE, & CREATE ANOTHER DFDXC.SAV
FILE THEN DO THE FOLLOWING:
PAGE 44
42. GET DFDXC.SAV
--- ---------
YOU NOW WANT TO INSERT THE PATCH INTO THE PROGRAM USING MONITOR.
DO A DEPOSIT
43. D 30725 306100,,10061 ;DEPOSITING THE PATCH
- ----- -------------
44. E ;THIS WILL EXAMINE THE LOCATION
- ;THAT YOU JUST PATCHED
45. D 30741 201000,,10061
- ----- -------------
46. E
-
47. D 43254 306040,,10061
- ----- -------------
48. E
-
YOU ARE NOW GOING TO SAVE THE PROGRAM THAT YOU HAVE JUST PATCHED.
49. CSAV DFDXC.SAV
---- ---------
DFDXC SAVED
YOU NOW HAVE TO CONVERT THE .SAV PROGRAM THAT YOU PATCHED BACK TO
AN .A10 PROGRAM.
50. .RUN CONVRT.SAV
--- ----------
CONVRT - DECSYSTEM DIAGNOSTIC ASCIIZER CONVERSION PROGRAM [DDQDG]
TYPE /H<CR> FOR HELP
51. FILE:DFDXC.SAV
---------
CONVERTING COMPLETED, INPUT BLOCKS = 144, OUTPUT BLOCKS = 281
EXIT
52. .DIR DFDXC.*
--- -------
DFDXC.A10
DFDXC.SAV
NOW DELETE & EXPUNGE THE .SAV PROGRAM THAT YOU USED.
YOU DO NOT NEED THIS ANYMORE.
***************************************************************
NOTE: IF THE PROGRAM THAT YOU HAVE JUST PATCHED DOES NOT BELONG
ON THE FRONT-END STOP HERE, YOU ARE DONE. IF THE PROGRAM
DOES GO ON THE FRONT-END CONTINUE ON WITH THIS PROCEDURE.
***************************************************************
PAGE 45
53. $FE ;START FE(FE STILL MOUNTED)
--
54. CTRL "\" ;GET PARSER
---
55. RU MOU ;STARTS RSX20F MOUNT TASK FILE
-- ---
56. MOU>FE0: ;MOUNTS "FE" DEVICE
----
MOU -- MOUNT COMPLETE
57. MOU>CTRL "Z"
--
58. CTRL "\" ;GETS YOU TO PARSER
--
59. PAR>RU PIP ;START PIP
-- ---
60. PIP>DB0:[6,11]DFDXC.A10;1/DEL ;DELETE OLD VERSION, SO THAT
------------------------- ;KLDCP FINDS THE RIGHT ONE
;OUT OF PIP
61. PIP>DB0:[6,11]*.*=FE:[340,34]DFDXC.A10;1
------------------------------------
;TRANSFER FILES TO 11
62. PIP>TT:=DB0:[6,11]DFDXC.*/LI
------------------------
;CHECK IF FILES GOT OVER
DIRECTORY DB0:[6,11]
14-AUG-77 18:38
DFDXC.A10;1 92. 15-AUGUST-77 18:38
63. PIP>CTRL "Z"
--
64. CTRL "\" ;GETS YOU TO PARSER
--
65. PAR>MC DMO ;GETTING DISMOUNT PROGRAM
-- ---
66. DMO>FE0: ;DISMOUNTS THE "FE" DEVICE
----
DISMOUNT COMPLETE
67. CTRL "Z"
--
68. 2 CTRL "C"S ;TO STOP FE-PROGRAM
-
69. $DEL *.* ;CLEAN UP <5-DIAG> FOR THE
-------
70. $EXP ;NEXT TIME YOU USE IT
---
71. $I DIS ;CHECK TO SEE IF THE AREA
- ---
;IS DELETED
0 PAGES ASSIGNED
1000 WORKING, 1000 PERMANENT ALLOWED
7536 SYSTEM PAGES FREE
PAGE 46
72. CTRL "\" ;GET PARSER
---
73. PAR>SHUT
----
**HALTED**
%DECSYSTEM-20 NOT RUNNING
74. PAR%M BOO
- ---
75. BOO>DBOOT
-----
DECSYSTEM DIAGNOSTIC CONSOLE
VERSION 0.15
SWR = 001207 DTE # 0
CMD:
76. >.RP0
77. >.P DFDXC
78. >.EE ##### ;EXAMINE LOCATION THAT YOU PATCHED
035036 /000107 ;SHOULD BE WHAT YOU PATCHED
>.
NOTE: BEWARE!! YOU HAVE JUST CHANGED (IN THIS EXAMPLE) THE CONTENTS
OF THE 11-SIDE OF KLAD. IF YOU HAVE A LITTLE TIME LEFT, YOU
SHOULD ALSO RE-SAVE YOUR KLAD20 UPDATE TAPES. SEE THE
PROCEDURE IN (KLAD20.MEM-APPENDIX C).
--------