github.com/PDP-10.its
1
0
Fork 0
mirror of https://github.com/PDP-10/its.git synced 2026-01-25 19:56:53 +00:00
Code Issues Releases Wiki Activity

Updated info;tips > to include information on how to add an additional disk to ITS.

Browse Source
This commit is contained in:
Eric Swenson
2020-12-31 21:32:04 +00:00
parent 71bc19c1a2
commit 6eaacb8e7f
1 changed files with 226 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

227
doc/info/tips.1 → doc/info/tips.2
View File

@@ -12,6 +12,7 @@ to other documentation.
* DSKDMP:: Some useful hints about using DSKDMP
* Debugging JOB Devices:: Instructions on how to debug JOB devices
* Assembling a new ITS:: Instructions on assembling a new ITS
* Adding an additional disk:: Instructions on adding an additional disk to ITS

File: TIPS, Node: DSKDMP, Previous: TOP, Up: TOP, Next: Debugging JOB Devices
@@ -93,6 +94,7 @@ stopped at the breakpoint.
$1B; GO+4>>.CALL 3316 (RFNAME)
You are now free to debug the BDH to your heart's content.

File: TIPS, Node: Creating a Bootable ITS Image, Up: TOP
@@ -139,8 +141,9 @@ that starting address.
The second sequence loads the image from the file system (".;@ ITS") and then
starts it at the image's starting address.

File: TIPS, Node: Assembling a new ITS, Up: TOP
File: TIPS, Node: Assembling a new ITS, Up: TOP, Next: Adding an additional disk
Note: In the following description XX refers to the two-character ITS machine name
you are building -- for example DB.
@@ -239,3 +242,225 @@ You're now in DDT and you can examine ITS, set breakpoints, etc. Type $g to star
6. When the new ITS has passed testing, rename the old .; @ ITS to .; @ OITS. Rename the
new ITS to .; @ ITS.

File: TIPS, Node: Adding an additional disk, Next: Build new version of SALV or NSALV, Up: TOP
* Menu:
* Build new version of SALV or NSALV::
* Build new version of ITS::
* Build new version of DSKDMP (optional)::
* Shut down ITS::
* Update emulator configuration for new disks::
* Boot SALV or NSALV::
* Format new disk pack::
* Copy user directories from first disk to new disk(s)::
* Create new bootable ITS::
* Boot new ITS::

File: TIPS, Node: Build new version of SALV or NSALV, Up: Adding an additional disk, Next: Build new version of ITS
1. Edit the file KSHACK;NSALV > or SYSTEM;SALV >.
2. Update NDRIVE to specify the total number of drives desired.
For RP06 and RP07 drives, the number of drives equals the number of packs.
For a 1-pack system (default), NDRIVE==1. If you are adding a second drive, change this to NDRIVE==2.
3. Update NUNITS to specify the total number of pasks desired.
For RP06 and RP07 drives, the number of drives equals the number of packs.
For a 1-pack system (default), NUNITS==1. If you are adding a second pack, change this to NUNITS==2.
4. Update LASTPK to specify the 0-based number of the last pack
For a 1-pack system (default), LASTPK==0. If you are adding a second disk/pack, change this to LASTPK==1.
5. Back up active version of NSALV or SALV:
a. For NSALV:
:RENAME .;nsalv bin,nsalv obin
b. For SALV:
:RENAME .;salv bin,salv obin
5. Assemble a new NSALV or SALV:
a. For NSALV:
:MIDAS dsk0:.;_kshack;nsalv
b. For SALV:
:MIDAS dsk0:.;_system;salv

File: TIPS, Node: Build new version of ITS, Previous: Build new version of SALV or NSALV, Up: Adding an additional disk, Next: Build new version of DSKDMP (optional)
1. Edit the file SYSTEM; CONFIG >.
2. Update the value of NQS to reflect number of packs.
For a 1-pack system (default), NQS==1. If you are adding a second pack, change this to NQS==2.
3. Back up active ITS binary:
:RENAME .;its bin,oits bin
4. Assemble a new ITS:
:MIDAS dsk0:.;_system;its

File: TIPS, Node: Build new version of DSKDMP (optional), Previous: Build new version of ITS, Up: Adding an additional disk, Next: Shut down ITS
This step is optional, however recommended. It is quite possible that you may need to perform operations
from DSKDMP on the new drive. Your existing DSKDMP may only know about your current number of drives,
and therefore not be able to manipulate your new drive. If this is the case you should update DSKDMP
to know about the new drive and reassble it.
1. Edit the file SYSTEM; DSKDMP >.
2. Make sure that the value of NDSK is equal or greater than the total number of disks you have defined in ITS.
3. Back up active DSKDMP binary:
:RENAME .;dskdmp bin,dskdmp obin
3. Reassemble DSKDMP:
:MIDAS DSK0:.;_SYSTEM;DSKDMP

