This is at base a good book, and certainly important for MGB owners. However, the book is written from a distinctly European perspective. With the vast majority of MGBs having been sold into the North American market, the European slant is rather a negative. The author is almost distainful of the aforementioned reality. My message to him would be: "Deal with it!"Also, as was true with his tome on the MGA, Clausager has the tendency to focus on the unusual at the expense of the cars owned by the vast majority of owners. My view is the time to include information of only passing utility is after all critical information has been included. The author would do better if he could focus on his readers' interests more, and on his own less. All of the basics should be included before mention of the fancy stuff begins.If you are not an American, but are an MGB fan, buy the book straightaway. If you are an American, you probably still will want it - but you have been warned.

This is an excellent book, and I recommend it to everyone who owns and/or loves MGBs.

I agree with "Pennsylvania" though, that Clausager's perspective is very rooted in England and Europe. I feel there needs to be a full section for the differences in every major market, with North America, especially the US, being the largest. In fact, on page 126 Clausager says: "North American cars have not been split into US Federal, US Californian, and Canadian cars -- there is a limit to what even I will do!" (notice Mexico isn't mentioned), but on page 127 he states: "There is little doubt, however, that apart from the USA and the UK, some of the biggest markets were Australia, Canada, and Germany..." With the US and Canada being two of the biggest markets, more North American centricity is appropriate.

I do understand the enthusiest's disdain for the US market though; it 'mandated' all British cars into floaty, bloated, tall, weak mushballs, which is why Mark I cars are so valued.

Also, I have only found one discrepency, and that's one example of the piping of interior trim for Mark I cars. The second-from-top-left picture on page 40 shows a white 'B which has red interior with white piping (but Clausager does not note it as incorrect, which he does often about other details throughout the book). But, the Colour Schemes chart on page 131 shows Old English White or Snowberry White to have an optional red interior with black piping, which does not match with the picture on page 40 (should say white piping, or the picture should be noted as incorrect). Is this nit-picky? Yes, but that's what this book is all about.

Buy it, enjoy it, and write the publisher to make a future edition with more US information.

Well it seems that some of us don't like the way Mr. Clausager, who, in BMHIT circles is regarded as an authority, writes. My advice would be to get over it. Mr. Clausager has spent countless hours researching and writing about some of the world's most loved automobiles. The compromises that these automakers had to make just to satisfy the U.S.' federal regulations could be seen to bastardise the "original" designs of these cars. Unfortunately, the previous poster can't get over that fact.
This book is the rosetta stone to those who seek to find out what an "original MGB..." is after discovering that all of the unknowing previous owners chose to augment their cars with their ideas of improvements. Maybe you just want inspiration for your restoration from the excellent photography. Or, to those seeking a concours restoration, this is a valuable resource. Yes, I'm mad because there is only --one-- "Original MGB..."

