search

PDP-10 / its

Incompatible Timesharing System
Other
858 stars 81 forks source link

GUNNER dies with .value #2148

Closed eswenson1 closed 1 year ago

eswenson1 commented 1 year ago

The DM GUNNER daemon does a whole bunch of .eval UUOs on startup (or perhaps on one-time startup/purification). Several of the symbols looked up (from ITS) are not found, and the error return of the .eval causes a .value to be executed. You can $P past each of these .value UUOs, and the daemon will eventually come up.

Some of the symbols that it cannot evaluate are: NFSTTY, IMPSTL, NETDUI -- but there are others. I don't see these variables defined in any of the files in the SYSTEM directory. I wonder if they have to do with old NCP networking?

eswenson1 commented 1 year ago

One of the side effects of this is that when you start up COMBAT ZONE, it attempts to launch GUNNER, which will .value. Each time BATCH-COMPIL is run in COMBAT ZONE, it will launch a new GUNNER (which will also .value). I believe the code thinks there isn't a GUNNER running, and thus thinks it needs to start it up each time.

larsbrinkhoff commented 1 year ago

It could be that parts of the Muddle ecosystem expects the particular features of DM ITS to be present. If so, we would have to build an ITS that more closely match those features.

I did find the three symbols you mention above in the ITS source code. NFSTTY is defined in TS3TTY, IMPSTL in IMPOLD, and NETDUI in ITS itself. Yes, the two latter are for NCP networking.

eswenson1 commented 1 year ago

I've managed to get GUNNER to run on ES. I commented out the attempts to evaluate symbols associated with old IMP networking, as well as the code that referenced these. It appears to run ok and does its other functions.

eswenson1 commented 1 year ago

Closing this issue as the latest GUNNER is conditionalized so as not to attempt to .eval symbols that are in the old IMP implementation. It no longer .VALUEs and runs fine.