Skip to content

Commit 5c22f76

Browse files
committed
Maxc monitor files.
From SUMEX <PUP>
1 parent a972d14 commit 5c22f76

File tree

593 files changed

+386987
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

593 files changed

+386987
-0
lines changed

monitor/1-newos.boot.1

130 KB
Binary file not shown.

monitor/1000-ethgat-mjh.boot.7

33.4 KB
Binary file not shown.
30.1 KB
Binary file not shown.

monitor/1000-sumex-mjh-gateway.boot.1

35.1 KB
Binary file not shown.

monitor/100001-ppong.boot.2

130 KB
Binary file not shown.
30.1 KB
Binary file not shown.

monitor/1001-test-gateway.boot.1

34.7 KB
Binary file not shown.
29.3 KB
Binary file not shown.

monitor/1007-ethgat-mjh-16k.boot.1

29.7 KB
Binary file not shown.

monitor/1010-clock.boot.1

60.5 KB
Binary file not shown.

monitor/11-dump.protocol.1

+34
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
First start the memdump on the 11 using the sense switches as directed.
2+
Be sure to put the BOOT FILE NUMBER of the program you want booted
3+
in ssw before depressing start. An auto boot over the Net is done at
4+
the completion of the dump.
5+
6+
NOW USING 2 jobs: (both must be enabled!)
7+
1. Use <schoen>puptst: (The "a" command allows you to build
8+
an arbitrary PUP-caution typing RETURN will send the
9+
PUP so don't do that until you are ready. ">" will move
10+
the cursor to the next PUP field. If you haven't done
11+
this before, practice before actually trying it for real)
12+
13+
BUILD an arbitrary PUP of PUPTYPE 205 to 55#111#23 with
14+
i. ID1 = 152357 (The pass word)
15+
ii. ID2 = socket 0 of EFTP receive server
16+
iii. DEST. Socket 0= Net,,Host of EFTP receive server
17+
iv. DEST. Socket 1= socket 1 of EFTP receive server
18+
19+
2*. Start Eftp receive on host 55#111#23 - enable yourself
20+
and force the use of socket 20.
21+
3. Now send the PUP you just BUILT by typing RETURN.
22+
4. If the PUP was built correctly the EFTP should begin. You can
23+
tell if it has by watching the console TTY on the 11 being
24+
dumped or running etherwatch on an ALTO-like machine.
25+
In the former case, and ! is typed for each 1K words that
26+
are dumped.
27+
28+
* When using the PDP10 for the EFTP you will set up (a) as follows:
29+
(i) (ID1) 152357
30+
(ii) (ID2) you place 0
31+
(iii) (dest Sock 0) you place 026523, ie, 55,,123 in 8 bit bytes
32+
(iv) (dest Sock 1) you place 20
33+
34+
--WJY March 23, 1982

monitor/11-gateway-iprouting.map.5

5.59 KB
Binary file not shown.

monitor/11-gateway-iprouting.map.6

5.72 KB
Binary file not shown.

monitor/11-gateway-old.map.1

5.22 KB
Binary file not shown.

monitor/11-gateway.tools.1

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
If you need to BOOT the gateway do the following:
2+
1. Take the key which is on the right side of the processor on
3+
the cardboard box, and unlock the cpu.
4+
2. Halt the cpu.
5+
3. Load the address 166244 (double check this. This address is also
6+
listed on the front of the CPU).
7+
4. Then put 1100 in the sense switches and press start. You can
8+
watch it boot on the heath. $ means we sent a packet. ! means
9+
we received an EFTP data, T means timeout, and R means retransmitted
10+
the last EFTP ack. Usually you see something like
11+
$!$!$TT$R$!$!$!$!....etc If too many TTTTTs happen then you
12+
may have to restart everything.
13+
5. LEAVE 1100 in the sense switches. If the gateway crashes it
14+
does an auto reboot. 1100 is the number of the file on the 2020
15+
which is booted. If for some reason the 2020 is down, use 1000
16+
instead which is the same boot file on the 10.
17+
6. CAUTION: Don't try and boot the gateway when the 10 is loaded
18+
or the 2020 is running CLASS 0. The EFTP sends on these systems
19+
sometime hang in these situations.
20+
7. LOCK the CPU and put the key back where you found it.
21+
8. By setting bit 15 while the gateway is running, you can
22+
get status reports on the Heath every 13 seconds.
23+
DO NOT leave bit 15 set if you are not intending to
24+
watch these reports. It slows down the throughput
25+
considerably to output these, and there are only
26+
for brief diagnostics...
27+
28+
If you need to restart the gateway. Do 1 and 2 above. Load 1100 and
29+
just start. That is why 1100 is used for the most frequently booted
30+
file, since it is easy to forget to change the boot file number to
31+
the start address number when restarting in a HURRY. So I just use
32+
1100 for everything, but NOT for the same file on different systems.
33+
I have never booted from the 10 since I could boot from the 2020,
34+
since the 2020 is much faster and usually less loaded. The boot
35+
should take about 30 seconds.
36+
37+
If we should have hardware problems with the gateway, then the following
38+
diagnostics reside on <pup>:
39+
1. xdboard0.lda This tests the 160000 addressed board.
40+
It can test the other board by just changing
41+
its address and placing it in the correct
42+
slot on the backplane, ie, where the 160000
43+
board resides.
44+
2. xdecho.lda This is an echo server.
45+
46+
These can only be loaded via a tty line and Nick knows how to do this.
47+
If there are CPU or memory problems, Nick and Bud know of the pdp11
48+
diagnostics on the <pdp11> directory.
49+
50+
Bill

0 commit comments

Comments
 (0)