All at your fingertips: this book has all of the basic stats for each and every player who played a game in 2000. However, I felt that this book could have been a lot better. I have to stress that this book only presents the classic basic stats such as batting averages, RBIs, etc, but not slugging percentages, on base averages, or WHIPs. Also, the book provides no photographs (even Who's Who In Baseball has photos of most of the 700 players in their little book) and very skimpy player biographies. STATS Inc provided the statistics for this book and publish their own line of books, including Major League Handbook, which would probably have more of the numbers that more hardcore fans would want. What would have set this book apart from Major League Handbook would have been interesting biographies or photos, not tidbits such as "led California League in total chances in 1994". Save your money for STATS' Major League Handbook.

For stat lovers, this is a must. Gives stats on all players plus prospects. Also year end league leading stats. They could improve on a few things - like showing a players slugging average and on-base average, which are much more important than showing how many times a guy turned a double play in the minors.

The plot is lousy but the cast of characters is tremendous! This is the standard reference work used by announcers for those endless trivia games they play with each other and the audience while filling the time taken up by intentional walks and visits to the mound. The Sporting News has sponsored this book for the past umpteen years--I have kept every copy I bought right next to my TV chair for easy reference during the season. Great for finding past players without searching through the hardbound, 5-pound encyclopedia. My copies are well-thumbed.

Wenham sets out to prove that the Synoptic Gospels were written in the early to mid 40's A.D., a good 20-25 years before the earliest generally-accepted date for Mark. His analysis is thoroughgoing, well-researched, and heavily documented. Unfortunately, his defense of evidence for the early dating lacks the cogency and forcefulness of his attack on the evidence for later dating. While Wenham is vociferously dismissive of evidence contrary to his viewpoint, he uncritically accepts evidence supporting his viewpoint. He bedrocks his early dating on a two pronged analysis: 1. Dismissal of the documentary solutions to the Synoptic Problem, and 2. Heavy reliance on the Patristic evidence of authorship. Firstly, the documentary explanations of the Synoptic Problem must be dismissed because if the Gospels were based on earlier documents, they must perforce be later documents. Secondly, from acceptance of the Patristic evidence of authorship, Wenham can infer a very early date for each of the Synoptics. The book makes interesting reading, but it fails to carry the day in establishing such an early date for the Synoptic Gospels.

One caveat: If you can't read Greek, the first half of the book will be rough sailing, as it analyzes many gospel pericopes in Greek. With a little patience you can, however, muddle your way through it.

Wenham's work is, as noted above, thoroughly documented, researched and conducted. And I would go further than the earlier review. If you don't have a working knowledge of Greek, this will probably be too painful for you.

However, I would say it rewards careful reading of the one willing to examine the issue without buying into the current dogmas of NT scholarship. I did not find him uncritically assuming his own evidence true, rather in several places I recall him saying he would not dogmatically assert either way. The point is to him much of the evidence can be used to support whatever theory one wishes to contrive. "Q" can be made to look reasonable to many, as can Markan priority, if we don't examine the facts behind WHY these works were written.

As to counting Patristic evidence, one could say NT scholarship today dogmatically REJECTS Patristic evidence whenever it doesn't fit their hypothesis. Who's to say that scholars sitting in their offices 2000 years removed automatically have a better concept of the events than 2nd & 3rd century scholars? Am I attacking all NT scholarship? No. But I think it is fair to give the author a reasonable hearing. And I think, after a reasonable hearing, it is not unreasonable to see at least Matthew and Mark written before AD55, and see some measure of MUTUAL dependance between the Gospels.

Neither of these would be fashionable in many NT circles today. But that doesn't mean they are not real possiblities.

Wenham has done a remarkable job of examining the external evidence (the words of the fathers) and the internal evidence (the Gospels themselves) to demonstrate not only the plausability, but the probability of:

1. An early date for the Gospels.
2. The traditional order of Mt, Mk, Lk.
3. The involvement of not only written but oral tradition in Gospel formation.

Critics charge Wenham with relying too heavily on patristic sources. But such charge thus if one relies on the patristics at all in this matter. The critics of the Augustinian order have never satisfactorily explained the origin of the traditional order if a different order is true. In any case, Wenham does solid work in establishing the essential trustworthiness of the patristic sources.

He is perhaps even stronger is his examination of the interrelations between the synoptics as he works through the various synoptic theories and how they fare in terms of how they used or allegedly used each other in their mutual formation.

Wenham believes strongly that oral tradition played a key role in determining the form and the content of each of the Gospels. Despite this, he eschews the idea that they were written in ignorance of each other. He argues dispassionately but forcefully that each successively impacted the ones that followed.

Those who hold variant opinions of the origins of the Gospels do not hold them well until they have positively worked through Wenham's arguments.

I further recommend the writings of B.C. Butler on this topic.

This is a good basic pathology book with good black and white photos. The strength of this book is that all of the features are illustrated with pointers to the significant feature. The drawbacks are that the photomicrographs are not in color and the text is not all encompassing. Some of the newer immunohistochemical staining techniques are not fully explained.

This book fills a special niche in the field of dermatopathology texts. Many excellent texts are available unfortunately the average student or resident cannot afford to buy color illustrated large volume texts. This selection is affordable and well designed to teach dermatopathology to the pathology resident, dermatology resident or interested student. The illustrations are clear and easy to follow with the accompanying arrows. While the range of entities discussed is not encyclopedic the full range of expected entities are present. Overall a good value and useful book for someone just introduced to the field.

Elk Talk is a very informative book, which I have found to be very useful and has given me ideas for the upcoming archery season. Mark Henckel and Don Laubach seem to have all there hunting ideas together and are very experinced on the topic of elk calling wether it be for hunting or for enjoyment. I would recommend this book to anyone who would like to be a more succesful hunter or just enjoys the world of elk.

I read Elk Hunter about 4 years ago and found it to be a vital part to my elk hunting library. This books gives many ideas and strategies that will pay off when your chasing those majestic elk around. I have used some of the tactics that are mentioned in the book and found them to be quite useful at times. They cover a lot of ground in this book and I would recommend this book to anybody who is looking to start elk hunting . Ever since I read this book I have harvested 4 bulls in 4 years. Do I owe it all to the book you ask? No way. Hard work and leg work is something you have to do by yourself. I would also like to say that this book does not get into the bow hunting side and that was something I just had to deal with. So if your a person who would like to know about elk and the habits then this book will suit your needs just fine.

I mostly agreed with Eric Ma. There are some areas that Wrox needs to review the whole process of publishing Java-related books. Here are some drawbacks that I can draw from reading recent Java-related books:

(1) Repeated Contents: Materials about Servlet, JSP, EJB, JNDI, JDBC, XML, etc are repeated over and over many books. This could waste time, money, and papers for both Wrox and readers.

(2)Books or Articles?: I asked myself: is Wrox publishing books or articles? Each book is written by many authors and the book's flow is inconsistent. The assessment that it is not a book but a collection of articles may partially true. It is true that a book if written by a team of authors could speed up the process of releasing it, but if Wrox editors and coordinators have to do their better jobs.

I suggest that Wrox should review its strategy of publishing books to avoid the repeating of materials over and over and thus bring down the cost associated with publishing the books. The final result is: readers and publisher will both save time and money. Otherwise, readers will loose their belief with Wrox.

For the past 2 years Wrox has been publishing books dedicated to Windows-based data access (ADO etc.), but the same cannot be said about their Java/database collection. Although you find chapters on JDBC scattered all-over almost all server-side Java related books by Wrox, there was no single volume from them that teaches JDBC first, and then show how it is used by the newer dependent technologies, until this book arrived. After looking through this book, I must say the authors and editors have done a rather commendable job.

Why do I make the above conclusion? Let me give you my general impression of the book first. A theme repeated in several of my recent reviews on books from Wrox is about the problem in coherence associated with multi-author books. Well, having more than a dozen of authors for a single book seems to be a fact of life (for books from Wrox at least) now, as the publication cycle gets shorter. I was rather surprised to find out that the organization and coherence is very good in this book, i.e., there is very little overlap among chapters. Also, this books uses JDBC cleverly to tie other pieces of J2EE together, making smooth transitions from one chapter to another. If you want to know, this factor alone prompted me to add an extra star to the overall rating of the book.

Let's now run down the chapters of this book quickly. The first 115 pages deals object-oriented and database modeling, and can be skipped by any "Professional" developer. Then after your obligatory intro to JDBC API, the next chapter covers the JDBC 2.0 optional package. This is the best treatment of this topic I have seen. Then another chapter is all about SQLJ, another first. The effort of having a chapter on database performance should be lauded, where connection pooling, prepared statements and stored procedures usage are demoed. The reminder of the book is about applying JDBC in various J2EE components, such as JSP, servlets, EJB, JMS, and XML. For this part of the book, even though I accept the fact the proper stage has to be set for each one of them, I still don't believe the book found the right balance between focusing on JDBC and showing what these other technologies are about. A large number of pages are used to teach basic JNDI, servlets, JSP's, and EJB's stuff (remember there is already a book on J2EE from Wrox!). Therefore, it is up to the reader to discover the real nuggets of gold hidden in this pile, which are far and in between in places. I found that some critical issues are not highlighted or details are lacking, such as how to use connection pooling/data sources in servlets, JSP's, and EJB's, the threading issues related to sharing database connections, and good database practices in BMP EJB's. However, the one thing I cannot complain about is that the book did not forget to teach the transaction aspect of EJB with a good depth (there is a short ans sweet chapter on using JTA/JTS inside EJB). There is also a chapter on the brand-new JDO framework, even though the spec is still in a state of flux. Finally, there are 4 case study chapters in the book - although the design and implementation are limited in scope and as a whole those samples do not teach all you need to do know about enterprise scale J2EE system development, they do provide a flavor of how JDBC is used in real world, together with setting up Tomcat, JRun, Orion, and WebLogic to access MS SQL Server and Oracle databases.

Now my overall take of this book. For VB/SQL and pure back-end PL/SQL developers who are eager to jump on the Java express train and need a suitable platform (especially for the ones who learn best from playing with actual code), I recommend this book as one of several you should own. Compared to other JDBC books from say O'Reilly and Sun's JDBC Tutorial, this book is the most up-to-date, contains the most source code, and has the broadest coverage of related topics. But keep in mind some of the advanced topics such as EJB and JMS can be intimidating for new-comers. On the other side of the coin, people who are advanced in various server-side Java technologies are unlikely to benefit a great deal from this book and should look elsewhere for info (for example Wrox's J2EE and upcoming EJB titles).

While this is starting to show signs of age, published in 1984, this is still one of the better history of science texts available; an excellent text for an undergraduate class. The focus is primarily after 1650. Where this text succeeds is in its analysis of the social effects of discovery. This is a great primer to other texts that can focus in more detail, such as Charles Gillispie's 16 volume, Dictionary of Scientific Biography, for technical depth, and Anthony Alioto, A History of Western Science for analysis and insight.

I read this book as a requirement for an upper division class in college. This book pulled together everything that I'd been learning: science, art, philosophy, politics. It broadened my view point and showed me that scientific discoveries, philosophical views, art movements--everything we, as people, do influences something or someone else.

Pretty uninteresting stories with the Man of Steel and the Dark Knight living different lives in alternate histories. Nothing new about them, but it does see how comic book writers have run out of creative stories to do with these two heroes.

I liked the Batman story. It was kind of laid out like a movie. The Superman story was a little weak.

I thouroughly enjoyed this collection of new takes on the dc comics mythologies. The piratwe \\ Joker was the best!!!!!

I liked the book for what it did cover but, when the title includes "ATM, IP, Frame Relay, and SMDS explained" I expected the authors to give more than a 50,000 foot overview. The book fell horribly short of the mark especially with respect to IP. IP wasn't even mentioned more than six times in the whole text. If you are looking for an overview of networking technologies this book is "ok" but , if you are looking for a book that explains the technoligies listed in the title this is not it!

Nice & basic, but needs to expand on WAE as it relates to ATM. The evolution of the net will use hodge-podge connections, but there is little doubt that consumers are pushing for "roving" wireless net connections -- which I think will still use ATM @ some "point". The question is, is that ATM point going to grow as a result of consumer mobility? Anyone know of another book (or info) on how to view this from a different viewpoint?

The book has three main sections. One explains network technologies like IP and ATM. The next tells you where they fit into the real world and the third illustrates it.

The style is really nice. It is easy to read, even when some difficult things are being explained. There is plenty of good advice and sharp observation throughout.

Overall, it is a good read and a useful book to have close by. I work with a lot of telecomms people and it has done a lot for my credibility.