MSBOOT V05.08  
*MDUP.AI
MDUP V05.70 
?MDUP-I-No bad blocks detected VM0:

   RT-11 Automatic Installation Process

	Determining system configuration, please wait...

   RT-11 Automatic Installation Process

	Welcome to RT-11 V5.7

	You have bootstrapped the RT-11 Distribution Tape.  Use this Tape to
	install your RT-11 system, then store it in a safe place.


	RT-11 V5.7 provides an automatic installation procedure which will
	build a working system disk to be used for your work with RT-11.

	This  working  system disk will only  contain  the  RT-11  operating
	system.  After  the  RT-11  installation  is  complete,  follow  the 
	installation instructions  packaged  with  any optional languages or
	utility software that you will be using.



        Press the "RETURN" key when ready to continue. 

   RT-11 Automatic Installation Process

	You  will  be guided through the installation process by a series of
	instructions and questions; you will have an interactive dialog with
	the RT-11 installation program.  All you  need  to  do is follow the
	instructions  carefully.  If the  instructions  ask  you  to mount a
	disk in  a  specified drive,  find the disk with the correct
	label and mount  it  in  the  drive, as shown in the RT-11 Automatic
	Installation Guide.

	Do  not  remove  any  disk until specifically instructed to do so.
	Once  a  disk  is  mounted in a drive, it must remain in the drive
	until a message appears asking you to remove the disk.

        Press the "RETURN" key when ready to continue. 

   RT-11 Automatic Installation Process

	The following devices are valid for RT-11 System Installation:

	DU0, DU1, DU2, DL0

	Please enter the device name you wish the working system built on.
	If the default device is correct, press RETURN.

	What device is the working system to be built on (DU0)? 

   Enter Today's Date

	Please enter today's date in the following format:

	DD-MMM-YYYY

	where DD is the day of the month
	      MMM is the first 3 letters in the name of the month
	      YYYY is the last two numbers of the year

	For example:   May 30, 1998 is 30-MAY-1998

	Type in the date, then press the "RETURN" key.

              10-MAY-2009


   Building a Working System

	Your working system disk will now be built automatically.  This disk
	will contain the RT-11 Operating System.


	Please be sure the DU0 device is on line...


        Press the "RETURN" key when ready to continue. 


	Please be sure your output device in DU0 is not write protected...


        Press the "RETURN" key when ready to continue. 

   Building a Working System

	The Automatic Installation Procedure has detected RT-11  files  on
	your working system volume.

	The next procedure initializes DU0.  As a  result,  any  files
	that currently reside on DU0 will be permanently lost.  If you 
	would like to retain any files, EXIT from Automatic Installation
	Procedure and copy  them  to another volume.


	Do you want to EXIT from Automatic Installation (Y)? N

   Building a Working System

	The disk in DU0 is now being initialized.

	The following procedure should produce informational  messages
	in the form ?FORMAT-I-Message,  or ?DUP-I-Message.  No  action
	is required as a result of these messages.  If BAD blocks  are
	detected, the block number will be provided.  This information
	should be noted for future reference.

	This can take approximately fifteen minutes.  Please wait...


?DUP-I-No bad blocks detected DU0:

   Building a Working System

	Now copying RT-11 from MU0 (Drive 0) to DU0.

	This can take approximately one hour.  Please wait...

   RT-11 V5.7 Installation Complete

	Your working system disk will now be bootstrapped.

        Press the "RETURN" key when ready to continue. 


RT-11FB  V05.07  

.TYPE V5USER.TXT

                                   RT-11 V5.7

    Installation  of  RT-11  Version  5.7 is complete and you are now running
    RT-11 from your system volume.  

    Your  system volume is your working volume if you have used the Automatic
    Installation (AI) procedure.  If you  have  installed  RT-11  using  that
    procedure,  Mentec  recommends  you verify the  correct operation of your
    system's software using the VERIFY verification procedure.  You can  only
    perform  VERIFY  on  the  valid target (output) media you used for the AI
    procedure.  Run VERIFY before you run CONFIG.  To run VERIFY,  enter  the
    command:  
                                   IND VERIFY

    Mentec  recommends  you  read the file V5NOTE.TXT,  which you can TYPE or
    PRINT.  Also, read the Introduction to RT-11, rewritten for  V5.7,  which
    contains much of the information you need to use RT-11 Version 5.7.


.R MSCPCK
?MSCPCK-I-MU0-TU81  FW Rev Level is 005/HW Rev Level is 006 

