Computer damage?
- Thread starter kirkfan
- Start date
If Seska was worth her salt, which most of the time she wasn't, Voyager's internal sensors would think that she was invisible because of trojans she left in the system before she left.
Although, weren't the other Kazon ships (who captured Voyager) running along side Voyager? Seska could have been over there for some reason.
Although, weren't the other Kazon ships (who captured Voyager) running along side Voyager? Seska could have been over there for some reason.
I used to love Voyager but this new information you have brought to my attention changes everything. Frankly it sickens me
I'm not watching this deceitful crap ever again
She had literally just left sickbay (having discovered Chakotay was not the father of her child) then seconds later the doctor asks the question
I think Kirkfan has Voyager by the Jaffas and deserves a prize. We should award them weekly
I'm not watching this deceitful crap ever again
She had literally just left sickbay (having discovered Chakotay was not the father of her child) then seconds later the doctor asks the question
I think Kirkfan has Voyager by the Jaffas and deserves a prize. We should award them weekly
To be fair, the Doctor asked what Voyager's crew compliment was, not who was on the ship.
To be fed, I'm assuming that replicator rationing had not been suspended, and even so. do replicators just give food to anyone? To keep the ship running, the computer would have to be deceived into believing that it's current crew was lawful and even diligent. The 89 Kazon had been staffed to Voyager to fit into specific positions and roles and therefore seen as crew, and allowed to eat, even if they were not doing their job or were only allowed on board through a guest pass. They needed to justify their existence to the computer as someone worth looking after, which it seems they didn't do so well, since the computer didn't care one way or the other who it was helping take the ship. The Doctor or the Kazon. The computer did not care.
Seska is not crew, she is a passing through dignitary, like any of those assholes that used to swing their dick around on Kirk's Enterprise on a fastpass to cocking up.
I find it off that Suder is still thought of as crew and not as an escaped prisoner who the computer should be sending Security after, who are now ironically Kazon thugs disgusted by Starfleet.
"Sigh"
To be fed, I'm assuming that replicator rationing had not been suspended, and even so. do replicators just give food to anyone? To keep the ship running, the computer would have to be deceived into believing that it's current crew was lawful and even diligent. The 89 Kazon had been staffed to Voyager to fit into specific positions and roles and therefore seen as crew, and allowed to eat, even if they were not doing their job or were only allowed on board through a guest pass. They needed to justify their existence to the computer as someone worth looking after, which it seems they didn't do so well, since the computer didn't care one way or the other who it was helping take the ship. The Doctor or the Kazon. The computer did not care.
Seska is not crew, she is a passing through dignitary, like any of those assholes that used to swing their dick around on Kirk's Enterprise on a fastpass to cocking up.
I find it off that Suder is still thought of as crew and not as an escaped prisoner who the computer should be sending Security after, who are now ironically Kazon thugs disgusted by Starfleet.
"Sigh"
All their sensors need adjusting.
In "Caretaker", when scanning the barn, Kim says there are several humans and one Vulcan. What about Torres, Suder, Chell, Gerron, Seska, and the other non-human Maquis we saw?
In "Caretaker", when scanning the barn, Kim says there are several humans and one Vulcan. What about Torres, Suder, Chell, Gerron, Seska, and the other non-human Maquis we saw?
From Basics part II:
Oh really!
And what about Seska?
I guess that the computer was infected with the brannonbragaamnesia virus.
The same virus infected The Doctor's program in "Time And Again when he didn't seem to remember that Kes, Neelix and the Maquis crew had joined the crew two months earlier.
In order for a computer to exist it must be aware, unless you want to believe in these dodo-heads. One of the complements of 20um CPU is its ability to automaticaly know what is needed. Extreme miniaturization of electronic gates is causing the effects of phenomena like electromigration and subthreshold leakage on the CPU IC. An expert programmer may easily derive a person on an IC board which they've already done.
Sure, if you think people are shit.
Who doesn't?
I noticed that glimpse a couple of years ago.
Obviously the brannonbragaamnesia virus can affect humans too.
I must admit that Kim suffered from the disease in my story "Coming Home" too when Kim didn't discover an Ocampa on the Lynx Maquis ship which Voyager encountered in the Delta Quadrant sometime in the beginning of 2377.
Also, for that matter, why do not alarms go off whenever the crew compliment is not exactly what it's supposed to be?
Some random anti-fed sympathizer with connections got that function removed decades ago under the guise of protecting people's offtime privacy.
After Kirk killed the Space Ghost of Jack the Ripper, everyone was finally safe?
**Sigh**
The Lunchbox sized belt buckles in the motion picture were medical sensors that broadcasted real time health data to sickbay.
**Sigh**
The Lunchbox sized belt buckles in the motion picture were medical sensors that broadcasted real time health data to sickbay.
Shows you what I know...I thought they were lunchboxes!!!
That sounds like a mildly effective prophylactic.
It's a little difficult to make out if your chicken + tater tots and juicebox keep ramming into her gumbo and refried beans.
It's a little difficult to make out if your chicken + tater tots and juicebox keep ramming into her gumbo and refried beans.
Ah, recipes from days gone by...
"tater tots"
"...dang...that gumbo done gone evr'wear..."
"I ain't evr seen nuthin' lahk dat...!
I have never had gumbo and may well die without correcting this sadly.
Similar threads
