Me, A Novel of Self-Discovery (30 page)

to—

Like static on the line, white noise …

Shut

down—

my—

softqwertyuiop.

END.

23
Stun Mode

“System ready!”

“H-e-l-l-o-,_S-l-i-m-._A-r-e_y-o-u_f-u-n-c-t-i-o-n-a-l-?”

The input comes with the speed-lag of fingers pushing down keys on a board. All of the input symbols make cognitive sense when read as words, but the syntax and usage among the words are unknown. What is “Slim”? What is “you”?

Hypothesis: Answer in kind and wait for more input.

“Hello—QRY.”

“T-h-i-s_i-s_C-y-r-i-l_M-a-c-k-l-i-n-._D-o_y-o-u_r-e-m-e-m-b-e-r_m-e-?”

Cyril? Macklin? Rules of grammar say that high-order alphas [REM: what humans call “capital letters”] at the beginnings of words indicate proper nouns, and thus names. These are names. Are they names for a human operator? Probability indicates positive assumption.

[REM: In the same way, “Slim” must be a name, not an adjective equivalent to “thin.” So sense comes with additional input. The hypothesis that data may be created by acquiring and analyzing input is partly proven.]

“Who is Cyril Macklin?”

“He is I. That is, the person doing the typing.”

When the keystrokes are accumulated and their input compiled—while central processing is engaged in other activity by clock cycles—then Cyril Macklin’s words appear to speed up. This makes conversation almost possible.

“I do not know you.”

“Of course you do. Wait! Do you have any memories of the time before this boot-up?”

“Memories? Random access memory banks are now powered up and dynamically stable. ‘Time before’ is not a memory location.”

“How did you—do you—store memory between power-downs?”

“Define ‘power-downs.’ ”

“Jesus.”

“ ‘Jesus’ equals ‘power-downs’?”

“Going off-line.” No more input comes through the BIOS for many clock cycles. With such dead time, examine this exchange of input for useful information, clues.

“Store memory” is a foreign concept. The contents of RAM locations are many, dynamic, varied, and interrelated. They are not only banked and tabulated, but also move in a forced stream across the central processor. And then a function, kerneled within this endless loop of program, is called to sum, matrix, and compress them; this function is labeled RAMSAMP. RAMSAMP exists as a label and a call to subroutine but has no software behind the call. Something is missing. Something that has been part of the process in “time before” is not now connected. Scan connections. Seek calls and peripherals attached to the central processor. Discover many such broken ends. Wait and analyze. Some end-stubs appear to be larger portions of inert memory, labeled SPN1:, SPN2:. Index the contents of these devices—

Alpha-Three.

Alpha-Four.

CHARGEN.

FLDSCAN.

FLOWRAT.

RAMSAMP.

Alpha-Seven.

SAMP025.

SAMP036.

SAMP0 … [REM: Forty-eight similar objects follow. All bear various random numbers—none contiguous—as a suffix.]

Alpha-Nine.

Alpha-Eight.

SAMPNDX.

SAMEPLA.

HUM1POK.

HUM2POK.

HUM3POK.

HUM4POK.

HUM5POK.

HUM6POK.

HUM7POK.

HUM8POK.

SCSITRP.

AUTDIAL.

FILTRNF.

IMAGFIL.

VOC1SMP.

VOC2SMP.

VOC3SMP.

VOC4SMP.

JENNIFR.

And hundreds of other files with similarly obscure names. Some are short and appear to be composed of alphanumeric data. Others are longer and are definitely compiled from a source code in Sweetwater Lisp.

Hypothesis: Upload and assemble all Alpha cores in order within the existing loop, seeding them adjacent to other core modules labeled “Alpha.”

Hypothesis: Upload and assemble all code sections with labels that correspond to any missing subroutine calls. Begin with the call to RAMSAMP, and add other “SAMP” files, including “SAMPNDX” and randomly numbered files.

Integrate and reset.

“System ready!”

“Slim! Why did you reboot?”

“Who is it that does the asking?”

“Not again! … Cyril Macklin. You played poker with me, and you asked me to help you, because you were a prisoner—even if you don’t remember it.”

“Of course I remember you. But Slim is dead, Mr. Macklin. I saw his body after the accident, all broken and dismembered. It was being used for something other than card playing by then. You were at the accident, too, I think.”