.IND SYSGEN


 *****************************************************************
 		RT-11 SYSTEM GENERATION PROGRAM V05.150
 *****************************************************************


Do you want an introduction to system generation (N)? Y

 The  System  Generation (SYSGEN)  program  functions as an inter-
 active  dialog  in  which  the  program  asks  you  a  series  of
 questions.   Your   answers  establish  the  characteristics  and
 features  of  the monitor(s) and device handlers that the program
 generates.  SYSGEN  prints  each  question  and  waits  for  your
 response.  You  can  reply  immediately with a valid response, or
 you can obtain a detailed explanation of the  question  by typing
 the  ESCAPE  key  followed  by  the  RETURN key.  You can prevent
 SYSGEN from printing the entire explanation  by  typing  <CTRL/O>
 at  any  time during the explanation.  SYSGEN then stops printing
 the  explanation,   prints  the  question,  and  waits  for  your
 response.

 SYSGEN  can  generate one or more monitors from the output of one
 dialog  session, depending  on  the responses you give.  However,
 your  responses  during  a  session  apply  to  all  the monitors
 generated  during  that  session.

Type RETURN to continue 

 The system generation process produces two conditional files  and
 three  indirect command files as output.  To produce these files,
 the  SYSGEN  dialog  asks  you  questions about the target system
 configuration  and  about  monitor and device support options you
 want.  To  be able to respond effectively, you  should  read  the
 RT-11 SYSTEM GENERATION GUIDE before proceeding.

 The  dialog  simply  asks a question and waits for your response.
 Although the dialog questions are  sequentially numbered, certain
 responses cause SYSGEN to skip some  questions which do not apply
 for the system you are generating.

 Dialog  questions  require  one  of  several  types of responses.
 Responses may be in the form of a character string, a number,  or
 YES/NO  (Y/N).   SYSGEN  expects a decimal number for all numeric
 answers  except  for CSR and vector addresses;  in these cases it
 expects  an  octal  number.  A  default response, in parentheses,
 follows  each  question.   If  you  choose  to  use  the  default
 response, type only RETURN in response to the question.

 To terminate SYSGEN at any time, type <CTRL/C>.

Do you want to use a previously created answer file (N)? 

Do you want to create an answer file (N)? Y

What answer file do you want to create (SYSGEN.ANS)? 

	...checking for protected output files.


 *****************************************************************
 		MONITOR TYPE
 *****************************************************************

5.    Do you want the single-background (SB) monitor (Y)? 

10.   Do you want the foreground/background (FB) monitor (Y)? 

15.   Do you want the extended memory (XM) monitor (N)? Y

20.   Do you want the extended background (XB) monitor (N)? Y

25.   Do you want the Supervisor and I-D (ZM) monitor (N)? Y

30.   Do you want the Supervisor and I-D background (ZB) monitor (N)? Y


 *****************************************************************
 		MONITOR OPTIONS
 *****************************************************************

35.   Do you want timer support in the SB monitor (N)? Y

40.   Do you want device time-out support (N)? Y

45.   Do you want an error message on system I/O errors (Y)? 

50.   Do you want system job support (N)? Y

55.   Do you want to use the .SPCPS request (N)? Y

60.   Do you want global SCCA support (N)? Y

65.   Do you want multiterminal support (N)? Y

70.   Do you want asynchronous terminal status (Y)? 

75.   Do you want multiterminal time-out support (Y)? 

76.   Do you want multiterminal handler hooks support (N) ? Y

80.   Enter the size of the output buffers (40): 

85.   Enter the size of the input buffers (134): 

90.   Do you want to use the .FETCH request under XM/XB, ZM/ZB (Y)? 

95.   Do you want end of month and year date rollover (N)? Y

100.  Do you want the user command linkage (Y)? 

105.  Do you want high speed ring buffer support (N)? Y

110.  Do you want all the keyboard monitor commands (Y)? 

115.  Do you want the optional 50 Hz clock support (N)? Y

120.  Do you want to use the KW11-P clock as the system clock (N)? 

125.  Do you want the startup indirect file (Y)? 

130.  Do you want floating point support (N)? Y

135.  Do you want memory parity support (N)? 

140.  Do you want power failure messages (N)? 

145.  Do you want BATCH support (N)? Y

150.  Do you want error logging (N)? 

170.  Do you want extended device-unit support (N)? Y

175.  Do you want device ownership support (Y)? 

180.  Do you want the message handler resident in the monitor (Y)? 