File: TIPS, Node: Shut down ITS, Previous: Build new version of DSKDMP (optional), Up: Adding an additional disk, Next: Update emulator configuration for new disks
1. Logout all users except on system console.
2. On system console, invoke LOCK to shut the system down
LOCK^K
5DOWN
y
^C
3. Wait until ITS has shut down.

File: TIPS, Node: Update emulator configuration for new disks, Previous: Shut down ITS, Up: Adding an additional disk, Next: Boot SALV or NSALV
This procedure is different for the various emulators used to boot ITS. For KLH10, update the dskdmp.ini file to
add a new line similar to this one:
devdef dskN rh0.N rp type=rp06 format=dbd9 path=rpN.dsk iodly=0
where the value N is replaced with the the disk number. For example, the default system contains a single line like this:
devdef dsk0 rh0.0 rp type=rp06 format=dbd9 path=rp0.dsk iodly=0
If you are adding a single new disk, the resulting lines should look like this:
devdef dsk0 rh0.0 rp type=rp06 format=dbd9 path=rp0.dsk iodly=0
devdef dsk1 rh0.1 rp type=rp06 format=dbd9 path=rp1.dsk iodly=0

File: TIPS, Node: Boot SALV or NSALV, Previous: Update emulator configuration for new disks, Up: Adding an additional disk, Next: Format new disk pack
1. Boot the old (or new) version of DSKDMP.
2. Invoke NSALV or SALV.
a. For NSALV:
l$ddt
t$nsalv bin
b. For SALV:
l$ddt
t$salv bin

File: TIPS, Node: Format new disk pack, Previous: Boot SALV or NSALV, Up: Adding an additional disk, Next: Copy user directories from first disk to new disk(s)
1. Make sure you are in DDT with NSALV or SALV loaded.
2. Format the new pack:
MARK$SG
Format pack on unit #1
Are you sure you want to format pack on drive # 1 (Y or N) y
Pack no ?1
Pack 1., Drive #1 is serial #2.
Begin formatting 815. cylinders....Hardware formatting complete.
Verify pack? (Y or N) n
Swapping Alloc? 3000
Pack #1. ID?DISK2
DDT
3. Check the drive:
CHKR$G
Salvager 262
Active unit numbers? 01
Unit #1. ID is DISK2, Pack #1 (hardware says 0.)
Unit #0. ID is FOOBAR, Pack #0 (hardware says 58562.)
Use MFD from unit: 0
Directories out of phase.
Unit #0, Pack 0. Ascending dir number is 212
Unit #1, Pack 1. Ascending dir number is 0
Verify that the proper packs are mounted.
If you aren't sure, get help. If they are proper,
and one is just coming on-line after being off for
a while, you will have to UCOP to it.
Read all blocks of all files? (Y or N)
Get user dirs from unit: 0
Write out changes in MFD (y or N) y
DDT

File: TIPS, Node: Copy user directories from first disk to new disk(s), Previous: Format new disk pack, Up: Adding an additional disk, Next: Create new bootable ITS
Make sure are in DDT with NSALV or SALV loaded in memory.
Copy user directories from unit 0 to unit 1.
UCOP$G
Copy directories
From unit #0
only unit #1
Copy from unit #0 onto unit #1, OK (Y or N) y
Note that no DDT prompt is provided at the end of UCOP. Just wait about 10 seconds. You can tell if you are back to DDT
by typing a DDT command. For example:
0/
That should display the contents of location 0.

File: TIPS, Node: Create new bootable ITS, Previous: Copy user directories from first disk to new disk(s), Up: Adding an additional disk
1. Make sure you are in DSKDMP. If you are at DDT, type:
$U
2. Load DDT and ITS into memory:
l$ddt
t$its bin
3. Reenter DSKDMP.
$U
4. Merge in NSALV or SALV
a. For NSALV:
m$nsalv bin
b. For SALV:
m$salv bin
5. Dump out its
d$nits
6. Start ITS
g$
7. If ITS doesn't start, reenter DSKDMP:
$U
8. And load and start the new ITS:
nits
$g

File: TIPS, Node: Boot new ITS, Previous: Create new bootable ITS, Up: Adding an additional disk
1. Make sure you are in DSKDMP. If you are at DDT, type:
$U
2. Load and run ITS.
nits