[Simh] Getting rsxs to run on the pdp11 emulator
Rhialto
rhialto at falu.nl
Tue Mar 3 16:26:41 EST 2015
On Tue 03 Mar 2015 at 13:05:50 -0500, Christian Gauger-Cosgrove wrote:
> My simulator config is big, and somewhat redundant, I actually have
> the installation phase and its tape swap automated with:
> SET TU0 LOCK
> ATTACH TU0 TAP\BB-J0830-01.M01_RSX11M+_V4.6_1999.tap
> BOOT TU0
> ATTACH TU0 TAP\BB-J0830-01.L01_RSX11M+_V4.6_BRU_1999.tap
> CONTINUE
> I have the tapes in a subfolder called "TAP". And I swap the tapes
> between drives after the standalone boot tape has booted by just
> hitting Ctrl+E just once.
Nice trick! I've used it immediately in my test setup. This time I
started with a configuration which is closer to the system I had set up
already anyway.
After quadruple checking the csr and vector addresses (and no, if SHOW
TU doesn't list them, it doesn't mean they are fixed and therefore
correct; instead I had to do SHOW RHB to find the values. This might be
a small point of improvement for simh; I could also use some help from
simh to find out that connection, which may be obvious to the
experienced, but it wasn't for me. I only discovered it by crosschecking
device names in my running RSX system)
One difference that at first I did not understand, was that I got this:
BRU - Starting Tape 1 on MM0:
BRU - This disk will not contain a hardware bootable system
BRU - End of Tape 1 on MM0:
BRU - Starting verify pass Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Completed
However, after reading the actual documentation :)
AA-H431H-TC_RSX-11M-PLUS_4.3_System_Generation_and_Installation_Guide_Jan90.pdf
I see that I need to swap the tapes between booting and running BRU.
I didn't see that happening in your log file somehow, although you do
mention it.
Anyway, by also copying from the tape I booted from, I probably copied a
bit too much. Any way to get a listing of what's on the tape?
Both files are not small:
11M BB-J0830-01.M01_RSX11M+_V4.6_1999.tap <-- booted off this one
30M BB-J0830-01.L01_RSX11M+_V4.6_BRU_1999.tap <-- contains the string
***THIS VOLUME DOES NOT CONTAIN A HARDWARE BOOTABLE SYSTEM ***
I've attached my console log. I've stopped at the point where I get the
MCR prompt, I haven't done the sysgen. I have removed extraneous ^Ms for
readability.
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for
\X/ rhialto/at/xs4all.nl -- 'this bath is too hot.'
-------------- next part --------------
Logging to file "console-log"
Logging to file "console-log" at Tue Mar 3 21:24:26 2015
CPU 11/94, NOCIS, idle disabled, autoconfiguration enabled
4088KB
RS Massbus adapter 2, 8 units
RS0 524KW, not attached, write enabled
RS04
RQ0: creating new file
RQ address=17772150-17772153, no vector, RQDX3, 4 units
RQ0 159MB, attached to fresh.ods1, write enabled
RD54, autosize, SIMH format
RQ1 159MB, not attached, write enabled
RD54, autosize, SIMH format
RQ2 159MB, not attached, write enabled
RD54, autosize, SIMH format
RQ3 800KB, not attached, write enabled
RX50, autosize, SIMH format
TU Massbus adapter 1, FORMATTER, TM03, 8 units
TU0 not attached, write enabled, TE16
SIMH format, unlimited capacity
TU1 not attached, write enabled, TE16
SIMH format, unlimited capacity
TU2 not attached, write enabled, TE16
SIMH format, unlimited capacity
TU3 not attached, write enabled, TE16
SIMH format, unlimited capacity
VH address=17760440-17760537*, vector=300-334*, lines=64, 4 units
VH0 not attached, DHU mode, Modem
Hangup
VH1 DHU mode, Modem, Hangup
VH2 DHU mode, Modem, Hangup
VH3 DHU mode, Modem, Hangup
Listening on port 2312
PDP-11/94 System #: 05349 (012345)
RSX-11M/RSX-11M-PLUS STANDALONE COPY SYSTEM V4.8
RSX-11M/RSX-11M-PLUS Standalone Configuration and Disk Sizing Program
Valid switches are:
/CSR=nnnnnn to change the default device CSR
/VEC=nnn to change the default device vector
/FOR=n to change the default magtape formatter number
/DEV to list all default device CSR and vectors
Enter first device: /dev
Device CSR Vector CSR Status
------ ------ ------ ----------
DB 176700 254 Present
DK 177404 220 Not Present
DL 174400 160 Not Present
DM 177440 210 Present
DP 176714 300 Present
DR 176300 150 Not Present
DU 172150 154 Present
MM FOR=0 172440 330 Present
MS 172522 224 Not Present
MT 160000 320 Not Present
MU 174500 260 Not Present
Enter first device: mm0:/vec=224
Enter second device: du0:
Hit RETURN and enter date and time as 'TIM HH:MM MM/DD/YY'
>tim 21:25 03/03/15
>run bad
>
BAD>du0:/list
BAD -- DU0: Total bad blocks= 0.
BAD>^Z
>run bru
>
BRU>/init/rewind/verify/maximum:19143/headers:9571 mm0: du0:
BRU - Starting Tape 1 on MM0:
BRU - This disk will not contain a hardware bootable system
BRU - End of Tape 1 on MM0:
BRU - Starting verify pass Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Completed
BRU>^Z
>
Simulation stopped, PC: 001344 (CLRB (R1)+)
>run bru
>
BRU>/verify mm0: du0:
BRU - Starting Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Starting verify pass Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Completed
BRU>^Z
sim> boot rq0
RSX-11M-PLUS V4.6 BL87 2044.KW System:"Baseline"
>RED DU:=SY:
>RED DU:=LB:
>RED DU:=SP:
>MOU DU0:"RSX11MPBL87"
>@[2,54]BASTART.CMD
>SET /CRASHDEV=MM0:
SET -- Crash device MM000: has been successfully loaded
>;Z[c
SET -- Inquire cannot determine terminal type
>;
>; Please ignore any random characters that may have printed on your
>; terminal just now. They came from a SET /INQUIRE=TI: command.
>; Evidently your terminal does not recognize escape sequences.
>; This will not affect the running of this command file.
>;
>;
>; RSX-11M-PLUS V4.6 Distribution Kit
>;
>; This is the baseline system of the RSX-11M-PLUS V4.6
>; distribution kit. This system contains an assortment of
>; devices and may in fact be of some use on your target
>; system. The main purpose of the baseline system, however,
>; is to provide a working system environment which may be
>; used to generate a custom-tailored operating system for
>; your target hardware. We will now provide instructions
>; to guide you through the startup procedure.
>;
>* Please enter time and date (Default:03-MAR-2015 21:30) [S]:
>;
>; Now allocate checkpoint space for use by system utilities.
>;
>ACS SY:/BLKS=1024.
>;
>; The following information is necessary for this command file
>; to correctly access the remainder of the distribution kit.
>;
>* Did you receive your RSX-11M-PLUS distribution kit on magnetic tape? [Y/N]: y
>;
>; Please enter the name of the magnetic tape drive, which should
>; still contain the distribution tape. The name is of the form:
>;
>; MM1: or
>; MS0: etc...
>;
>* Which tape drive contains the distribution tape [S]: mm0
>* Do you have the 1600-bpi magnetic tape distribution kit? [Y/N]: y
>;
>; We will now set the CSR of the controller that will be
>; used to bring in the remainder of the distribution kit to
>; the standard value. If your controller is not at this address
>; it will be necessary for you to manually configure the system
>; by issuing the appropriate CON commands. Answer Yes to the
>; manual configuration question to do this. If your controller
>; is at the standard address, you do not have to do a manual
>; configuration.
>;
>CON SET MSA CSR=160000
>CON SET MTA CSR=160000
>CON SET MUA CSR=160000
>;
>; We will now bring on line all devices which were generated into
>; this baseline image and which exist in your hardware system.
>;
>; If there is hardware in your system occupying a control
>; register address which conflicts with a standard DIGITAL
>; register assignment, it is possible that the "CON ONLINE
>; ALL" command might cause a system crash. This is because
>; a supplied device driver is attempting to manipulate foreign
>; hardware or the CSR address assignments in your system are
>; different from those assumed in this baseline configuration.
>; On the first pass through this file please answer No to the
>; following question. If such a mismatch exists and a crash
>; does occur, rebootstrap the baseline system and answer Yes
>; to this question. Instructions will then be provided to help
>; circumvent the problem.
>;
>* Do you need to do manual configuration? [Y/N]: n
>;
>CON ONLINE ALL
>;
>; Prepare to bring in the remainder of the distribution kit
>;
>* Is your target system disk an RC25, RK07, or RD52? [Y/N]: n
>;
>; Since the files in the second backup set are not necessary to generate
>; your system you may wish to skip the verify pass to save time.
>;
>* Do you want to verify the second backup set? [Y/N]: y
>;
>; We will now mount the tape in MM0: for access by BRU.
>;
>MOU MM0:/FOR/DENS=1600
>;
>; Ensure that the BRU task is installed.
>;
>INS $BRU
>;
>; We will now load the remainder of the distribution kit.
>;
>TIME
21:31:58 3-MAR-15
>;
>BRU /BAC:MPBL87SRC/UFD/NOINI/DENS:1600/VER MM0: SY:
BRU - Starting Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Starting verify pass Tape 1 on MM0:
BRU - End of Tape 1 on MM0:
BRU - Completed
>;
>DMO MM0:/LOCK=UNLOAD
21:32:11 *** MM0: -- Dismount complete
DMO -- TT0: dismounted from MM0: *** Final dismount initiated ***
>;
>TIME
21:32:11 3-MAR-15
>;
>; We will now create any UFDs that must be created on your disk(s).
>; You will not see the UFD commands.
>;
>TIME
21:32:11 3-MAR-15
>;
>;
>; The preparation of the RSX-11M-PLUS kit is now complete. The next
>; time this disk is bootstrapped, this dialog will only be repeated
>; on request. We will now record the successful installation in the
>; log file on the new system disk, and either exit if the installation
>; was done on line, or proceed with the normal startup sequence if the
>; baseline system was used.
>;
>SET /UIC=[2,54]
>PIP LB:[1,1]KITIDENT.DAT/AP=LB:[2,54]INSTALOG.DAT
>;
>;
>SET /UIC=[200,200]
>; PLEASE NOTE
>;
>; If you have not yet read the system release notes, please do so
>; now before attempting to perform a SYSGEN or to utilize the new
>; features of this system.
>;
>;
>; In order to start the SYSGEN process, type:
>;
>; >@SYSGEN
>;
>; When SYSGEN has completed and your generated system is
>; running, you may wish to edit several supplied prototype
>; command and text files to suit your system and application:
>;
>; File Purpose
>; ---- -------
>; [0,0]RSX11.SYS An account/password file
>; This file does contain privileged accounts.
>;
>; [1,2]STARTUP.CMD (This file) Invoked at bootstrap time to
>; control bringing up the system.
>;
>; [1,2]QMGSTART.CMD Invoked by STARTUP to start up the Queue
>; Manager and spooling system.
>;
>; [1,2]SHUTUP.CMD Invoked by SHUTUP when taking down the system
>; to perform system dependent shutdown tasks.
>;
>; [1,2]QMGSTOP.CMD Invoked by SHUTUP to stop the Queue Manager
>; and spooling system.
>;
>; [1,2]LOGIN.TXT Displayed on user's terminal when logging in.
>;
>; [1,2]BATCH.TXT Displayed at the beginning of each batch log
>; file.
>;
>;Z[c
SET -- Inquire cannot determine terminal type
>;
>; Please ignore any random characters that may have printed on your
>; terminal just now. They came from a SET /INQUIRE=TI: command.
>; Evidently your terminal does not recognize escape sequences.
>; This will not affect the running of this command file.
>;
>ELI /LOG/LIM
>CLI /INIT=DCL/CTRLC/DPR="<15><12>/$ /"
>INS LB:[1,1]RMSRESAB.TSK/RON=YES/PAR=GEN
>INS LB:[1,1]RMSLBL.TSK/RON=YES/PAR=GEN
>INS LB:[1,1]RMSLBM.TSK/RON=YES/PAR=GEN
>INS $QMGCLI
>INS $QMGCLI/TASK=...PRI
>INS $QMGCLI/TASK=...SUB
>QUE /START:QMG
>INS $QMGPRT/TASK=PRT.../SLV=NO
>QUE LP0:/CR/NM
>START/ACCOUNTING
>CON ESTAT LP0:
>QUE LP0:/SP/FL:2/LOWER/FO:0
>QUE BAP0:/BATCH
>QUE LP0:/AS:PRINT
>QUE BAP0:/AS:BATCH
>@ <EOF>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20150303/5566dece/attachment-0001.sig>
More information about the Simh
mailing list