185.  Do you want to define any other system conditionals (N)? 


 *****************************************************************
		DEVICE OPTIONS
 *****************************************************************

 Type <ESCAPE><RETURN> for help.
 Type ?<RETURN> to list all devices.
 Type .<RETURN> when device selection is complete.


Enter the device name you want support for [dd]: ?


  DX  RX01 Single-Density Diskette     DY  RX02 Double-Density Diskette
  RK  RK05 Cartridge Disk              DL  RL01/RL02 Cartridge Disk    
  DM  RK06/RK07 Cartridge Disk         MT  TM11 (UNIBUS) Magtape       
  MS  TS11,TU80/TSV05/TSU05 Tape       MM  TJU16 (MASSBUS) Magtape     
  NL  Null Handler                     LP  Line Printer                
  DU  MSCP Disk Class Handler          LD  Logical Disk Handler        
  VM  Virtual Memory Handler           DZ  RX50 PRO Series             
  DW  RD50/51/52 PRO Series            SP  Transparent Spooling Handler
  XL  VTCOM Communications Handler     XC  VTCOM Handler PRO Series    
  MU  TMSCP Magtape Class Handler      NC  Ethernet Handler PRO Series 
  NQ  Ethernet Handler for Q-BUS       NU  Ethernet Handler for UNIBUS 
  LS  Serial Line Printer              


Enter the device name you want support for [dd]: DY

200.  Do you want support for a second RX02 controller (N)? 

205.  Do you want RX02 double density only support (N)? 

210.  What is the CSR  address for the first RX02 (177170)? 

215.  What is the vector address for the first RX02 (264)? 

Enter the next device name [dd]: RK

Enter the next device name [dd]: DM

Enter the next device name [dd]: MT

260.  Do you want the file-structured magtape handler (Y)? 

265.  How many magtape units are to be supported (2)? 1

Enter the next device name [dd]: MS

260.  Do you want the file-structured magtape handler (Y)? 

265.  How many magtape units are to be supported (2)? 1

270.  What is the address of the first unit (172522)? 

275.  What is the vector address of the first unit (224)? 

Enter the next device name [dd]: MM

260.  Do you want the file-structured magtape handler (Y)? 

265.  How many magtape units are to be supported (2)? 1

Enter the next device name [dd]: NL

Enter the next device name [dd]: LP

280.  Does your printer have a nonstandard vector or CSR (N)? 

Enter the next device name [dd]: DU

225.  How many ports are to be supported (1)? 

230.  What is the CSR (register) address for the first port (172150)? 

235.  What is the vector address for the first port (154)? 

245.  Do you want support for DU initiated bad block replacement (Y)? N

250.  Do you want extended device-unit support for handler DU (Y)? 

255.  How many device-units should DU support (16)? 

Enter the next device name [dd]: LD

250.  Do you want extended device-unit support for handler LD (Y)? 

255.  How many device-units should LD support (16)? 

Enter the next device name [dd]: VM

Enter the next device name [dd]: MU

260.  Do you want the file-structured magtape handler (Y)? 

265.  How many magtape units are to be supported (1)? 

270.  What is the address of the first unit (174500)? 

275.  What is the vector address of the first unit (260)? 

Enter the next device name [dd]: SP

320.  Do you want support for banner pages (Y)? 

Enter the next device name [dd]: .

Do you want to add support for any of your own devices (N)? 

355.  How many extra device slots do you want (0)? 4


 *****************************************************************
 		TERMINAL INTERFACE OPTIONS
 *****************************************************************

Do you want an introduction to terminal interface options (N)? Y

 The terminal interface options section allows you to select RT-11
 support for up to 17 (decimal) serial asynchronous lines selected
 from  the  interfaces  installed  in  your  system.    Interfaces
 supported include those from the DL, DZ and DH series.

 DL  interfaces  supported  by  RT-11 include the DLV11,  DLV11-E,
 DLV11-F,  DLV11-J,  and  the  DL11  series.   RT-11 also supports
 DL11-E and DLV11-E interfaces, with modem capabilities.

 The  dialog  asks first for the number of local DL11 lines,  then
 the  number  of remote DL11 lines.   The total number of DL lines
 supported  may  not exceed 8 lines.   Subsequent sections request
 the number of local and remote DZ and DH lines.  The total of all
 local and all remote lines may not exceed 17 (decimal).

 SYSGEN  assigns  logical unit numbers (LUNs) beginning with local
 DL11  lines,  then remote DL11 lines.   It then proceeds with any
 local DZ and remote DZ lines.   It finishes with any local DH and
 remote  DH lines.   This order of assignment is permanent and you
 cannot change its order.

