The sound was garbled, but running it through processes to slow it down and clean it up, optimizing for speech, got
something. The fraction-of-a-microsecond sound slowed down into a (garbled) conversation, although it was unclear as to just
who the voices belonged to.
- Code: Select all
...ike?"
"**n't m*** me, I'm just k**ping you from blowing out the psi-dampeners."
"I'm sorry. I didn't think it would b* * ***blem..."
The voices died out there.
The codes structure was unfamiliar, yet not -- not entirely different from how she constructed the campus' security logins, but different enough to throw up error codes. She could see herself creating this data structure, had she started with a different set of instructions.
With a little bit of effort, then, she could un-scramble some of the codes. The code that had triggered the error message was "DAUGHTRY", and was apparently trying to override the lock on a previously running program. There was, of course, no DAUGHTRY in the system, nor had a program been running when the code had been entered. Either would have been enough to pop open an error.