--
You received this message because you are subscribed to the Google Groups "PiDP-10" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pidp-10+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pidp-10/e5cb0cd4-68ab-45cb-a9a2-1617752a5aa3n%40googlegroups.com.
I work on reanimating old AIs.
Lars Brinkhoff wrote:
> Have you looked into ELIZA's friend PARRY?
I have, actually. I have all the code (which I got from SAIL DART!) It
is written in MLisp -- a Meta-Lisp written (I think) at SAIL -- and
LAP, a lisp assembler for the Dec10. It would not be difficult to
translate MLisp to CL, and I don't think that the LAP does a lot that
I couldn't replace with CL code. In fact, I was musing recently about
just handing the who task to Claude. But that would be extremely
in-authentic. I'm guessing that since I got it all from SAIL DART, one
of your systems can actually run it directly.

EXPR SUMEXALLOW(); BEGIN NEW FILCHAN,FLAG,STATUS; FILCHAN EVAL<'INPUT,DIAFILEAREA,'QPARRY>; INC(FILCHAN,NIL); STATUS READ(); FLAG READ(); IF STATUS='OK THEN INC(NIL,T) ALSO RETURN FLAG; INC(NIL,NIL); EVAL < 'OUTPUT, DIAFILEAREA, 'QPARRY >; OUTC(T,NIL); PRINT(0); PRINT FLAG; OUTC(NIL,T); % RESET FILE% IF STATUS=0 THEN SLEEP(10) ALSO EXIT() ALSO CAR NIL; RETURN STATUS; END;
There are numerous other <letter>PARRY files; maybe as a hail mary copy on of them into QPARRY.<whatever> and see if it does anything sensible, under the theory that some execution script copies in one of them to QPARRY ebfore running? This seems unlikely since these are all different.
Google also can't find anything called QPARRY that seems related. (There's a collision detection utility called "PARRY", which suddenly gave me a new, and very apt, reading of the name "PARRY"! :-)
Hmmm. QPARRY is a bit of a mystery.
So you made Parry run? Want to share some computational paranoia with us? :-)
I know that IPL-V ran on Dec-10s bcs the SAIL documentation mentions it!