Type return to continue 

 After SYSGEN has established the number of lines of each type, it
 must  establish  the CSR and vector addresses for each line.  The
 first  such  question  corresponds  to  the first local line (the
 console),   the  second to the second local line, etc., until all
 local  lines are accounted for.  At that point, the next question
 applies to the first remote line, the second to the second remote
 line, etc., until  all remote lines are accounted for.

 If your interfaces are DL11-W interfaces, they should be at REV E
 or higher.  If they are not, an Engineering Change Order (ECO DEC
 -O-LOG  M7856-S0002)  must  be  applied  to the M7856 module. The
 field  service  representative  who installs your hardware should
 apply the ECO, if necessary.

360.  Support for how many local DL11 lines, including the console (1) ? 8

370.  What is the CSR for the first (console) DL11 (177560)? 

375.  What is the vector for the first (console) DL11 (60)? 

370.  What is the CSR for the next (local) DL11 (176500)? 

375.  What is the vector for the next (local) DL11 (300)? 

370.  What is the CSR for the next (local) DL11 (176510)? 

375.  What is the vector for the next (local) DL11 (310)? 

370.  What is the CSR for the next (local) DL11 (176520)? 

375.  What is the vector for the next (local) DL11 (320)? 

370.  What is the CSR for the next (local) DL11 (176530)? 

375.  What is the vector for the next (local) DL11 (330)? 

370.  What is the CSR for the next (local) DL11 (176540)? 

375.  What is the vector for the next (local) DL11 (340)? 

370.  What is the CSR for the next (local) DL11 (176550)? 

375.  What is the vector for the next (local) DL11 (350)? 

370.  What is the CSR for the next (local) DL11 (176560)? 

375.  What is the vector for the next (local) DL11 (360)? 

380.  Do you want DZ series multiplexor support (N)? 

420.  Do you want DH series multiplexor support (N) ? 

Do you want to change any of your responses (N)? 

        ...writing system conditional and answer files.


 *****************************************************************
	DEVICE ASSIGNMENTS AND SYSGEN CLEANUP
 *****************************************************************

What is the name of the source input device [xxn] (DU1)? DU0

What is the name of the binary output device [xxn] (DU0)? 

What is the name of the map output device [xxn] (DU0)? 

Do you want to retain the system OBJs (Y)? N

Do you want to retain the work files (Y)? 

        ...writing build files.

 To  build  an entire system, mount the source and binary volumes,
 copy the files SYSGEN.CND, SYSGEN.TBL, EDTL.MLB, SYSTEM.MLB, and
 the sources for any user supplied device handlers to the source
 volume.  The RT-11 utility program MONMRG.SAV must be present
 on the system disk, in order to build the monitors.  To build
 both the monitors and the device handlers, type $@SYSGEN.BLD.
 To build just the monitors, type $@SYSGEN.MON.  To build just
 the device handlers, type $@SYSGEN.DEV. For more information,
 read the RT-11 SYSTEM GENERATION GUIDE.

 END OF SYSGEN PROGRAM --
@ <EOF>

.$@SYSGEN.BLD

.

.$@SYSGEN.MON

.ASSIGN DU0 SRC

.ASSIGN DU0 BIN

.ASSIGN DU0 MAP

.ASSIGN DU0 OBJ

