We will all go together when we go [Closed to bomb teams]

Aug 24, 2010 22:42

There were 8 bombs spread around the ship. The teams were assigned. They had their orders, now they had to carry them out. And pray to whatever they held dear that they could disarm them in time.

Tick tock.

ben skywalker, lash, dustin silver, cowabunga, ratchet_idw, seeley booth, tenaya, angie spica, celena vantari, !plot: the mole, tenth doctor, renne, starfire, lowe guele, stature, jacob keyes, jake berenson, beastboy, lord zetta, axl

Leave a comment

quark_assassin September 13 2010, 20:53:39 UTC
Yes, how unfortunate for Alex that he no longer had to worry about counteracting potential system barriers via port insertion and modified drive readers, nor did he have the luxury of modifying, even creating entire chunks of code specifically for running a program through all the possible insertion points at Dustin's discretion, who had oh so horribly decided that a direct connection with his phone serving as intermediary, which would read and translate anything thrown though it either automatically or via on-the-spot proofreading, was the more efficient way to go due to time constraints and the simple concern of not being preoccupied with conflicting software and keeping on task.

In the meanwhile, Dustin ignored Alex and continued to work.

The wires themselves were proving less of a problem than might be expected of such an endeavor--they were easy enough to retrieve with the aforementioned pair of needle-nose pliers and a LED flashlight--figuring out which ones were required, however, and identifying all of the bizarre machinery within, took a different sort of finesse. Dustin, of course, rose to the challenge just about as casually as taking a stroll on a sunny day, first tracing back the wires, the thinner prosthetic half-buried inside the rigged console, finding some parts that were familiar and others that were completely alien (as would be expected); then he delicately embraced the electronic board in question and pressed his ear to the metal bones of his false arm.

Different programs have a unique electrical signal created through the streaming of data between cables and chips and the like, in turn creating an identifiable, if not very difficult to pick up (let alone immediately discern), audible vibration, a sort of resonance that sensitive equipment can identify and categorize. Technopaths, as studied in a past life, are physical manifestations of these devices, wherein they not only detect these signals but can also create their own. Dustin found that he was capable only of the former; the chemistry of his brain, with the Element running over its surfaces, rushing around his skull and spine in a bizarre mix of conductive proteins and spinal fluid, transferred these signals into physical waves that, in the right situations and places, had the capacity to completely consume him.

For such a complex process it was surprisingly brief, and it thus only took a few minutes for Dustin to know exactly what was inside this terminal, how it worked, what data was going where, and how he could safely intercept said data without blowing this dysfunctional collective to tiny bits. The wires in question were rerouted, cleanly cut, and extended soon after.

"That won't be necessary." With practiced ease he sorted each cable and fed them into his moble's various feeds, which devoured the ends greedily in a conductive feast but kept the lines dead until further notice. Dustin would not risk sending what code Alex had created before reading it over first, and especially not before he'd finished what he'd started.

"Ready when you are."

Reply

hack_rat September 14 2010, 21:01:19 UTC
Alex would have gladly thanked Dustin, though Dustin failed to explain any of that to him, and so he was left in the dark.

It seemed that both were terribly incompetent at communication, which, while functional, made for a rather poor group. At least each were sufficiently competent at their own tasks.

Alex's humming faded as he began reading through his code for errors. Having found none after three checks, he nodded, "done." He hadn't actually heard Dustin say 'Ready when you are,' having at that point been running the code and it's reactions through his mind, but it worked out that he finished only moments after Dustin had.

Reply


Leave a comment

Up