Device Extensions User's Guide - Welcome to the van der Mark Site
Contents
1. 05 8 Device Extensions User s Guide Order No AA D319A TA OS 8 Device Extensions User s Guide Order No AA D319A TA ABSTRACT This document describes the software support for the KT8A Memory Management Option and the RX02 and RLO1 devices SUPERSESSION UPDATE INFORMATION This manual is an update of sections of the OS 8 Handbook DEC S8 OSHBA A D OPERATING SYSTEM AND VERSION OS 8 V3D digital equipment corporation maynard massachusetts First Printing December 1978 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such license No responsibility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies Copyright 1978 by Digital Equipment Corporation The postage prepaid READER S COMMENTS form on the last page of this document requests the user s critical evaluation to assist us in pre paring future documentation The following are trademarks of Digital Equipment Corporation DIGITAL DECsystem 10 MASSBUS DEC DECtape OMNIBUS PDP DIBOL 05 8 DECUS EDUSYSTEM PHA UNIBUS FLIP CHI2. 0003 JMS IO AC2000 RLSA TAD 7600 RLWC 0006 JMS IO CLEAR CONTROLLER REGISTERS CLEAR DRIVE REGISTERS AC 1004 BYTE MODE READ HEADER FUNCTION NOTE THAT THIS WORD MUST BE AT LOC 0004 READ NEXT HEADER IN ORDER TO FIND OUT CURRENT CYLINDER READ HEADER BYTE 1 GET LSB OF CYLINDER READ HEADER BYTE 2 CONSTRUCT CYLINDER ADDRESS USE IT AS DIFFERENCE WORD TO SEEK TO CYLINDER 0 SURFACE 0 AC SEEK FUNCTION SEEK TO TRACK O0 AC SECTOR 20 058 BLOCK 0 LOAD SECTOR ADDRESS LOAD WORD COUNT FOR 1 PAGE READ FUNCTION READ SECONDARY BOOTSTRAP READING IN SECONDARY BOOTSTRAP PREVENTS IO FROM RETURNING CONTROL CONTINUES IN SECONDARY BOOTSTRAP C377 C7600 IO 377 7600 RLCB RLSD JMP 1 RLSE JMP I IO JMP BOOT SUBROUTINE TO DO I O TO DISK 0 EXECUTE THE FUNCTION WAIT UNTIL DONE NOTE THIS WORD AND NEXT ONE MUST BE LOCATED HERE IN ORDER TO MATCH UP WITH SIMILAR INSTRUCTIONS CON TAINED IN THE SECONDARY BOOTSTRAP NO ERROR RETURN ERROR TRY AGAIN ABSLDR 15 Bad block mapping on RLOI BASIC patch for BRTS 4 BATCH use with RLO1 23 BOOT program 5 32 Bootstraps for RLOl 6 for RX02 5 BUILD program 5 37 CDF instruction use with extended memory 13 CIF instruction use with extended memory 13 Command registers RLO1 26 27 Core Control Block altering with SAVECB 17 use with FUTIL 5 Data space RLOl 28 Device names
3. eco deme mem e dem No Postage Necessary if Mailed in the United States Cut Along Dotted Line
4. CYLINDER ADDRESS Track Format for Devices A B and C 28 5 2 Handler Description The standard OS 8 device designation format cannot be used with the RLO1 Normally the standard format would use RLA0 to represent Device A of unit drive 0 The single word format used internally to store device names does not distinguish between RK devices and RL devices resulting erroneous RESORC reports and in other anomalies RLO1 therefore uses RLOA to represent unit 0 Device and so forth Table 9 provides information on the RL01 handlers SYS is the same device as RLOA Drive 0 Device A Table 9 RLOl Handler Information Device Entry Device Octal Decimal Name Point Code Length Length Offset Octal Blocks Blocks Octal A brief description of RLOl handler operation is as follows l When initially called each 01 handler executes once only code to read the bad block 115 for its drive handler error return is taken with AC 4000 if an I O error occurs or if the bad block list is found to be invalid valid bad block list begins with a special identification code 2 Get handler arguments 3 Map each block to be transferred around bad blocks by incrementing the block number once for each bad block as listed in the bad block list for the requested device less than or equal to the present block This procedure makes bad blocks effectively disappear 4 Transfer one page sec
5. RLO1 23 RX02 18 Disk format RLO1 25 33 Distribution media 3 Extended mode register 14 FIELD pseudo operator use with extended memory 13 FORTRAN patch for FRTS 4 FUTIL 5 Hardware disk address RLO1 28 INDEX Instruction set RLO1 27 IOT instructions use with KT8A 4 KT8A 7 18 Loading instructions RLO1 31 LXM instruction 14 Memory address register RLO1 25 MEMORY command 12 Monitor head moving with PIP 4 ODT use with extended memory 9 11 PALS8 use with extended memory 12 15 Patches for BRTS 4 for FRTS 4 PIP 4 RESORC 3 Restrictions on extended memory for ABSLDR 15 for MEMORY 12 for Monitor 8 for START 9 RL8A controller format 25 27 RLFRMT 33 messages 34 37 RLOl disk 22 37 bad block mapping 22 bootstrapping 6 32 building a system on 37 command registers 26 27 data space 28 1 INDEX Cont RLOl disk Cont RX02 diskette devices A B and C 23 device names 18 disk format 25 33 formatting with RXCOPY 19 22 handlers 30 interleave scheme for dual hardware disk addresses 28 density 21 instruction set 27 loading instructions 31 memory address register 25 SAVE command RL8A controller 25 27 use with extended memory 8 9 RLFRMT 33 SAVECB program 17 ROM bootstrap 32 Sector address register 26 sector address register 26 START command word count register 26 restrictions on use 9 ROM bootstrap for RLO1
6. RX02 BOOTSTRAP PROGRAM PAL8 V10A NO DATE CLA IAC CLA CML RTL CLA CML IAC RTL RX02 S MUST RUN ON AN OMNI BUS LL CLA CML RAR LL CLA CMA RAR LL CLA CMA RTL E IOT SYMBOLIC EQUATES LOAD COMMAND TRANSFER DATA SKIP IF READY TO TRANSFER SKIP ON ERROR SKIP ON DONE 20 TAD UNIT TRY NEXT COMBINATION OF DENSITY AND UNIT TAD CON360 ADDING IN 360 AND CON420 KEEPING ONLY 420 BITS DCA UNIT CYCLES 400 420 0 20 400 AC6 COMMAND TO READ DISK TAD UNIT UNIT AND DENSITY LCD COMMAND TO CONTROLLER 1 TO SET SECTOR AND TRACK TO 1 JMS LOAD SECTOR TO CONTROLLER LEAVES AC ALONE JMS LOAD AND TRACK 7004 LEAVING A 2 IN AC SERVES AS LITERAL WING IS PART OF WAIT LOOP SAME SECONDARY BOOTS OLD PRIMARY BOOT SDN HAS DONE COME UP CODE STARTS HERE JMP LOAD 1 NO GO CHECK FOR READY TO TRANSFER DONE OR ERROR SER SKIP ON AN ERROR TRY ANOTHER DENSITY ETC SNA NASTY 2 FOR ABOUT TO DO SILO 0 ON START UP JMP READ START UP GO SET UP UNIT THEN READ SILO TAD UNIT ALREADY 2 PUT IN UNIT DENSITY LCD TO EMPTY THE SILO TAD UNIT 6 UP LOC 60 FOR OLD SECONDARY BOOT AND CON360 KEEPING ONLY DENSITY BIT TAD LITRAL ADDING IN 7004 BECAUSE THAT S WHAT SYS WANTS DCA RXlSAV OLD SECONDARY BOOT MOVES IT TO HANDLER 360 LITERAL EXECUTES IN LINE AS A NO OP FALLS THRU TO NEXT PAGE OF LISTING WING CODE SAME AS OLD PRIMARY BOOT JMS LOAD GRAB NEXT ITEM FROM SILO DCA 2 TRADITION SECONDARY BOOT STARTS LO
7. b Support the cartridge from underneath with the left hand C Lower the handle and push the handle slide to the left with the thumb of the right hand d Raise the handle to its upright position to separate the cartridge from the protection cover 2 Place the cartridge in the drive shroud with the handle recess facing the rear of the machine 3 Rotate the cartridge a few degrees clockwise and counter clockwise to ensure that it is properly seated within the shroud 4 Gently lower the handle to a horizontal position to engage the drive spindle 5 Place the protection cover on top of the cartridge 6 Carefully close the drive lid 7 Push the LOAD RUN pushbutton 30 5 3 2 Booting from BOOT SV Boot from the BOOT SV program by using the BOOT or R commands as follows BOOT RL or BOOT RL or R BOOT 7RL 5 3 3 Booting from the Console Switches The following procedure enters the bootstrap program into PDP 8 A memory 1 Press in order the MD and DISP buttons to see what octal numbers are being deposited 2 Press in order 0 and LXA to select memory field 0 3 Press in order 1 and LA to start loading instructions at address 1 4 Deposit the octal values given in Table 3 following each value with D NEXT 5 After all values are deposited press in order 0001 and LA to allow the program to start at location 1l 6 Press in order INIT and RUN to start the bootstrap program 5 3 4 ROM B
8. DIGITAL software or diagnostic programs continued on next page 33 Table 10 Cont RLFRMT Formatter Messages l Normal Messages Cont Message OS 8 OLD DISK PACK SERIAL NUMBER XXXXXXXXXX FACTORY DETECTED BAD BLOCKS PREVIOUS OS 8 BAD BLOCKS NEWLY FOUND BAD BLOCKS NEW OS 8 BAD BLOCKS FORMAT PACK WITH THIS NEW LIST DONE 2 Operator Error Messages Message PLEASE SPECIFY DRIVE NUMBER 0 3 ON WHICH PACK TO BE FORMATTED IS MOUNTED PLEASE WRITE ENABLE DRIVE THEN HIT RETURN Meaning Disk contains valid OS 8 bad block lists A formatted pack contains octal 0123 in words 100 177 of sector 16 octal of surface 0 of cylinder 0 The serial number is the ten digit octal number assigned to the pack at time of manufacture The list of bad blocks manufacturing found at time is printed in the format d nnnn where d A B or the device and nnnn the block number on that device which is bad The current OS 8 bad block are printed lists The list of bad blocks just found by read checking the entire disk is printed This list results from combining the previously printed lists It is the list that is written the pack as the new 05 8 bad block lists User types Y or N to allow or prevent writing the new OS 8 bad block lists Indicates that new OS 8 bad block lists have been written on the pack The pack now may be removed
9. Device Device B and Device Figure 2 1 shows device designation an RLO1 disk The 05 8 Device Extensions provide for the standard 05 8 System Non System I O transfer of 1 to 32 decimal memory pages to or from one of three RLO1 devices devices are located on any one of four RLO1 disk drives Disk data space consists of 777 octal tracks As shown in Figure 2 data on a single track is made up of 40 equal length sectors numbered 0 through 47 octal This results in 20 decimal blocks four assigned to Device C and 16 to Device A or B DISK DATA SPACE ONE RLO1 TRACK Track and Sector numbers are octal Block numbers are decimal Figure 2 Devices B C on RL01 Disk Approximately 10 000 decimal 05 8 blocks are supported per drive 40 as Device A 40 as Device B and 20 as Device C This scheme provides some user control over the tradeoff between the number of devices and the length of each device Device C has a different length from Devices A In general Device C is used only when a maximum amount of data is to be stored on the disk 22 Each device supports up to 15 decimal bad blocks to provide bad block mapping These blocks may be thought of as spares and should never be accessed by the user This support involves invisible mapping of OS 8 block numbers into the set of actual good disk blocks utility program need be changed including SQUISH and user
10. HERE TAD CORLOC SAVE CURRENT CONTENTS NOP FOR PDP 8 DCA CORI TAD COR2 7000 IS A GOOD PATTERN DCA I CORLOC 37 HACK FOR PDP 8 NO OP TAD I CORLOC TRY TO READ BACK 7000 7400 HACK FOR PDP 8 NO OP TAD CORX GUARD AGAINST WRAP AROUND TAD CORV TAD 1400 52 JMP COREX NON EXISTENT FIELD EXIT TAD CORI RESTORE CONTENTS DESTROYED DCA CORLOC ISZ CORSIZ TRY NEXT HIGHER FIELD JMP CORO COREX CDF LEAVE WITH DATA FIELD O0 TAD CORSIZ 1ST NON EXISTENT FIELD JMP I CORE CORLOC CORX ADDRESS TO TEST IN EACH FIELD CORV 1400 7000 7400 1400 0 CORSIZ 1 CURRENT FIELD TO TEST C4 4 Figure 1 Memory Size Subroutine 3 4 VXAO Extended Memory Device The VXAO device handler enables you to use the extended memory provided by the KT8A as though it were a separate device You call VXAO in the same way that you call any system device For example this command UXA0 S MPLEXRXAOt SAMPLE copies a program called SAMPLE into an area of memory above 32K words The VXAO device provides high speed I O for users with diskettes users who want the performance of a fixed head disk type of storage device 15 3 5 The SAVECB Program SAVECB is a demonstration program that enables you to alter the contents of a program s Core Control Block You will find this routine useful in a SAVE with arguments involving more fields memory than you can specify in a single SAVE command line This is likely to h
11. awareness of this feature is not required Bad block lists are kept resident to reduce the extra reads required Bad block lists that occur during disk manufacture are maintained in factory generated lists which are stored on track 777 of the disk The OS 8 system preserves five copies of the factory list all of which are identical When a disk is initially formatted using OS 8 the formatting program RLFRMT ascertains that the disk is new program then reads in the factory list and checks the disk for any new bad blocks The factory 115 and the new bad block list are then combined and after the user s go ahead the formatting program writes the newly generated 05 8 bad block list on track 0 of the disk When running OS 8 you may generate an I O error because of bad block You can check this by again running the formatter program RLFRMT ascertains that the disk is already formatted so it reads the previous 05 8 bad block list and checks the disk for any new bad blocks When you instruct it to proceed the formatting program writes the updated 05 8 bad block list on track 0 of the disk You should not allow the bad block list to be written if unexpectedly large number of bad blocks are reported formatting to remove bad blocks is a permanent irreversible procedure During an I O transfer the handler first reads in the 05 8 bad block list for the device The system effectively maps around the bad blocks This ha
12. ffnnnn ffmmmm that you wish to SAVE must both exist in the same field You may not cross field boundaries In the following example both entries specify field 22 SAVE SYSSEXAMPL 220055 220643 e you specify an area on a page SAVE takes the entire page If you call for another part of that page in the same command line SAVE sends a BAD ARGS error message to the terminal informing you that it has already saved the page SAVE RXA1 FLOF 120077 120122 120146 120177 The first argument writes locations 77 to 122 in field 12 to RXAl and calls the file FLOP SV The second argument which specifies locations on the same page produces the error message ARGS e Do not SAVE locations 7600 7777 in fields 0 l and 2 The resident Monitor code resides in these areas of memory To avoid accidently destroying a portion of the Monitor restrict SAVE operations involving 7600 to fields above 2 e If you specify an address on an odd numbered page SAVE save it only if it also saves the preceding page The system does this automatically If you wish to specify more locations a SAVE command than you fit in a single command line use the SAVECB program described in Section 3 5 NOTE The Monitor START command currently accepts field specifications the range of 0 to 7 only 3 1 2 ODT Command ODT accepts and returns 6 digit addresses the following commands ffnnnn ffnnnnB ffnnnn
13. if desired DONE is always followed by DRIVE to allow formatting another pack Meaning RLFRMT could not interpret user response to DRIVE User can try again RLFRMT found the selected drive write locked just before attempting to write new OS 8 bad block lists on the pack continued on next page 34 Table 10 Cont RLFRMT Formatter Messages 3 Warning Messages formatting can still be done If the user permits the new OS 8 bad block lists to be written the OS 8 block numbering scheme will changed due to a new bad block found during the read check of the entire pack This will make garbage out of any files located at and after the block number Message WARNING AN ADDITIONAL BAD BLOCK FOUND ZERO DISK BEFORE USE WARNING BAD BLOCK IN SYSTEM AREA DO NOT USE AS SYSTEM DISK bad block was found during the read check of the pack This new bad block was on Device A between 0 and 66 inclusive Since no bad blocks allowed in this area for the system device due to bootstrapping constraints permitting the pack to be formatted disallows future use as a system device Non system use is unaffected WARNING ALL FACTORY WRITTEN LISTS DESTROYED All copies of the manufacturing detected bad block list and disk pack serial number have been destroyed by non Digital software Formatting continue
14. last breakpoint Open the Search Mask location initially set to 7771 To change the Search Mask type a new value into the location Open the lower search limit location Type in the location four octal digits where the search will terminate Open the upper search limit location Type in the location four octal digits where the search will terminate Search the portion of memory defined by the upper and lower limits for the octal value nnnn The search must be restricted to a single memory field See the F command Open for modification the location containing the data field 0 to 37 that was in effect at the last breakpoint To change the field enter a number from 0 to 37 Open for modification the word containing the field 0 to 37 used by ODT in the last W or uparrow command search or indirect addressing or in the last breakpoint depending on which occurred most recently To modify this location enter a number from 0 to 37 Interrupt a lengthy search output and wait for the next ODT command Cancel a number previously typed up to the last non numeric character entered ODT responds with a question mark after which you enter the correct location 10 3 1 3 CCL Memory Command The MEMORY command finds the highest field available hardware up to field 37 It also limits the available fields in software but this feature is currently restricted to 32K words The format of the command is
15. 001 RL8A Disk Controller Maintenance Manual EK RL8A TM 001 1 1 Distribution Media The OS 8 Device Extensions are distributed on the following media RX02 diskette RLOl disk RK05 disk TD8E DECtape 1 2 RESORC Program The new RESORC program lists the system and non system handlers for the RX02 RL0l1 devices In addition it lists a special handler called VXAO that enables you to use the extended memory provided by the as though it were a separate device RESORC now has an overlay structure enabling a user who buys the source program to enter information on user written handlers 2 1 3 Changes in BASIC and FORTRAN IV for RLOl and RX02 Users 01 and RX02 users must add the following patches to the BASIC FORTRAN IV run time systems so that these programs recognize and properly allocate space in memory for the second page of the system handlers To patch the BASIC run time system enter the following commands LOAN SYS iBRTS SUZ T LOAN SYSTBRTS SU where dev is the distribution device BPAT BN is the BASIC patch To patch the FORTRAN IV run time system enter the following commands SYSTIFRTS SUZI LOAN 5 65 is the distribution device FPAT BN is the FORTRAN IV patch 1 4 System Wide Changes for Users with the KT8A KT8A users must ensure that user written programs and user writt
16. 1l Table 1 Device Extensions Modules OS8 MONITOR system head capable of being run from the device supports 128K words of memory System Programs ABSLDR SV loads binary and image code into fields gt 7 PAL8 SV uses fields gt 7 CCL SV CCL MEMORY command recognizes up to 128K words available in system PIP SV works with RLO1 RX02 VXAO and new system head RESORC SV includes 01 RX02 and VXAO BOOT SV includes primary bootstrap for RLOl RX02 and VXAO RXCOPY SV formats single or double density diskettes copies single density to single density and double density to double density FUTIL SV recognizes new core control block format for programs in extended memory continued on next page Table 1 Cont Device Upgrade Kit Modules Patches to be added with LOAD and SAVE commands BPAT BN Patch for BASIC Comment FPAT BN Patch for FORTRAN IV Handlers to be inserted with BUILD RLSY BN RLOl System Handler RLO BN RLOl Non system Handlers RL1 BN RL2 BN RL3 BN RLC BN VXSY BN VXAO0 System Handler RXSY1 BN RX0l System Handler RXSY2 BN RX02 System Handler RXNS BN RX01 RX02 Non system Handler This manual assumes that the user is familiar with the material in the following documents OS 8 Handbook DEC S8 OSHBA A D 05 8 Handbook Update DEC S8 OSHBA A DNA4 OS 8 Software Support Manual DEC S8 OSSMB A D Memory Management Control User s Guide EK KTO8A UG
17. 32 01 diskette VXAO device 16 compatibility with RX02 19 formatting with RXCOPY 22 interleave scheme 20 Word count register 26 Index 2 Please cut along this line 05 8 Device Extensions User s Guide AA D319A TA READER S COMMENTS NOTE This form is for document comments only DIGITAL will use comments submitted on this form at the company s discretion If you require a written reply and are eligible to receive one under Software Performance Report SPR service submit your comments on an SPR form Did you find this manual understandable usable and well organized Please make suggestions for improvement Did you find errors in this manual If so specify the error and the page number Please indicate the type of reader that you most nearly represent Assembly language programmer Higher level language programmer Occasional programmer experienced User with little programming experience Student programmer Other please specify Nae c et ee Date Organization Street Oltyu i gt SAC Zip code or Country DoNotTear Fold Here and Tape BUSINESS REPLY MAIL FIRST CLASS PERMIT NO 33 MAYNARD MASS POSTAGE WILL BE PAID BY ADDRESSEE RT C SOFTWARE PUBLICATIONS ML 5 5 E45 DIGITAL EQUIPMENT CORPORATION 146 MAIN STREET MAYNARD MASSACHUSETTS 01754 eom conos Do Not Tear Fold Here cm mcm
18. 600 040777 y 030200 030600 020200 020377 016400 017377 000000 007577 To place this core control block in the system area on the device type after the prompt 0 To make a memory image file of the segments specified in the run FLOP SV with the R command aborting execution with CTRL C Then save the segments under the new name with a SAVE command without arguments aR FLOP SV 2 SAUE FLAP SY To change a segment first subtract the entire segment with the 5 command Then enter the altered version with the A command 4 0 THE RX02 DUAL DENSITY DISKETTE The OS 8 V3D Device Extensions include system and non system handlers for RX01 and RX02 the devices for single density and double density diskettes The new handlers run on both RX01 and RX02 hardware NOTE e The old 05 8 handlers including BOOT RX will not run on RX02 e RX02 with a single density hardware switch set is identical to an RXOIl 4 1 RX02 Device Names To specify an RX02 diskette OS 8 command line enter the same device names you use for RXxXOl OS 8 recognizes the following permanent names DSK Default output device usually same as SYS SYS System device usually the diskette in drive 0 RXAO The diskette in drive 0 1 diskette drive 1 17 SYS is most accurately defined as the device that you have bootstrapped This is usually the device in drive 0 However the hardware will also bootstrap a device in dri
19. ADING AT 2 157 50 INCREMENT LOAD ADDRESS JMP 47 GO BACK FOR ANOTHER DARY BOOT LOADS OVER PRIMARY BOOT UNIT LOCATION 47 IS LOADED CONTROL PASSES TO SECONDARY BOOT 00053 90054 00055 00056 00057 00060 00061 0000 6753 5033 6752 5453 9420 0020 LOAD 0 5 JMP XDR JMP I RX02 BOOTSTRAP PROGRAM START LOAD SUBROUTINE TO GIVE AND TAKE DATA FROM CONTROLLER 15 HE READY TO TALK TO US NO IS HE PERHAPS DONE WITH SILO OR IN ERROR XES DATA IN OR OUT IF DATA TO CONTROLLER AC UNCHANGED NO MAGIC JUST EXIT FROM SUBROUTINE 60 GOES TO OLD SECONDARY BOOT 61 HAS DENSITY AND UNIT THAT BOOTED SUCCESSFULLY CON420 RX1SAV 420 UNIT 20 USE IT TO HOLD 420 LITERAL TO START OUT UNIT 20 7004 TO GO TO SYS HANDLER XDENSITY 400 UNIT 20 THAT BOOTED OK 00001 00002 00003 00004 00005 00006 00007 00010 00011 00012 00013 00014 00015 00016 00017 00020 00021 00022 00023 00024 00025 00026 00027 00030 00031 00032 00033 00034 00035 6600 7201 4027 1004 4027 6615 7002 7012 6615 0025 7004 6603 7325 4027 7332 6605 1026 6607 7327 4027 0377 7600 0000 6604 6601 5031 6617 5427 5001 APPENDIX RLO1 BOOTSTRAP PROGRAM 0001 IAC 0003 CLL CML IAC RAL 0006 CLL CML RTL AC2000 CLA CLL CML RTR BOOT RLDC 0001 JMS IO TAD JMS IO RRSI BSW RTR RRSI AND C377 RAL RLCA
20. G where ff is a field from 0 to 37 nnnn is a location The D and F command allow you to specify fields in the range of 0 to 27 To indicate the first eight fields type a single octal digit 0 7 Note that this is a change from previous versions of ODT which required you to enter field specifications as multiples of 10 for example field 2 as 20 Table 4 summarizes all of the OS 8 128K ODT commands For complete information on ODT see the chapter on the ODT program in the OS 8 Handbook Table 4 128K ODT Command Summary Operation Open location ffnnnn where ff is a field from 0 to 37 ODT displays the contents of the location prints a space and waits for you to enter new value for the location or close the location If you omit ff ODT assumes field 0 ffnnnn Reopen the most recently opened location Deposit nnnn in the currently opened location close the location and open the next location in the sequence for modification The semicolon lets you deposit a series of octal values in sequential locations To skip locations in the sequence type a semicolon for each location you wish to leave unchanged RETURN key Close the currently open location LINE FEED key Close the currently open location open the next location in the sequence for modification and display its contents Open the current location plus n and display the contents Open the current loc
21. K under 05 8 will also operate with the new monitor addition systems with the KT8A and 128K software support will run user written programs memory fields 0 to 37 05 8 high level languages and system programs however do not make use of memory greater than 32K words This section describes the 05 8 commands and PAL8 instructions that allow you to run user written programs in fields 0 through 37 addition it includes a subroutine for finding the amount of memory available at run time and describes a program that enables you to change the Core Control Block of a program in complex SAVE operations This section also notes current software restrictions on the use of the extended memory For a description of the KT8A device including operating and programming instructions see the KT8A Memory Management Control User s Guide EK KT08A UG 001 3 1 128K Monitor and CCL Commands SAVE ODT and MEMORY The SAVE and ODT monitor commands now support fields 0 to 37 The CCL MEMORY command finds the highest field available in hardware up to field 37 MEMORY also limits the available fields software but this feature is currently restricted to 32K NOTE The OS 8 Monitor currently requires that all user written programs contain at least one segment l page minimum below 32K 3 1 1 SAVE Command The SAVE command makes memory image file of the program currently in memory assigns it a name and saves it on a d
22. MEMORY or MEMORY nn where nn is an octal number in the range of 0 to 37 representing the number of 4K fields available to OS 8 Table 5 lists all the values of n memory fields octal and the corresponding memory size Table 5 Field Specifications for 128K MEMORY Command Words of Memory all available memory 0 1 2 3 4 5 6 7 To limit memory enter the highest file you want to make available to OS 8 in the command line For example the following command limits the available memory to 16K words MEM 3 To find the amount of memory that OS 8 is using type the command with no argument MEMORY 12K 32K MEMORY In this example MEMORY prints the information that a 32K system has been limited to 12K words MEMORY caused the execution of the CCL SV program 3 2 128K PAL8 The following PAL8 instructions accept field specifications the range of 0 to 37 permitting you to run programs in areas above 32K ll 3 2 1 FIELD Pseudo Operator The pseudo op FIELD instructs PAL8 to output a field setting so that it can recognize more than one memory field The format of this pseudo op is FIELD ff where ff is an integer a previously defined symbol or an expression in the range 0 to 37 FIELD causes the PAL8 assembler to output a field setting from 0 to 37 during the second pass of assembly This setting which appears as the high order bits of the location counter in the program listing te
23. P RSTS COMPUTER LABS FOCAL RSX COMTEX INDAC TYPESET 8 DDT LAB 8 TYPESET 11 DECCOMM DECSYSTEM 20 TMS 11 ASSIST 11 RTS 8 ITPS 10 VAX VMS SBI DECnet IAS i Aa C CO CO CO CO F mb mPmbmpbmPmPBouuuu uttmpmpmotur PWN e e e e e 4 w NEF WN HP Ee PEPER WWWWWW WWNEPRPEPP mpppmPmp CONTENTS INTRODUCTION AND OVERVIEW Distribution Media The RESORC Program Changes in BASIC and FORTRAN IV for 01 and RX02 Users System Wide Changes for Users with the KT8A Changes in PIP for RLO1 RX02 and VXAO The BOOT SV Program Changes in FUTIL BOOTSTRAP AND BUILD INSTRUCTIONS THE KT8A MEMORY MANAGEMENT OPTION 128K Monitor and CCL Commands SAVE ODT and MEMORY The SAVE Command The ODT Command The CCL Memory Command 128K PAL8 The FIELD Pseudo Operator Specifying Data and Instruction Fields CDF and CIF The ABSLDR Determining Memory Size at Run Time The VXAO Extended Memory Device The SAVECB Program THE RX02 DUAL DENSITY DISKETTE RX02 Device Names Formatting Diskettes for RX02 RXOl and RX02 Compatibility Interleaving Using RXCOPY with RX02 Formatting Diskettes with RXCOPY RXCOPY Options THE RLOl DISK System Description Disk Format RL8A Controller Format Instruction Set OS 8 Data Space Converting Block Numbers to Hardware Disk Addresses Handler Description Loading and Bootstrap Procedure Loadi
24. ROYED FREVIQUS 05 8 BLOCKS NONE NEWLY FOUND BAD BLOCKS A 6374 63795 0360 B 4347 B 4350 COSLA C 0515 C 2073 WARNING ADIDITION L BLOCK FOUND ZERO HISK BEFORE USE NEW 05 8 BLOCKS A 6374 A 6375 0360 B 4347 B 4350 C 0514 05150 2073 FORMAT FACK WITH THIS NEU LIST The formatter program then writes or does not write special 05 8 block lists on the pack depending on a Y or N user response These lists include only the factory detected and newly detected bad blocks for new packs or previous OS 8 and newly detected bad blocks for old packs Warnings are given for various conditions as appropriate see Table 10 NOTE Reformatting a previously used disk pack will make any newly detected bad blocks effectively disappear from the Any files located at or after any such new bad blocks however will turn to garbage due to the implicit renumbering of all OS 8 blocks past those points Table 10 lists normal formatter messages operator error messages and program error messages Table 10 RLFRMT Formatter Messages l Normal Messages Message Meaning RLFRMT Vvp Identifies start of operations v is version number is patch level letter DRIVE Requests user to type drive number and RETURN key UNFORMATTED NEW DISK PACK Disk does not contain 05 8 bad block lists either because the disk 15 brand new or because these lists have been destroyed by non
25. appen in systems with 128K words of memory since the number of fields you may wish to specify increases from 10 to 40 octal The format for summoning SAVECB is R SAVECB file SV where file SV is the name of program whose CCB you want to change SAVECB responds with a number sign to indicate that it is ready to accept one of the following commands TYPE displays core control block of file SV Affmmmm ffnnnn adds segment to CCB Sffmmmm ffnnnn subtracts segment from CCB To exit from the program type 0 This writes the updated Core Control Block onto the system area of the device In order to change the program s CCB you must load the program with the R command typing CTRL C to abort execution and then create a memory image file with SAVE For example assume you want to save segments of program FLOP SV as a memory image file called FLAP SV First you modify the CCB with SAVECB SAVECE FLOF SU 96 SAVECB responds with a number sign inspect the CCB of your program type SAVECB displays the starting location of the program its Job Status Word and the segments in memory that it uses START 0000 5 2000 CORE SEGMENTS 040200 040377 020200 0202377 016400 0173577 000000 007577 To add segments to the enter them after the prompt 0200 50600 40600 40777 16 Now examine the CCB again START O00200 SSW 2000 CORE SEGMENTS 3 040290040377 s 040
26. ation minus n and display the contents uparrow or circumflex Close the location read its contents asa memory reference instruction and open the location it points to displaying its contents e ODT makes no distinction between instruction op codes when you use this command It treats all op codes memory reference instructions Take care when you use this command with indirectly referenced auto index registers If you use the command this way the contents of the auto index register is incremented by Check to see that the register contains the proper value before proceeding continued on next page Command underline ffnnnnB ffnnnnG M lt LF gt lt LF gt CTRL O DELETE key Table 4 Cont 128K ODT Command Summary Operation Close the current location read the contents as a twelve bit address and open that location for modification displaying its contents Establish a breakpoint at location ffnnnn where ff indicates a field from 0 to 37 ODT permits only one breakpoint at a time Transfer control of the program to location ffnnnn where the first two digits ff represent a memory field Remove the breakpoint if one exists Open for modification the location in which ODT stored the contents of the accumulator when it encountered the breakpoint Open for modification the location in which ODT stored the contents of the Link when it encountered the
27. der 05 8 including system building Mount the RLOl disk pack Section 4 2 Format the RLO1 disk by using the following procedure l Type aR RLFRMT to run the formatter program RLFRMT Vvp is printed on the terminal signifying the start of the operation where v is the version number p is the patch level letter the program then prompts with 2 the drive number 0 3 which the pack is mounted The formatter program then reads all blocks on the disk to detect any new bad blocks The process takes 35 to 40 seconds After this period an initial display is presented as follows UNFORMATTED NEW DISK PACK SERIAL NUMBER nnnnnnnnnn FACTORY DETECTED BAD BLOCKS NONE NEWLY FOUND BAD BLOCKS NONE NEW OS 8 BAD BLOCKS NONE FORMAT PACK WITH THIS NEW LIST The messages are explained in Table 10 RLFRMT Formatter Messages 3 Type a Y or N followed by a RETurn in response to the last message FORMAT PACK WITH THIS NEW LIST to either allow or prevent the writing of the new OS 8 bad block lists The program signifies completion of this operation by displaying DRIVE Type CTRL C to return to the OS 8 monitor Remove the pack or designate another drive for formatting 32 The following example illustrates possible messages that be generated during a particular sequence of 05 8 01 formatting operations if bad blocks are found 05 8 COLD DISK WARNING ALL FACTORY WRITTEN LISTS UEST
28. en handlers do not contain the following combination of instruction steps CIF Change instruction field IOT Any PDP8 IOT instruction JMP I The instruction that does the CIF If you enable the KT8A and turn on the interrupts for example to run OS 8 background task under RTS8 the KT8A hardware will return to the wrong place on traps between the CIF and JMP I instructions 1 5 Changes in PIP for RLOl RX02 and VXAO The new version of PIP recognizes the RLO1 RX02 VXAO devices PIP sets the proper length for directories on the ZERO command and determines whether it is dealing with a double density or single density diskette PIP also recognizes the new Monitor head If you attempt to use the Y option on the old version of PIP to move the new system head PIP responds with the error message RAD SYSTEM HEAT 1 6 The BOOT SV Program The BOOT SV program now includes a primary bootstrap for RLOl 02 and VXAO The format is BOOT dd or BOOT dd where dd is a legal OS 8 device specification including RL RX or VX 1 7 Changes in FUTIL The new version of the OS 8 file utility program FUTIL recognizes the new Core Control Block format for user programs in extended memory For a complete description of FUTIL see the OS 8 Handbook Update 2 0 BOOTSTRAP AND BUILD INSTRUCTIONS Since the Extensions package includes the system head you can bootstrap the RX01 RX02 RLO1 or RK05 distribution medi
29. eset drive errors 2 get drive status 3 seek 4 read next header 5 write 6 read 7 read no header check Command Register B 5 1 3 Instruction Set The following instructions operate the disk system Note that the AC is cleared after a transfer from the AC to a register the controller Also the AC is cleared first before a transfer is made from a controller register to the AC The skip instructions are skip and then clear IOT s that is if a given condition function done is true the function done flag will be cleared at the completion of the skip IOT Octal Code Mnemonic Function 6600 RLDC Clear device all registers AC and flags do not use to terminate a disk function 6601 RLSD Skip on function done flag then clear it 6602 RLMA Load memory address register from AC 6603 RLCA Load command register A from AC 6604 RLCB Load command register from execute command 6605 RLSA Load sector address register from AC bits 0 5 6606 Spare will clear the AC 6607 RLWC Load word count register from AC 6610 RRER Read error register into AC bits 0 2 and 11 6611 RRWC Read word count register into AC 6612 RRCA Read command register A into AC 26 Octal Code Mnemonic Function 6613 RRCB Read command register B into AC 6614 RRSA Read sector address register into AC bits 0 5 6615 RRSI Read silo word 8 bit into AC bits 4 11 6616 Spare does not clear 6617 RLSE Skip on composite erro
30. evice You can specify areas in memory that you want to save fields from 0 to 37 The format of the command including all optional arguments is SAVE device file ex ffnnnn ffmmmm ffpppp ffssss cccc where ffnnnn is 6 digit octal number representing a field from 0 to 37 ff and the first address of a continuous portion of memory you want to save f mmmm is the final address in the same field of the section of memory you want to save ffpppp is a 6 digit octal number representing the field and address of one location in memory If you specify a single address on an even numbered page in the command SAVE writes the entire page on which the location occurs If you specify an odd numbered page SAVE also saves the preceding page ffssss is a 6 digit octal number representing the field and starting address of the program you are saving is a 4 digit octal number representing the contents of the Job Status Word for the program See below If you omit the extension on the file name SAVE appends SV If you omit the other arguments SAVE finds the locations it requires in the current Core Control Block For a discussion of the Core Control Block see the 05 8 Handbook and the 05 8 Software Support Manual The SAVE command places the following restriction on arguments in the command line e You must specify the output device SAVE does not default to DSK e The first and last location of a segment in memory
31. field from 0 to 37 that you specify in the FIELD pseudo op However the ABSLDR option n is restricted to fields 0 to 7 only The ffnnnn option sets the starting address of the program in memory to ffnnnn where ff is a field from 0 to 37 and nnnn is a location If you omit the option or specify 0 the ABSLDR inserts starting address of 0200 in field 0 3 3 Determining Memory Size at Run Time It is frequently helpful to know the amount of memory currently available to the program you are running The sub routine in Figure 1 determines the amount of memory available in a 128K system at run time The program returns a value in the range of 0 to 40 to indicate the first non existent field in the system To use this routine above 32K you must first load the Extended Mode Register with the LXM instruction For complete information on the Extended Mode Register see the KT8A Memory Management Control User s Guide 14 SUBROUTINE TO DETERMINE MEMORY SIZE PAL8 V10A 04 AUG 78 SUBROUTINE TO DETERMINE MEMORY SIZE THIS SUBROUTINE WORKS ON ANY PDP 8 FAMILY COMPUTER THE VALUE FROM 1 TO 40 OCTAL OF THE FIRST NON EXISTENT MEMORY FIELD IS RETURNED IN THE AC NOTE THIS ROUTINE MUST BE PLACED IN FIELD 0 CORE 0 CLA CLL CORU CDF 0 NEEDED FOR PDP 8L TAD GET FIELD TO TEST AND MASK USEFUL BITS CLL RTR TRANSFORMS RTR 37 TO 174 BSW FOR CDF SZL TAD C4 AND COREX DCA orl SET UP CDF TO FIELD CDF CDF IS PROCESSED
32. ion program for 05 8 see the 05 8 Handbook for a detailed description of BUILD 3 Load RLSY BN RLO BN RL1 BN RL2 BN RL3 BN or RLC BN desired see Table 9 for names of devices in each group For example a complete system for two disk drives would include SYS RLOB RLOC RLl1A RL1B and RLIC partial system to support all four drives could include SYS RLOA RLOB RL1A RL1B RL2A RL2B and RL3B 4 Issue the BOOT strap command This will build 01 system RLOA and start it It then asks a question as to whether a new zero directory should be written on the new device Answer yes to place a zero directory on the device RUN all programs with the RUN command until moved to the RLO1 disk pack 36 00020 00021 00022 00023 00024 00025 00026 00027 00030 00031 00032 00033 00034 00035 00036 00037 00040 00041 00042 00043 00044 00045 00046 00047 00050 00051 00052 7301 7326 7327 7330 7350 7346 6751 6752 6753 6754 6755 0020 1061 1046 0060 3061 7327 1061 6751 7301 4053 4053 7004 6755 5054 6754 7450 5020 1061 6751 1061 0046 1032 3060 0360 4053 3002 2050 5047 AC1 CLL AC2 CLL AC6 CLL AC 4000 C AC3777 C AC7775 C DEVIC LCD 6751 XDR 6752 STR 6753 SER 6754 SDN 6755 7 7 READ LITRAL FOLLO START NOW CON360 FOLLO SECON THEN APPENDIX A
33. l disk pack with the 05 8 Operating System using the RLO1 05 8 software support package The RLO1 disk pack a high density mass storage device utilizes bad block mapping Bad blocks occur during the manufacture of disks or develop as a result of use and age Bad blocks that present after manufacture are recorded in factory written lists Each disk preserves its own individual list The RLFRMT formatter program detects and lists new bad blocks that occur during disk operation in the field Each RLO1 disk maintains up to 45 bad blocks this allows the life of the disk to be prolonged as a mass storage device The 01 requires a PDP 8A E F or M with at least 12K of memory Non omnibus PDP 8 family computers are not hardware compatible with the RLOl 21 System and non system RLO1 handlers are standard two page 05 8 handlers Two page handlers require 12K of memory because the second page of the handler resides in the last page of field 2 BATCH may be run using RLO1 disks even on a system with 12K words of memory However disk formatting cannot be done under BATCH This section includes a system description detailing disk RL8A controller and software formats addition it contains bootstrap procedures and operating instructions including a detailed presentation of messages that are generated during disk formatting 5 1 System Description The RLO1 disk pack has three logical devices that are designated as
34. lls the ABSLDR which field to load information into For example the following FIELD pseudo op specifies memory field 26 The next line sets the location counter to begin at 400 Note that the FIELD instruction must precede the starting location FIELD 26 CORRECT EXAMPLE x400 The following example is incorrect and will not generate the code you want X400 INCORRECT EXAMFLE 26 3 2 2 Specifying Data and Instruction Fields CDF and CIF The CDF and CIF instructions let you specify field 0 to 37 as data and instruction fields Entering the argument requires knowledge of the bit arrangement of these two instructions A CDE B CDF 6201 110 010 000 001 CIF 6202 110 010 000 010 Bits A CDE B indicate the data or instruction field that the program will jump to at the next indirect JMP or JMS positioning of ABCDE is eccentric as ACDEB maintains compatibility between existing 32K systems To specify a field from 0 to 7 you use bits CDE only format of the instruction is CDF or CIF n0 where nO is an octal number that PAL8 ORs with the instruction code n is an octal digit from 0 to 7 bits CDE 12 For example this instruction 60 specifies field 6 by causing PAL8 to do the following OR A CDE B Instruction code 6201 110 010 000 001 Argument 60 000 000 110 000 6261 110 010 110 001 To specify a field from 10 to 17 use bits CDE and set bit B The format of the instructi
35. ng the RLOl Disk Pack Booting from BOOT SV Booting from the Console Switches ROM Bootstrap Switch Settings Operating Instructions Disk Formatting System Building iii iQ Fo i gt amp WW W NNP NE NPRPRPRPRPPRPPRPRP O 000 1 10 UP AN NN CONTENTS Cont Page APPENDIX A RX02 BOOTSTRAP PROGRAM A 1 APPENDIX B RLOl BOOTSTRAP PROGRAM B 1 INDEX 1 FIGURES FIGURE 1 Memory Size Subroutine 15 2 Devices B C on RLOl Disk 22 TABLES TABLE 1 Device Extensions Modules 1 2 RX02 Bootstrap 4 3 RLOl Bootstrap 5 4 128K ODT Command Summary 9 5 Field Specifications for 128K MEMORY Command 11 6 RXOl RX02 Compatibility 18 7 05 8 Single Density Diskette Interleave Scheme 19 8 OS 8 Double Density Diskette Interleave Scheme 20 9 RLOl Handler Information 29 10 RLFRMT Formatter Messages 33 iv 1 0 INTRODUCTION AND OVERVIEW The OS 8 V3D Device Extensions support the following new devices under 05 8 e The KT8A Memory Management Option limited support e The RLOl Disk and Controller e The RX02 Double Density Diskette and Controller In addition the Extensions package is a support release for RTS 8 V3 and MACREL LINK Version 2 both of which can use the extended memory provided by the KT8A RTS 8 V3 also supports the RLO1 and RX02 The Extensions package is a superset of some 05 8 modules It remains completely compatible with OS 8 V3D and contains the modules listed in Table
36. on is CDF or CIF n4 where n4 is an octal number that PAL8 ORs with the instruction code n is an octal value from 0 to 7 bits CDE 4 is an octal value indicating a field range of 10 to 17 sets bit B For example this instruction CLF 64 indicates field 16 Keep in mind that to call for fields above field 7 above 32K with CIF you must first load the KT8A Extended Mode Register with the LXM instruction For example the following code deposits 7777 in field 12 location 1000 LXM 24 TAn 7777 CA I 1000 To specify a field from 20 to 27 use bits CDE and set bit The format is CDF or CIF lnO where 1 0 is an octal number that PAL8 ORs with the instruction 1 is octal value indicating field range 20 to 27 sets A n is a value from 0 to 7 bits CDE For example this instruction CUF 160 indicates field 20 13 To specify a field from 30 to 37 use bits CDE and set bit The format is CDF or CIF 1 4 where 1n4 is an octal number that PAL8 ORs with the instruction 1 4 are octal values indicating a field range of 30 to 37 set bits A and B n is an octal digit in the range 0 to 7 bits CDE For example this instruction CIF 164 specifies field 36 One way to avoid confusion with this unusual bit configuration is to define high fields with convenient mnemonics For example 36 164 CLF F36 3 2 3 The ABSLDR The ABSLDR will load information into
37. ootstrap Switch Settings Set the bootstrap switch settings for ROM s labeled 465A2 and 469A2 as follows Program 52 5 82 6 52 7 52 8 51 1 51 2 51 3 Memory Address RL8A OFF ON OFF OFF OFF ON OFF 4000 5 4 Operating Instructions You must format new RLOl disk packs by running the RLFRMT program prior to any OS 8 use including system building This is required because RLFRMT constructs and writes specially formatted bad block lists on the pack 05 8 RLOl operations on disks that have not been formatted with RLFRMT result in error reports Therefore you should run RLFRMT even before using BUILD to build a new system head Device C non system handlers are provided to access all available storage capacity of the RLOl disk packs Transfers to or from Device C are slower than those to or from Devices A This is because while Device and B use 80 of each track Device C only uses 20 of each track only 4 blocks are stored on each track Thus the time spent in seeking new tracks will be higher for Device C 31 Because different RLOl packs may have different patterns of bad blocks it is good practice to end an OS 8 session with the monitor BOOT command or R BOOT so that other users will be able to type RL to boot their disks course this procedure is unnecessary if the computer system has a hardware bootstrap for the 01 5 4 1 Disk Formatting Format all new RLOl disk packs prior to use un
38. r flag then clear it 5 1 4 05 8 Data Space The layout of 05 8 data space on Devices B and C is as follows Devices A and B Block Track Sectors 0 0 20 22 1 9 24 26 2 0 30 32 3 9 34 36 4 0 40 42 5 0 44 46 6 0 1 3 7 0 5 7 10 0 11 13 11 0 15 17 12 0 21 23 13 0 25 27 14 0 31 33 15 0 35 37 16 0 41 43 17 0 45 47 20 1 20 22 1 Block Track Sectors 0 1 0 2 1 1 4 6 2 1 10 12 3 1 14 16 4 2 0 2 5 1 5 Converting Block Numbers to Hardware Disk Addresses Use the following procedures For Devices A and B The sector address is 4 times the sector code minus 27 If the sector address is negative add 47 27 Device A has MSB of cylinder 0 cylinders 0 177 Device B has MSB of cylinder 1 cylinders 200 377 The block number software format for Devices A and is shown the following diagram 0 11 BLOCK NUMBER LSB OF CYLINDER SECTOR CODE Block Number Format for Devices A and B For Device C The sector address is 4 times the sector code track is one plus the track code Tracks 0 and 777 cannot be addressed this ensures the integrity of the factory detected and 05 8 bad block lists which reside on these tracks The block number software format for Device C is shown the following diagram BLOCK NUMBER TRACK CODE Block Number Format for Device C The track software format for Devices A B and C is shown in the following diagram 0 11
39. ram press INIT and RUN Table 3 RLOl Bootstrap Press in order the MD and DISP buttons to display memory data in the octal readout Press in order 0 and LXA to select memory field O0 Press in order address 1 l and LA to start loading instructions at continued on next page Table 3 Cont RLOl Bootstrap 4 Deposit the octal values given below following each value with D NEXT Address Contents 00001 6600 00002 7201 00003 4027 00004 1004 00005 4027 00006 6615 00007 7002 00010 7012 00011 6615 00012 0025 00013 7004 00014 6603 00015 7325 00016 4027 00017 7332 00020 6605 00021 1026 00022 6607 00023 7327 00024 4027 00025 0377 00026 7600 00027 0000 00030 6604 00031 6601 00032 5031 00033 6617 00034 5427 t 00035 5001 5 After all values are deposited press in order 0001 and LA to allow the program to start at location 1 6 Press in order INIT and RUN to start the bootstrap program The complete RX02 and 101 bootstrap programs are listed in Appendix and B 3 0 KT8A MEMORY MANAGEMENT OPTION The OS 8 V3D Device Extensions provide limited support for the KT8A Memory Extension and Management Option which increases the amount of allowable memory in PDP8 systems from 32K to a maximum of 128K words The KT8A supports all available sizes of continuous memory from 32K to 128K System programs devices and languages that run in 32
40. rs NOTE RLFRMT PA contains complete descriptions of bad block list formats as comments at the start of the program 5 1 2 RL8A Controller Format The following registers perform software control of the system Memory Address Register The Memory Address Register is a l2 bit register that contains the location at which the first transfer is to be performed 0 1 2 3 4 5 6 7 8 9 10 11 Memory address Memory Address Register 24 Word Count Register The Word Count Register is 12 bit register that contains the negative of the number of words to be transferred at one time Word count 7771 Word Count Register Sector Address Register The Sector Address Register contains the sector address bits 0 through 5 Sector address Sector Address Register Command Register A Command Register A contains the direction surface and cylinder address It has the following format Direction 0 towards lower cylinder addresses outside 1 towards higher cylinder addresses inside Surface 0 upper surface 1 lower surface Cylinder address or cylinder difference Command Register A Command Register B Command Register B designates maintenance mode byte mode interrupt enable drive select memory field and function 1 has the following format 25 Maintenance mode Byte mode 0 truncated 1 byte Interrupt enable Drive select Memory field Function 0 maintenance 1 r
41. s assuming no factory detected bad blocks 4 Error Messages formatting cannot be done If this message appears immediately it indicates that the OS 8 bad block lists contain physical errors The pack should not be used further under 05 8 If this message appears after attempting to write new 05 8 bad block lists it indicates that an I O error occurred The most common cause will be a write locked drive Message FATAL I O ERROR continued on next page 35 Table 10 Cont RLFRMT Formatter Messages 4 Error Message formatting cannot be done Cont Meaning Message CANNOT FORMAT DISK All error messages end with this one to indicate that the formatting operation has failed This message is always followed by DRIVE to allow formatting another pack OVER 15 BAD BLOCKS ON ONE DEVICE The new 05 8 bad block lists to be written contain more than the maximum number of bad blocks supported under OS 8 OVER 63 NEWLY FOUND BAD BLOCKS Indicates RLOl hardware problem detected during read check of disk a pack with more than 63 bad blocks RLO1 diagnostics should be run and the drive and or controller fixed before attempting to format disk packs 5 5 System Building The following procedure is used for building a system l Format the disk pack as described in Section 5 4 1 2 Run BUILD from any device BUILD is the system generat
42. s the effect of making them appear to have disappeared so that standard OS 8 block numbers can be used All permanent information stored on RLO1 disk packs such as bad block lists is protected from destruction by 05 8 handler calls by being outside of the OS 8 data space An annulus data scheme reduces the average intra device seek time This means that data continues from the track on surface 0 to the track on surface 1 for each cylinder The bootstrap routine is under 32 decimal words length suitable for ROM implementation and or direct toggle in Three tries two retries attempted before an error is reported NOTE Unless otherwise noted all numbers in this section are octal 23 5 1 1 Disk Format The format of the 01 disk is as follows Track Sector Contents 9 0 Reserved for future use by DIGITAL 0 2 Reserved for future use by DIGITAL 4 Reserved for future use by DIGITAL 0 6 Reserved for future use by DIGITAL 0 10 Reserved for future use by DIGITAL 0 12 Reserved for future use by DIGITAL 0 14 Bad Block Lists for Devices and 0 16 Bad Block List for Device C 0 20 Device A Block 0 first half 0 22 Device A Block 0 second half 1 0 Device Block 0 first half 1 2 Device C Block 0 second half 400 20 Device B Block 0 first half 400 22 Device B Block 0 second half 711 0 Disk Pack Serial Number List of Manufacturing Detected Bad Sectors and Field Detected Bad Secto
43. tem Single density Non system Double density Non system 18 4 4 Interleaving 05 8 writes blocks on single density diskettes with an interleave of 2 This means that it skips a block between each block that it reads Or writes With double density diskettes 0S 8 uses interleave Scheme of 3 skipping two blocks Tables 7 and 8 show the interleave Schemes for both single and double density diskettes Table 7 OS 8 Single Density Diskette Interleave Scheme OS 8 Logical Block octal Diskette Sectors track sector decimal 19 Table 8 OS 8 Double Density Diskette Interleave Scheme OS 8 Logical Block octal Diskette Sectors Track sector decimal 0 1 1 1 4 1 1 7 1 10 2 1 13 1 15 3 1 19 1 22 4 1 25 1 2 5 1 5 1 8 6 1 11 1 14 7 1 17 1 20 8 1 23 1 26 9 1 3 1 6 10 1 9 1 12 11 1 15 1 18 12 1 21 1 24 13 2 1 2 4 mettere 05 8 does not use Track 0 and you cannot access it in the 12 bit mode 4 5 Using RXCOPY with RX02 RXCOPY copies both single density and double density diskettes on RX02 drives If the output diskette does not match the input diskette RXCOPY will re format it to the proper density In default mode RXCOPY compares the two diskettes for identical contents before it makes a copy For a quicker transfer use the N option which inhibits the comparison For double density transfers involving a comparison of contents RXCOPY will use 16K words of memory if it is available on the sys
44. tem for faster operation If possible use the MEMORY command to provide the necessary memory 20 4 5 1 Formatting Diskettes with RXCOPY RXCOPY with the S D option formats diskettes for single density or double density use To format a diskette enter it by itself in the command line followed by the option RXCOPY considers device entered by itself to be an output device For example the following command sequence re formats the diskette in drive 1 from single density to double density aR RXCOFY XRXA1 To change it back to single density type aR RXCORY eRXALE ZS 4 5 2 RXCOPY Options RXCOPY provides the following options e RXCOPY pauses and waits for user response before and after transfers To continue type Y e N RXCOPY transfers the contents of one diskette to another but does not check for identical contents e RXCOPY checks both diskettes for identical contents and lists the areas that do not match but performs no transfer e R RXCOPY reads every block on the input device and lists bad sectors but performs no transfer e V RXCOPY prints its current version number e S RXCOPY formats the diskette specified as an output device to single density e RXCOPY formats the diskette specified for output to double density e C This option is equivalent to default copy and match 5 0 THE RLO1 DISK This section describes the booting formatting and building of the RLO1
45. tor at a time up to the requested number of pages 5 If an I O error occurs for any 01 read or write operation retry twice then take the System or Non System Handler error return with AC 4000 29 5 3 Loading and Bootstrap Procedure The following sequence of operations occurs during bootstrapping to the RLO1 1 BOOT 1 the primary bootstrap routine is read into locations 00001 00035 from a ROM from BOOT SV or toggled in through the console switches starting address is 00001 BOOT 1 clears Drive 0 and reads and starts BOOT 2 If an I O error occurs BOOT 1 will repeat until it is successful 2 BOOT 2 occupies locations 00000 00177 BOOT 2 reads the OS 8 Resident Monitor into the last pages of fields 0 1 and 2 If an I O error occurs BOOT 2 will hang as an indication of failure to boot 3 BOOT 2 then calls the Keyboard Monitor by jumping to location 07605 NOTE Never replace the system disk pack without rebooting each pack has its own 05 8 block numbering scheme that 15 determined during formatting Replace non system disk packs only after the Monitor dot appears the terminal This is done to ensure that the bad block list read by the handler is correct 5 3 1 Loading the RLO1 Disk Pack Prepare an RLOl1 Disk for loading as follows 1 Separate the protective cover from the disk pack using the following steps a Lift the cartridge by grasping the handle with the right hand
46. um as a system device Table 2 and Table 3 contain the bootstraps for the RX02 and RLO1 device The bootstraps for the RK05 disk and the TD8E DECtape are included in Chapter 1 of the 05 8 Handbook The new handlers must be inserted into 05 8 with the BUILD program For information adding handlers to OS 8 see the BUILD chapter in the OS 8 Handbook NOTE The console instructions in Tables 2 and 3 describe a PDP8 A For other PDP8 computers see the OS 8 Handbook Table 2 RX02 Bootstrap 1 Press in order the MD and DISP buttons to display memory data in the octal readout 2 Press in order 0 and LXA to select memory field 0 3 Press in order 20 and LA to start loading instructions at location 20 continued on next page 4 Table 2 Cont RX02 Bootstrap Deposit the following octal with D NEXT 00020 00021 00022 00023 00024 00025 00026 00027 00030 00031 00032 00033 00034 00035 00036 00037 00040 00041 00042 00043 00044 00045 00046 00047 00050 00051 00052 00053 00054 00055 00056 00057 00060 00061 l061 1046 0060 3061 7327 1061 6751 7301 4053 4053 7004 6755 5054 6754 7450 5020 1061 6751 1061 0046 1032 3060 0360 4053 3002 2050 5047 0000 6753 5033 6752 5453 0420 0020 values start the program at location 33 terminating each value After you have deposited all the values press 0033 and LA to To start the bootstrap prog
47. ve 1 making SYS DSK equivalent to RXAI1 The permanent names RXAO0 RXAl remain unchanged 4 2 Formatting Diskettes for RX02 Diskettes arrive from the factory already formatted for use in single density RX01 drive To format them for RX02 use the RXCOPY program with the D option specifying the diskette you want to re format as an output device If you enter a device by itself in the command line RXCOPY considers it to be an output device Diskettes formatted for the RX02 device contain 981 blocks besides the directory in a 12 bit mode 4 3 01 and RX02 Compatibility double density system diskette runs only on RX02 double density drive Similarly sSingle density SYS requires an 1 drive RX02 accepts both single density and double density non system diskettes The non system handler determines which kind of device it is dealing with and proceeds accordingly e 1 hardware accepts only diskettes formatted for single density use NOTE If you place an RX02 diskette on an RXOl drive you can currently write to it without producing error message Avoid this procedure as it results in a mixed diskette Table 6 matches single density and double density diskettes both system and non system with the drives that they run on Table 6 RXO0l RX02 Compatibility Diskette Type Drive type Single density Double density Single density System Double density Sys
Download Pdf Manuals
Related Search