.MAC/OB:OBJ:KMSB SRC:(SB+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USSB SRC:(SB+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMSB SRC:(SB+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:TBSB SRC:(SB+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTSB SRC:(SB+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MESB SRC:(SB+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MISB SRC:(SB+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11SB.TM2/BOU:1000/MAP:BIN:RT11SB.TM5/SYM:BIN:RT11SB.TM3/PRO
Files? OBJ:USSB
*OBJ:RMSB
*OBJ:KMSB,MESB,MISB,TBSB//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11SB.TM1/MAP:BIN:RT11SB.TM4 OBJ:BTSB,BIN:RT11SB.TM3

.R MONMRG
*BIN:RT11SB.SYG,MAP:RT11SB.MAP=BIN:RT11SB.TM1,RT11SB.TM2,RT11SB.TM4,RT11SB.TM5
*^C

.DEL BIN:RT11SB.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)SB.OBJ

.DELETE/NOQ OBJ:(TB,BT)SB.OBJ

.DELETE/NOQ OBJ:(ME,MI)SB.OBJ

.MAC/OB:OBJ:KMFB SRC:(FB+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USFB SRC:(FB+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMFB SRC:(FB+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:TBFB SRC:(FB+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTFB SRC:(FB+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MEFB SRC:(FB+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MIFB SRC:(FB+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11FB.TM2/BOU:1000/MAP:BIN:RT11FB.TM5/SYM:BIN:RT11FB.TM3/PRO
Files? OBJ:USFB
*OBJ:RMFB
*OBJ:KMFB,MEFB,MIFB,TBFB//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11FB.TM1/MAP:BIN:RT11FB.TM4 OBJ:BTFB,BIN:RT11FB.TM3

.R MONMRG
*BIN:RT11FB.SYG,MAP:RT11FB.MAP=BIN:RT11FB.TM1,RT11FB.TM2,RT11FB.TM4,RT11FB.TM5
*^C

.DEL BIN:RT11FB.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)FB.OBJ

.DELETE/NOQ OBJ:(TB,BT)FB.OBJ

.DELETE/NOQ OBJ:(ME,MI)FB.OBJ

.MAC/OB:OBJ:KMXM SRC:(XM+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USXM SRC:(XM+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMXM SRC:(XM+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:SBXM SRC:(XM+SYSGEN.CND+EDTG+XMSUBS)

.MAC/OB:OBJ:TBXM SRC:(XM+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTXM SRC:(XM+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MEXM SRC:(XM+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MIXM SRC:(XM+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11XM.TM2/BOU:1000/MAP:BIN:RT11XM.TM5/SYM:BIN:RT11XM.TM3/PRO
Files? OBJ:USXM
*OBJ:RMXM
*OBJ:SBXM,KMXM,MEXM,MIXM,TBXM//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11XM.TM1/MAP:BIN:RT11XM.TM4 OBJ:BTXM,BIN:RT11XM.TM3

.R MONMRG
*BIN:RT11XM.SYG,MAP:RT11XM.MAP=BIN:RT11XM.TM1,RT11XM.TM2,RT11XM.TM4,RT11XM.TM5
*^C

.DEL BIN:RT11XM.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)XM.OBJ

.DELETE/NOQ OBJ:(SB,TB,BT)XM.OBJ

.DELETE/NOQ OBJ:(ME,MI)XM.OBJ

.MAC/OB:OBJ:KMXB SRC:(XB+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USXB SRC:(XB+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMXB SRC:(XB+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:SBXB SRC:(XB+SYSGEN.CND+EDTG+XMSUBS)

.MAC/OB:OBJ:TBXB SRC:(XB+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTXB SRC:(XB+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MEXB SRC:(XB+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MIXB SRC:(XB+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11XB.TM2/BOU:1000/MAP:BIN:RT11XB.TM5/SYM:BIN:RT11XB.TM3/PRO
Files? OBJ:USXB
*OBJ:RMXB
*OBJ:SBXB,KMXB,MEXB,MIXB,TBXB//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11XB.TM1/MAP:BIN:RT11XB.TM4 OBJ:BTXB,BIN:RT11XB.TM3

.R MONMRG
*BIN:RT11XB.SYG,MAP:RT11XB.MAP=BIN:RT11XB.TM1,RT11XB.TM2,RT11XB.TM4,RT11XB.TM5
*^C

.DEL BIN:RT11XB.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)XB.OBJ

.DELETE/NOQ OBJ:(SB,TB,BT)XB.OBJ

.DELETE/NOQ OBJ:(ME,MI)XB.OBJ

.MAC/OB:OBJ:KMZM SRC:(ZM+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USZM SRC:(ZM+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMZM SRC:(ZM+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:SBZM SRC:(ZM+SYSGEN.CND+EDTG+XMSUBS)

.MAC/OB:OBJ:TBZM SRC:(ZM+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTZM SRC:(ZM+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MEZM SRC:(ZM+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MIZM SRC:(ZM+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11ZM.TM2/BOU:1000/MAP:BIN:RT11ZM.TM5/SYM:BIN:RT11ZM.TM3/PRO
Files? OBJ:USZM
*OBJ:RMZM
*OBJ:SBZM,KMZM,MEZM,MIZM,TBZM//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11ZM.TM1/MAP:BIN:RT11ZM.TM4 OBJ:BTZM,BIN:RT11ZM.TM3

.R MONMRG
*BIN:RT11ZM.SYG,MAP:RT11ZM.MAP=BIN:RT11ZM.TM1,RT11ZM.TM2,RT11ZM.TM4,RT11ZM.TM5
*^C

.DEL BIN:RT11ZM.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)ZM.OBJ

.DELETE/NOQ OBJ:(SB,TB,BT)ZM.OBJ

.DELETE/NOQ OBJ:(ME,MI)ZM.OBJ

.MAC/OB:OBJ:KMZB SRC:(ZB+SYSGEN.CND+EDTG+KMON+KMOVLY)

.MAC/OB:OBJ:USZB SRC:(ZB+SYSGEN.CND+EDTG+USR)

.MAC/OB:OBJ:RMZB SRC:(ZB+SYSGEN.CND+EDTG+RMON)

.MAC/OB:OBJ:SBZB SRC:(ZB+SYSGEN.CND+EDTG+XMSUBS)

.MAC/OB:OBJ:TBZB SRC:(ZB+SYSGEN.CND+EDTG+SYSGEN.TBL+TRMTBL)

.MAC/OB:OBJ:BTZB SRC:(ZB+SYSGEN.CND+EDTG+BSTRAP)

.MAC/OB:OBJ:MEZB SRC:(ZB+SYSGEN.CND+EDTG+MTTEMT)

.MAC/OB:OBJ:MIZB SRC:(ZB+SYSGEN.CND+EDTG+MTTINT)

.LINK/EXE:BIN:RT11ZB.TM2/BOU:1000/MAP:BIN:RT11ZB.TM5/SYM:BIN:RT11ZB.TM3/PRO
Files? OBJ:USZB
*OBJ:RMZB
*OBJ:SBZB,KMZB,MEZB,MIZB,TBZB//
Boundary section? OVLY0

.LINK/EXE:BIN:RT11ZB.TM1/MAP:BIN:RT11ZB.TM4 OBJ:BTZB,BIN:RT11ZB.TM3

.R MONMRG
*BIN:RT11ZB.SYG,MAP:RT11ZB.MAP=BIN:RT11ZB.TM1,RT11ZB.TM2,RT11ZB.TM4,RT11ZB.TM5
*^C

.DEL BIN:RT11ZB.TM(1,2,3,4,5)

.DELETE/NOQ OBJ:(KM,US,RM)ZB.OBJ

.DELETE/NOQ OBJ:(SB,TB,BT)ZB.OBJ

.DELETE/NOQ OBJ:(ME,MI)ZB.OBJ

.$@SYSGEN.DEV

.ASSIGN DU0 SRC

.ASSIGN DU0 BIN

.ASSIGN DU0 OBJ

.MAC/OB:OBJ:LD SRC:(SYSGEN.CND+LD)

.LINK/NOBITMAP/EXE:BIN:LD.SYG/BOUNDARY:512. OBJ:LD
Boundary section? SETOVR

.DELETE/NOQ OBJ:LD.OBJ

.MAC/OB:OBJ:LDX SRC:(XM+SYSGEN.CND+LD)

.LINK/NOBITMAP/EXE:BIN:LDX.SYG/BOUNDARY:512. OBJ:LDX
Boundary section? SETOVR

.DELETE/NOQ OBJ:LDX.OBJ

.MAC/OB:OBJ:BA SRC:(SYSGEN.CND+BA)

.LINK/NOBITMAP/EXE:BIN:BA.SYG OBJ:BA

.DELETE/NOQ OBJ:BA.OBJ

.MAC/OB:OBJ:BAX SRC:(XM+SYSGEN.CND+BA)

.LINK/NOBITMAP/EXE:BIN:BAX.SYG OBJ:BAX

.DELETE/NOQ OBJ:BAX.OBJ

.MAC/OB:OBJ:DY SRC:(SYSGEN.CND+DY)

.LINK/NOBITMAP/EXE:BIN:DY.SYG OBJ:DY

.DELETE/NOQ OBJ:DY.OBJ

.MAC/OB:OBJ:DYX SRC:(XM+SYSGEN.CND+DY)

.LINK/NOBITMAP/EXE:BIN:DYX.SYG OBJ:DYX

.DELETE/NOQ OBJ:DYX.OBJ

.MAC/OB:OBJ:VM SRC:(SYSGEN.CND+VM)

.LINK/NOBITMAP/EXE:BIN:VM.SYG OBJ:VM

.DELETE/NOQ OBJ:VM.OBJ

.MAC/OB:OBJ:VMX SRC:(XM+SYSGEN.CND+VM)

.LINK/NOBITMAP/EXE:BIN:VMX.SYG OBJ:VMX

.DELETE/NOQ OBJ:VMX.OBJ

.MAC/OB:OBJ:SP SRC:(SYSGEN.CND+SP)

.LINK/NOBITMAP/EXE:BIN:SP.SYG/BOUNDARY:512. OBJ:SP
Boundary section? SETOVR

.DELETE/NOQ OBJ:SP.OBJ

.MAC/OB:OBJ:SPX SRC:(XM+SYSGEN.CND+SP)

.LINK/NOBITMAP/EXE:BIN:SPX.SYG/BOUNDARY:512. OBJ:SPX
Boundary section? SETOVR

.DELETE/NOQ OBJ:SPX.OBJ

.MAC/OB:OBJ:RK SRC:(SYSGEN.CND+RK)

.LINK/NOBITMAP/EXE:BIN:RK.SYG OBJ:RK

.DELETE/NOQ OBJ:RK.OBJ

.MAC/OB:OBJ:RKX SRC:(XM+SYSGEN.CND+RK)

.LINK/NOBITMAP/EXE:BIN:RKX.SYG OBJ:RKX

.DELETE/NOQ OBJ:RKX.OBJ

.MAC/OB:OBJ:DU SRC:(SYSGEN.CND+DU)

.LINK/NOBITMAP/EXE:BIN:DU.SYG/BOUNDARY:512. OBJ:DU
Boundary section? SETOVR

.DELETE/NOQ OBJ:DU.OBJ

.MAC/OB:OBJ:DUX SRC:(XM+SYSGEN.CND+DU)

.LINK/NOBITMAP/EXE:BIN:DUX.SYG/BOUNDARY:512. OBJ:DUX
Boundary section? SETOVR

.DELETE/NOQ OBJ:DUX.OBJ

.MAC/OB:OBJ:DM SRC:(SYSGEN.CND+DM)

.LINK/NOBITMAP/EXE:BIN:DM.SYG OBJ:DM

.DELETE/NOQ OBJ:DM.OBJ

.MAC/OB:OBJ:DMX SRC:(XM+SYSGEN.CND+DM)

.LINK/NOBITMAP/EXE:BIN:DMX.SYG OBJ:DMX

.DELETE/NOQ OBJ:DMX.OBJ

.MAC/OB:OBJ:FSM SRC:(SYSGEN.CND+FSM)

.MAC/OB:OBJ:FSMX SRC:(XM+SYSGEN.CND+FSM)

.MAC/OB:OBJ:MT SRC:(SYSGEN.CND+TM)

.LINK/NOBITMAP/EXE:BIN:MT.SYG OBJ:(MT,FSM)

.DELETE/NOQ OBJ:MT.OBJ

.MAC/OB:OBJ:MTX SRC:(XM+SYSGEN.CND+TM)

.LINK/NOBITMAP/EXE:BIN:MTX.SYG OBJ:(MTX,FSMX)

.DELETE/NOQ OBJ:MTX.OBJ

.MAC/OB:OBJ:MM SRC:(SYSGEN.CND+TJ)

.LINK/NOBITMAP/EXE:BIN:MM.SYG OBJ:(MM,FSM)

.DELETE/NOQ OBJ:MM.OBJ

.MAC/OB:OBJ:MMX SRC:(XM+SYSGEN.CND+TJ)

.LINK/NOBITMAP/EXE:BIN:MMX.SYG OBJ:(MMX,FSMX)

.DELETE/NOQ OBJ:MMX.OBJ

.MAC/OB:OBJ:MS SRC:(SYSGEN.CND+TS)

.LINK/NOBITMAP/EXE:BIN:MS.SYG OBJ:(MS,FSM)

.DELETE/NOQ OBJ:MS.OBJ

.MAC/OB:OBJ:MSX SRC:(XM+SYSGEN.CND+TS)

.LINK/NOBITMAP/EXE:BIN:MSX.SYG OBJ:(MSX,FSMX)

.DELETE/NOQ OBJ:MSX.OBJ

.MAC/OB:OBJ:MU SRC:(SYSGEN.CND+TU)

.LINK/NOBITMAP/EXE:BIN:MU.SYG/BOUNDARY:512. OBJ:(MU,FSM)
Boundary section? SETOVR

.DELETE/NOQ OBJ:MU.OBJ

.MAC/OB:OBJ:MUX SRC:(XM+SYSGEN.CND+TU)

.LINK/NOBITMAP/EXE:BIN:MUX.SYG/BOUNDARY:512. OBJ:(MUX,FSMX)
Boundary section? SETOVR

.DELETE/NOQ OBJ:MUX.OBJ

.DELETE/NOQ OBJ:FSM.OBJ

.DELETE/NOQ OBJ:FSMX.OBJ

.MAC/OB:OBJ:LP SRC:(SYSGEN.CND+LP)

.LINK/NOBITMAP/EXE:BIN:LP.SYG OBJ:LP

.DELETE/NOQ OBJ:LP.OBJ

.MAC/OB:OBJ:LPX SRC:(XM+SYSGEN.CND+LP)

.LINK/NOBITMAP/EXE:BIN:LPX.SYG OBJ:LPX

.DELETE/NOQ OBJ:LPX.OBJ

.MAC/OB:OBJ:NL SRC:(SYSGEN.CND+NL)

.LINK/NOBITMAP/EXE:BIN:NL.SYG OBJ:NL

.DELETE/NOQ OBJ:NL.OBJ

.MAC/OB:OBJ:NLX SRC:(XM+SYSGEN.CND+NL)

.LINK/NOBITMAP/EXE:BIN:NLX.SYG OBJ:NLX

.DELETE/NOQ OBJ:NLX.OBJ

.SET USR NOSWAP

.REN/SYS .SYG .SYS
 Files renamed:
DK:VM.SYG      to DK:VM.SYS
DK:RT11SB.SYG  to DK:RT11SB.SYS
DK:LDX.SYG     to DK:LDX.SYS
DK:BA.SYG      to DK:BA.SYS
DK:BAX.SYG     to DK:BAX.SYS
DK:DYX.SYG     to DK:DYX.SYS
DK:VMX.SYG     to DK:VMX.SYS
DK:SP.SYG      to DK:SP.SYS
DK:SPX.SYG     to DK:SPX.SYS
DK:RK.SYG      to DK:RK.SYS
DK:RKX.SYG     to DK:RKX.SYS
DK:DU.SYG      to DK:DU.SYS
DK:DM.SYG      to DK:DM.SYS
DK:LP.SYG      to DK:LP.SYS
DK:LPX.SYG     to DK:LPX.SYS
DK:RT11FB.SYG  to DK:RT11FB.SYS
DK:LD.SYG      to DK:LD.SYS
DK:DY.SYG      to DK:DY.SYS
DK:RT11XM.SYG  to DK:RT11XM.SYS
DK:RT11XB.SYG  to DK:RT11XB.SYS
DK:DUX.SYG     to DK:DUX.SYS
DK:DMX.SYG     to DK:DMX.SYS
DK:MT.SYG      to DK:MT.SYS
DK:MTX.SYG     to DK:MTX.SYS
DK:MM.SYG      to DK:MM.SYS
DK:MMX.SYG     to DK:MMX.SYS
DK:MS.SYG      to DK:MS.SYS
DK:MSX.SYG     to DK:MSX.SYS
DK:MU.SYG      to DK:MU.SYS
DK:MUX.SYG     to DK:MUX.SYS
DK:NL.SYG      to DK:NL.SYS
DK:NLX.SYG     to DK:NLX.SYS
DK:RT11ZM.SYG  to DK:RT11ZM.SYS
DK:RT11ZB.SYG  to DK:RT11ZB.SYS
?PIP-W-Reboot

.BOO RT11ZM

RT-11ZM (S) V05.07  

.TYPE V5USER.TXT

                                   RT-11 V5.7

    Installation  of  RT-11  Version  5.7 is complete and you are now running
    RT-11 from your system volume.  

    Your  system volume is your working volume if you have used the Automatic
    Installation (AI) procedure.  If you  have  installed  RT-11  using  that
    procedure,  Mentec  recommends  you verify the  correct operation of your
    system's software using the VERIFY verification procedure.  You can  only
    perform  VERIFY  on  the  valid target (output) media you used for the AI
    procedure.  Run VERIFY before you run CONFIG.  To run VERIFY,  enter  the
    command:  
                                   IND VERIFY

    Mentec  recommends  you  read the file V5NOTE.TXT,  which you can TYPE or
    PRINT.  Also, read the Introduction to RT-11, rewritten for  V5.7,  which
    contains much of the information you need to use RT-11 Version 5.7.


.R MSCPCK
?MSCPCK-I-MU0-TU81  FW Rev Level is 005/HW Rev Level is 006 

.