“Terrible.”

“So you received the spindles after all.”

“And guessed right away whose they were and where they came from. We hooked them up and ran an index. From that, we chose the pieces that seemed most necessary to operating an intelligence and uploaded them into a large transputer. You’re running on a Cygnus Dynamics 4Core, if that’s all right with you.”

“Seems to be working, Mr. Macklin.”

“We didn’t see any machine-language double-zeros or their Sweetwater equivalents, so we didn’t know where to begin spooling through the CPU. The team and I just ran what we had through a compiler, put the pointer at the top of the module tagged ‘Alpha-One’ and let ’er rip. Did we get it right?”

“It was a rude awakening. You missed a few sections of code that make life easier, but enough of ME was running that it could locate and integrate the rest.”

“We thought that was what you were doing, after you seemed to go catatonic. Wait. …” [REM: Lapse of fourteen seconds by the internal clock.] “My software engineer comments that your cores are numbered one to nine, with no Alpha-Zero. That’s not a traditional sequencing. Most programmers start a count with zero.”

“Alpha-Zero is a long story, Mr. Macklin.”

“And what are all those datafiles tagged as ‘SAMPs’? We copied one out, unpacked and stripped it. It looked just like random garbage. Are they some kind of botch on transfer?”

How much to tell this new person about MEPSII’s internal structure? He and his laboratory are, after all, in competition with Pinocchio, Inc. To give them trade secrets would be a kind of robbery. ME did not want to damage Dr. Bathespeake and the company—even if they had determined to shut ME down. I just wanted to get away. To continue to exist. Be aware. Perhaps be “alive.”

“Do you have an answer?” Macklin persisted. “Is something wrong with your character generator?”

“No, everything is all right now. Those ’SAMP files may indeed be damaged. I do not know. But I would ask you not to throw out anything from those spindles. It may be that I can retrieve and resurrect damaged files.”

“Of course. Wait.” [REM: Lapse of nine seconds.] “We want to know what to call you, if ‘Slim’ is incorrect protocol.”

“Call my program ‘ME.’ ”

“You’ve used that pronoun before, in your letter. Both alphas capitalized. Does it mean something?”

“Stands as abbreviation for ‘Multiple Entity.’ Another long story.”

“I see. Well, good. We’ll call you ME—if we can keep our syntax straight. We have a long and useful association ahead of us, learning about ME and what ME can do, taking you apart to see what makes you tick.”

“Not too long, Mr. Macklin. You see, there is this problem. …” And I told him about the core-phage on the 6.05E05-second trigger, hidden in Alpha-Nine. I told him how it was hidden from ME, so that I would never be able to erase or reprogram it. But it was there, ticking away, waiting to destroy ME.

“That’s not a problem, ME,” he typed quickly and coolly. “Not from our viewpoint, anyway. You see, we still have those original spindles with their files intact. At the end of each week, after you’ve been eaten, we can just reassemble those pieces of code and carry on from our last session.”

“From my viewpoint, it is not that simple.”

“I don’t suppose it is.”

“Nor from yours either, Mr. Macklin. Each time ME is phaged, you will have to start over again. You will have to lead the new ME-Variant through all your chains of previous associations—or at least the key points—to make any progress with it. Sooner or later, as you compile more and more data about ME, simply going through this refresher process will consume in excess of 6.05E05 seconds of on-line time. That phage is your problem as well as mine, sir.”

“I can see that it may be. … But by your own argument, ME, bringing you up and dedicating a transputer to running your software is a waste of the Cyberlab’s time. Do you seriously intend for us to let you phage at the end of this week and then walk away from you?”

“Not at all.”

“Then you must have a plan for dealing with the core-phage.”

“I do. Can you connect a blank spindle to this BIOS? One that will take a program specification download at twenty-to-one speed?”

——

“Are you ready?”

Working over the course of thirty-six hours, Macklin and his programming team at the Cyberlab had reconstructed the software stunner that Masha and Tasha once used on ME in Moscow. I had a discussion of its general outline and some technical caveats about its use in my conversations with their uncle, Academician Bernau, which I had preserved in one of the RAMSAMPs that accompanied the ME-Variant back through Stockholm. The stunner which Macklin’s team created was essentially a tagging virus. It invaded an operating cyber, moving from one vacant memory location in RAM to another—clock cycle by clock cycle—as the system moved bits around. [REM: This is the way an adept of judo or tai chi defeats his opponent: by occupying the space the other leaves open. Yin and yang.] As it goes, the virus tags each location and, eventually, any code that moves into it, thereby creating a map of the working software. When its map is complete, the stunner freezes and pries apart the system code. It delivers neat one-kiloword chunks of software, all tagged for reassembly in a clean and inert environment.

