From BACKUP; @ ITS binary backed up 1972-04-21, ASMDAT = 720414.
MTAPE 107 was reconstructed from MTAPE 112; the version number was
taken from backup tape listings showing 107 was contemporary with ITS
724.
To get the exact binary, it needs to be assembled with MTAPE 107.
Then apply PATCH 724.
From .; @ OOITS binary backed up 1973-06-15, ASMDAT = 721007.
IMP 93 was reconstructed from IMP 99, timestamp XXX.
To get the exact binary, it needs to be assembled with IMP 93, MTAPE
135, ITSUTP 6, MDSK 1, and ITSDIN 4. Then apply PATCH 768.
From .; @ OITS binary backed up 1973-06-15, ASMDAT = 721103.
IMP 95 was reconstructed from IMP 99, timestamp XXX.
To get the exact binary, it needs to be assembled with IMP 95, MTAPE
135, ITSUTP 6, MDSK 1, and ITSDIN 5. Then apply PATCH 771.
From .; @ ITS binary backed up 1973-06-15, ASMDAT = 721127.
MTAPE 135 was reconstructed from MTAPE 136, timestamp 1973-02-24.
IMP 96 was reconstructed from IMP 99, timestamp XXX.
To get the exact binary, it needs to be assembled with IMP 96, MTAPE
135, ITSUTP 6, MDSK 1, and ITSDIN 5. Then apply PATCH 773.
From BACKUP; ITS COPY binary backed up 1973-06-15, ASMDAT = 721222.
ITSDIN 5 was reconstructed from ITSDIN 6, timestamp 1973-02-24.
To get the exact binary, it needs to be assembled with IMP 98 (same as
99?), MTAPE 136, ITSUTP 6, MDSK 1, and ITSDIN 5. Then apply PATCH
776.
From 785 source dated 1973-03-08, and 781 binary backed up 1973-06-14.
To get the exact binary, it needs to be assembled with IMP 99, MTAPE
136, ITSUTP 6, MDSK 1, and ITSDIN 7, then apply PATCH 781.
disk parameters to separate file (system;rp04 >) from system;rh10 >.
Made build default to RP04 when RH10 is specified, but switches
can select RP06 for relevant components. Resolves#1648.
Use 21-bit addressing instead. This an MIT modification of a DF10 to
store three bits of address inverted in the word count.
Also adapted the code for the RP10 case to save two instructions.
Written primarily by David Moon. This is version 195. The PURQIO
Lisp image will only run on machines named AI, ML, MC, or DM; this is
fixed in another commit.
This is the same change as in the new IMP with the comment
;; KLH: "fixed" 11/1/99
Not doing this will e.g. make the FTP server fail because it can't
look up its own IP number in the host table.
An IMP will only allow five outstanding messages to a host without
receiving an RFNM message. The 1985 file SYSTEM; INET 115 had
tracking of RFNM in place. At some point, the old IMP code was saved
as IMPOLD WTHNCP. Later the code in INET was moved to the new IMP
file as the routine IMPCTS, but IMPOLD was not updated.
The problem is that the MP1 loop assumes that the object type in the C
accumulator stays constant. When the ships collide, one is changed to
a fireball, and the other is erased. When the collision with the sun
is detected, the object type in C is still "ship". Getting C fresh
each time at MP2 fixes the bug.
