42: Ducky Go Down The Hole

terminal 0

unfinished

// Decoding message from host [unnamed] @ [no translation] \\ For security reasons, I am not [?able?permitted] to access the transport grid within my own datacore. You must therefore enter on foot from this position, locate an appropriate receptical for the artifact you are carrying, and insert it. I will then [?read?load] the command codes from the artifact and attempt to resume defense procedures. Return here when you are finished, and we may discuss further plans regarding the disposal of entity which has caused this. \\ Message ends //

success

// Decoding message from host [unnamed] @ [no translation] \\ I have loaded the command codes from the artifact and am resuming standard defense procedures. Much of the defense network has been damanged beyond use and the remainder is likely insufficient to cope with the numbers of [?enemy] ships and individuals flooding the installation. Nevertheless, all hope is not lost. I have formulated a strategy to destroy the interloper, which identifies itself as "Hathor". I will send you near to the installation's main datacore. For security reasons I cannot transport you directly inside. You must make your way into the main datacore and deactivate the peripheral datastores. This will force the Hathor entity to reorder its [?mind?program] to preserve it's more vital activity.

Eventually it will be forced to discard the key to an inactive circuit. The nonvolatile nature of these circuits will keep the key intact. You may then purge the active memory core, activating the backup circuits. Hathor's child processes will fail with no central host, and the key will reintegrate itself, activating the weapon. It is unfortunate that the crew's only course of action was to fire the installation's primary weapon. With the installation's interior overrun by the [?enemy], it is unlikely that sufficient members of your biological species will survive to reproduce. But our civilization will live on, in mechanized form. \\ Message ends //