***This is an automated message to all LPI, LN and LSF vessels***
Good day everyone, except for those affected by the strange goings on with my beloved Sentinels.
For those who were involved with the route of one of those Keeper ships, you may have noticed that they have somehow been able to access the Sentinel logic core and upload some sort of communication file. What exactly was the communication, we do not know, but during the logic core corruption the New York communication logs showed the following:
"***Machine***
***Unclean***"
This message is apparently the Sentinel's attempt to decode the message, but from initial repair work, it completely overloaded the primary CPU, memory bank Alpha and all weapon targeting systems. The Sentinel then attempted to reroute to the backup systems that act as its redundant systems.
Sadly during the reroute process, the file managed to manipulate the secondary logic core and the Sentinel then moved to engage a LPI SWAT team member, and a local Xenos bomber. Somewhere in the midst of the skirmish, the Sentinel's primary logic core booted up again and restored its primary directives to normal. The LPI SWAT member then ordered the Sentinel to perform a thorough scan.
During the scan, a file was detected, it is suspected that this is the file the Keeper ships somehow implanted into the Sentinel's core. But when the Sentinel scanned it, it opened it up and the Sentinel lost its communication control, and uploaded the file to Sentinel 201 Alpha.
This is not good at all. Sentinel 101 then proceeded to dock with Norfolk for a full diagnostic.
It doesn't end there however folks, Sentinel 201 Alpha then stormed into the New York system demanding to find its 'brother'. Once 101 was located, 201.A went to dock with Norfolk spouting all about "syncing the files".
We have contained the situation and both ships are undergoing a complete format and installation of backups are ongoing.
We are concerned about this development when the Sentinel's come into contact with Nomad vessels. Therefore we ask that all Liberty police, and military assets order the Sentinels to stay the hell away from the Nomads until we understand what is going on.
I will inform you of what the diagnostic results show us.
I was the SWAT ship that Sentinel 101A tried to engage. There was actually some warning before Sentinel 101A tried to open the file. Once it accessed the file, all outside command protocols were cut off. The Sentinel did minimal damage to me, but that Xeno got quite a display.
After I was able to order the Sentinel to reset and it complied, it reset and shot off. It then rebooted and transferred the file to Sentinel 201A.
Sentinel 201A went looking for it's "Brother" on Baltimore, where it had landed. Quite the bit of weirdness there.
Hope that helps,
Deputy Chief O'Brian
Formerly known as LPI Police Chief Hull O'Brien.
Creator of Sgt. V. Price, 207th Precinct out of Chula Vista Station
Ah, yes yes this complies with our initial reports and communication logs. We apologize for the havoc caused and Sentinel 201.A has been quarantined until further notice. We have also had to halt production of the Sentinel 300 series for the time being.
There is a suspicion that the Navy had some involvement in the cause of the 'corruption'. But this needs further investigation.
Opening Transmission Comm ID: ********51
Name:Chief Matt Myers Location: Fort Bush
Target: Professor Farnsworth
Professor, your program just became a full-blown insurance law suit waiting to happen. Luckily, the Xeno isn't likely to file anything, nor is Deputy Chief O'Brian. However, we're going to have to ask you to move both Sentinels to Springfield Station in Illinois for a more full quarantine for the time being. You will be granted access to all our facilities there, which I assure you, are quite substantial.
Any Nomads would have to fight their way through the McNeil Island, and I highly doubt that's gonna happen.
Until I see evidence that this 'glitch' can be dealt with effectively, I can't risk the safety of my people or, lawsuits forbid, the public.
Good news everyone! It seems that our dedicated team of engineers have managed to identify and remove the file from the Sentinel memory banks. The file will be kept in a completely isolated system for further study in how to eradicate it once it enters a Sentinel, or any of our systems.
The Sentinel 100 series, and the 200 series has rolled back to a day prior to the incident and the memory banks that were affected have been removed and isolated from our networks. We have replaced the Sentinel's with newer memory banks fresh from the laboratories. We also put in the new backup system, and a new communication blocking device to hopefully prevent any nasty files from entering the system and whatnot.
We have also gained new information as to how the Sentinel was corrupted in the first place. The blame lies partially with your damned Liberty Navy pilots. It seemed that when the original 'Keeper file' was implanted into the Sentinel, it was in the process of isolating the file as per protocol. During combat off course.
Then the Navy officer engaged the combat override sequence to get the Sentinel out of the combat area, with this system override, the isolation protocols were also overridden letting the Keeper file infect the primary systems on the Sentinel 101.
While knowledge of this system loophole was known, it wasn't predicted that a Keeper would get so close to the Sentinel's patrol path. What were you imbeciles doing!? That Navy territory out there in the wasteland. Tell those Juneau idiots to get off their asses and defend the gate for goodness sakes!
To summarize, the Sentinel's are repaired, the Keeper file is isolated and we've upgraded their communication systems.
Try not to hit the override switch while in combat with a Keeper again please!! We can't fix it since its hard coded into the prime directives of the Sentinel.