DOCUMENTATION CHANGES FOR: HOW TO LOAD AND GENERATE RDOS PART NUMBER 069-400013-00 THIS FILE (FILENAME 069400013.00) CONTAINS INFORMATION THAT AFFECTS THE FOLLOWING PAGES OF YOUR MANUAL: 25 *47 27 49 *28 *61 *30 74 *31 76 *32 78 *34 79 *36 86 *37 *44 45 *46 THIS SECOND REVISION OF 069400013.00 WAS UPDATED ON JANUARY 20, 1989. ITEMS APPEARING HERE SINCE THE LAST REVISION ARE EASY TO IDENTIFY: IN THE LIST ABOVE, ASTERISKS (*) MARK PAGES WITH CHANGES PRINTED IN THIS FILE FOR THE FIRST TIME. AND, IN THE MARGIN OF PAGES THAT FOLLOW, CHANGE BARS (|) MARK THE NEW MATERIAL. FOR EXAMPLE, THIS REVISION OF 069400013.00 CONTAINS A CHANGE TO PAGE 28 OF ITS PARENT MANUAL. YOU ARE SEEING THIS CHANGE FOR THE FIRST TIME, AND BARS APPEAR NEXT TO IT. TO KEEP YOUR MANUAL CURRENT, YOU SHOULD DO EITHER OF THE FOLLOWING: O MARK THE AFFECTED PAGES OF YOUR MANUAL SO THAT YOU WILL KNOW TO REFER TO THIS FILE FOR ADDITIONAL INFORMATION. O PRINT THIS FILE, PUNCH HOLES TO FIT YOUR BINDER, AND INSERT THE PAGES INTO YOUR MANUAL. COPYRIGHT (C) DATA GENERAL CORPORATION, 1983-1989 ALL RIGHTS RESERVED LICENSED MATERIAL - PROPERTY OF DATA GENERAL CORPORATION HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 CHAPTERS 2, 3, AND 4 BECAUSE OF THE INTRODUCTION OF ADDITIONAL DISK DRIVES, THE BOOT.SV PROGRAM HAS BEEN REPLACED WITH THE THREE BOOTSTRAP PROGRAMS ABOOT.SV, EBOOT.SV, AND MBOOT.SV. THESE PROGRAMS OPERATE EXACTLY LIKE BOOT.SV. DELETE ALL REFERENCES TO BOOT.SV IN THESE CHAPTERS AND REPLACE THEM WITH ABOOT.SV, EBOOT.SV, OR MBOOT.SV, DEPENDING ON WHICH PROGRAM APPLIES TO YOUR SYSTEM: * USE ABOOT TO INSTALL RDOS IF YOU HAVE AN ECLIPSE COMPUTER WITH | A MODEL 6236 (354 MBYTE), A MODEL 6239 (592 MBYTE), OR A MODEL | 6357 (862 MBYTE) DISK. * USE EBOOT TO INSTALL RDOS IF YOU HAVE A NOVA OR ECLIPSE COMPU- TER AND ANY DISKS OTHER THAN THE THREE LISTED ABOVE. * USE MBOOT TO INSTALL RDOS IF YOU HAVE AN S/20 MICROECLIPSE COMPUTER. NOTE THAT THIS CHANGE DOES NOT AFFECT THE BOOTSYS OR TBOOTSYS FILES, THE TBOOT OR CBOOT PROGRAMS, OR THE CLI BOOT COMMAND. NOTE ALSO THAT YOUR RELEASE DISKETTES MAY CONTAIN MORE THAN ONE OF THE PROGRAMS. THIS WILL CAUSE NO PROBLEM, HOWEVER, IF YOU USE THE CORRECT VERSION OF THE BOOTSTRAP PROGRAM FOR YOUR SITUATION. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 25 TABLE 2.1 DISCUSSES HOW TO LOAD THE BOOTSTRAP ROOT FROM A RELEASE DISKETTE IN A DRIVE ON THE SECONDARY CONTROLLER. BEGINNING WITH REVISION 7.50, ALL RELEASE DISKETTES ARE INTENDED FOR USE WITH A DRIVE ON THE PRIMARY CONTROLLER. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 27 THE SECTION "TROUBLESHOOTING GUIDELINES" MENTIONS LOADING THE RDOS BOOTSTRAP ROOT FROM A DISKETTE DRIVE ON THE SECONDARY CONTROLLER. AS MENTIONED ABOVE, THIS PROCEDURE WILL NOT WORK WITH RDOS REVS. 7.50 AND LATER. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 28 ADD THE FOLLOWING DISK DRIVE MODEL NUMBERS AND UNIT NAMES TO THE LIST OF SEALED MOVING-HEAD DRIVES IN TABLE 2.3. 5 MBYTES 6225 DPN 15 MBYTES 6222 DEN (S/20) 15 MBYTES (ON BMC) 6224 DMN 50 MBYTES (ON BMC) 6280 DMN 354 MBYTES 6236 DAN 592 MBYTES 6239 DAN | 862 MBYTES 6357 DAN ADD THE FOLLOWING DISKETTE DRIVES TO THE SAME TABLE: 360 KBYTES (5.25") 4514 DJN 1.2 MBYTES (8") 6096 DEN (S/20) PLACE THE FOLLOWING INFORMATION AFTER THE LINE THAT READS "FULL." IF YOU REQUEST A FULL INITIALIZATION, DKINIT NOW POSTPONES THE "NUMBER OF PATTERNS TO RUN?" QUESTION AND ASKS: DO YOU WANT A CORESIDENT DIAGNOSTIC AREA? (FOR A COMPLETE DISCUSSION OF CORESIDENT DIAGNOSTICS, SEE THE DOCUMENTATION CHANGES FOR PAGE 74.) VALID RESPONSES ARE YES AND NO. IF YOU ANSWER NO, DKINIT MOVES ON TO THE "NUMBER OF PATTERNS TO RUN?" QUESTION. IF YOU ANSWER YES, IT DISPLAYS THE FOLLOWING MESSAGE: THE DEFAULT CORESIDENT DIAGNOSTIC AREA SIZE IS 5000 BLOCKS. HOW BIG WOULD YOU LIKE YOUR DIAGNOSTIC AREA TO BE? YOU ANSWER THIS QUESTION BY ENTERING A NUMBER BETWEEN 1 AND 32767 THAT REPRESENTS THE NUMBER OF BLOCKS YOU WOULD LIKE RESERVED. AS LONG AS YOU DO NOT REQUEST SO LARGE AN AREA FOR DIAGNOSTICS THAT THERE IS INSUFFICIENT ROOM ON YOUR DISK FOR THE OPERATING SYSTEM, DKINIT SETS ASIDE THIS SPACE. THE PROGRAM THEN CONTINUES WITH THE "NUMBER OF PATTERNS TO RUN?" PROMPT. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 30 AT THE BOTTOM OF THE FIRST COLUMN, THE MANUAL SAYS "TYPE 5 TO INVOKE THE BOOTSTRAP INSTALLER." IF YOUR MASTER DISK HAS THE UNIT | NAME DAN (THAT IS, IT IS A 354, 592, OR 862 MBYTE DISK), YOU SHOULD TYPE 8 INSTEAD OF 5. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 31 | REPLACE THE SECTION "INSTALLING FROM MAGNETIC TAPE" WITH THE | FOLLOWING ONE: | | INSTALLING FROM MAGNETIC TAPE | | IF YOU ARE INSTALLING THE STARTER SYSTEM FROM TAPE AND YOU HAVE | JUST COMPLETED THE INSTRUCTIONS LISTED IN THE SECTION ENTITLED | "INITIATING A LOADER PROGRAM," THE FOLLOWING MESSAGE FROM | TBOOT.SV HAS APPEARED AT YOUR SYSTEM CONSOLE. | | FROM MT0: | | TYPE 2 TO BRING THE STARTER SYSTEM INTO MEMORY. SEE TABLE | 2.3.1 AT THE END OF THIS SECTION FOR A LIST OF THE MESSAGES | TBOOT DISPLAYS IF IT DETECTS AN ERROR. | | NOW THE STARTER SYSTEM ASKS YOU TO CHOOSE EITHER A FULL | INITIALIZATION, A RESTORATION, OR A PARTIAL INITIALIZATION AND | TO ENTER THE UNIT NAME OF YOUR MASTER DISK. (SEE THE UPDATES | FOR PAGE 32 FOR AN EXPLANATION OF HOW TO USE THE RESTORE AND | PARTIAL COMMANDS.) YOU MAY RECALL REQUESTING A FULL INITIALIZA- | TION WHEN YOU RAN DKINIT EARLIER; ASKING FOR A FULL INITIALIZA- | TION NOW CAUSES THE SYSTEM TO ESTABLISH MASTER ALLOCATION AND | SYSTEM DIRECTORIES ON YOUR DISK. | | FULL (F), RESTORE (R), OR PARTIAL (P)? | | INDICATE THAT YOU WANT A FULL INITIALIZATION BY TYPING F. | THE STARTER SYSTEM THEN ASKS YOU FOR THE UNIT NAME OF THE DISK | ON WHICH YOU PLAN TO LOAD THE OPERATING SYSTEM: | | INITIALIZE WHAT DISK? | | ENTER THE UNIT NAME OF WHAT WILL BE YOUR MASTER DISK (SEE TABLE | 2.3). FOR EXAMPLE, TYPE | | DP0 | | AT THIS POINT THE SYSTEM ESTABLISHES A MASTER ALLOCATION | DIRECTORY AND SYSTEM DIRECTORY ON THE TARGET DISK; IT LOADS THE | CONTENTS OF TAPE FILE 1 ONTO THAT DISK; AND IT BEGINS TO BRING | UP THE OPERATING SYSTEM WITH THE TARGET DISK AS THE MASTER | DIRECTORY. THE SYSTEM ANNOUNCES ITSELF WITH THE MESSAGE RDOS | REV N.NN. | | YOU MUST NOW SET THE SYSTEM DATE AND TIME. WHEN THE SYSTEM HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | CONSOLE DISPLAYS THE PROMPT DATE (M/D/Y)?, ENTER THE DATE | (FOLLOWED BY A NEW LINE) IN ONE OF THE FOLLOWING FORMATS: | | 4 28 88 | 4,28,88 | 4-28-88 | 4:28:88 | 4/28/88 | APR 28 88 | APR,28,88 | 28-APR-88 | | THE SYSTEM THEN PROMPTS YOU FOR THE TIME. AFTER THIS PROMPT, | ENTER THE TIME (FOLLOWED BY A NEW LINE) IN ONE OF THE FOLLOWING | FORMATS: | | 14 30 00 | 14,30 | 14-30 | 14:30 | 14/30 | 2 30 PM | 2:30 P | | ONCE YOU HAVE ENTERED THE DATE AND TIME, THE STARTER SYSTEM | INVOKES ITS COMMAND LINE INTERPRETER, THE RDOS CLI. THE CLI IS | AN INTERACTIVE PROGRAM THROUGH WHICH THE OPERATING SYSTEM AND | ITS USERS COMMUNICATE WITH ONE ANOTHER. THE CLI ANNOUNCES | ITSELF WITH THE FOLLOWING PROMPT: | | R | | THIS PROMPT SIGNALS THAT YOUR RDOS SYSTEM IS UP AND RUNNING | FROM YOUR MASTER DISK. THE STARTER SYSTEM SAVE AND OVERLAY | FILES ARE STORED UNDER THE NAMES BOOTSYS.SV AND BOOTSYS.OL. | (ON S/20 SYSTEMS THESE FILES ARE NAMED TBOOTSYS.SV AND | TBOOTSYS.OL.) THE SAVE, OVERLAY, AND ERROR FILES OF THE CLI, | ALONG WITH THE BOOTSTRAP ROUTINE XBOOT.SV, HAVE ALSO BEEN | INSTALLED ON THE DISK. YOU CAN NOW PROCEED TO THE NEXT | SECTION, "LOADING THE UTILITIES," AND EXECUTE THE FEW STEPS | THAT REMAIN. | | TABLE 2.3.1 TBOOT'S ERROR MESSAGES | | ABORT: STATUS= 104501 END OF TAPE | | TBOOT ENCOUNTERED THE LOGICAL END OF TAPE WHILE SEARCHING FOR | A FILE OR WHILE READING THE FIRST RECORD OF A FILE. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | ABORT: STATUS= [Y] [EXPLANATION] | [MEMORY LOCATION WHERE ABORT ROUTINE WAS CALLED] | | A SINGLE OPERATION HAS TAKEN TOO LONG (OVER 20 SECONDS ON AN | S/130 OR S/280 SYSTEM), OR TBOOT HAS TRIED TO READ ONE BLOCK | TEN TIMES. | | PROGRAM MAY BE TOO BIG | | TBOOT RAN OUT OF MEMORY WHILE READING A TAPE FILE. | | RETRY: BLOCK # [X] STATUS= [Y] [EXPLANATION] | | TBOOT WAS UNABLE TO READ SOME OF THE DATA ON YOUR TAPE ON ITS | FIRST ATTEMPT. THE BLOCK NUMBER IS THE OFFSET, IN TAPE | RECORDS, FROM THE FIRST RECORD OF THE TAPE FILE. THE STATUS | IS THE ERROR WORD RETURNED BY THE TAPE DRIVE. AN EXPLANATION | IS DISPLAYED FOR THE MOST COMMON ERRORS: "PARITY," "END OF | TAPE," "BAD TAPE," OR "TIMEOUT." HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 32 REPLACE THE CURRENT SECTION "INSTALLING FROM DISKETTE" WITH THE FOLLOWING ONE: | IF YOU ARE INSTALLING THE STARTER SYSTEM FROM DISKETTE, | XBOOT.SV ASKS FOR A FILENAME. | | FILENAME? | | TYPE SYS OR CARRIAGE RETURN TO INVOKE THE RDOS STARTER | SYSTEM. THE SYSTEM ANNOUNCES ITSELF WITH THE MESSAGE RDOS REV | N.NN. | | YOU MUST NOW SET THE SYSTEM DATE AND TIME. WHEN THE SYSTEM | CONSOLE DISPLAYS THE PROMPT DATE (M/D/Y)?, ENTER THE DATE | (FOLLOWED BY A NEW LINE) IN ONE OF THE FOLLOWING FORMATS: | | 4 28 88 | 4,28,88 | 4-28-88 | 4:28:88 | 4/28/88 | APR 28 88 | APR,28,88 | 28-APR-88 | | THE SYSTEM THEN PROMPTS YOU FOR THE TIME. AFTER THIS PROMPT, | ENTER THE TIME (FOLLOWED BY A NEW LINE) IN ONE OF THE FOLLOWING | FORMATS: | | 14 30 00 | 14,30 | 14-30 | 14:30 | 14/30 | 2 30 PM | 2:30 P | | ONCE YOU HAVE ENTERED THE DATE AND TIME, THE STARTER SYSTEM | INVOKES ITS COMMAND LINE INTERPRETER, THE RDOS CLI. THE CLI IS | AN INTERACTIVE PROGRAM THROUGH WHICH THE OPERATING SYSTEM AND | ITS USERS COMMUNICATE WITH ONE ANOTHER. THE CLI ANNOUNCES | ITSELF WITH THE FOLLOWING PROMPT: | | R | | ONCE THE SYSTEM HAS REACHED THE CLI PROMPT, YOU SHOULD ENTER HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | THE INSTALL COMMAND. INSTALL IS A MACRO THAT EXECUTES THE | PROGRAM INITIALIZE.SV. INITIALIZE.SV GATHERS THE NECESSARY | INFORMATION FROM YOUR ANSWERS TO ITS QUESTIONS AND THEN IN- | STALLS RDOS ON THE DISK YOU HAVE SPECIFIED. INITIALIZE CON- | TAINS HELP MESSAGES THAT YOU CAN DISPLAY AT ANY TIME BY TYPING | A QUESTION MARK. AFTER THE HELP MESSAGE HAS BEEN DISPLAYED, | THE PROGRAM'S PROMPT IS REDISPLAYED ALONG WITH ANY PREVIOUS | INPUT, AS IN THE FOLLOWING EXAMPLE: | | INITIALIZING WHAT DISK? DP? | | VALID DISK NAMES ARE: | DA0 - DA7 | DE0 - DE7 | DH0 - DH1 OR DH0F - DH1F | DJ0 - DJ7 | DM0 - DM7 | DP0 - DP7 OR DP0F - DP7F | DS0 - DS7 | DZ0 - DZ7 | | INITIALIZING WHAT DISK? DP_ | [THE UNDERSCORE REPRESENTS THE POSITION OF THE CURSOR WHEN | THE PROMPT IS REDISPLAYED.] | | A HELP MESSAGE IS DISPLAYED AUTOMATICALLY IF YOU ENTER AN | INVALID CHARACTER FOR THE CURRENT QUESTION. INITIALIZE SHOWS | YOU A LIST OF VALID RESPONSES AND THEN REDISPLAYS ITS PROMPT | AND THE PORTION OF YOUR FIRST ANSWER THAT IS LEGAL. YOU DO NOT | HAVE TO DELETE THE INVALID INPUT. FOR EXAMPLE: | | INITIALIZING WHAT DISK? DB | | VALID DISK NAMES ARE: | [AS ABOVE] | | INITIALIZING WHAT DISK? D_ | [THE UNDERSCORE REPRESENTS THE POSITION OF THE CURSOR WHEN | THE PROMPT IS REDISPLAYED.] | | INITIALIZE.SV ACCEPTS INPUT IN UPPERCASE OR LOWERCASE CHARAC- | TERS AND RECOGNIZES NEW LINE, CARRIAGE RETURN, DOWNARROW, ERASE | PAGE, AND NULL AS LINE TERMINATORS. | | NOTE THAT INSTALL.MC AND INITIALIZE.SV MUST BE EXECUTED FROM | THE BACKGROUND CONSOLE AND IN THE MASTER DIRECTORY. IN | ADDITION, (T)BOOTSYS.SV, (T)BOOTSYS.OL, CLI.SV, CLI.OL, CLI.ER, | RCLI.SV, AND THE PROPER VERSION OF THE BOOTSTRAP PROGRAM MUST HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | EXIST IN THE MASTER DIRECTORY. | | AFTER YOU ENTER THE CORRECT NAME OF YOUR MASTER DISK, INITIAL- | IZE DISPLAYS THE FOLLOWING PROMPT: | | ***** NOW INSPECTING THE DISK. PLEASE BE PATIENT. ***** | | AT THIS POINT, THE PROGRAM DETERMINES WHETHER IT IS NECESSARY | FOR YOU TO INITIALIZE YOUR DISK FULLY. A FULL INITIALIZATION | DESTROYS ANY DATA ON YOUR TARGET DISK BY PERFORMING AN INIT/F | ON IT AND THEN INSTALLS THE BOOTSYS FILES, THE CLI FILES, AND | THE PROPER VERSION OF THE BOOTSTRAP PROGRAM. TO MAKE THIS | DETERMINATION, INITIALIZE SCANS YOUR DISK FOR THE FILE | (T)BOOTSYS.OL. IF IT CANNOT FIND THIS FILE, WHICH IS VERY | LIKELY SINCE YOU PROBABLY JUST RAN DKINIT ON THIS DISK, OR IF | THE FILE IS THE WRONG SIZE OR IN THE WRONG LOCATION, YOU MUST | INITIALIZE YOUR DISK FULLY. YOU WILL SEE THE FOLLOWING | MESSAGES: | | **** DISK REQUIRES FULL INITIALIZATION **** | | DO YOU WANT TO QUIT? (Y/N) | | ANSWER N. THE REMAINDER OF YOUR DIALOG WITH THE PROGRAM WILL | LOOK LIKE THIS: | | A FULL INITIALIZATION DESTROYS THE CURRENT DISK STRUCTURE. | | DO YOU WANT TO CONTINUE? (Y/N) Y | | ABOUT TO PERFORM FULL INITIALIZATION ON DP0 | IS THIS CORRECT? (Y/N) Y | | **** NOW PERFORMING REQUESTED OPERATIONS **** | . | . [FILENAMES MAY APPEAR HERE.] | . | FULL INITIALIZATION COMPLETE. | | AT THE END OF THIS PROCESS, YOU ARE STILL RUNNING THE RDOS | STARTER SYSTEM ON YOUR RELEASE DISKETTE. TO RUN THE SYSTEM YOU | HAVE JUST INSTALLED ON YOUR HARD DISK, EITHER CLOSE DOWN THE | CURRENT SYSTEM AND START UP THE NEW SYSTEM ACCORDING TO THE | INSTRUCTIONS IN CHAPTER 4 OR USE THE CLI COMMAND BOOT. | | NOTE: IF INITIALIZE DISCOVERS THAT THE FILE (T)BOOTSYS.OL IS ON | YOUR DISK, IS THE CORRECT SIZE, AND IS IN THE CORRECT LOCATION, | YOU ARE NOT REQUIRED TO PERFORM A FULL INITIALIZATION. INSTEAD HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 | OF THE MESSAGE "DISK REQUIRES FULL INITIALIZATION," YOU WILL | SEE THIS PROMPT: | | FULL (F), RESTORE (R), OR PARTIAL (P)? | | THE THREE COMMANDS WORK AS FOLLOWS: | | FULL INITIALIZATION IS EXPLAINED ABOVE. BEFORE SELECTING THIS | OPTION, YOU SHOULD BACK UP ALL THE IMPORTANT FILES ON YOUR DISK | USING THE CLI DUMP COMMAND OR THE UTILITY DDUMP OR FDUMP. | | THE RESTORE OPERATION HAS BEEN IMPLEMENTED TO HELP YOU IF YOU | LOSE THE CLI OR THE OPERATING SYSTEM AND WANT TO RECOVER | WITHOUT PERFORMING A FULL INITIALIZATION. THE RESTORE OPERA- | TION ALLOWS YOU TO INSTALL THE BOOTSYS FILES, CLI.SV, CLI.OL, | CLI.ER, RCLI.SV, AND THE PROPER VERSION OF THE BOOTSTRAP | PROGRAM ON YOUR DISK. | | PARTIAL INITIALIZATION JUST LOADS BOOTSYS.OL ONTO THE TARGET | DISK. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 34 | IN THE NUMBERED LIST IN THE LEFT COLUMN, DELETE ITEM 3 AND ADD THE | MATERIAL BELOW: | | 3. REPLACE DISKETTE NUMBER 5 WITH DISKETTE NUMBER 6 AND TYPE | | LOAD/V/R DP0:6 | | 4. REPLACE DISKETTE NUMBER 6 WITH DISKETTE NUMBER 7, IF ANY, | AND TYPE | | LOAD/V/R DP0:7 HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 36 | IN THE LEFT COLUMN, ADD THE FOLLOWING MATERIAL JUST BEFORE THE LINE | THAT READS "NUMBER OF PATTERNS TO RUN? 5". | | DO YOU WANT A CORESIDENT DIAGNOSTIC AREA? YES | | THE DEFAULT CORESIDENT DIAGNOSTIC AREA SIZE IS 5000 BLOCKS | HOW BIG WOULD YOU LIKE YOUR DIAGNOSTIC AREA TO BE? | | IN THE RIGHT COLUMN, DELETE LINES 9 THROUGH 12 (STARTING WITH "RDOS | REV 7.10"), AND THEN ADD THE FOLLOWING MATERIAL JUST AFTER THE LINE | ABOUT THE TIME. | | R | | INSTALL | | INITIALIZING WHAT DISK? DE1 | | ***** NOW INSPECTING THE DISK. PLEASE BE PATIENT ***** | | **** DISK REQUIRES FULL INITIALIZATION **** | | DO YOU WANT TO QUIT? (Y/N) N | | A FULL INITIALIZATION DESTROYS THE CURRENT DISK STRUCTURE. | | DO YOU WANT TO CONTINUE? (Y/N) Y | | ABOUT TO PERFORM FULL INITIALIZATION ON DE1 | IS THIS CORRECT? (Y/N) Y | | **** NOW PERFORMING REQUESTED OPERATIONS **** | . | . [FILENAMES MAY APPEAR HERE.] | . | FULL INITIALIZATION COMPLETE. | . | . | . HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 37 | IN THE LEFT COLUMN, ADD THE FOLLOWING MATERIAL JUST BEFORE THE LINE | THAT READS "NUMBER OF PATTERNS TO RUN? 5". | | DO YOU WANT A CORESIDENT DIAGNOSTIC AREA? YES | | THE DEFAULT CORESIDENT DIAGNOSTIC AREA SIZE IS 5000 BLOCKS | HOW BIG WOULD YOU LIKE YOUR DIAGNOSTIC AREA TO BE? | | IN THE RIGHT COLUMN CHANGE THE LINE "FULL (F) OR PARTIAL (P OR | )? F" TO READ "FULL (F), RESTORE (R), OR PARTIAL (P)? F". HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 44 | REPLACE THE CURRENT SECTION "PROCESSOR TYPE" WITH THE FOLLOWING | MATERIAL: | | PROCESSOR TYPE | | ENTER PROCESSOR MODEL (CURRENTLY SUPPORTED MODELS INCLUDE: NOVA | NOVA/2 NOVA/3 NOVA/4 NOVA/800 NOVA/820 NOVA/830 NOVA/840 | NOVA/1200 S/20 S/120 S/130 AP/130 S/140 C/150 S/200 S/230 S/250 | S/250IAP S/280 C/300 C/330 AND C/350): | | ENTER THE PROCESSOR MODEL ON WHICH THIS RDOS SYSTEM WILL RUN. | BECAUSE SYSGEN DOES NOT ASK A SEPARATE QUESTION FOR ARRAY | PROCESSORS, YOU MUST ANSWER AP/130 TO SUPPORT AN ARRAY PROCES- | SOR ON YOUR S/130 COMPUTER. SIMILARLY, IF YOUR S/250 COMPUTER | FEATURES THE INTEGRAL ARRAY PROCESSOR OPTION, ENTER S/250IAP. | | SYSGEN ASKS THE NEXT QUESTION ONLY IF YOU ANSWER S/20, S/120, | S/140, S/250, S/250IAP, S/280, OR C/350 TO THIS ONE. IF THE | BURST MULTIPLEXOR CHANNEL (BMC) AND MAPPED MEMORY OPTIONS ARE | NOT AVAILABLE WITH YOUR PROCESSOR, SYSGEN SKIPS TO THE QUES- | TIONS PERTAINING TO UNMAPPED SYSTEMS AND ASKS YOU TO SUPPLY A | NUMBER OF PATCH SPACE BLOCKS. | | BURST MULTIPLEXOR CHANNEL (BMC)? ("0"=NO "1"=YES) | | THE BMC IS AN OPTIONAL HIGH-SPEED DATA CHANNEL INTERFACE | AVAILABLE ON THE PROCESSORS MENTIONED ABOVE. IT CAN BE USED | WITH FIXED-HEAD DISK MODELS 6063 AND 6064; WITH FREESTANDING | MODELS 6060, 6061, 6067, AND 6122; AND WITH WINCHESTER-TYPE | DISK MODELS 6160/6161, 6224/6280, 6236, 6239, AND 6357. ADD THE FOLLOWING NOTE TO THE FOURTH PARAGRAPH: IF YOU ARE WORKING ON AN S/20 SYSTEM AND ANSWER 1, SYSGEN WILL ASK YOU FOR THE NUMBER OF 6224/6280 DISK DRIVES YOU HAVE. THESE DISKS REQUIRE A BMC, SO YOU DO NOT NEED TO IDENTIFY THEM AS BEING ON THE BMC. ADD THE FOLLOWING NOTE AT THE END OF THE DISCUSSION OF RESIDENT SYSTEM OVERLAYS: NOTE: ANSWERING YES TO THIS QUESTION MAY ALTER THE NUMBER OF EXTRA BUFFERS THAT YOU NEED TO SPECIFY. WITH THIS OPTION, RDOS MUST HAVE AT LEAST ONE MORE BUFFER THAN THE NUMBER OF STACKS, OR THE SYSTEM WILL HANG AT INITIALIZATION. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 45 IN THE SECTION, "STANDARD NOVA AND ECLIPSE CONFIGURATIONS," DELETE THE DISCUSSION OF NOVADISK CONTROLLERS. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 46 INSERT THE FOLLOWING MATERIAL IN THE LEFT COLUMN JUST BEFORE THE PROMPT "NUMBER OF OTHER TYPES OF MOVING-HEAD DISK CONTROLLERS (0-2)": | NUMBER OF 6236/6239/6357 DISK CONTROLLERS? (0-2) SYSGEN POSES THIS QUESTION ONLY IF YOU ARE GENERATING RDOS ON A MAPPED ECLIPSE COMPUTER AND REQUESTED SUPPORT FOR A BURST MULTIPLEXOR CHANNEL. ADD THE FOLLOWING TEXT AFTER THE FIRST PARAGRAPH IN THE SECTION "MICROPRODUCTS CONFIGURATIONS": IF YOU REQUESTED SUPPORT FOR A BMC, SYSGEN ASKS NUMBER OF 6224/6280 DISK CONTROLLERS? (0-2) IF YOU ANSWER 1 , SYSGEN THEN INQUIRES DEVICE PRIMARY("0") OR SECONDARY ("1")? | THE PRIMARY CONTROLLER HAS A DEVICE CODE OF 25 AND CONTROLS | UNIT DM0. THE SECONDARY CONTROLLER HAS THE DEVICE CODE 65 AND | GOVERNS UNIT DM4. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 47 ADD THE FOLLOWING MATERIAL JUST BEFORE THE QUESTION "NUMBER OF 6095 DISK CONTROLLERS? (0-2)": | THE NEXT QUESTION CONCERNS MODEL 4513 DISKETTE CONTROLLERS. THESE CONTROLLERS MANAGE 5.25" DISKETTE DRIVES, WHICH ARE RACK MOUNTABLE IN A STANDARD CHASSIS. EACH CONTROLLER MAY OPERATE UP TO FOUR DISKETTE DRIVES. | NUMBER OF 4513 (5 1/4 INCH) DISKETTE CONTROLLERS? (0-2) IF YOU ANSWER 1 TO THE QUESTION SYSGEN WILL ASK: DEVICE PRIMARY("0") OR SECONDARY("1")? THE PRIMARY CONTROLLER HAS A DEVICE CODE OF 20 AND CONTROLS UNITS DJ0-DJ3. THE SECONDARY CONTROLLER HAS THE DEVICE CODE 60 AND GOVERNS UNITS DJ4-DJ7. FOR EACH CONTROLLER SELECTED, SYSGEN WILL ASK: NUMBER OF DEVICES FOR CONTROLLER #N ? (1-4) HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 49 REPLACE THE FIRST PARAGRAPH IN THE SECTION "MAGNETIC AND CASSETTE TAPE DRIVES" WITH THE FOLLOWING ONE: ENTER NUMBER OF CONTROLLERS FOR MTA (0-2) ENTER THE NUMBER OF MAGNETIC TAPE CONTROLLERS, NOT DRIVES, THAT THIS SYSTEM WILL SUPPORT. SOME ECLIPSE AND NOVA CONTROLLERS CAN HANDLE UP TO EIGHT DRIVES; OTHERS, SUCH AS THOSE THAT MANAGE MODEL 6299 AND 6300 TAPE DRIVES, CAN HANDLE FOUR UNITS; AND A MICROPRODUCTS CONTROLLER CAN HANDLE ONE DRIVE. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 61 | ADD THE FOLLOWING SUBSECTION JUST BEFORE THE HEADING "CLOSING DOWN | THE SYSTEM": | | RUNNING RESTART | | WHEN YOU BOOTSTRAP A SYSTEM CONVENTIONALLY, IT ASKS QUESTIONS | ABOUT THE DATE AND TIME AND THEN INVOKES THE CLI. HOWEVER, IF | ALL DATA SWITCHES ARE IN THE UP POSITION OR THE SWITCH REGISTER | CONTAINS -1, RDOS TRIES TO EXECUTE A FILE NAMED RESTART.SV, AND | IF UNABLE TO DO SO, INVOKES THE CLI. LIKEWISE, IF A PROGRAM | ISSUES THE .BOOT SYSTEM CALL OR YOU ENTER THE CLI COMMAND BOOT | WHILE ALL DATA SWITCHES ARE IN THE UP POSITION OR THE SWITCH | REGISTER CONTAINS -1, THE NEW SYSTEM COMES UP AUTOMATICALLY | WITH THE DEFAULT DATE OF JANUARY 1, 1968 AND CHAINS CONTROL ON | LEVEL 0 TO RESTART.SV. IF THIS FILE DOES NOT EXIST, YOU ARE | ASKED THE CONVENTIONAL LOG-ON QUESTIONS. | | THE FILE RESTART.SV DOES NOT EXIST INITIALLY. YOU CREATE IT, | USUALLY TO BOOTSTRAP YOUR SYSTEM WITHOUT USER INTERVENTION. | HOWEVER, RESTART COULD ALSO BE THE NAME OF ANY USER PROGRAM IN | THE MASTER DIRECTORY OR A LINK TO ANY PROGRAM LOCATED THERE. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 74 INSERT THE FOLLOWING MATERIAL AFTER THE COMMAND PROMPT: IN RDOS REVS. 7.50 AND LATER, IF YOU ISSUE THE FULL COMMAND, THE UTILITY ASKS IF YOU WANT TO RESERVE SPACE ON YOUR DISK FOR CORESIDENT DIAGNOSTICS: DO YOU WANT A CORESIDENT DIAGNOSTIC AREA? IF YOU ANSWER YES TO THIS QUESTION, DKINIT SETS ASIDE A CONTI- GUOUS AREA AT THE END OF YOUR DISK. THIS AREA IS OFF LIMITS TO THE OPERATING SYSTEM AND MOST OF THE SYSTEM UTILITIES. IT IS RESERVED TO HOLD DIAGNOSTIC PROGRAMS THAT A DATA GENERAL FIELD ENGINEER CAN LOAD FOR YOU. FOR DETAILS ABOUT THE DIAGNOSTICS THAT FIELD ENGINEERING CAN PROVIDE, PLACE A HARDWARE SERVICE CALL. TO ESTABLISH A CORESIDENT DIAGNOSTIC AREA, SIMPLY ANSWER YES TO DKINIT'S QUESTION. (IF YOU ARE NOT INTERESTED IN SUCH AN AREA, ANSWER NO AND SKIP THE REST OF THIS SECTION.) A YES RESPONSE PRODUCES THE FOLLOWING MESSAGE: THE DEFAULT CORESIDENT DIAGNOSTIC AREA SIZE IS 5000 BLOCKS HOW BIG WOULD YOU LIKE YOUR DIAGNOSTIC AREA TO BE? TYPE A CARRIAGE RETURN TO ACCEPT THE DEFAULT SIZE, OR ENTER AN INTEGER BETWEEN 1 AND 32767 (DECIMAL) TO DEFINE THE SIZE, IN BLOCKS, OF THE DIAGNOSTIC AREA. IF YOUR RESPONSE WOULD RESULT IN A DISK WITH FEWER THAN 128 BLOCKS LEFT FOR THE OPERATING SYSTEM, THE ERROR MESSAGE "DIAGNOSTIC AREA SIZE IS TOO LARGE FOR THIS DISK" APPEARS, AND DKINIT REPEATS ITS QUESTION. ONCE YOU SPECIFY AN ACCEPTABLE NUMBER OF BLOCKS FOR YOUR CORESIDENT DIAGNOSTICS, THE PROGRAM SUBTRACTS THE REQUESTED SIZE FROM THE TOTAL DISK SIZE AND STORES THE COMPUTED VALUE IN THE DISK'S IDENTIFICATION BLOCK (BLOCK 3). THEN THE DKINIT FULL DIALOG CONTINUES WITH A QUESTION ABOUT THE NUMBER OF PATTERNS YOU WANT DKINIT TO USE IN ANALYZING THE SURFACE OF YOUR DISK. WARNING: SINCE CREATING A CORESIDENT DIAGNOSTIC AREA IN EFFECT CHANGES THE SIZE OF YOUR DISK, YOU MUST BE CAREFUL WHEN YOU USE THE BURST UTILITY. YOU CANNOT LOAD A BURST BACKUP OF A DISK WITH A CORESIDENT DIAGNOSTIC AREA ONTO A DISK OF THE SAME TYPE WITHOUT A DIAGNOSTIC AREA OR WITH A DIAGNOSTIC AREA OF A DIFFERENT SIZE. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 76 PLACE THE FOLLOWING MATERIAL AT THE END OF THE SECTION "LIST COMMAND." THE PRECEDING EXAMPLES ASSUME THAT YOU ARE SEEKING INFORMATION ABOUT A DISK WITHOUT A DIAGNOSTIC AREA. IF YOUR DISK HAS A DIAGNOSTIC AREA, LIST'S OUTPUT WILL LOOK MORE LIKE THIS: FRAME SIZE = 21 REMAP AREA SIZE = 37 REMAP AREA START BLOCK NUMBER = 066000 DIAGNOSTIC AREA SIZE = 4000 DIAGNOSTIC AREA START BLOCK NUMBER = 070000 DIAGNOSTICS HAVE NOT BEEN INSTALLED THERE ARE NO BAD BLOCKS IN ADDITION, BEGINNING WITH REV. 7.50, LIST HAS A PAGE MODE. AFTER LIST HAS DISPLAYED A SCREEN FULL OF INFORMATION, IT STOPS TEMPORARILY AND ASKS YOU TO "TYPE RETURN TO CONTINUE." HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 78 ADD THE FOLLOWING ERROR MESSAGES TO TABLE 5.7: ERROR MESSAGE CORRECTIVE ACTION ----- ------- ---------- ------ ILLEGAL REMAP AREA THE MAXIMUM SIZE FOR THE REMAP SIZE AREA IS 126 BLOCKS. ENTER A SMALLER NUMBER. NNN CONTIGUOUS BLOCKS THE NUMBER OF BLOCKS YOU REQUESTED ARE NOT AVAILABLE - IS GREATER THAN THE LARGEST NUMBER PLEASE TRY A SMALLER OF CONTIGUOUS GOOD BLOCKS BETWEEN SIZE MAP.DR AND THE END OF THE DISK OR A CORESIDENT DIAGNOSTIC AREA. USE A SMALLER NUMBER. REPLACE THE PARAGRAPHS FOLLOWING THE MESSAGE "IT NEEDS TO BE AT LEAST YY BLOCKS LONG" WITH THE FOLLOWING MATERIAL. REMAP AREA SIZE (TYPE RETURN FOR DEFAULT) ? THE DEFAULT ANSWER IS RECOMMENDED WHERE YY IS A NUMBER LESS THAN XX. OTHERWISE, SPECIFY A DECIMAL NUMBER SLIGHTLY GREATER THAN YY (BUT NOT MORE THAN 126). IF THE DISK IS NOT LARGE ENOUGH TO HOLD A REMAP AREA OF THE SIZE YOU SPECIFY, DKINIT REPEATS ITS SIZE QUESTION. REMAP AREA START BLOCK NUMBER (TYPE RETURN FOR DEFAULT) ? SPECIFY THE DEFAULT ANSWER TO LOCATE THE REMAP AREA AMONG THE HIGHEST ADDRESSES ON THE DISK. OR DEFINE AN AREA ELSEWHERE ON THE DISK, MAKING SURE THAT IT CONTAINS AT LEAST ONE USABLE DISK BLOCK FOR EVERY FLAWED ONE, AND ENTER THE STARTING BLOCK NUMBER IN OCTAL. (TABLE 5.6, SHOWN EARLIER, LISTS THE HIGHEST BLOCK NUMBER ON EACH RDOS-SUPPORTED DISK AS A POINT OF REFERENCE.) DKINIT DOES NOT ALLOW THE REMAP AREA TO BEGIN BEFORE THE END OF MAP.DR. COMMAND? HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 79 PLACE THE FOLLOWING SECTION AT THE END OF CHAPTER 5. REFORMATTING A DISK WITH A CORESIDENT DIAGNOSTIC AREA AS YOU ENCOUNTER NEW BAD BLOCKS, YOU MAY RUN DKINIT TO PERFORM THE PARTIAL, TEST, REMAP, OR ENTER OPERATION, AND YOU MAY OCCASIONALLY PERFORM AN INIT/F ON THE DISK. NONE OF THESE COMMANDS WILL TOUCH THE DIAGNOSTIC AREA, HOWEVER. ITS LOCATION, SIZE, AND CONTENTS AND THE SPECIAL POINTERS AND FLAGS FOR IT WILL BE LEFT UNMODIFIED. COMBINATIONS OF THESE COMMANDS ARE SUFFICIENT FOR MOST DISKS AS THEY AGE. EVEN IF THE FILE SYSTEM CHANGES IN A FUTURE REVISION OF THE OPERATING SYSTEM, COMBINATIONS OF THESE COMMANDS MAY BE ENOUGH TO BRING THE DISK UP TO THE NEW FORMAT. IF YOU CONTINUE TO HAVE SERIOUS PROBLEMS WITH YOUR DISK AND NEED TO PERFORM A DKINIT FULL, CHANCES ARE THAT THE DIAGNOSTIC AREA HAS ALSO BECOME CORRUPT AND THE DISK SHOULD BE BOTH HARDWARE AND SOFTWARE REFORMATTED. IT IS POSSIBLE, THOUGH, TO SOFTWARE REFORMAT THE DISK WITH DKINIT'S FULL COMMAND WHILE PRESERVING NOT ONLY THE DIAGNOSTIC AREA SIZE AND CONTENTS BUT ALSO THE POINTERS AND FLAGS. TO DO THIS, YOU SHOULD: 1) USE DSKED TO RETRIEVE THE VALUES IN LOCATIONS 245 THROUGH 254 DECIMAL IN DISK BLOCK 3; 2) EXECUTE THE DKINIT LIST COMMAND TO DETERMINE THE SIZE OF THE CURRENT DIAGNOSTIC AREA; 3) USE THE DKINIT FULL COMMAND TO SOFTWARE FORMAT THE DISK, SPECIFYING THE SAME SIZE DIAGNOSTIC AREA; 4) USE DSKED TO REPLACE THE VALUES RETRIEVED EARLIER FROM DISK BLOCK 3. HOW TO LOAD AND GENERATE RDOS, 069-400013-00 20/JAN/89 DOCUMENTATION CHANGES, REVISION 02 PAGE 86 ADD THE FOLLOWING SENTENCE TO THE ERROR MESSAGE PARTITION IN USE. TYPE C TO CONTINUE. ON SYSTEMS THAT SUPPORT DUAL-PORTED DISKS, IF THE USE COUNT ON THE MASTER PARTITION IS NONZERO, RDOS ISSUES THIS MESSAGE TO INDICATE THAT THE OTHER SYSTEM MAY BE USING THE DISK. --END OF UPDATE FILE--