Skip to content

Add to NITS.md what to do if DMPCPY moves @ ITS. #2374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
larsbrinkhoff merged 1 commit into from
Dec 22, 2025
Merged

Add to NITS.md what to do if DMPCPY moves @ ITS. #2374

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions doc/NITS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ If you want to connect your machine to a network, this is also where you define
Common options you may want to consider:
- NQS, the number of disk drives.
- IMPP, whether there's an IMP interface.
- IMPUS, the machine's ARPANET host number.
- IMPUS3, the machine's **IP address**.
- NCPP, INETP, CHAOSP, network protocols.

Expand Down Expand Up @@ -109,3 +110,8 @@ If you're in DSKDMP and want to run ITS right away after dumping it, type <code>

## Step 7
When the new ITS has passed testing, rename the old `.; @ ITS` to `.; @ OITS`. Rename the new ITS to `.; @ ITS`.

## Step 8
The DMPCPY crash dump manager is prone to moving files on the `.`
directory to another disk pack. If this happens to the new `@ ITS`,
you can move it back with e.g. `:MOVE .;@ ITS, DSK0:`