Friday 10th May, 2019

My break-point hack was not needed, and has been removed. A change to the script's statement ordering has fixed the problem. I've now reproduced the entire SYSGEN process from scratch to running $SYSBAT. As I knew that the steps I used manually don't work, due to the "corrupt" distribution kit, I tried a different route. I selected RSX as a default run-time system (RTS), which uses the pre-compiled system programs (CUSPs). This also failed, as the *.CSP files are not on the tape.

This isn't a complete failure though, as:

Both failed sysgen's successfully built the monitor, so I should be able boot into the new SIL.
I now have a set of SCP scripts that allow me to reproduce all, or parts, of the sysgen really quickly.

e.g. to re-run just the sysgen Q&A and build:

set env sv8_diskImage=sysgen_v8_rm03.dsk
 
do Configure1184.do
do AttachSysgenMediaV8.do %sv8_diskImage%
 
do BootDevice.do RP0
do StartSysgen.do
do RunSysbat.do

A tape directory listing shows that the *.CSP files really aren't on the single tape volume that I have. The annoying thing is that I had complete distribution kits, for RSTS/E and BASIC-PLUS-2. I threw them away, 20 years ago, when I relocated to Ireland. Moving my complete set of micro-PDP-11's and peripherals would have been an extra trip in the van, and a rebuild of my garden "workshop". I decided against it.

8^th May 👈 Top of page 👉 19-SEP-2019

Find me coding on GitHub, networking on LinkedIn, answering questions on Stack Exchange and hanging out on twitter.