Cassie Chin shrugged helplessly. “Tina's in shock. They took her down to the clinic and put her under sedation. Iwato's watching her closely. I think he's pretty worried about her.”
“Damn it. What about Michael?”
“Couple of the riggers volunteered to stay with him. They had to lock down the main bay to keep him from going out in a suit.”
Hedrickson's fingers drummed nervously on the console. “How much do they know?”
“They've figured out Amy's in there somewhere. They know the lights are out and the heat is going, that the AV lines are down and that no one inside is responding to queries through the board.”
The engineer exhaled slowly. “Do they know about the leak?”
“No.” Cassie stared at him. “That I couldn't tell them. Nobody else is up to that either.
They'll find out when the crew goes in. There isn't much hope, is there?”
“I'm afraid not. The rescue specs are working like maniacs, but even if the leak doesn't get any worse, the air in there'll be gone before they can cut the door. Morrie Reuschel was engineer on duty when it happened. We haven't heard from him. If he's that bad hurt, then the girl…” His words trailed off into inaudibility, foundering in despair.
“The only communication we have with the module is via its independent Module Lifesystems Monitor. It says it got wanged pretty good, but you know how much redundancy those suckers have built into them. It took stock of its losses and shifted all necessary functions to undamaged components outside the module. That's the only reason we have some idea of what's going on inside. One boardline survived the damage, so we're still getting reports.”
The woman frowned. “But there's no power to the module.”
“The section there is operating on standard multiple battery backup.”
“I know.” She leaned curiously over the console. “But it shouldn't be. It's designed to render a report and then shut itself down when it loses primary power, to preserve programming and functions. Something else is wrong. Has it requested repair instructions yet?”
“I would imagine.” Hedrickson checked a readout. “Yeah. Right here. Haven't been sent out, though.”
“Why not?”
“Central's dealing with more serious damage elsewhere.”
Chin straightened. “Instead of cycling through shutdown the way it's supposed to, it keeps requesting repair instructions. There's got to be a reason.” She thought furiously.
“Can you override Central from here?”
Hedrickson frowned at her. “I think so, but you'd better have a damn good reason for messing with prescribed damage-control procedure.”
“As a matter of fact, I don't have any reason at all. But it seems as if the Molimon does.
If it's internal diagnostics are functioning well enough to tell you what's wrong, can you send it the necessary instructions on how to fix itself?”
“Just so I'll have something to tell the board of inquiry, why bother?”
“I just told you: it's got to have a reason for not shutting itself down.”
Hedrickson looked dubious. “You'll take the responsibility?”
“I'll take the responsibility. See what you can do, Karl.”
The technician bent to work. Cassie stood staring at the wall. Halfway around the station the darkened, leaking module swung precariously on the end of its connector tube, to all intents and purposes dead along with everything it contained. Except for one semi-independent device, which was disobeying procedure.
Computers do not act on whims, she thought. They respond only according to
programming. Something was affecting the priorities of the Molimon unit that supervised the hydroponics module. But it couldn't proceed without human directives.
Sometimes you just had to have faith in the numbers.
The darkness and gathering chill did not trouble the Molimon. It was immune to all but the most extreme swings of temperature. Reserve power continued to diminish. Still it did not commence shutdown.
Information on how to affect necessary repairs finally began to arrive. Gratefully, the incoming instructions were processed. The problem with the critical downed memory was located and a solution devised. Memory reintegration proceeded smoothly, enabling the Molimon to bypass one of the downed molly drives.
The system component that most concerned the Molimon reported borderline functional.
It sent out the command, to no response. Clearly the trouble was more serious than anyone, including its programmers, had anticipated.
That did not mean that the problem was insoluble. It merely required a moment of careful internal debate. The Molimon's internal voting architecture went to work. One processor opted for procedure as written, even though that had already failed. The second suggested an alternative. Noting the failure of the first, processor three sided with two. Having thus analyzed and debated, it tried anew.