wall e - Why does Auto wake up the ship's captain when EVE returns?

When EVE returns to the ship, Auto is notified of the findings. He then proceeds to wake up the captain to let him know of the plant. Then they open EVE and don't find anything: Auto got rid of it due to directive A113.

Well then, why did Auto even bother waking up the captain? Why not just dispose of EVE and call it a day?

Answer

My reading was that Auto was deeply conflicted. On the one hand he was attempting to obey his original programming under Operation Recolonize (sending out probes, monitoring for lifesigns, passing that data onto the ship's Captain) and on the other he had directive A-113 (that the ship shouldn't return to Earth under any circumstances).

For about 600 years he was absolutely fine. Since there was no life detected, there was no need to worry about the hidden orders. It wasn't until the Eve probe came back with a plant that his directives suddenly came into sharp conflict. His programming was telling him to return to Earth and to not return to Earth. At that point, like HAL-9000 before him he went insane. Auto decided that the best course of action would be to destroy the offending plant even if it meant taking over the ship, disobeying the Captain and risking of the lives of everyone on board.

In the film's script you can actually pinpoint the precise moment he goes gaga:

Auto detects Eve's plant light.
Goes still...
Begins computing rapidly.
The number "A113" flashes on his lens.
An ELECTRONIC EXCHANGE begins between Auto and Gopher.

Wall-E watches the interchange. Nervous.
Without warning, Auto heads in his direction.
Wall-E boxes up.
A CIRCULAR SECTION OF FLOOR lights directly below him.

Irises open, like a trapdoor.

As to the specific question of why Auto woke up the captain, the answer is that he didn't. He checks on the captain to make sure he's not awake before asking Go-4 to remove the plant. A few seconds later, he goes back to see the Captain as he's awoken by his automated alarm clock:

Auto lowers through the portal. A CLOCK ALARM BUZZER activates.

AUTOPILOT: Captain. You are needed on the bridge.

Comments

languages - Do we ever see written English in the Star Wars films?

In Empire Strikes Back , we see a transcription of what R2's beeps and bloops mean, but it's not English (sorry for the low quality, it's from the 2004 DVDs): I'd assume it's what Basic looks like when written, but is there some point in the the Star Wars films we see written English instead? (This sort of spun off from a discussion in How do people understand astromech droids? .) Answer At one point there was English but it has been phased out in subsequent versions of the films. Chris Gould at DVD Active did a comparison of all versions of each of the Star Wars films, and in his comparison of Episode 4 , there are a couple of screenshots showing how the power gauge for the Death Star tractor beam was changed. I imagine there are probably more to be found in his other comparisons but I haven't got around to reading those yet.

Was the "pure soul" of Harry's what had really hurt Voldemort?

In the Order of the Phoenix, Voldemort possesses Harry, and it hurts. Greatly. I think that Dumbledore explained that it was because Voldemort's rotten soul was incapable of assimilating Harry's pure soul, that Voldemort didn't understand the love and friendship etc that Harry has in his heart. But, I think it was a lie. Remember that in Deathly Hallows, while looking for information regarding Horcruxes, it is discovered that it is in fact possible to merge a soul fragment back, but that the process was extremely painful. Now then, if Voldemort tried to possess Harry, and Harry had a fragment of Voldemort's soul, I think that it could have been the true cause of Voldemort's pain: the fact of having his soul so close of another fragment. I think that Dumbledore knew that fact, but had to lie to Harry because it was inappropriate to let him know that he had one of Voldemort's soul fragments at the moment. Is that right? Or was it truly the pure soul of Harry's...

star wars - What "exactly" happens when someone turns to the Dark Side?

When I saw the original Star Wars saga as a kid, the concept of the Dark Side imprinted in me was quite simple. You did a bad thing, so you're a bad person so you go to the Dark Side and keep doing bad things. Now, obviously this doesn't hold true in reality. In my mind it is perfectly reasonable for Luke to kill the Emperor and Vader and then just flee the Death Star and rejoin the Alliance. After all they are at war, those are enemy officers that have captured him and are taunting him by threatening with death of all loved ones and the whole operation was intended to kill the Emperor anyway. The same would hold true for Anakin. He could have killed Mace Windu to save the Chancellor and Padme but that doesn't mean he's going to then go mad and kill all Jedis including children. It doesn't add up from a merely psychological point of view. He had a set of objectives and that made him want to keep the Chancellor alive (quite valid by the way, Mace Windu is quite clums...

star trek - Warning regarding forward saucer section in Nemesis?

In Star Trek: Nemesis , just before the Enterprise rams into the Scimitar, Picard sends a text message from his captain's chair arm pad to Troi — who is manning the helm in lieu of the crewman who was just blown out through what was once the view screen — indicating that she should put full impulse on standby. (Literally, if you watch the scene closely, Troi's console prefaces the order with "TXT MSG" !) My question is: Did Picard also somehow warn crew members in the forward saucer section about what was about to happen? The ramming of the Scimitar was a heat of the moment decision. Considering that he also resorted to calling the auto-destruct sequence shortly after (which ended up being offline), he probably was of the mindset that any losses would be acceptable in order to hault Shinzon's march to Earth. Still, I'm curious. Answer The original script indicates that he called for the crew to " brace for impact ". Whether that call (or the comma...

Blog

Search This Blog