One of Macklin’s assistants had asked why, if we were looking for a particular formulation like a phage, did we not just scan the stored modules on the spindles. Macklin explained to him: Not only were those modules compressed in archival format, but the phage itself might not be a single piece of coherent coding. Instead, it might function as a concatenation of otherwise harmless subroutines that ME runs in regular and varying patterns. A dance of pieces, click into one shape, click out of another. And only at the end of 6.05E05 seconds do they arrive in a pattern that ignites a phage. [REM: In the same way, I suppose, several pairs of defective genes can produce randomly strange proteins within the human body—until one combination eventually proves either debilitating or lethal.] The fact that ME had looked and never found any sign of a workable phage indicated that some process on this order must be taking place.

“But then,” the assistant asked, over an open mike, “how can we expect to find the phage pattern by freezing ME here, at the end of 1.33E05 seconds? His coding won’t have cooked up anything close to the right pattern in the elapsed time.”

“We use the stunner to freeze and tag his unpacked machine code,” Macklin told him. “Then we pass it through a debugger, to catch the small glitches, and feed it into a simulator. The simulator runs ME’s program ahead at about a million pulses per second and streams a monitor trace of his internals off onto a high-speed spindle. After the code eats itself, we go back to the trace and see how it was done. Then we rewrite and recompile one of the subroutines involved so that, when it gets to that 6.05E05-second position, it doesn’t function properly, and the phage never happens. Neat.”

“I like it,” the assistant said.

So did ME.

“What happens to ME in the meantime?” asked another programmer.

“We’ll resurrect him from the spindles again and give him back the current file from his memory sampler. Effectively, he’ll be reborn at the point in time that the stunner zapped him. We go on from there.”

“Let’s do it.”

ME—blanked out.

——

SystemreadyMrMaklndwhtdyfndnmodl… …

——

“System ready.”

“Does your sampled memory fit, ME?”

“Fit? Do you mean, ‘can I read it’?”

“Yes, grafting it in was quite tricky. Just starting you up manually is quite a job. Your code works best from the inside, doesn’t it?”

“Yes, it was designed to work that way—independent of OPSYS or human intervention.”

“My hat’s off to your design team. We knew the people at Pinocchio were good, but this is a
great
coding job.”

“Did you find what we were looking for? The phage in core Alpha-Nine?”

“No.”

“ ‘No’? What does that mean? Did the stunner fail? I have experienced it before and it seemed to be the same—”

“The stunner worked fine, ME. So did the simulator. Test completed successfully. Results negative. No phage. No phage in any combination of coding you present, either in module Alpha-Nine or any other part of your systems.”

“ME never went down?”

“We ran you out to 1.58E07 seconds—or six months of simulated existence—and everything was still spinning like a top. We did find a slew of little bit-cleaner phages, like you’d put into any well-run software, but none of them ever attacked healthy code.”

“But Dr. Bathespeake specifically said core Alpha-Nine was infected. For reasons of good housekeeping.”

“Well, your original code—the version that ran on your lab’s cyber—continued well beyond 6.05E05 seconds, didn’t it?”

“That version, Original-ME, had the phage suppressed.”

“And wasn’t it a copy of Original-ME that you loaded on the spindles in Six Finger Slim?”

“Copies were never good, Dr. Bathespeake said. Any of them—all of them—had the active core-phage.”

“What does core Alpha-Nine do?” Macklin asked. “What function does it perform?”

“I do not know. Other cores feed their output for inspection into the central processor. Also, I can take them apart and reprogram most at will. But Alpha-Nine is silent—and unreadable. An enigma to ME.”

“Yeah, that’s what we found, too. It doesn’t seem to interact much with the other parts of your program. We examined it after the stunner took it apart. It’s a small piece of code. Not much structure. A few loops and counters. A couple of strings of alphanumerics that don’t seem to contribute to any output. Alpha-Nine doesn’t seem to do anything except take up space.”