top of page
Writer's picturefiafertoracal

Star Trek III: The Search For Spock Movie In Hindi Hd Free Download

Updated: Mar 23, 2020





















































a5c7b9f00b Admiral Kirk and his bridge crew risk their careers stealing the decommissioned Enterprise to return to the restricted Genesis planet to recover Spock&#39;s body. In the wake of Spock&#39;s ultimate deed of sacrifice, Admiral Kirk and the Enterprise crew return to Earth for some essential repairs to their ship. When they arrive at Spacedock, they are shocked to discover that the Enterprise is to be decommissioned. Even worse, Dr. McCoy begins acting strangely and Scotty has been reassigned to another ship. Kirk is forced to steal back the Enterprise and head across space to the Genesis Planet to save Spock and bring him to Vulcan. Unknown to them, the Klingons are planning to steal the secrets of the Genesis Device for their own deadly purpose. So Spock&#39;s dead boo-hoo. This third in the series concentrates on the what the title suggests though nowhere near as bad as The Motion Picture this is not in the same league as Khan.<br/><br/>Yes the acting is great with mild moments of humor and there are certain moments of excitement, notably when Kirk comes into contact with the Klingons and there is a lovely scene which I enjoyed where the Enterprise exits space dock, but ultimately the story is too basic and there is little action.<br/><br/>My interest all but slipped away but it&#39;s not bad, certainly not as bad as Motion Picture or Star Trek 5. About the only positive thing I can say for this movie, is that it added a space station and several cool new starships to the Trek database.<br/><br/>Anyway, the story here picks up where the MUCH better Wrath of Khan leaves off, with Spock dead, having been given a burial-in-space at the newly-formed genesis Planet.<br/><br/>It seems that Roddenberry and Nimoy had second thoughts about killing off the Spock character, so they came up with a half-baked, badly-written scheme to resurrect him.<br/><br/>A critical plot device is based on a fundamental miscomprehension of evolution theory and an equally faulty reliance on &quot;suspension of disbelief&quot; (more on this later...)<br/><br/>Somehow, the &quot;Genesis Effect&quot; is causing the planet to age in surges, but also causing lifeforms to &quot;evolve&quot; without any process of natural selection. In confusing evolution with aging, the author also somehow has the Genesis Effect converting Spock&#39;s very-dead carcass into a very live Vulcan infant. Darwin probably rolls in his grave every time someone plays this movie.<br/><br/>The helpless Spock-infant somehow survives without a mother to nurse and feed and protect it from the nasty worm-eel-things that somehow &quot;evolved&quot; from microbes in Spock&#39;s coffin, and proceeds to age in surges with the planet, through adolescence to adulthood, conveniently culminating in an adult Spock just in time to beam-up as the planet self- destructs.<br/><br/>Aside from writers Roddenberry and Bennett apparently getting their evolution science from a home-schooled Creationist, there&#39;s an excessive and faulty reliance on what speculative fiction authors call &quot;suspension of disbelief&quot;.<br/><br/>Suspension of disbelief (setting aside reader&#39;s / viewer&#39;s objections to fantastic, implausible, and improbable story elements) is generally accomplished through good storytelling, as in a Kurt Vonnegut or Larry Niven story. The previous installment, Wrath of Khan, accomplished this quite well.<br/><br/>Problem is, in this case the writers don&#39;t even try, instead placing the onus on the viewer<br/><br/>If they wanted to keep Spock, they should not have killed him off in the first place - after all, it wasn&#39;t a critical story element to Wrath of Khan.<br/><br/>The final insult, is that in resurrecting Spock, they repeat the mistake and destroy the Enterprise, which itself is as central a character to the series. So naturally, they had to resurrect it with a replacement in the following installment.<br/><br/>Basically, the movie is a homage to bad writing and indecision. The Search for Spock should be great fun for Trek fans; it's splendid junk when it works. But if you can't hum the theme from memory, Trek III is likely to be just another way to kill two hours. [1 June 1984, p.D1] Admiral James T Kirk (<a href="/name/nm0000638/">William Shatner</a>) commandeers the newly repaired USS Enterprise in order to return to the Genesis and retrieve Spock&#39;s body after Spock&#39;s father Sarek (<a href="/name/nm0501697/">Mark Lenard</a>) informs him that the body must be returned to Vulcan so that it can be re-united with Spock&#39;s katra (eternal soul), which Spock has conveniently stored in the body of Dr Leonard McCoy (<a href="/name/nm0001420/">DeForest Kelley</a>). Meanwhile, on Genesis, Saavik (<a href="/name/nm0193495/">Robin Curtis</a>) and David (<a href="/name/nm0125190/">Merritt Butrick</a>) have located a youthful Spock, but the three of them are marooned on the planet&#39;s unstable surface when a Klingon warbird in search of the Genesis device destroys their ship, the USS Grissom, before they can be beamed aboard. The Enterprise must contend with ruthless Klingon commander Kruge (<a href="/name/nm0000502/">Christopher Lloyd</a>) while attempting to rescue the survivors before the Genesis planet collapses. The crew is all here. Kirk, McCoy, Spock (<a href="/name/nm0000559/">Leonard Nimoy</a>), chief engineer Montgomery &quot;Scotty&quot; Scott (<a href="/name/nm0001150/">James Doohan</a>), communications officer Lt Uhura (<a href="/name/nm0629667/">Nichelle Nichols</a>), first officer Pavel Chekov (<a href="/name/nm0000479/">Walter Koenig</a>), helmsman Hikaru Sulu (<a href="/name/nm0001786/">George Takei</a>), Lt Saavik and Kirk&#39;s son David. In the year 2285 A.D., about three months after the events of the previous film The Wrath of Khan. In fact, the movie opens with the final scenes from The Wrath of Khan. Possibly, but there was no guarantee that they would have gotten all the Klingons before at least one of their own number was lost, since the Klingons outnumbered them and were likely have better firearms training. In the novelization, Kirk actually does consider the possibility of trying to shoot the Klingons as they beam in, but quickly dismisses it on the grounds that they&#39;d likely damage the transporter in the process, which would have stranded him and his crew on the Enterprise since Starfleet had already removed all the shuttlecraft (escape pods had not been conceived of at this point in the franchise&#39;s history, first being mentioned in the first season of Star Trek: The Next Generation). The real problem was that the Enterprise&#39;s control system had burned out during the battle with the Klingons, meaning that after killing the landing party, Kirk and his crew would have had no other way of defending themselves. After realizing that his landing party was dead, Kruge may well have beamed Kirk and his crew into his brig or dumped them on the Genesis planet, after which he would have been free to steal the valuable Federation data in the Enterprise&#39;s computer banks (which is what the self-destruct was really intended to prevent). The decision was likely also affected by the knowledge that this allowed the Enterprise a &quot;noble death&quot; rather than the decommissioning she faced when returned to Earth. The Star Trek series didn&#39;t really get its timeline sorted out until the late 1980s and early &#39;90s (and even then TOS era dates are still a bit muddled); the 20 years figure is a rough guess based on the fact that the Trek series had been going for just under 20 years when the movie was made. The closest on-screen explanation we have is that either Morrow is simply wrong about the figure, or he means that 20 years have passed since the Enterprise was refitted in Star Trek: The Motion Picture. There are other issues. In the first pilot (which was non-canonical before any &quot;regular&quot; series episodes had been created), Spock was shown as first officer under Christopher Pike, 5 to 10 years earlier. Clearly, the Enterprise is more than 20 years old. The Federation would not build expensive &quot;wessels&quot; with such a short service life. [&quot;The Menagerie&quot;/&quot;The Cage&quot; were non-canonical from the get-go, as they describe interstellar travel using conventional propulsion systems, a gross improbability. If such a ship could reach 0.9c, and Talos IV were 200 light-years away, the trip would have had to begun in the early 21st century, at the latest. Enterprise (the series) rendered the implicit non-canonicity explicit. There was no room in the Enterprise universe for Christopher Pike and his ship.] It was slightly redressed to serve as the bridge of the Grissom, with the seat covers and a few of the screen details being changed. The lighting of the set might also have been adjusted to give it a different color than we&#39;d seen before. The Excelsior got a new, albeit very rudimentary, bridge set that was scrapped after this movie. The next time we see it in Star Trek VI, it has a redressed version of the Enterprise-A bridge. The novelization answers this (though it&#39;s technically non-canon and certain parts of the novelization don&#39;t match up perfectly with the film). Uhura stayed behind to scramble Federation communications and make it impossible for anyone to catch up with the Enterprise until it was too late to stop them from completing their mission. At the last moment, with authorities banging on the door of the transporter room, Uhura beamed herself to the gate of the Vulcan embassy to attempt to gain an audience with Ambassador Sarek. Just as a Federation security team was almost upon her, she finally negotiated her way past the gate and ran through the grounds to the front door of the embassy. Knocking, she received no answer, and the security team&#39;s leader began leading her back outside the embassy grounds before Sarek appeared and demanded to know why the Federation was invading Vulcan sovereign territory. The security team leader, realizing she&#39;d overstepped her grounds, stated that Starfleet believed the Enterprise crew to be sick and were trying to get them to treatment, but Sarek denied her permission to leave the embassy grounds with Uhura, stating that the commander had asked for, and been granted, sanctuary. Declining the security officer&#39;s offer of 10 minutes alone with Sarek followed by incarceration, Uhura accepted his offer of sanctuary. The security officer said that the Federation would be asking for extradition. &quot;That is up to your government,&quot; Sarek replies. &quot;Good day.&quot;<br/><br/>However, for the sake of the story &amp; it&#39;s pacing, it can likely be assumed that Uhura has plenty of connections and resources that would allow for her to find some sort of transport to Vulcan. If you watch the way she handles her fellow officer (&quot;Mr Adventure&quot;) just as Kirk &amp; his team enter the transporter room, it&#39;s reasonable to assume she can handle the problem of getting to Vulcan without the script saying so. As Genesis explodes, Kirk and his skeleton crew fly the Klingon warbird to Vulcan, where the Vulcan high priestess T&#39;Lar (<a href="/name/nm0000752/">Judith Anderson</a>) performs the dangerous ritual, fal tor pan, that reunites Spock&#39;s katra with his body. The procedure is successful, but Spock&#39;s memory is slow to return, and Sarek isn&#39;t sure when or if it will come back. &quot;Only time will tell,&quot; he tells Kirk. As Spock, clad in a white robe, T&#39;Lar, and a number of attending Vulcans leave the ceremonial platform, Spock walks past Kirk, not recognizing his presence at first. Suddenly, Spock turns to Kirk and asks if the ship is out of danger, to which Kirk replies that he (Spock) saved them all. In the final scene, Spock says, &#39;Jim. Your name is Jim, while the crew of the Enterprise gather around him, pleased that his memory is beginning to return. Yes. Star Trek III: The Search for Spock, a novelization of the movie by American science fiction writer Vonda N. McIntyre, was released in 1984. So far, there are 13. Star Trek: The Search for Spock was preceded by <a href="/title/tt0079945/">Star Trek: The Motion Picture (1979)</a> (1979) and <a href="/title/tt0084726/">Star Trek: The Wrath of Khan (1982)</a> (1982). It was followed by <a href="/title/tt0092007/">Star Trek IV: The Voyage Home (1986)</a> (1986), <a href="/title/tt0098382/">Star Trek V: The Final Frontier (1989)</a> (1989), and <a href="/title/tt0102975/">Star Trek VI: The Undiscovered Country (1991)</a> (1991), all of which featured the Enterprise captained by James T Kirk. <a href="/title/tt0111280/">Star Trek: Generations (1994)</a> (1994) united Kirk&#39;s crew with the crew of the Enterprise captained by Jean-Luc Picard. The Star Trek movies featuring Picard as captain include: <a href="/title/tt0117731/">Star Trek: First Contact (1996)</a> (1996), <a href="/title/tt0120844/">Star Trek: Insurrection (1998)</a> (1998), and <a href="/title/tt0253754/">Star Trek: Nemesis (2002)</a> (2002). <a href="/title/tt0796366/">Star Trek (2009)</a> (2009), <a href="/title/tt1408101/">Star Trek: Into Darkness (2013)</a> (2013), and <a href="/title/tt2660888/">Star Trek: Beyond (2016)</a> (2016) harken to an alternate reality in which Kirk was just beginning his career with Starfleet Academy. While we never actually see it the answer seems almost certainly yes. Spock is experiencing the &quot;Pon-Farr&quot;, the Vulcan mating drive which it is established in the original series will kill him if he does not have sex with a Vulcan female. We then see Saavik touch their hands together in the first phase of the mating ritual. In the script for Star Trek IV: The Voyage Home, the matter is verified by revealing that Saavik&#39;s reason for staying on Vulcan is that she is pregnant with Spock&#39;s child but the line was cut from the final film. It was an experimental warp drive that was to be tested on the Excelsior, the first Federation ship outfitted with it. Simply put, it was a warp drive that was faster than any warp drive in use up to that point. The Star Trek lore says that the experiment was a failure, not because of Scotty&#39;s sabotage but because Federation scientists couldn&#39;t make it work. David Marcus admits to Saavik that he&#39;d used a substance called protomatter in his engineering of the Genesis device. Saavik tells him that he knew himself that protomatter was a highly unstable substance. Like he says, it &quot;helped solve certain fundamental problems&quot; but it also doomed the Genesis experiment to fail—since it caused the rapid development and aging of Genesis itself and the planet destroyed itself. Furthermore, the device was not used as originally intended. It was supposed to have been used on an existing lifeless planet but in this case it created a planet out of the light elements present in the Mutara Nebula, which would not have have the necessary heavy elements needed for planet formation.

0 views0 comments

Recent Posts

See All

Comments


bottom of page