So,

Expect will be immensely complicated; lots of the patches and layered projects don't quite install in a predictable manner.

The base isn't likely to change enough to justify the effort, either.

I am likely going to keep a binary base, and provide utilities to customize the image:

• Expect script interacting with REACT for password changing
• Expect script interacting with MONGEN for configuring DECnet address
• Expect script interacting with the eventual TCP/IP script config

Please suggest other things that might want to be customized by the end user.

You've got lots of unusual bits that could be included.

• Clear CompuServe TOPS-10 REing stuff for distribution if possible
• Add the extant TCP/IP stacks (clear redistrib permissions first!) (oh god there are multiple!)
• Add compilers (KCC, DEC layered products)
• Combine documentation from various places
• Try to get a dynamic disk geometry driver

basically put a lot of the "junk" zpool in one place where people can see it

Hi,

With TSU disk added, does this contain Cobol, Fortran, Algol, APSLF, BLISS compilers?

This disk image runs fine in klh10. It's a smooth running Tops 7.04 image with SOS and BASIC.
I noticed it's the same twonky file system that was included with the original klh10 2.0A release back in 2001, except
for the addition of the TSU disk which is specified in the pdp10.ini as:
devdef dsk0 rh0.0 rp type=rp06 sn=1024 format=dbd9 path=disks/T10-RP06.0-dbd9
devdef dsk1 rh0.1 rp type=rp06 sn=1026 format=dbd9 path=disks/T10-RP06.1-dbd9
devdef dsk2 rh0.2 rp type=rp06 sn=1028 format=dbd9 path=disks/tsu

So with the addition of thatl tsu disk, I had the hope that it might contain the Cobol, Fortran, Algol, APSLF, BLISS compilers.

I see them listed in dir SYS:, but when trying to run them they don't run.

Could there be any commands needed to add what is in the tsu disk to the search list or some other way to make the compilers work
that I am not seeing?

Thanks,
Bill