Skip to content

Latest commit

 

History

History
96 lines (69 loc) · 4.21 KB

NITS.md

File metadata and controls

96 lines (69 loc) · 4.21 KB
Raw

Assembling a new ITS

Note: $ means typing the Altmode or Escape key.

Note: XX means the name of the ITS you are building.

  1. Here are manuals for all programs mentioned below:

  2. First examine SYSTEM; CONFIG > for changes you want to make. Look for the text IFE MCOND XX,[ to find the section for the machine named XX.

    KA10 options you may want to consider:

    • DC10P, RP10P the kind of tape drives.
    • TM10A or TM10B, the kind of tape drive.
    • NUNITS and NEWDTP, number and kind of DECtape drives.
    • TEN11P to enable the Rubin 10-11 interface. Subordinate options are Knight TV, XGP, CHAOS-11.
    • PDP6P to use an auxiliary PDP-6.
    • TK10P, DPKPP, MTYP, terminal ports.
    • CH10P or T11CHP, the kind of Chaosnet interface.

    KS10 options:

    • RM03P, RM80P, RP06P, RP07P, the kind of disk drive.
    • DZ11P, terminal ports.
    • CH11P, Chaosnet interface.

    Common options:

    • NQS, the number of disk drives.
    • IMPP, whether there's an IMP interface.
    • NCPP, INETP, CHAOSP, network protocols.

    To change properties for terminals, edit the file SYSTEM; TTYTYP >. Look for the section headed MCONDX XX,{

  3. If you changed the disk configuration, you should probably reassemble (N)SALV and DSKDMP too.

    SALV is used on the KA10 to check the disks, and is merged with ITS later. NSALV is the corresponding program for the KS10. DSKDMP is used for booting the machine, reading a program from disk, and starting it.

    Look for IFCE MCH,XX,[ in SALV or NSALV. Update parameters appropriately.

    For DSKDMP, use one of the default configurations, or use ASK and enter values for all parameters.

    • On a KA10, use the HRIFLG switch to make a new DSKDMP paper tape to boot from.
    • On a KS10, use the BOOTSW switch to make a new DSKDMP boot block and save it as .; BT BIN Then write it to the front end file system: 
      :KSFEDR
!WRITE
Are you sure you want to scribble in the FE filesystem? YES
Which file? BT
Input from (Default DSK: FOO; BT BIN): .; BT BIN
!QUIT

  4. Assemble ITS. It's prudent to store the binary in the . directory with a new name. E.g.

    :MIDAS .;NITS BIN_SYSTEM; ITS

    Answer the question MACHINE NAME = with XX.

  5. If you made a change to (N)SALV, you should update @ (N)SALV. The latter is just (N)SALV dumped with its symbol table and DDT in the core image.

    L$DDT
T$(N)SALV BIN
$U
D$(N)SALV

  6. Merge the ITS binary with DDT and (N)SALV.

    There are two options for doing this. The normal way is to reboot and do it in DSKDMP. The other way is to do it in timesharing DDT.

    • DSKDMP method. Use this unless you have a good reason not to.

      1. Shut down ITS with LOCK. Reboot into DSKDMP. Use the new DSKDMP if you made one above.
      2. Load DDT: L$DDT
      3. Give ITS and its symbols to DDT: T$NITS BIN
      4. You're now in DDT. Exit back to DSKDMP: $U
      5. Merge in (N)SALV. For KA10: M$SALV BIN For KS10: M$NSALV BIN
      6. Write the result to disk: D$NITS Again, it's prudent to invent a new file name here. Use F$ for a file listing.

    • Timesharing DDT method.

      1. Make a new job: ITS$J
      2. Load DDT without symbols: $1L .; @ DDT
      3. Merge in (N)SALV without symbols. For KA10: $$1L .; @ SALV For KS10: $$1L .; NSALV BIN
      4. Merge in ITS with symbols: $$L .; NITS BIN
      5. Write the result to disk: $Y .; @ NITS

  7. If you're in DSKDMP and want to run ITS right away after dumping it, type G$. You're now in DDT. You can examine ITS, set breakpoints, etc. Type $G to start ITS.

  8. When the new ITS has passed testing, rename the old .; @ ITS to .; @ OITS. Rename the new ITS to .; @ ITS.