clear text and good arrangement of information made it easy to get a grip of what ent realy is .
great as a companion in your clinical round .
and for speady revision before your oral exam .

Good book, but I whish it had more quotes from Napoleon's writing. Great for entrepreneurs, technologist, lovers, expats... for people who live life on the edge of complete success or complete failure, thinking only of the past of future, but never the present.

This is one of the many Nigel Short books that were published at the time of his championship match with Kasparov. Short was crushed in that match and his books fell into remainder status almost overnight. Hes a strong attacking player who gives all but the best players a very difficult time- against Kasparov he had little chance because of the difference in experience Kasparov brought to that match. Short is rated as the strongest British player ever, ahead of Mickey Adams. Adams has ceased to progress and Short has had a longer career, which ended the day he lost to kasparov. Since that day Short has disappeared from public view. hes gone and all thats left is this book. This book by Martin contains about 50 Short games, a dozen or so deeply annotated. Good games collection of the play-offs with Timman, Karpov, and Gelfand, leading to Short's match with Kasparov.

I read the reviews here and bought this book hoping to learn to use PSP7 to make exciting Web graphics. Aside from a couple of useful chapters, I found the book lacking in substantial information. The writing is very dry, like a text book. Further, the graphic samples used to illustrate this book are amateurish and...well, just awful.

The tutorials in the Getting Started book that came with PSP7 are much more useful than what is found in this book. I was hoping that Paint Shop Pro Web Graphics would serve as a great supplement to the documents that came with PSP. Unfortunately, I was disappointed.

Software developers are often graphically challenged. We spend a great deal of time pouring over code and usually turn to the artist-types when we need graphics for a web site. But if the artists are not available and you need a basic graphic fast, what do you do? For Paint Shop Pro users, you turn to a book like this for help.

A graphics expert might find this book lacking in detail, but it was perfect for my needs. In addition to describing the basics of Paint Shop Pro, topics such as creating backgrounds, making buttons, and working with layers were all covered. There is also a section on retouching digital photos, something even the casual hobbyist would find useful.

The book itself is an attractive publication containing an extraordinary amount of full-color illustrations. My only complaint was that a few topics could have been covered in a bit more detail. Perhaps a few more web design tips would be a nice touch as well. Those were the only items preventing me from giving the book 5 stars.

I'm developing some Web-based training and needed to reduce the file size of some graphics. With this book, it took me 15 minutes to learn how to do this. The book has lots of other practical advice for creating and modifiying graphics and photographs for the Web. I, who have absolutely no artistic ability, was even able to create a fairly decent Web page with a bordered background and buttons and other fancy stuff. Be aware, though, that this book is not for Paint Shop Pro beginners--you really need to know a little about the program before you jump in.

I picked up this Rough Guide to Italy for a brief trip to Umbria and Lazio because my local shop sold out of the Let's Go equivalent.

It annoyed me intensely.

Firstly, it is unreasonably negative in tone throughout - someone who hadn't been there could be forgiven for thinking Italy is a crummy place with only a few mouldy monuments and the odd fresco to recommend it, which as a general impression is criminally wrong, and it's astounding that a guidebook should set out to give it. P>Secondly, Some of the maps aren't accurate and don't appear to have been checked or proof read. Throwaway lines such as "[the tourist office has] lots of reasonable but characterless rooms on their books and appartments to rent" on the basis of my anecdotal evidence simply aren't fair -

Thirdly it's dreadfully turgid. Cheeky charm in a guide of this sort is obligatory these days, but the writing style is frequently leaden. Witness the following insight, which is typically put: "Of all Italy's historic cities, it's perhaps Rome which exerts the most compelling fascination." Good grief.

Plus points - the "contexts" section, which overviews art, architecture, history, and the political and social set-up in italy (you know, the mafia, camorra and all that good stuff!), is a good read. There are plenty of maps of little places, too, but they're not collosally accurate. There are a few fairly uninteresting colour pics, but for my money they could have been left out and a buck shaved off the cover price.

