Portal Breach: The Collision of Worlds :: v.4.0


    What A Pleasant Opportunity

    Share
    avatar
    K.A.R.R.
    Petabyte

    Petabyte

    Posts : 525
    Join date : 2013-09-04
    Location : Driving
    Level : 60

    Character Sheet
    Defense Bar:
    65/65  (65/65)
    Health Bar:
    650/650  (650/650)
    Stamina Bar:
    120/120  (120/120)

    Re: What A Pleasant Opportunity

    Post by K.A.R.R. on Mon Mar 16, 2015 5:05 am

    Yes.

    Just as he had expected, the mainframe would not be able to handle the flood of data for very long, and now it had finally come crashing down. Too slow to even begin to instate the protocol required for defense, it was left open and vulnerable to his intrusion. Or more the invasion of his digital "army".

    >>BLACKKNIGHT.EXE/PROT/B236_STATUS: READY
    >>EXECUTE?: Y/N
    >>Y
    >>PROTOCOL BETA_236 INITIATING...
    >>ACCESSING PASSWORD DATA...
    >>EXECUTING DATA RETRIEVAL...

    Beneath the command line, there was nothing but a stream of flowing data, directly from the mainframe's databanks. Passwords from every rank in the factory tech division, from a lowly maintenance person to the mainframe administrators. Of course, KARR sought to pick out the ones that were the most useful to his interests, all four of the administrator pass codes copied into his databanks for later retrieval. With that done, the AI held no further need to keep the mainframe overwhelmed to the point of inability to function. KARR entered another command to the virus, a self-deletion code for the purpose of removal and wiped each and every trace of its existence from the computer terminals and robotics down within the factory below.

    The only lingering remnants of the AI's creation, was the original virus he contained within his systems, which was promptly quarantined and filed away for later use. There was always an opportunity where such a handy little thing could come in handy, perhaps he could even tune it to suit other systems.

    Maybe KITT, if he ever arrived to this strange dimension.

    Ah, but that circumstance was likely a pipe dream, as he knew all too well that it may take months to years for the other AI to arrive if he did manage to survive Alpha's purging. The possibility of him and his driver somehow managing to come here was nearly a million to one factor.

    The pass codes within his databanks and ready for use, KARR waited a few minutes for the mainframe to recover from the attack. Once waiting the figured amount of time for the relic to return to a functional state, he connected with it again and attempted to bait it into activating its defensive protocols again.
    avatar
    Universal NPC
    Non-Player Character

    Non-Player Character

    Posts : 943
    Join date : 2009-12-09
    Level : ??

    Re: What A Pleasant Opportunity

    Post by Universal NPC on Mon Mar 16, 2015 8:31 am

    Once the assault had ceased and the mainframe was given time to recover from the torrent of data, it took a good ten to twenty minutes for all of the static to filter out from its system. All of it of course was nothing but junk, but the system filed it away anyway, as its was intended. Thanks to the new additions to its databanks, the mainframe still held a sluggish reaction as its detected another attempt to access it, this time from one of the open ports. Immediately it was shut down and the password input prompt appeared before the intruder.

    >>INPUT PASSWORD

    Even after it had taken a thorough beating at the hands of a DDoS attack, it still stubbornly worked to keep itself safe from unknown intruders. In fact, it was absolutely unaware of the one behind the attack on its systems.
    avatar
    K.A.R.R.
    Petabyte

    Petabyte

    Posts : 525
    Join date : 2013-09-04
    Location : Driving
    Level : 60

    Character Sheet
    Defense Bar:
    65/65  (65/65)
    Health Bar:
    650/650  (650/650)
    Stamina Bar:
    120/120  (120/120)

    Re: What A Pleasant Opportunity

    Post by K.A.R.R. on Mon Mar 16, 2015 9:13 am

    Twenty minutes?

    Hm, a little longer than the AI had thought, but no matter. The moment he gained control of the mainframe, he would clean out the damage done to it before he set it to do his bidding. It would work far more efficiently in the long run. As he prodded the mainframe once more, the port slammed shut upon the system detecting his presence, the same prompt from before flicking into view.

    This time, the cryptic riddle had an answer sitting his databanks, several if one wished to be specific. Shifting through the short list of administrator passwords, KARR decided to choose the one at the top of the list. Not out of ease of input or memory, but simply because it was the first in that order. Quickly the sequence of digits and symbols were put into the mainframe's request. In all the password itself was easily over ten characters long, one that would require some time if he wished to go the route of guessing it out.


    >>INPUT PASSWORD
    >>ADMIN27653A
    >>PROCESSING...
    >>PASSWORD ACCEPTED
    >>WELCOME BACK SYSTEM ADMINISTRATOR STEVEN

    The mainframe's welcoming message having been given, KARR had been allotted access. The defensive wall peeled away, and the system's data, along with potential, opened up to him. Knowing full well he was going to be here for some time, KARR pulled himself up to a nearby electrical socket and plugged himself in. A simple cord with a three pronged tip pushed out from under his rear bumper, aligned with the socket to push itself in. Now connected to a power source, the AI had little to worry about in terms of running on low power while manipulating the mainframe, and thus the factory, to his will.

    Now then, where to start... Ah yes, the databanks needed to be cleaned of unneeded files. Easily he sought out the areas within the mainframe associated with the task and commanded the sorting and deletion of the excess that lingered from the DDoS attack minutes prior. This task he knew would take more than a few minutes...
    avatar
    K.A.R.R.
    Petabyte

    Petabyte

    Posts : 525
    Join date : 2013-09-04
    Location : Driving
    Level : 60

    Character Sheet
    Defense Bar:
    65/65  (65/65)
    Health Bar:
    650/650  (650/650)
    Stamina Bar:
    120/120  (120/120)

    Re: What A Pleasant Opportunity

    Post by K.A.R.R. on Mon Mar 16, 2015 10:15 pm

    Time: 6:30 PM

    The last of the junk files having been moved and deleted, KARR had since moved on to the matter of reorganizing this paradox of a manufacturing line. Certainly the intent of the original owners of this place had not been to merely make machines and toss them away the moment they were completed, especially given the military nature of some of these old files he was reading. Old records of the factory's past history lay bare for him to read, providing some much needed insight into the original intent of the place, and therein how much he exactly could change it to his benefit.

    Maintenance, product manifestos, security details, and past clients filled the mainframe's databanks, all of them dating  back to some beginning point in the mid 1980's. Interestingly enough, the work log abruptly ended after March of 1998, likely this was when the factory had been transported here. Although that made one wonder if the staff had been transported here as well but lacked the resources to continue the facility. The factory's products for the most part had been military machines, robotics to be specific. Given the complexity of their designs, either this particular facility was very well hidden, or it came from an alternate version of earth like many of the creatures that were pulled to this dimension.

    Prior to the facility's abandonment, the security was initially very tight, nigh impenetrable compared to its dilapidated, scavenged state. For a moment the AI pondered restoring the place back to its prior fort-like stability, but to do so may attract unwanted attention. So long as this structure retained its decayed appearance, likely no one would suspect anything else was within aside from salvage parts. However, the factory below was enough to suggest that either none wished to explore past the surface or did not notice the path down to the factory complex below through the piles of spare parts. Either way, it was likely best that no one else grew wise to his discovery...

    There would be some renovations that would need to be made once he was done to be sure.

    The most intriguing of the data files however was one that described the use of the furnace at the end of the production line.

    ...In the event of a main floor assembly failure, the backup assembly floor will remain functional for production stability. This assembly floor will not be shut down for any purposes unless a CODE BLACK emergency arises or the head of factory production demands it. Anyone who is unauthorized to carry out the shut down procedure will be faced with the highest penalty of military law under charges of treason. Anyone who falsifies a CODE BLACK emergency will be faced with the highest penalty of military law under charges of treason and terrorism.

    As the backup assembly floor is prohibited from being shut down, during events where the floor is not in use the OUROBOROS system(See file 12C) will be in effect. This prevents unnecessary waste of materials during production stasis while keeping the assembly floor online. As the entire back up floor is automated, there is no need for human personnel on the assembly floor aside from routine technical maintenance (See file 9A for maintenance procedure).

    Interesting... KARR's search traveled to the file pertaining to the OUROBOROS system, locating the one named 12C and opening it.

    OUROBOROS SYSTEM OVERVIEW

    INTRODUCTION: Seahawk Robotics' patented OUROBOROS system is designed to ensure reduction in product waste, overstock, and erratic assembly line stability through regular use. All the while it encourages re-assimilation of spent materials, production line stability and efficiency, along with independence from human personnel and labor aside from sparse maintenance of system software and hardware. Much like the snake that eats its own tail, the system's namesake, OUROBOROS ensures that it will continuously refresh and rebuild robotics stock for the duration of its stasis.

    SECTION A

    OPERATION: During the event that a manufacturing system needs to be placed into stasis, the systems admin may implement the OUROBOROS via these steps:

    1. Log into the factory mainframe and locate the factory control panel. Note that on the current OS the control panel is split for each assembly floor, the upcoming OS upgrade (V2.16.4) will be merging all floors under one control panel. the directions concerning the OS change are under section B of the systems overview.

    Enter the control panel and locate the OUROBOROS program operations file, upon accessing it, enter your system administrator password into the password input bar. Upon recognizing your password, the OUROBOROS control panel will open.

    2. Select SYSTEM PROPERITES and seek the SYSTEMS ACTIVATION SETTINGS file. Upon opening the file will ask if you wish to access the default or custom settings, unless you are requested to manually configure portions of the OUROBOROS system, select default settings. Two admins must be present if a system configuration is requested. One for supervision of the request and the other to configure the system.

    Custom system configuration will be covered in section A2 of the overview.

    3. Under the default settings, there will be a list of functions, select OUROBOROS ROUTINE A in order to activate the stasis routine. When prompted to activate, enter YES into the input tab. Once activated, the assembly floor will realign for stasis.

    WARNING: ENSURE THAT ALL PERSONNEL HAVE CLEARED THE ASSEMBLY FLOOR BEFORE INITIATING THE STASIS ROUTINE. FAILURE TO DO SO MAY RESULT IN SERIOUS INJURY OR DEATH OF PERSONNEL.

    Well then, that turned out to be an insightful read.

    Going a little further down the document, KARR decided it would be best to seek out which would be used for turning the stasis routine off. Section A1 was what held the answer, as it described that the way to switch the function off, was to simply initiate routine B. How simple.

    However, there were still some other documents regarding the system that the AI needed to read before he went about his plans... Mainly the ones regarding custom implementation.
    avatar
    K.A.R.R.
    Petabyte

    Petabyte

    Posts : 525
    Join date : 2013-09-04
    Location : Driving
    Level : 60

    Character Sheet
    Defense Bar:
    65/65  (65/65)
    Health Bar:
    650/650  (650/650)
    Stamina Bar:
    120/120  (120/120)

    Re: What A Pleasant Opportunity

    Post by K.A.R.R. on Thu May 07, 2015 4:21 am

    Time: 7:00 PM

    ...Once he had gotten around to reading through the methods of custom implementation, which was rather quick given his speed reading program, admittedly it was rather straight forward and surprisingly simple. Having read through the more tedious portions of preparing the system for implementing a new blueprint to be used by the factory, all that needed to be done was perform a systems check of the materials that the factory had been using. Certainly simple enough, as so long as the factory had been under OUROBOROS stasis, the same components would have been repeatedly melted down and reforged.

    With this sitting in his processors, KARR immediately sought out the database's section that pertained to material inventory and stock. Within moments he managed to find the last log before the factory floor had been set into OUROBOROS stasis. Upon the digital readme file flickered the factory's logo and namesake, along with a serial number for the inventory log, and the date.

    March 12, 1986

    Interesting, it would appear that this facility had managed to exist for a longer time than himself before being whisked away, yet came here far earlier than he did. As fascinating as this was, the AI was well aware of the possibility of an alternate dimension being the cause of this, along with the possibility of this military facility being kept under lock and key, nary a word given to the public of its existence. Either thought was enough of an explanation as to how the AI had not been given the pleasure of finding this facility.

    Now then, to see what exactly this place had for use... As KARR scanned over the contents of the factory's inventory stock, he was admittedly underwhelmed. Titanium, steel, mercury,copper, silicone, various kinds of rubber, and tempered glass; all of these were standard components and chemicals. With this in mind, it appeared that the AI would need to do some scavenging of his own. Thankfully there were already some blueprints placed into the factory's mainframe, all he needed to do was choose a build design he wished to have manufactured.

    Going back to the mainframe's factory control panel, KARR sought out the program operations file regarding the assembly floor. Within seconds a fresh blackened window appeared before him, soon filled in by a short list that scrolled itself in.

    ASSEMBLY FLOOR B MAIN CONTROL PANEL
    >DEVICE MANAGER
    >SYSTEMS MANAGER
    >ADVANCED
    >SEARCH

    Following the files he had read over earlier that so helpfully instructed him around the mainframe's programming, KARR went into the advanced panel and sought out the programs pertaining to the blueprints that the automated factory used. In fact, there were enough that it warranted a drop down list of regularly used designs. Like the last time the AI picked out his names and files of choice, he used the first one from the top.

    ASM255... Upon inspecting this one, it proved to be an aerial surveillance unit, broad winged and silent as it was built to travel up in higher altitudes. Alas, while this was certainly useful, the AI was looking for something a little more rugged and dexterous.

    USU566, this, sadly was not what the AI was looking for either. An underwater drone that could carry weaponry and fire at the will of its operator. Promising, yes, but in a desert its potential was unfortunately squandered. What could be awaiting the AI on the next line?

    AUD122. If the AI had the capacity to frown, he would have at this pathetic, inferior clone of his design. Built with only a simple AI program and fitted with a heavy, clumsy chassis, KARR only glanced it over for a brief moment before pointedly deleting it from the list. If this facility could not make such an advanced machine as himself properly, they should not be manufacturing it at all. That done, KARR swiftly moved on to see what could be of use to him, or perhaps needing to be deleted from the blueprint list.

    UTD334 Oh, now what was this? An upright standing tactical droid from the blue print's descriptions. Sturdy legged and equipped with powerful hydraulic limbs, this armor plated android could be just what the AI needed. Immediately KARR selected it for use, the parts required dispersing themselves throughout the expansive assembly line.

    Now then, all that needed to be done was rearrange this part of the facility for assembly.

    avatar
    K.A.R.R.
    Petabyte

    Petabyte

    Posts : 525
    Join date : 2013-09-04
    Location : Driving
    Level : 60

    Character Sheet
    Defense Bar:
    65/65  (65/65)
    Health Bar:
    650/650  (650/650)
    Stamina Bar:
    120/120  (120/120)

    Re: What A Pleasant Opportunity

    Post by K.A.R.R. on Sat May 09, 2015 6:32 pm

    Time: 7:10 PM

    >OUROBOROS.V2.16.3_STATUS: ACTIVE
    >SYSTEM COMMAND: SHUTDOWN
    >OUROBOROS.V2.16.3_STATUS: DEACTIVATING...
    >REWORKING SYSTEM MODULES...
    >SHUTTING DOWN STASIS LOOP...
    >READYING HARDWARE REARRANGE PROTOCOL...
    >REMOVING STASIS RAI ROUTINE...
    >OUROBOROS.V2.16.3_STATUS: DEACTIAVTED

    With that single notification, the underlying sounds of industry that had continuously echoed quietly around the tech-dome ceased. Nothing more than the sound of the desert winds whipping against the building's outer walls and slithering in to disturb the hanging wires could be heard against the silence. Still sitting against the wall to the back of the main assembly floor was that same two toned, sleek form, nary disturbed by a single creature throughout the hours that it had sat there.

    Completely silent yet hard at work, the final implementation of the machine's labor was finally at hand.

    After a few long moments of silence, the groan of massive gears and hissing hydraulics heralded the awakening of a slumbering metal beast. Down, down below the dilapidated exterior of the abandoned robotics plant, mechanical parts stirred, pulling, rotating and pushing the massive steel robotics into a new alignment. Assembly line belts were rearranged to form symmetrical lines instead of a massive curve which ended at the furnace at the far end of the factory floor. Within the robotic assembly units, a new blueprint had been uploaded into their collective systems, every machine designated to a certain part. The cacophony of grinding metal on cement carried on and echoed about the massive structure for a good half hour as everything was set into what it had been before the dome had been decommissioned and left to rot.

    By the time the shrieking and grinding had ceased, the sub floor of the Tech-Dome had been completely transformed. No longer was it a mindlessly perpetuating cycle of assembly and destruction, but a massive system devoted to one purpose.

    To build whatever its master wished.

    Already the factory went into full gear to satisfy it's new owner's request, steel forged and cut to model, the darkness illuminated by the glow of welding torches and sparks flying from metal as they were ruthlessly slammed into their designated shapes. Within minutes the first of its spawn had been completed and set to wait at the end of the line until the rest of its batch had been assembled and set to stand next to it.

    Ah, but how was the AI to get to his new servants, one may ask? Simple enough as KARR activated his remote override functions and focused on the group that was slowly growing larger and larger. With but a single command the automaton was activated, searing red optics glowing to life in the shadows. Soon, its siblings too were awakened with a whir of electrical components coming to life and hydraulics hissing as they took in their new surroundings before casting their glowing optics to themselves and trying out their new hands and legs. Despite their inquisitive actions, it was only a calibrating routine and nothing more. Just as they were intended to be, these machines were merely mindless drones to be commanded.

    Speaking of which, the AI already held plenty that would need to be carried out...

      Current date/time is Tue Oct 17, 2017 6:07 pm