Star Trek: Enterprise: Daedalus and over one million other books are available for Amazon Kindle. Learn more

Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
More Buying Choices
Have one to sell? Sell yours here
Start reading Star Trek: Enterprise: Daedalus on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Star Trek: Enterprise: Daedalus [Mass Market Paperback]

Dave Stern
4.1 out of 5 stars  See all reviews (11 customer reviews)
List Price: CDN$ 10.50
Price: CDN$ 9.98 & FREE Shipping on orders over CDN$ 25. Details
You Save: CDN$ 0.52 (5%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 1 left in stock (more on the way).
Ships from and sold by Amazon.ca. Gift-wrap available.
Want it delivered Monday, November 3? Choose One-Day Shipping at checkout.

Formats

Amazon Price New from Used from
Kindle Edition --  
Mass Market Paperback CDN $9.98  

Book Description

Dec 1 2003 Star Trek: Enterprise
October 5, 2140. After a half-dozen years of research and testing, Starfleet prepares to launch its first warp 5 vessel -- Daedalus. Propelled by a radical new engine designed by Earth's most brilliant warp field theorist, Victor Brodesser, the new ship will at last put the stars within mankind's reach.
But on the eve of her maiden voyage, a maintenance engineer, Ensign Charles Tucker III -- "Trip" to his friends -- discovers a flaw in Daedalus's design. When he confronts Brodesser, the scientist -- as charismatic as he is brilliant -- eases Trip's concerns. The ship launches on schedule, and as Trip watches in horror, it explodes in a catastrophic ion cascade reaction, killing all aboard.
Thirteen years pass. Still haunted by memories of that disaster, Trip now serves as chief engineer aboard Enterprise. When a freak explosion cripples his vessel, leaving her helpless before a surprise attack, Trip is forced to abandon his ship -- and his shipmates. As he is on the verge of mounting a desperate rescue attempt, however, a shocking turn of events forces him to confront the ghosts of Daedalus one final time.

Frequently Bought Together

Star Trek: Enterprise: Daedalus + Star Trek: Enterprise: Shockwave + Star Trek: Enterprise: The Romulan War: Beneath the Raptor's Wing
Price For All Three: CDN$ 29.45


Customers Who Bought This Item Also Bought


Product Details


Product Description

About the Author

Dave Stern is the author of numerous books, amongst them the novelisation of Lara Croft: Tomb Raider and The Blair Witch Project.

Excerpt. © Reprinted by permission. All rights reserved.

Chapter One

"Commander?"

Trip looked up from the intermix chamber, where he'd been monitoring the composition of the matter-antimatter stream. Engineer Second Class K. P. Ryan -- tall, lanky, usually quiet to the point of reclusive -- stood on the access ladder below him.

"Ryan. What's up?"

"You have a moment? It's about the cell-ship."

Trip -- Commander Charles Tucker III, chief engineer aboard the Starship Enterprise -- frowned. He had a systems status meeting with the captain in a few minutes, and he was already running behind schedule.

But the cell-ship...

Analyzing the captured Suliban vessel had been a priority for Trip over the last several months. First on his own, then with key members of his department -- including Ryan -- Trip had turned the cell-ship virtually inside out, trying to plumb the secrets of the Suliban's superior technology.

"What about the cell-ship?" Trip asked.

"Their warp drive. The propulsion system." Ryan's eyes gleamed with excitement. He looked more animated than Trip had ever seen him. "I think I've figured it out."

"You're kidding."

"No, sir." Now Ryan actually smiled. "I'm not."

"Sonuvagun." Trip set down his diagnostic spanner on top of the intermix chamber. "Come on. Show me."

Ryan led him out of engineering and down to Launch Bay Two. The cell-ship sat in the far corner -- looking like nothing so much as a multisided dice cube precariously balanced on one edge, perhaps a third as big as one of Enterprise's shuttlepods. Its forward hatch was open, and portions of the hull had been removed, exposing layers of exotic-looking circuitry. Cables of varying thickness and color -- most of them supplying power, but some more diagnostic in nature -- ran from various nodes in the circuitry to a diagnostic station nearby. One of those nodes was the warp-drive module -- a rectangular box roughly the size and shape of an old orange crate -- which had been pulled out from the instrument panel and now lay on top of the cockpit console.

Trip hadn't gotten very far in analyzing that module -- but one thing was clear. Unlike Enterprise, which used a series of controlled matter/antimatter explosions to achieve warp velocity, the Suliban drive depended on an exotic series of reactions between charged particle streams -- the exact composition of which had defied decipherment.

At least until now.

"We've been doing a black-box analysis on the module the last few days," Ryan said. "Feeding different particle streams in, measuring the energy that comes out."

"Yeah," Trip said impatiently. He knew that -- he was the one who'd started the black-box analysis a week ago. The last few days he'd had to spend most of his free time in engineering, though, so he'd handed over that analysis to others. "Go on."

"At approximately" -- Ryan consulted the display screen -- "fifteen hundred hours we input a series of discrete ion streams into the warp module. The power output was negligible -- until I had an idea. Alternate the charge on each succeeding stream -- follow a positive stream with a negative, then another positive, and so on. And if you -- "

"Hold on a minute." Trip felt suddenly light-headed. "Are you trying to tell me the Suliban ship runs off an ion drive?"

Ryan smiled. "Yes, sir. I think so."

Trip kept his gaze neutral.

But inside, his mind -- and his heart -- were racing.

An ion drive.

Daedalus.

Ryan was still talking, Trip realized.

"...somehow prevent the streams from crossing until the last possible second -- then all that pent-up energy gets released at once. I think that's what the Suliban drive does -- the ions come together like real streams do, to make a river."

"Cascading," Trip said softly. "The word you're looking for is cascading."

"A cascading ion drive." Ryan nodded. "That sounds about right. Of course, we can't be certain that's exactly what we're dealing with here -- it is a black box, after all, but..."

Ryan continued talking, but Trip no longer heard him. He was hearing another voice in his mind, a voice coming from fourteen years and billions of kilometers in the past.

Victor Brodesser's voice, as the most controversial scientist Earth had produced in a dozen generations stood up from behind his desk and reached forward to shake Trip's hand.

"Welcome to the Daedalus Project, Mister Tucker." Brodesser -- in his early sixties, a broad, barrel-chested man with a massive shock of wild gray hair that made him look every inch the mad scientist his reputation made him out to be -- had a fierce grip. "We're here to make history."

And they had. Just not in the way Brodesser had hoped.

* * *

"Commander?"

Trip realized Ryan had asked him a question.

"Sorry, K.P. Say again?"

"With your permission -- I'd like to follow this full-time. If these power curves hold, and we could gather enough data -- maybe we could even reverse-engineer the drive...."

Ryan's voice trailed off. The young engineer looked at Trip, and frowned.

"Is something the matter, sir? I suppose I should have called you down when I started to get results, but -- "

Underneath the ensign's worry, Trip could sense a hint of anger and suddenly realized what was going on. Ryan thought he was jealous of the ensign's discovery.

"Hey, no, no, Ensign. Everything's fine. Just...

preoccupied with something, that's all."

"About the cell-ship?"

"No," Trip answered, wondering if he should tell Ryan about Daedalus. No. He needed a conversation with the captain first. And -- there was no need to shoulder Ryan with the burdens of the past just now.

"Listen, this is good work, Ensign. Good work. You absolutely deserve to be the one following up on it."

"Thank you, sir."

"Now, full-time...I don't know about that. But for the next few days I'll switch you off the maintenance roster. You'll have to make up those shifts, though...down the line."

"Yes, sir. Thank you, sir."

Ryan smiled so broadly his teeth showed.

Trip couldn't help but smile back.

The companel sounded.

"Archer to Tucker. Archer to Commander Tucker."

The smile froze on Trip's face.

The status meeting.

Trip strode quickly to the nearest companel.

"Tucker here, sir. Be there in a minute. Just finishing up a little something in Launch Bay Two."

"The Suliban ship?"

"Yes, sir."

"Good. That's one of the things we'll need to discuss. When you get here."

"On my way, sir."

Trip closed the channel and turned back to Ryan.

"Keep me posted, K.P. Progress reports every day."

"Yes, sir."

Trip would be studying those reports carefully -- and certainly dropping by frequently to check up on Ryan's progress in person.

He'd put his heart and soul into Daedalus. Even after all this time...it would be nice to see that work -- not to mention Brodesser's belief in the ion drive -- validated. Even if the professor himself was no longer around to see it happen.

Still, as he headed for the turbolift, the ion drive wasn't uppermost in his mind.

Trip was wondering why in the world Captain Archer wanted to talk about the Suliban ship at the status meeting.

The captain, Sub-Commander T'Pol, the ship's armory officer, Lieutenant Malcolm Reed, and -- to Trip's surprise -- ship's physician Doctor Phlox, who almost never attended these status meetings -- were gathered around the situation room table as Trip entered.

T'Pol was in the middle of a heated speech -- heated for her, anyway; after serving with the Vulcan this long Trip had come to recognize the cutting tone her voice took on when she felt particularly strong about making her point -- and Trip waited for her to finish before making his presence known.

"...so my preference remains a continued series of long-range scans, rather than the uncertain -- and potentially catastrophic -- alternative Lieutenant Reed proposes, which would -- "

"Now, hold on a minute, Sub-Commander." Malcolm Reed -- who was also the ship's tactical officer -- frowned. "I grant you that by using the cloaked vessel we take a chance, but catastrophic? Surely that's a bit of an exaggeration -- "

"On the contrary, Lieutenant, catastrophic describes precisely the consequences almost certain to result should our presence be detected by the inhabitants of -- "

"All right. T'Pol, Malcolm -- please." Archer's own voice had an edge. "I think both of you have made your positions clear on this. Now -- "

Trip cleared his throat. "Excuse me -- Captain?"

Archer looked up at him and smiled. "Ah -- Commander Tucker, isn't it? Join us, please."

Everyone around the table -- everyone except T'Pol, of course -- laughed.

"Sorry about being late, sir. But" -- he looked around the table, from Reed to T'Pol to Doctor Phlox, and then back at the Captain -- "cloaked vessel? I have to guess you mean the cell-ship, but...would someone please fill me in on what else I missed?"

"We are talking about the cell-ship" Archer nodded. "As to what else is going on...T'Pol? If you wouldn't mind bringing Commander Tucker here up to speed..."

"Certainly." T'Pol shifted in her chair and spoke directly to Trip. "As you may or may not be aware, several days ago we entered the K'Pellis Cluster, an aggregation of previously unexplored stellar systems. Almost immediately sensors detected a massive gravitational anomaly within one of those systems. We have been conducting intensive studies of the anomaly since that initial contact -- and have agreed a series of close-up observations are in order."

Trip got it instantly. "And you want to use the cell-ship to do that."

Reed spoke up. "Yes."

"But cloaked -- why?"

"I will show you." T'Pol touched a button on the table in front of her, and the display set in the center of the table came to life. From left to right it showed a blinking white oval, a band of much smaller, irregularly shaped objects, and two circles, one much larger than the other.

"This is the Cole One-twenty-eight system -- which the anomaly here" -- she pointed to the blinking oval -- "is located in. The system also contains an extensive asteroid belt" -- she pointed to the band of irregular objects -- "a single Minshara-class planet" -- to the smaller of the two circles -- "and a yellow sun, point-six-hundred-seventy-six on the K'uda luminosity spectrum."

She looked up at Trip.

"The planet is inhabited. A bipedal, humanoid race -- "

"With, I might add, an unusual amount of genotypical similarity to Earth humans," Phlox interjected. "If the preliminary data holds up, in fact, we're looking at an almost ninety-nine point nine percent congruity between these aliens and your species. Which is remarkable, considering the distance between Earth and this world. Wouldn't you agree, Sub-Commander?"

T'Pol raised an eyebrow. "Remarkable is a very strong word, Doctor. I would characterize the preliminary data as 'of interest.'"

"Ah. Remarkable, of interest -- we're talking about the same thing. A -- noteworthy situation, hmm?" Phlox smiled. "Forgive the interruption. Please -- continue."

She did so -- Trip noting that however you wanted to characterize the data, it at least explained Phlox's presence at the situation table.

"This race, Commander Tucker, has minimal space-flight capabilities. Based on intercepted E-M transmissions, they are at least a century away from warp flight capability. Should they detect our presence, it would undoubtedly have far-ranging consequences for the development of their civilization. Potentially" -- she inclined her head in Lieutenant Reed's direction -- "catastrophic in nature."

Reed rolled his eyes.

Archer held up a hand before the lieutenant could start in again.

"Well...hold on a minute," Trip said. "I still don't see why you need the cloaked ship." He pointed to the display. "You've got the asteroid belt between your anomaly here and the planet."

"This civilization has ships in the asteroid belt," T'Pol said. "Most likely performing mining operations."

"Most likely with limited scanning ability," Trip countered. "If we know where those ships are, I'd bet we can get Enterprise in and out without being detected -- and you'd have plenty of time to run your scans...."

His voice trailed off as he noticed Reed shaking his head.

"She needs a week," Malcolm said.

"At minimum. And there are dozens of ships in the belt," T'Pol said. "Too many for us to remain hidden that long."

"Which is why I suggested cloaking the cell-ship," Reed said. "That way -- "

T'Pol shook her head. "If the cloak should malfunction..."

"Trip," Archer asked. "What do you think? Can you get the cloak up and working again -- and guarantee it won't fail?"

Trip let out a long, slow whistle. They'd used the cell-ship's cloak on one previous occasion -- a life-or-death occasion -- and though it had ultimately done what they required of it, its function had been...well, intermittent at best.

Trip had also ended up cloaking his own hand for the better part of a week while working with the cloak. One of the most unsettling experiences of his life -- looking down and seeing your hand gone from the wrist up, made doubly unsettling by the fact that even though he couldn't see the hand, he could still feel it.

Still...

"Guarantee is a pretty strong word, Captain. But I tell you what -- I wouldn't mind taking another crack at it. A couple days of solid work and I'll be able to let you know one way or another."

"Commander," T'Pol said. "With all due respect -- one can be certain that the Suliban did not develop their cloaking technology in a 'couple of days.' To think that you will be able to decipher the principles behind it in that span of time -- "

"I don't need to understand the principles," Trip said. "I just need to get it working."

"If we do not understand the principles on which the cloak is built, we cannot be sure of its reliability."

Archer nodded. "A fair point."

Trip frowned. "Well...maybe. But you don't necessarily have to know how something works to use it, Captain. I mean, half the people on this ship couldn't fix the impulse engines, let alone the warp drive. Am I right?"

Archer nodded again, and smiled. "You're right. So is T'Pol. Which is why" -- the captain leaned forward in his chair -- "I'll ask her to assist you in repairing the cloak. That way she can be assured of its reliability before we decide whether or not to undertake the survey."

"Of course, sir," T'Pol said.

"Yes, sir," Trip chimed in, biting down hard on his lip to avoid showing his irritation. He would far prefer to work on the cloak himself, having done a lot of work with that module already, all of which was in his head and only in his head, so he would have to spend a good chunk of time bringing T'Pol up to speed on where he was before moving forward on his analysis.

He looked up and saw Archer smiling at him -- as if the captain could read his thoughts.

"We'll get on it right away," Trip said, returning his commander's grin with as much sincerity as he could muster.

"Good." Archer looked around the table. "Now, if we're all done here -- "

"A moment, Captain." Doctor Phlox, who had remained silent during the entire discussion, spoke up.

"I would like to remind everyone of the unfortunate consequences of Commander Tucker's previous attempts at working with the cloaking device. The 'missing hand' episode, as I have come to think of it."

"You don't have to remind me," Trip said.

"But that is precisely what I wish to do," Phlox said, his voice growing suddenly earnest. Even after all this time serving with the doctor, that was the one thing about him that Trip still had a hard time getting used to -- how Phlox could go from irreverent to dead serious within the space of a single breath. "We found no long-lasting health consequences as a result of that incident, but it seems to me that Sub-Commander T'Pol's point is worth repeating and even amplifying. Playing with technology -- "

"I'm not playing," Trip said forcefully.

Phlox nodded. "An unfortunate choice of words. Forgive me. Experimenting with technology without fully understanding its ramifications is a

situation rife with -- shall we say, catastrophic potential -- especially aboard the cramped confines of a starship. I would urge extreme caution."

"Point well taken, Doctor. Trip, T'Pol..." Archer took them both in with a single glance.

"We'll bear that in mind, Captain," Trip said.

"Yes, sir," T'Pol concurred.

"All right, then. I'll want a progress report tomorrow by eighteen hundred hours -- we should make a decision by that time the following day." Archer looked around the table again, then stood.

"Dismissed."

But Trip had another matter he wanted to discuss with the captain.

He followed Archer into his ready room.

"Commander Tucker," the captain said as he sat down at his workstation. "Let me guess -- you'd prefer to work on the cloak alone."

Trip smiled. "Sure would. But that's not what I wanted to talk to you about."

"Oh?" Archer activated his monitor and began scrolling through his incoming messages. "What's on your mind?"

"Ryan's made a very interesting discovery -- about the warp drive on the cell-ship."

"Uh-huh. Go on." Archer was half-listening -- as absorbed in scrolling through the information on his monitor as he was in what Trip had to say.

"Captain." Trip leaned over Archer's shoulder. "Preliminary indications are that it's an ion drive."

"Really? An ion drive?" The captain still didn't look up from the screen.

"I think so, sir. Of a type very similar to the one we used in Daedalus."

Archer's fingers, in the middle of keying in a response to one of the on-screen messages, froze in midair.

The captain spun around in his seat to face Trip.

"And this is a functional ion drive?"

"Well...that's what we need to confirm," Trip said. "I told Ryan he could go at it full-tilt over the next few days -- that'll have to wait until we finish up with the cloak now, of course -- but even so, I'd like to get him access to the Daedalus files -- Brodesser's files -- as soon as possible. With your permission of course, sir."

The captain drummed his fingers on his desk.

"Daedalus," he said, wearing a faraway look. Trip knew what the captain was thinking about: Archer had lost friends as well -- good friends -- when Daedalus exploded. "That was a long time ago, Trip...."

"Fourteen years."

"Fourteen years. That long..." Archer shook his head. "You think about what people would be like now...what they might have done."

Trip nodded. He certainly did.

"Brodesser and Duvall -- if the drive had worked, Daedalus would have beat us out here by more than a decade. They would have half the quadrant mapped out by now. Both of them would be as famous as Zephram Cochrane."

The captain was talking in general terms -- "out here" meaning "unexplored space" -- but in point of fact, from what Trip remembered of the mission profile, K'Pellis and the surrounding sector had actually been in Daedalus's initial destination matrix.

"So the drive on the Suliban ship is similar to..." The captain frowned. "What was it called?"

"The cascading ion drive," Trip said. "Cid."

"That's right -- how could I forget? El Cid. Like the story."

Trip looked at the captain.

And once again, he saw Brodesser.

"The cascading ion drive," Brodesser had said that first day Trip had walked into his office. "I've spent the last five years of my life working on it. Here."

Brodesser turned the display on his desk so that Trip could see it.

The monitor was filled with line after line of equations. Trip couldn't make heads or tails out of half of them.

"You'll note" -- Brodesser pointed at one of the last few lines on the screen -- "the maximum speed the drive is capable of achieving."

That line was one of the ones Trip could understand.

"Warp seven-point-six." He blinked just to make sure he'd read it right. "Seven-point-six? The Vulcans aren't even there yet. Don't expect to be there for another hundred years."

"That's right," Brodesser said. "It would be nice to address them from a position of superiority for once -- wouldn't it?"

"Sure would," Trip said.

The two of them shared a smile.

"You'll need to get clearance from Starfleet to open up those old records on Daedalus."

The sound of Archer's voice brought Trip back to the here and now.

The captain had risen from his seat and was now standing by the ready room's sole window, his back to Trip. "Compose a request for me, and I'll forward it on."

"Will do."

Archer turned around then, and shook his head. "Daedalus. An ion drive. It's a small universe, after all."

"That it is, sir."

"It'd be nice to remove some of the clouds hanging over that project."

"Just what I was thinking."

"You'll be careful, though? You'll make sure Ryan's careful?"

"I'll watch him like a hawk."

"All right, then. Dismissed."

Trip headed back down to Launch Bay Two to break the good news -- and the bad -- to Ensign Ryan.

Copyright © 2003 by Paramount Pictures. All Rights Reserved.

Inside This Book (Learn More)
First Sentence
"COMMANDER?" Trip looked up from the intermix chamber, where he'd been monitoring the composition of the matter-antimatter stream. Read the first page
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Excerpt | Back Cover
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?


Customer Reviews

4.1 out of 5 stars
4.1 out of 5 stars
Most helpful customer reviews
4.0 out of 5 stars Enterprise: Daedalus April 7 2004
Format:Mass Market Paperback
As I sit here writing this, the future of the TV show Enterprise is still uncertain. Will there be a Season 4? We don't know. Then there's that other vicious rumour...that Jolene Blalock may be trying to walk away from the show; if it's true it would just about crush me (she's such a wantable Vulcan!--and I don't just mean the gum-card, or the pop-together model). Meanwhile, I've had to endure weeks of repeats while we wait for the show to get back to new episodes.
My solution to all this frightening uncertainty married to scads of repeats has been to read this Enterprise: Daedalus thing and see what I think. Despite my chagrin at the Enterprise novel line seeming to ignore Captain Archer as a main character--do they not want him to even come close to rivalling Kirk?--I must say that this Trip adventure (with Hoshi in tow) is a complete success! It's exciting all the way through, it's full of twists and turns as it drops Trip in the midst of an unfamiliar but dangerous war, and there's even time for some romance and a Trip back-story that seems to pertain to things as they unfold. Admittedly, our author is not a memorable stylist, but I'll forgive that.
I'm not going to discuss much more of the plot, because it will sound very trad if I avoid all the clever twists and turns. Just join the fun as Trip allies himself with some rebellious asteroid miners, and other enemies of a ruthless usurper of power, to help stop a conflict that he's not even sure he should get involved in, while also trying to rescue the Enterprise and her crew from capture at the hands of the evil tyrant Sadir. In doing so, our plucky Engineer runs right into a sinister piece of his past.
I had a terrific time with this book, even though I've done myself a bit of a disservice.
Read more ›
Was this review helpful to you?
5.0 out of 5 stars Warning Jan. 16 2004
Format:Mass Market Paperback
.... This book is Part 1 of at least 2 parts (who knows?).
The story of Daedalus does not resolve by the end of the book. You have to read Book 2 to find out what happens to the people who are all in dire straights. I hope Book 2 ends the story, because I don't want to be caught in a hardcover "soap opera."
That said, I am looking forward to Daedalus Children (Part 2). I only regret that the publishers spaced the books so far apart. I will have forgotten what this book was about by the time Part 2 is ready for sale and I've already sold my copy of this one.
By the time this Daedalus story comes to an end, I also hope that it deviates from what has become "standard" Star Trek plots (time-space continuum anomalies, etc). I am ready to move on to good science fiction with some new Trek ideas.
As far as Stern's ability to TELL a story, he did a good job. I enjoyed his style.
Regardless of my concerns, Daedalus is entertaining enough to be worth the cost of the book.
Was this review helpful to you?
4.0 out of 5 stars ST-Enterprise: Daedalus Part 1 of 2 Dec 27 2003
Format:Mass Market Paperback
Star Trek - Enterprise: Daedalus part 1 of 2 written by Dave Stern is a well-wrtten storyline where the main characters in this book that are known to us are Charles (Trip) Tucker, III and Hoshi chief engineer and communications respectively. After the first fifty pages Trip becomes the primary character, as Hoshi plays a minor role.
The book is full of Trip's memories of the Daedalus Project man's first attempt at warp drive... a cascading ion drive a full ten years ahead of the matter-anitmatter warp drive. This project was headed by Professor Victor Brodesser a rather forward thinker and hard working man. But, the cascading ion drive propulsion system has some problems... Trip was a working engineer on this project and he has discovered a fatal flaw in the cascading design. Trip gets some concessions from the Professor but the Daedalus is lost on its maiden voyage.
Now, thirteen years have past and the Enterprise is investigating an anomaly when it is attacked and lost to a rather human-like race called the Denari. The Denari are in the middle of a civil war as one side has better technology than the other, but, how did they obtain such an advantage. That is one of the questions answered within the pages of this wonderfull story. There are twists and turns throughout this book and it moves right along keeping your interest till the end... well the end of part one. There is a leadin chapter to the second book Daedalus' Children.
The author does a good job of character development and piques your interest. The villian in this book is just hearsay untill the end and the Denari Doctor Trant has a liking for Trip as we find out in the book.
This is a solid 4 Star Trek novel and I hope that the second tome in this series is as well-written. It is finally refreshing to read a ST-Enterprise novel where there is good writing and character development. I just hope this trend will continue for some badly needed solid storylines for ST-Enterprise.
Was this review helpful to you?
3.0 out of 5 stars Full of Surprises Dec 26 2003
Format:Mass Market Paperback
What surprised me the most about "Daedalus" was how enjoyable a reading experience it was. I readily admit that I wasn't expecting much based on the previous Enterprise novels but "Daedalus", despite its weaknesses, was an interesting story with appealing characters that was solidly executed. Not great but certainly engaging and entertaining.
The title, Daedalus, refers to the ship of that name, an experimental warp capable vessel that exploded on its maiden voyage thirteen years earlier. Tucker, who had worked on the Daedalus project, finds his memories of that catastrophe coming back to haunt him in more ways than one in this story and it is Commander Tucker who quickly becomes the main character in the novel. Stern's characterization of Trip is excellent, the personality and voice of the engineer comes through marvelously.
While Hoshi and Tucker are the only two main Enterprise characters utilized in "Daedalus" after the first three chapters, and Hoshi plays only a limited role, the other characters are well drawn. They are sympathetic but strong. The Denari doctor, a woman named Trant is particularly likable. However, the apparent villain, General Sadir, is only seen superficially, primarily through hearsay.
Just after the midway point the plot of "Daedalus" takes it's first startling twist but it is in the final chapter that Stern guarantees you'll want to read part two, "Daedalus's Children", by dropping another astonishing, and hopefully unforeseen turn into the story. How the story is concluded in the second part will ultimately determine just how good this first part was, and hopefully the plot can maintain its momentum and we will have to wait until May 2004 to find out, but based on the story thus far I'm feeling a lot more optimistic than I expected.
Was this review helpful to you?
Want to see more reviews on this item?
Most recent customer reviews
5.0 out of 5 stars Yet another great "Star Trek" book!
Even though I grew up with the Original Series Star Trek, I also came to love TNG as well and, later, VOYAGER and ENTERPRISE. Read more
Published on June 16 2004 by Eric
4.0 out of 5 stars Superbly written book.
Fascinating story, good pacing, good action, deft handling of characters. The only flaw (if one agrees with me that it IS a flaw) is that it doesn't finish. Read more
Published on May 18 2004 by James Yanni
5.0 out of 5 stars The TV show should be written this well
We get to see part of federation history aboard a ship that didn't have a successful engine design. Years later Trip and Hoshi hope to prevent the same from happening while... Read more
Published on March 23 2004 by Picardfan007
4.0 out of 5 stars One of the better efforts in recent Star Trek fiction
I managed to pick up a copy of "Enterprise: Daedalus" from a local library and thought it would be a mildly pleasant diversion for a long subway ride. Read more
Published on Feb. 20 2004 by John Kwok
4.0 out of 5 stars Mirror, mirror?
This novel feels a lot like a character exploration of Chief Engineer Tucker. The plot is simple but surprising well done and I enjoyed the read. Read more
Published on Feb. 18 2004 by B. Everett
3.0 out of 5 stars Best Enterprise Story - so far
This was the best Enterprise novel, so far. Yes, it did only focus on Trip and Hoshi, and the supposed villan is removed a little too easily, but it keeps your attention in the... Read more
Published on Dec 11 2003 by P Weyer
4.0 out of 5 stars The Best Enterprise Book to Date
I found Enterprise Daedalus to be a refreshing and entertaining read. The book features only two of the main characters after the first 50 pages. Read more
Published on Nov. 27 2003 by J. McCain
Search Customer Reviews
Only search this product's reviews

Look for similar items by category


Feedback