A Crash

    Kevin typed into the console querying an overload procedure. Maybe there was an electrical pulse he could send through the system that would take out the Conglomeration - oh, look, there was the proper noun - and hopefully not fry the ability to send his information. That sounded farfetched as he thought it. Maybe there were explosives...       He looked around the room he was in for at least the fourth time - nothing explosive in here - and then scanned the room behind the glass. There weren't any of the red barrels in the room that signified something that would explode in fire. The hard drives could explode electrically he supposed, but he wasn't sure that he wouldn't destroy what he needed. Looking up... oh, okay, a catwalk. He could maybe drop that down onto the Conglomeration's... Well head didn't seem like the right word, but it was the closest.     Who designed this place?     Okay, so catwalks were usually bolted to somethin...

    Kevin inserted the drive into an open port in the console in front of him, ignoring the horrible sight of the conglomeration eating his friend, trying not to think of exactly what it was. Was it the final form of the fungal freaks he had been fighting? Was it their patron? Their god? Didn't he just  say he wasn't going to fixate on it? Why wasn't the drive connecting?     He tapped the console and the screen - which had been a cheery, compliant blue-green - shifted suddenly to a blazing red. The type of red that exclaimed "YOU FUCKED UP!" while physically saying something calm like: "There has been an unexpected error. Please attempt to blah blah blah. "      Learning about himself some more, that was nice. He evidently had little patience for computers. That was progress.     The "important text" indicated by the aforementioned "blah blah blah" in this case was "Please contact a system administrator for bypass through the ma...