Re: WHO ARE THE REAL MONSTERS?!?!?!??!? MAFIA D2: ONE DEATH??? IMPOSSIBLE
01-30-2013, 07:28 AM
Originally posted on MSPA by Paranoia.
<span style="font-family: system">Initializing Startup Sequence
Loading Core Directive ........ Done
Starting Up User Interface .... Done
Booting Personality Core ...... Done</span>
Password: ******************
Welcome to ParaOS.
Analysis suggests more than One Infected Process on Visceral wagon. Queries to Biological Process Visceral Terminators:
Process Palamedes: Yesterday you implied you were Suspicious of Biological Processes Luniex and Tea. What do your Logic Circuits conclude about them today?
Process Mr_Guy: Apparently suffered a Fatal Error In the Night.
Process Tea: I find your Vote Algorhythms have a anomaly: They will pop up in the middle of a Deletion Protocol unexplained. Query for Process Tea: Apart from Process Cat's Blocked Irregular Theory, do you have other reasons for claiming Process Solaris scans as Infected?
Process Mirdini: What was your Rational for supporting the Deletion Protocol of Process Visceral?
Process Seedy: Do you Still scan Process TehPilot as Infected? Do you scan Process Tea as Infected? What about Process Solaris?
Process Agent1022: In Light of Process TehPilots claims about Process Tea, does your scan of process tea's behavior still return a report of infected?
Process Namboto: Disturbing Affinity for Hooved Biological Creatures aside, you, like Tea, seem to Appear on Deletion Protocols out of thin air. Which processes do you believe are Infected today?
Process konec0: Assuming Process Tea also becomes confirmed Clean, who are your top picks as infected? What if Process Tea is infected?
Further Analysis suggests Process TehPilot requires further scrutiny still. His processor switch only proves a termination order was sent for Tea in the night - not Process Tea's infection status. Find Solaris deletion protocol questionable in face of ignoring visceral Wagon.
Suggested Course of Action: Ascertain Protocol TehPilot's Infection Status.
Deletion Protocol: TehPiLot</span>
<span style="font-family: system">Initializing Startup Sequence
Loading Core Directive ........ Done
Starting Up User Interface .... Done
Booting Personality Core ...... Done</span>
<span style="font-family: Impact">Para0S</span>
<span style="font-family: system">Username: MspafiaPassword: ******************
Welcome to ParaOS.
Analysis suggests more than One Infected Process on Visceral wagon. Queries to Biological Process Visceral Terminators:
Process Palamedes: Yesterday you implied you were Suspicious of Biological Processes Luniex and Tea. What do your Logic Circuits conclude about them today?
Process Mr_Guy: Apparently suffered a Fatal Error In the Night.
Process Tea: I find your Vote Algorhythms have a anomaly: They will pop up in the middle of a Deletion Protocol unexplained. Query for Process Tea: Apart from Process Cat's Blocked Irregular Theory, do you have other reasons for claiming Process Solaris scans as Infected?
Process Mirdini: What was your Rational for supporting the Deletion Protocol of Process Visceral?
Process Seedy: Do you Still scan Process TehPilot as Infected? Do you scan Process Tea as Infected? What about Process Solaris?
Process Agent1022: In Light of Process TehPilots claims about Process Tea, does your scan of process tea's behavior still return a report of infected?
Process Namboto: Disturbing Affinity for Hooved Biological Creatures aside, you, like Tea, seem to Appear on Deletion Protocols out of thin air. Which processes do you believe are Infected today?
Process konec0: Assuming Process Tea also becomes confirmed Clean, who are your top picks as infected? What if Process Tea is infected?
Further Analysis suggests Process TehPilot requires further scrutiny still. His processor switch only proves a termination order was sent for Tea in the night - not Process Tea's infection status. Find Solaris deletion protocol questionable in face of ignoring visceral Wagon.
Suggested Course of Action: Ascertain Protocol TehPilot's Infection Status.
Deletion Protocol: TehPiLot</span>