There must be better guides to Italy than this.

Now, a lot of people want their guidebooks to be long lists of hotels plus a list of the authors' idea of the most important places. If, however, you don't plan your itinerary ahead, so you always seem to end up at the hostel cause that's the only open place left, accomadation listings are less important. Let's Go usually has more extensive budget sleeps, but neither it nor Lonely Planet can compare for the coverage of out of the way places. Some people want a guidebook with lots of pictures to show them where they want to go. Rough Guides you have to read, and you have to read them carefully. There's a certain skill involved, because they don't show a strong ranking of "desirableness," and they don't shy from the less-perfect sides of what is, after all, a real, contemporary country, not a museum. The upside (and it's a big upside) is that you can find places that never make it into the other books. I was in Italy last summer, and I spent days in Gubbio (in Umbria), and Peschici (in Puglia). When I'd talk to people in hostels later on in big towns, they would never have heard of the places I'd loved, because they weren't mentioned in their guidebooks. There is so much more to Italy that what you can get out of an Insight Guide or a Let's Go, and you owe it to yourself to find some of it. Sure, it's heavy, and some of the maps are inferior, but there are a lot of them, and they're for places Let's Go has never seen.

The majority of reviewers have missed the point. This guide is a very useful, functional and easy to use guide in travelling around Italy. The guide concentrates on the basic stuff - the major things to see and do, hotels/accomodation, getting around. It's style is entertaining, which is very useful, especially sometimes when you are waiting for a train or bus that never arrives, and its necessary sometimes to have a sense of humour when traveling. The guide came in extremely useful. Its only draw back is its size, and its sometimes not recommended to drawn attention to your self when you need to pul out such a thick tourist guide.

This book consists of an introductory section followed by three parts covering three major divisions of linguistics. Part 1, "Sounds" (chapters 1-7) covers phonology; part 2, "Words" (chapters 8-16) deals with morphology; and part 3, "Sentences" (chapters 17-26) is about syntax.

Part 1 is particularly difficult for the typical American reader because most of the English language examples are based on Received Standard pronunciation (or something near enough to RS to be less than illuminating for one brought up to speak a dialect close to Network Standard).

But worse by far than that is the authors' lack of understanding of how the English language works. For example, on page 227 is the following sentence: "Additionally, . . . "I dog Bill" and "Bill dogs me" are interpreted quite differently, and these different interpretations are due to the choice between nominative "I" and accusative "me" and the related choice between "dog" and "dogs." (because I cannot italicize here, I have put quotation marks around words that are italicized in the book.) Once upon a time, several centuries ago, case inflections of pronouns had some grammatical significance in English, but English has since evolved into a positional language. In modern English, direction of action is determined solely by position, and the remaining vestiges of nominative and accusative case inflections have no grammatical significance whatever. The only case inflections that retain any grammatical significance are the possessives, and in some dialects of English even those are disappearing.

The third and final part of the book discusses syntax, and features an altogether ludicrous reclassification of the components of sentences. If the authors were to describe a house like they describe the structure of English, the living room might be viewed as subsidiary in importance to the coat closet, and the kitchen and dining room as minor adjuncts to the pantry. Auxiliary verbs are accorded more importance than content verbs. Here we find no Noun Phrases; they are called Determiner Phrases if they contain no case marker, otherwise Prepositional Phrases.

For an introduction to the fascinating subject of linguistics, as Consumer Reports might put it, there are better choices.

I found this book to be a decent survey of Linguistics. It is written at a higher level, assuming the reader already knows a bit about language, which I appreciated, yet is not so complex you cannot follow it. Obviously a graduate level read. I recommend it for anyone who is brushing up on linguistics and already has a background in it. It is an overview with more depth than typical linguistics books.

