From AGRE at AI.AI.MIT.EDU Fri Sep 30 20:39:01 1988 From: AGRE at AI.AI.MIT.EDU (Philip E. Agre) Date: Sep 30 88 15:39:01 EDT Subject: No subject Message-ID: <453833.880930.AGRE@AI.AI.MIT.EDU> Hi -- AI randomly drops my terminal connection a couple dozen times a day. In doing so it sometimes detaches me and sometimes flushes me altogether. Am I doing something to bring this on myself? If not it would be great if it stopped happening. From ROLL at AI.AI.MIT.EDU Fri Sep 16 06:16:04 1988 From: ROLL at AI.AI.MIT.EDU (Peter Lothberg) Date: Sep 16 88 00:16:04 EDT Subject: The "crack team", is dissasembling MX, for it's trip to Sweden Message-ID: <444460.880916.ROLL@AI.AI.MIT.EDU> The crack team has begun to work; A lot of the documentation for MX (KL-10) must be spread out, i can't find it around the machine. So all of you that has bits and pices, bring it to the 9:th floor before sunday, please. (As the system will not fill the container more than 40% or so, we vold like donations of other stuff, like Lisp-machines, AAA terminals, a IMP, Conection machines, retired 2060's etc, (I'm not joking...)) -Peter From DEVON at AI.AI.MIT.EDU Mon Sep 12 05:57:48 1988 From: DEVON at AI.AI.MIT.EDU (Devon Sean McCullough) Date: Sep 11 88 23:57:48 EDT Subject: supdup Message-ID: <441324.880911.DEVON@AI.AI.MIT.EDU> Date: Sep 11 88 09:39:59 EDT From: David C. Plummer To: DEVON at AI.AI.MIT.EDU Re: supdup Date: Sun, 4 Sep 88 12:41:31 EDT From: Devon Sean McCullough Subject: supdup To: DCP at AI.AI.MIT.EDU Message-ID: <437397.880904.DEVON at AI.AI.MIT.EDU> Many supdup servers around MIT emit %TDBS, which is not in any RFC I've ever seen, and breaks some user end supdups, such as ITS CRTSTY. Do you know if anyone has defined a new improved supdup that does allow %TDBS, and perhaps a few other useful things as well? I've been away from this kind of stuff for a LONG time. I'd suggest asking bug-ITS. From CENT at AI.AI.MIT.EDU Sat Sep 10 04:56:21 1988 From: CENT at AI.AI.MIT.EDU (Pandora B. Berman) Date: Fri, 9 Sep 88 22:56:21 EDT Subject: return of MD Message-ID: <440558.880909.CENT@AI.AI.MIT.EDU> i plugged MD back into the *MSG and INQUPD routines. From CENT at AI.AI.MIT.EDU Fri Sep 9 23:19:49 1988 From: CENT at AI.AI.MIT.EDU (Pandora B. Berman) Date: Fri, 9 Sep 88 17:19:49 EDT Subject: The end of the world as we used to know it Message-ID: <440394.880909.CENT@AI.AI.MIT.EDU> Date: 9 Sep 1988 1033-EDT From: BRAITHWAITE at TOPS20.DEC.COM To: Rob Austein Subject: Re: [Pandora B. Berman: The end of the world as we used to know it] ReSent-Date: Fri 9 Sep 88 10:40:40-EDT ReSent-From: Rob Austein ReSent-To: CENT at XX.LCS.MIT.EDU for our records --- what is MX's serial number ? -------- model PDP-1080 (or KL-10A), serial #1038 From CENT at AI.AI.MIT.EDU Fri Sep 9 03:39:25 1988 From: CENT at AI.AI.MIT.EDU (Pandora B. Berman) Date: Thu, 8 Sep 88 21:39:25 EDT Subject: The end of the world as we used to know it Message-ID: <439827.880908.CENT@AI.AI.MIT.EDU> "The time has come," said LCS, "MX at last must go. Its day has gone. We need that space Most urgently." And so Before we crate it, let us give A final cheerio. Once there was a KL-10 called MIT-MC which belonged to the Macsyma Consortium. It provided Macsyma, the symbolic algebra system, to researchers all over the world, and mail gatewaying and mailing list support to a large fraction of the Arpanet. Things continued in this fashion from 1975 to 1983. When the Macsyma Consortium dissolved in 1983, MC turned to providing cycles for MIT's Laboratory for Computer Science, and continued supporting much of the Arpanet's mail service. But the machine itself was growing old and cranky. In 1986, the mail services were moved to a smaller, more maintainable machine (a KS-10), and the name "MC" was moved with them. But the KL-10 continued to run under the new name "MX". Now the end has come. MX was down cold for several months, and has only been revived recently to copy some old 7-track tapes. LCS can't keep MX any longer -- it needs the space for other purposes. So the KL is being sent to the Home for Aged But Beloved PDP-10s; a crack team of hardware hackers will arrive next week to dismantle it and take it back with them to Sweden. In celebration of this momentous event, we are holding a small farewell gathering: Friday, 16 September 1988 16:00 NE43-8th floor playroom (545 Technology Square, Cambridge, MA) Reservations are strenuously requested (though not strictly necessary) -- we need a head count so we can figure out how many trays of institutional brownies to order. Send yours to: CENT at AI.AI.MIT.EDU Offers of refreshement are also very welcome -- do you think we have any budget for this kind of thing? Send all such offers also to CENT as above. From Moon at STONY-BROOK.SCRC.Symbolics.COM Wed Sep 7 03:12:00 1988 From: Moon at STONY-BROOK.SCRC.Symbolics.COM (David A. Moon) Date: Sep 6 88 21:12 EDT Subject: mc par errs In-Reply-To: <437950.880906.CENT@AI.AI.MIT.EDU> Message-ID: <19880907011222.0.MOON@EUPHRATES.SCRC.Symbolics.COM> Date: Tue, 6 Sep 88 06:50:56 EDT From: "Pandora B. Berman" the sysconsole died mysteriously this evening. it was in the middle of printing a msg to my DUMP about loading a tape and then saying ok, when all of a sudden it said ?rivPARITY and the console was talking to KLDCP. the easy way out was to reattach that hactrn to the vt52, so i took it. but when that tape was done and i tried to boot the system to regain access to the sysconsole, it died twice during the reboot process, at different places, each time with the blank but ominous msg: PARITY. the mem bays didn't indicate par errs, but i tried resetting them anyway. each time, after resetting bay D a couple times, its par err light would come on. after resetting more, the light would disappear, sometimes return, and then go away again. it did eventually cooperate and let the machine come up, but this was very odd.. These sound like parity errors in the front-end pdp-11's memory [I hope someone isn't going to tell me that that pdp-11 doesn't have parity on its memory and I've just made a fool of myself.] From CENT at AI.AI.MIT.EDU Tue Sep 6 12:50:56 1988 From: CENT at AI.AI.MIT.EDU (Pandora B. Berman) Date: Tue, 6 Sep 88 06:50:56 EDT Subject: mc par errs Message-ID: <437950.880906.CENT@AI.AI.MIT.EDU> the sysconsole died mysteriously this evening. it was in the middle of printing a msg to my DUMP about loading a tape and then saying ok, when all of a sudden it said ?rivPARITY and the console was talking to KLDCP. the easy way out was to reattach that hactrn to the vt52, so i took it. but when that tape was done and i tried to boot the system to regain access to the sysconsole, it died twice during the reboot process, at different places, each time with the blank but ominous msg: PARITY. the mem bays didn't indicate par errs, but i tried resetting them anyway. each time, after resetting bay D a couple times, its par err light would come on. after resetting more, the light would disappear, sometimes return, and then go away again. it did eventually cooperate and let the machine come up, but this was very odd.