Most helpful customer reviews
4.0 out of 5 stars
STV #4 Violations - A fairly decent early Voyager novel!, Nov 9 2003
This review is from: Violations (Paperback)
"Violations" is Susan Wright's second Star Trek novel and it is another example of some very good writing in the Star Trek genre. Of all of her novels, I've always enjoyed her writing style which is well paced and structured and "Violations" possesses those same qualities. Given how early this novel was written during the series run on television, one can tell that the author probably only had the series "bible" and some episodes to base her characterizations off of and I found them to be fairly accurate and in synch with the characters during the first season. The cover art for "Violations" is fairly decent, although the image of B'Elanna is a bit off. The premise: A group of aliens' volunteers to help Voyager but once they're on the ship, they steal the main computer. Forced to negotiate with the aliens to get the main computer back, Janeway soon finds that she's dealing with a consortium of planets where thievery is an acceptable way of life. As Janeway and the crew fight to retrieve the ever important main computer before the barely functioning ship ceases to function at all, they become embroiled in a political struggle that could not only cost them the ship but their lives as well. Overall, this is a fairly well written title for the time in which it was written and given the authors lack of a couple years of experience with the show. I would definitely recommend this early Star Trek Voyager title and any others written by this author. {ssintrepid}
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
1.0 out of 5 stars
I've Read Better Fan-Fiction, Oct 31 2003
This review is from: Violations (Paperback)
Let me start off by saying I have read a lot of books and fan fiction. And this one... well, let's just say I do not recommend this book. To start with, if you've seen the episode "Concerning Flight," you'll laugh out loud while reading this book. (And yes, I know the episode came *after* the book - still, it's no excuse.) Same premise as the episode, the main computer gets stolen. Ok, so Voyager just needs to get it back, right? Well, I started reading this and so they refer to the Doctor as Zimmerman. Ok, I can get over that and ignore that little bit. However, after about the 40th major error that anyone watching more than 15 minutes of any given Voyager episode could have spotted, that's when I got a bit annoyed. I mean, if you're going to actually write a book on something, shouldn't you do your homework? f your answer to that question is no, well, I have a few papers you can write for me. Why did I continue reading this book? Just to see how bad BAD could actually get. And let me tell you, bad got quite bad. Don't read this is you're expecting a good plot, characters and writing. DO read it if you have some time on your hands and are in the mood for something humorous. For a fan who needs to read everything, go for it. It won't kill you and it might just make you appreciate the other books even more.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
11 of 11 people found the following review helpful:
3.0 out of 5 stars
Many wrong details, April 23 2000
By "reubendb" - Published on Amazon.com
This review is from: Violations (Paperback)
This is surely not the best star trek voyager book. There are just too many wrong details. For examples, as far as I know, Captain Janeway never called Chakotay: "Number one". She always use "Commander" instead (Number one is the way capt. Picard calling Riker). And since when the EMH has a name (this book name the Doc: Zimmerman). It's mentioned also that Voyager's computer main processor had trouble of handling data 5000 Megabyte/second. Come on.. read ST TNG Tech. Manual at least about the computer capability. 5000MB/sec is too small. Last thing, The EMH always starts with the promp :"Please state the nature of medical emergency!" instead of the phrase "What is the medical emergency?" like this book used many times. The political intriques also kind of confusing sometimes. Not many action in this book. Certainly there are beter ST Voyager's books such as Battles lines, Ragnarok, Marooned.
7 of 7 people found the following review helpful:
3.0 out of 5 stars
Best VOY book ever? You're kidding, right? Right?, Sep 5 1999
By A Customer - Published on Amazon.com
This review is from: Violations (Paperback)
Not a bad offering overall, but whoever says this is the *best* Voyager book ever written obviously hasn't read too many! Unlike someone else, I enjoyed the planet's political situation. But I got *very, very, quite, extremely bored* when reading about the Doctor's "illness." It seemed like half the book was Kes and Harry standing in front of a computer in sickbay, trying to figure out what was causing his condition. Come *on*--they exchanged medical jargon like two dueling dictionaries. If you read this one, do it to see Captain Janeway and B'Elanna Torres as helpless hostages--an interesting position for those two characters, especially--NOT to see the Holodoc get sick.
4 of 4 people found the following review helpful:
1.0 out of 5 stars
I've Read Better Fan-Fiction, Oct 30 2003
By B. Hannan "ladymacbeth" - Published on Amazon.com
This review is from: Violations (Paperback)
Let me start off by saying I have read a lot of books and fan fiction. And this one... well, let's just say I do not recommend this book. To start with, if you've seen the episode "Concerning Flight," you'll laugh out loud while reading this book. (And yes, I know the episode came *after* the book - still, it's no excuse.) Same premise as the episode, the main computer gets stolen. Ok, so Voyager just needs to get it back, right? Well, I started reading this and so they refer to the Doctor as Zimmerman. Ok, I can get over that and ignore that little bit. However, after about the 40th major error that anyone watching more than 15 minutes of any given Voyager episode could have spotted, that's when I got a bit annoyed. I mean, if you're going to actually write a book on something, shouldn't you do your homework? f your answer to that question is no, well, I have a few papers you can write for me. Why did I continue reading this book? Just to see how bad BAD could actually get. And let me tell you, bad got quite bad. Don't read this is you're expecting a good plot, characters and writing. DO read it if you have some time on your hands and are in the mood for something humorous. For a fan who needs to read everything, go for it. It won't kill you and it might just make you appreciate the other books even more.
|
|
|