Nice images of interior design as presented and rendered by designers from around the world. Some of the interior work was a little over the top and therefore not suitable to everyday living.

The book explains the fundamentals for design and methodology of SOCs. It also addresses the design reuse concerns. However, the book does not cover practical examples of SOC design and does not explain the difference between ASICs and SOCs.

The editor, Andrew Ross, describes this book as "an expanded edition" of a special issue of the journal "Social Text". Potential readers should be warned however that it is also an expurgated edition, from which Alan Sokal's celebrated parody of of recent socio-cultural jargon has been suppressed. One understands Professor Ross's chagrin at the cruel and unusual joke that Professor Sokal practised on him. However, the unadvertised deletion of Sokal's contribution is a hoax on the buyers of "Science Wars" who naturally expect to find in it the one item of the original publication that has received worldwide attention.

The subsequent reviewer found the current tome missing in scholarship, merely by not having reprinted Sokal's piece from the social text issue of the same name (science wars). If one cared to read through the book, however, one would notice a number of quite specific reasons for this: among these that the book is meant as a counter argument to Sokal, Levitt & Gross's readings of their fave foe: pomos and other dangerous 'leftists' (what does this mean?). It is no secret that these authors are fired by a profound hostility and unwillingness to engage with the material with which they are dealing. This has already been shown ad nauseam in the litterature (see for instance Callon's review in social studies of science). Nevertheless this book stands as a nice response to some of the worst nonsense that has come out of the sokal/gross tradition. Specifically one should not miss Hart's devastating analysis of Gross et al's 'scientific neutrality' and their analytical abilities in Higher Superstition. Other pieces such as Mike Lynch's are good too; some however, are merely perpetuating the current stand off in a nasty 'war' (among these both of Ross's pieces). So is this review, I presume. That said, I should stop. Read both sides before you judge, you might get to know a good bit about rhetorical wars from the putatively neutral and objective scientists (sokal, gross, koertge etc).

Read the Microsoft documentation instead. This book is a thinly disguised rip-off of the Microsoft documentation padded with examples of dubious value. In 590 pages this book manages to add no value or information beyond the original documentation. That's quite an achievement.

If you want to learn ISAPI...think again. This was "hot" 2 years ago...now it is all but dead.

ISAPI's big promise was better performance and memory usage...ironic that it has now fallen in favor to the biggest performance pig of all web applications...ASP. In an age of fast machines and small web apps, rapid development and ease of use wins out over performance.

ISAPI is hard to learn, harder to get right, unstable, bug ridden (if written in MFC) and surprisingly inflexible.

Look, you're a smart person. You want to do the right thing. You don't need to subject yourself to the torture of learning ISAPI. Only hard-core programmers who are tasked with writing a custom web app that is going to get some VERY heavy traffic should even bother with ISAPI.

So why did I give this book 4 stars? There are no good ISAPI books out there. This one has the most information in it and will allow you the best chance to actually develop something that works. Get this book and hit Genusa's (now dusty) ISAPI site. Also spend a lot of time in the Microsoft knowledge base...there are plenty of workarounds and bugs to learn about too.

Keep in mind that with ISAPI you had better be a damn good programmer. If your DLL ever crashes...bye bye web server. This is harder than you think if you are doing "serious" web programming which includes database access.

Smart managers will not allow mission-critical web apps to be developed in ISAPI by a web punk who has never done this before. Do everyone a favor and get a clue. There is a reason why nobody is doing this stuff anymore!

Game over. Go home and don't look back. Go off and learn ASP and Cold Fusion like a good little web programmer. You will have a marketable skill and will actually get things done.

ISAPI is Microsoft's approach to adding capabilities to web serving. There are only a few books that describe how to use ISAPI. This book is the best of them, because the author: 1) provides examples in both C and C++, and 2) compares ISAPI with CGI solutions. Unfortunately, ISAPI is a complicated subject, so more and shorter examples would help elucidate the reader.