A series of heavy, metal steps, accompanied by a rain of fragments, heralded the Spiral Enforcer's arrive in its designated docking station. Its motors powered down, and then a long, long pause. The cockpit didn't open, even after five minutes went by. Finally, there was a muffled impact and the hatch creaked outwards, dropping to the ground below. A battered pilot stepped out, climbing onto the gantry to survey the machine with his own two eyes.
A low sigh, and he jumped onto the ladder, sliding down to the ground, tightening his grip to slow his descent only a few feet above the ground. Landing, he started walking to a point unclear, calmly sidestepping as a panel of his machine dropped off, landing where he had been standing mere seconds ago. Plucking his coffee cup from where he had abandoned it mere hours ago, he dumped the last dregs out and pulled a series of levers on the machine Gwen had dubbed the "Iron Coffee Cube", if he recalled correctly. He'd need the coffee. It was going to be a long, long night just to diagnose the Enforcer's issues, let alone repair them.
Coffee in hand, he scampered up the latter, grabbing his laptop from its charging station, and climbing back into the cockpit. After a moment of searching, he set his mug down on a panel next to him. He'd need both hands for this. Keying in his identification, he waited for the familiar whir and hum as the Enforcer came to life, only to be disappointed. The boot sequence began... Only to falter and fail moments after. the screen displaying an error message in place of the familiar display of information.>Boot command failed. Software and/or hardware components compromised. 9,001 errors found. No solutions found. Structural integrity compromised. Motor functions compromised. Higher functions compromised. Immediate evactuion rec0mndd. Sftre nt fond. O$ comro->Operating system not found.
"It's over nine thousand. You have to be kidding me." Alistair scowled, an expression rarely seen on his normally cheerful face. Reaching into a black bag near his feet, he withdrew a long black cord that he subsequently connected to both the console, and his laptop.>Select proper boot location, and press R>RAn instant later, the screen went blank, before powering on again. But before it could progress past the initial start screen, Abraham tapped a button on his keyboard.>Boot cancelled. Exiting to BIOS.
The clean, smooth facade most pilots were familiar with melted away, replaced by a crude blue and white bi-color interface. The controls most pilots would be familiar with, touch screens, buttons, levers, were ineffectual here, no matter how many times they tried to use them. Unbeknownst to most, the machines came with a backup keyboard interface hidden away in their cockpit, but they were crude, and rudimentary. Despite the fact that he knew how to make use of this interface, he preferred slaving the Enforcer's processor and functions to an external advice. It made diagnostics easier, especially when the Enforcer's systems were in such questionable condition.
Maneuvering the highlighted text to the operating systems tab, he frowned. The BIOS didn't even register the Enforcer as having an operating system, let alone one that could be booted from. Setting aside his computer, he clambered out of the cockpit and climbed to the top of his machine, using the damaged portions of armor as handholds. Once atop it, he hooked a parallel bar (Technically it housed and protected several of the power cords, but that was irrelevant) with his foot, and hung down it's back.Ignoring the blood rushing to his head, he unlocked and moved aside the paneling that protected the interior systems, squinting as he stared within. There was the hard drive, nestled within a bank of liquid cooling tubes. The liquid was flowing correctly, which meant that, at the very least, the cooling systems were functioning as they should. The drive was intact, which was... Puzzling. If it wasn't damaged, then the BIOS should register its presence, even if it couldn't boot from it properly. A more thorough examination revealed the cause; the cable that connected to to the rest of the system was burned and melted beyond repair. Without bothering to grab the standard safety gloves, he gripped the cord, and yanked it out, tossing it aside without another glance. Nor did he glance at the engineer who protested loudly when it landed on their head.
Reaching into a compartment next to his head, he withdrew the spare cord, connecting it to the contacts, and nodding in satisfaction when the indicator light glowed green. Flexing his abdomen, he pulled himself to the top of his machine in a single movement, dropping back into the cockpit, and rerunning the BIOS' diagnostic. After a moment, the screen changed to accommodate the re-found device. Not that the outlook was any better. If only thing, it made it worse. The Enforcer had crawled home on a wing and a prayer, and now it was held together by duct tape and good faith. The price for defeating ten Furies, he supposed."Alright you two byte son of a glitching motherboard, let's get you fixed."OOC:Splitting this into two parts to spare you all the pain of crawling through a wall of technically-accurate computer jargon. Now you just have to crawl through two half-walls. If anyone wishes, Alistair is open for interaction. Heck, you can even claim the role of the person hit with a defective cord.