Computers Books

This book was a big help in passing my TCP/IP exam, but I do not recomend it as a single source. My strategy, which has served me well, is to read the book once, take a practice test (eg Transender), figure out what concepts you do not get, study those areas of the book, take practice exam, repeat untill you are scoring high on the practice exams. This book work out great for that and it is cheap and a quick read. Perfect.

Only get this book if you're already experienced in the TCP/IP world. Passed the test with flying colors! I used this book to review beforehand. Wished it had a little more practice questions, but overall good material!

This is a great book. Even if you're not interested in takingthe test, this book is worth the price. It seems to cover almosteverything on the test. Buy the book if you want to take the test.

It is a very good book. It is not a thick book, but it contains many materials relevant to the exam, and you can get the main points from this book. I would say its content is even better than other training guide in the market. Of course, it is just a revision book, you cannot get any training from it, just get the facts only. In addition, I also find that its content is even same as the live questions that can help me pass the exam.

If you already know TCP/IP this book will help you slam-dunk the test! Its explanation on subnetting is the best I've seen. If you're new to WINS, DHCP and DNS then you better try another book. New Riders Training Guide on TCP/IP (ISBN 1562059203) is great- know this book and you know TCP/IP on NT! I studied both of these and scored a 966.

My opinion is anybody who gives this book less than five stars is REALLY hard to please or has some pet peeve they can't turn loose of.

I have spent (wasted in many cases) lots of money and time on GA training books in the past and ignored this one for quite a while as "just another book on flying." When I saw the price drop below $20, I decided to take a risk. Wow! This could be the best training book I have every bought. I hate to be dramatic about that but honestly, I probably have fifteen books of this nature and this is the clearest, most well laid out of any of them. I love the way the authors bring FSX into the training as yet another tool to help you practice your technique. The online material (especially the films) are very helpful too. It is obvious these guys did not write this book because they are "professional authors" but because they really do love flight training.

This book is a labor of love and you would do yourself a disservice by passing it by.

I've had all the Microsoft Flight Simulators since 1985 and have always winged it when it came to flying. That works but I never really knew what I was doing. I think this book is the best I've seen so far in helping one to learn to fly with the reasons why. Links to downloadable files are an extra bonus that expand the contents. The author also ties his content in with the lessons in the Simulator Program. Very comprehensive coverage.

This book is what I was looking for and did not find in Bruce Williams'Flight Simulator as a Training Aid. The authors are Real Pilots who have painstakingly incorporated their vast experience into a very readable and often entertaining soup to near nuts FSX-based teaching tool. I have been using the book for the last three weeks in preparation for a ten day intensive IFR training course. The proof of the West Cummings book's success will come with my flying pudding a few more weeks hence when I get checked out. I get the feeling I'll do ok which will be in no small measure due to the comprehensive and well organized approach taken in the book.
Hightly Recommended for real or simulated piloting.

I'm not a "real world pilot", and I am not planning to become one. But this book is a terrific resource if you're into the simulation challeneges that Flight Sim X offers. I've owned every Microsoft FS product since the first one, from the early 80's. Over the years, I've been saddened to see that as each release of the software becomes more realistic, the instruction manual grows thinner and more convoluted to use. This book solves all my "Why does this button do?" questions, with room to spare! It is obviously a labor of love for the authors, and it shows. They write with wit, humor, and above all, clarity. Every chapter of this book contains at least half a dozen or more of those "Oh! Why didn't I know that before?" type of moments. From first flight to IFR, with the concluding chapter on "Virtual Airline Operation", this is the definitive reference and training guide. It won't really tell you how FS functions, but if you want to really learn virtual flight, don't pass this one by! Warning: This isn't a casual read. You're expected to read, learn and practice each skill on your own, using customized lessons downloaded from the publisher's website. But isn't learning how to fly, or fly better, the reason you bought FS-X in the first place?

This book is everything it says and more. A must have for any sim pilot or student pilot who may use FSX or any MSFS series program. Geared toward the slightly more then just "gamer" enthusiast, the book covers almost all areas of flight from the basics to advanced situations which the book actually has links to a website to download flight plans, charts, videos with matching practical flight sessions, and all the pictures in the book in full color.

That is the only downside, is that all the pictures in the book are in black and white. It is a fairly thick book with a lot of information so I could see possibly saving a few dollars on full color ink.

For anyone who even thinks of flying in the future or likes to use Flight Simulators to freshen up their skills, get this book now. It is a must have for your aviation library.

This is a phenomenal book for PS use - I'm sorry I had already bought other books. I'll probably never look at those other books again, and will end up selling them.

I was skeptical of getting a CS3 book since most of the ones I've perused were a bit much, relying on adept knowledge on CS2. This book, however, has been so easy to read and understand, I can't put it down!
It has a wealth of how-tos and information on effective photoshop CS3 editing. Highly recommended!

As a web designer I've been using Photoshop professionally for years. I've also worked on lots of photographs, both my own and those I've gotten from clients. I don't need a how to book on layers, cropping and levels. I've got a good understanding of the basic Photoshop tools, and have benefitted from Scott Kelby's Photoshop CS for Photographers. But Kelby's book is a recipe book both useful and well presented, but I want more.

What I want to do now is take my own photography to another level. Past a certain point, improving becomes less a matter of collecting tricks and recipes and more a matter of learning the entire workflow from experts. For that a basic how-to cookbook is no longer of much use to me. I could probably spend a lot of time working out a good workflow and set of procedures through trial and error, but why not take advantage of the experience of those who have already taken the art of nature photography editing to a high place?

Enter Photoshop CS3 for Nature Photographers. As one reviewer has stated, much of the introductory Photoshop material is covered in other books, but not in quite the same way. Photoshop has many tools, each of which has many settings and options. It's perfectly possible to be familiar with one tool or filter in one context and not realize that it can be used in combination with another tool to achieve a completely different result. I once read that when Einstein proposed his theory of relativity maybe three people in the world understood it. I wonder if more than three people in the world completely understand all of what can be done with Photoshop. What I was looking for and found here is an expansion of my Photoshop horizons, a deeper exploration of the art and science of nature photography and photo editing.

Anon and Grey offer an excellent look over the shoulder of experts in both practice of nature photography and in the use of Photoshop as a digital darkroom. I can't emphasize strongly enough how helpful that approach is for someone who has some Photoshop chops or who has used the program for another end and who wants to get great results with nature photos. Their workflow is time tested and produces excellent results

And nature photograph editing benefits from following a slightly different approach from that of product photography, with which I have some experience, portraiture, photojournalism and so on. Again, I'm struck with how specific and helpful the presented workflow, and the mindset that using such a workflow creates is. And placing editing in context with a specific photographic goal informs my picture taking too.

I recommend this book to anybody interested in nature photography who has at least some experience with Photoshop, though a dedicate beginner could work through the introductory phases with this volume. For someone who has used Photoshop in another context and wants to expand into the nature photography realm this book is brilliant.

I gave this book as a gift, so I am quoting the recipient:
"The book gives a clear, well-written overview of both basic and advanced photoshop techniques geared toward editing nature photographs. One of the strenghts of the book is that it presents the differing views and techniques of two seasoned and highly skilled photographers. The explanations are clear, and the book proceeds logically through the various steps associated with the tools and features of photoshop CS3. A special treat are the beautiful photographs that illustrate the techniques discussed in the book. The methods presented by the authors are not necessarily limited to nature photography, and can be applied to a broad range of photographic subject matter. Very highly recommended."

I bought this book based on several positive reviews and also because of the focus on "nature photography". I was not displeased with it, but I was kind of disappointed. Most of the techniques given were stuff that could be found in almost any of the "how-to" books on Photoshop. Mostly it was just workflow, and workflow for nature photography vs other types of photography is not so different that a whole book can (or should) be written about it. On the bright side, I did pick up a couple of tips and techniques that I hadn't seen in other books. I was also pleased to note that the authors drew a distinction between documentary nature photography and nature photography to "make a pretty picture". They feel that so long as the photograph is not said to be representational of a moment in time, there's nothing wrong with compositing and modifying it to make it more aesthetically pleasing or artistic. Some of the resulting compositions are fabulous, and capture the "mood" of a scene beautifully. Since most readers of this book are likely to be shooting for their own pleasure primarily, this was good information.

Bottom line - if you have other Photoshop CS3 "how-to" books, you can pass this up, as there's virtually nothing that hasn't been told many times over. But, if you're fairly new to PS, focus primarily on landscape and/or nature, and are only going to invest in a couple of "how-to" books, then go ahead and get this one.

This book is easy to read, has good illustrations, symptom descriptions, and suggestions for diagnosis, treatment and prevention.

I found this to be the best book as far as having pictures to show how to do stretches and on good typing technique.

Other books I would recommend are:

`The Repetitive Strain Handbook by Robert M Simon, MD and Ruth Aleskovsky'.

`The Trigger Point Therapy Workbook by Clair Davies'

`Living Better Every Patient's Guide to Living with Illness by Carol j. Langenfeld'.

This book is the single most useful collection of practical RSI information I've found. Highly recommended for anyone trying to figure out how to stop hurting themselves when they're working. I have bought four copies for friends.

"Repetitive Strain Injury: A Computer User's Guide" by Pascarelli is a good introduction for those who know nothing about RSI. Even a cursory search of the Internet will turn up several references to this book as the classic on the subject. It describes what RSI is, what the risk factors are, how to evaluate your physician in terms of his or her RSI awareness, how to treat RSI symptoms, and it offers tips on workstation configuration, typing and mouse technique, monitor settings, and daily living. If you think you have RSI and your first instinct is to go out and buy yourself a wrist wrest and a splint, stop and read this book first, it explains why these amateurish attempts at self treatment are a bad idea. I was disappointed that the book didn't offer more specific advice for actually treating RSI, though I understand that would have been difficult given the large number of causes and manifestations of the disorder. The book claims on the front cover to contain a "seven point program for treatment", but most of the advice for treatment itself consists of "go see a doctor". This is frustrating given the book's repeated claim that most doctors know nothing about RSI or don't even believe in it in the first place. Another thing that really annoyed me was the book's assertion that employers are largely responsible for RSI. The basic message was: "RSI isn't your fault. It's just another example of how `the Man' exploits you in a thankless and mindless job." In my case, my RSI was caused by my own obsessive work habits. The book does list "Driven Behavior" as a risk factor for RSI, but it gets only a perfunctory mention. Another negative is that the book focuses on tendonitis-type RSI, whereas my problem was clearly nerve-related (numbness, weakness, and lack of coordination in hands, forearms, and upper arms). The book that really nailed my problem on the head, and that I recommend as a supplement to this one if your RSI is caused by obsessive computer use, was "It's Not Carpal Tunnel Syndrome!", by Damany, who worked under Pascarelli treating patients for many years.

After years of extreme pain caused by ...poor working conditions ..., I ended up disabled. I found this book four years later. In that time, I had seen two M.D.'s, three chiropracters and two orthopedic surgeons. I was diagnosed as having a pinched nerve.

After reading this book, I made an appointment with Dr. Pascarelli. I was the last new patient he took before retiring.

He diagnosed me as having thoracic outlet syndrome, and wrote up a script of physical therapy treatment for me, which I took back to Ohio and showed to the doctor's here. I still live in constant pain because of permanent muscle damage in my upper back because this wasn't diagnosed sooner, but at least the pain is bearable. I also have problems using my arms and hands. But, today I'm partially disabled instead of totally disabled.

Maybe, if one of the doctor's that had examined me before had Dr. Pascarelli's knowledge, I wouldn't be living in pain today. Or, if I had the knowledge this book provides....

If you use a computer, read this book and follow the advice. You don't have to end up living in pain.

Excellent high-lvel book for anyone involved with software development and implementation. This book digs deep with enough details of security in coding and testing practices and how to avoid security related bugs and vulnerabilities. The book also does well in terms of secure coding, white box and black box testing very well.

Few things where this book falls short "Ignorant" to emerging application landscape and the coding complexities in a multi-platform and application integration environment - J2EE, .NET, XML Web Services and SOA. I am sure, the author will agree on those gaps hopefully we see in the next edition of this book.

The book deserves 5 stars for the concepts + illustrations and 3 stars for those keen on development details for distributed applications.

A required reading for anyone involved with software development and implementation. This book drills-down to security in coding and testing practices and how to avoid security related bugs and vulnerabilities. The concepts illustrated on secure coding, white box and black box testing are excellent. As a developer/architect, I thoroughly enjoyed this book and I suggest to everyone who wants to get started on secure coding and testing practices.

Couple of things I QUIBBLE with are... the book does'nt realize the emerging issues and how-to's for build/refactor security for distributed application proliferation as your it - Portals, Web Services and SOA. The way we develop software is changing, the applications are becoming more pervasive and no-longer contained standalone to a system which makes the built-in security brittle impeding the agile business requirements for application/process orchestration, b2b federation and Web based application mashups. I am sure, the author will realize those gaps in the next edition of this book.

Havingsaid - This book is still a must-read for the budding security developer who wants to focus on secure programming and testing.

What is MISSING - You will not find answers for how you do secure web-centric applications, XML Web services - message-level security, identity federation and other b2b application complexities.

Software Security is the best book for learning to integrate security throughout your software development lifecycle. It contains all the security material that is missing from software engineering books. The author understands that your software development lifecycle is different from his, and so focuses on seven touchpoints that can be introduced into any software development lifecycle, instead of attempting to sell you a new lifecycle. He also understands that no matter how important security is to you, you can't change everything about you develop software tomorrow, so he introduces the touchpoints in order of effectiveness based on his extensive consulting experience, starting with tool-assisted code reviews and architectural risk analysis.

If you're a software developer, Software Security is an essential book to have on your shelf, and you'll also want a secure programming book like Secure Programming with Static Analysis (Addison-Wesley Software Security Series) or the author's own Building Secure Software: How to Avoid Security Problems the Right Way.

The root cause of many security vulnerabilities is poorly written software. Often, software applications are written without security in mind. The logical, yet elusive, solution is to ensure that software developers are trained in writing secure code.

Software Security: Building Security In is a valiant attempt to show software developers how to do just that. The book is the latest step in Gary McGraw's software security series, whose previous titles include Building Secure Software and Exploiting Software.

In past decades, writing secure code was left to the military and banking industry. Today, with everything on networks, all sectors must get into the act.

Much of the problem is that organizations target their security elsewhere--specifically on networks--rather than on software. But so many malicious attacks are directed at software that it is foolish to leave this vulnerability exposed.

McGraw goes into detail not only about writing secure code but also about key related areas, which he terms "the seven touchpoints of software security."

These points comprise code review, architectural risk analysis, penetration testing, risk-based security tests, abuse cases, security requirements, and security operations. A major portion of the book effectively discusses these "touchpoints," making the work a recommended tool for inculcating software developers with a security mind-set.

I read six books on software security recently, namely "Writing Secure Code, 2nd Ed" by Michael Howard and David LeBlanc; "19 Deadly Sins of Software Security" by Michael Howard, David LeBlanc, and John Viega; "Software Security" by Gary McGraw; "The Security Development Lifecycle" by Michael Howard and Steve Lipner; "High-Assurance Design" by Cliff Berg; and "Security Patterns" by Markus Schumacher, et al. Each book takes a different approach to the software security problem, although the first two focus on coding bugs and flaws; the second two examine development processes; and the last two discuss practices or patterns for improved design and implementation. My favorite of the six is Gary McGraw's, thanks to his clear thinking and logical analysis. The other five are still noteworthy books. All six will contribute to the production of more security software.

Gary McGraw's book gets my vote as the best of the six because it made the biggest impact on the way I look at the software security problem. First, Gary emphasizes the differences between bugs (coding errors) and flaws (deeper architectural problems). He shows that automated code inspection tools can be applied more or less successfully to the first problem set, but human investigation is required to address the second. Gary applauds the diversity of backgrounds found in today's security professionals, but wonders what will happen when this rag-tag bunch (myself included) is eventually replaced by "formally" trained college security graduates.

Second, Gary explains that although tools cannot replace a flaw-finding human, they can assist programmers trying to avoid writing bugs. Gary is the only author I encountered who acknowledged that it is unrealistic to expect a programmer to keep dozens or hundreds of sound coding practices and historical vulnerabilities in his head while writing software. An automated tool is a powerful way to apply secure coding lessons in a repeatable and measurable manner. Gary also reframed the way I look at software penetration testing, by showing in ch 6 that they are best used to discover environmental and configuration problems of software in production.

Third, Gary is not afraid to point out the problems with other interpretations of the software security problem. I almost fell out of my chair when I read his critique on pp 140-7 and p 213 of Microsoft's improper use of terms like "threat" in their so-called "threat model." Gary is absolutely right to say Microsoft is performing "risk analysis," not "threat analysis." (I laughed when I read him describe Microsoft's "Threat Modeling" as "[t]he unfortunately titled book" on p 310.) I examine this issue deeper in my reviews of Microsoft's books. Gary is also correct when he states on p 153 that "security is more like insurance than it is some kind of investment." I bookmarked the section (pp 292, 296-7) where Gary explained how the "19 Deadly Sins of Software Security" mix "specific types of errors and vulnerability classes and talk about them all at the same level of abstraction." He's also right that the OWASP Top Ten suffers the same problem. Finally, Gary understands the relationships between operators and developers and the importance of security vocabulary.

I was pleasantly surprised by "Software Security". I reviewed an early draft for Addison-Wesley and wondered where the author was taking this book. It ended up being my favorite software security book, easily complementing Gary's earlier book "Building Secure Software." In my opinion, Gary is thinking properly about all the fundamental issues that matter. This book should be distributed to all Microsoft developers to help them frame the software security problem properly.

This book is easy on Beginners. Load Linux to your machine and work on the examples. You will become good at it.

The format is good and you eat one bite at a time.

I found this book has some useful tricks that compensates for the chapters that maybe useless to someone who been using UNIX for sometime. This book made my life easier since I needed a book where I can get some of the useful Unix commands yet a little description with it to help me get by

I like easy to read book and I also assumed that learning UNIX is not necessarily has to a struggle. This book stood up to my expectations almost perfectly: it is very well written and clearly expressed work. It does not overwhelm with technical details and does not press too much. I followed an advise in some review and purchased Linux and UNIX for a beginner training suite, 4DVDs + 2CDs includes 4 Unix Academy Certifications ed.2008. These two nicely complement one another. You watch it and you read it. If you didn't catch it from the first try you watch it again and read it again. In two months I found myself confident to that extend that gave advises to our system administrator and he accepted them because there were subjects that he wasn't completely sure. It is a way to start.
I can't overstate how much I have learned from them. Don't be naive, though. You will have to learn and memorize many things. The fact of owning neither book nor DVD will not make you knowledgeable, but if you will work it trough, trust me, you will surprise many people around!

The book is a real help when you struggle with new operating system's commands and horrible command line syntax. I paired this book with "UNIX Essentials" DVD and can't be happier! Book shows conception the DVD shows complete workflow! WOW! That is really smooth learning.
The book is very well logically organized and easy to navigate and it is free from stupid repetitions that many other books have!

The book is easy to use and understand, good choice for beginners, but might be a bit wordy for advanced users.

Its structure is very similar to a reference book, runs along the UNIX commands in 17 chapters, and provides enough information and examples to their usage. It contains three appendices summarizing the UNIX files and directories, the UNIX commands and their flags. It contains no theoretic essays at all, so if you are interested in the inner working or philosophy of UNIX, this book is not for you.

I liked that it uses a color (red) to distinguish the commands and flags from the output. I was glad to find links to the related topics inside the book, but missed a bibliography. And I missed one or more full chapters paying attention to the most popular implementations such as Solaris, AIX.

An excellent book full of immediately useful tips to turn any business presentation into an interesting presention. Trying to put to death the idea that if the presentation isn't boring no one will take it seriously. Tom shows readers that even important topics can benefit by interesting presentations. A must for every business library!

Wow! Tom Antion did it. "Wake 'em Up! is a masterpiece. This is a 'must read' for anyone who speaks before an audience, regardless of the size. His tips will both keep you out of trouble and guide you toward mastering the art of public persuasion. Be careful, if you do what he suggests, you might start getting 'too many' speaking invitations. -Edwin Richard Rigsbee, Professional Speaker

Wake "Em Up is a complete source for everything you will ever need to know about making a great presentation. Whether you are a professional looking to move to the next level or just need to make a great presentation to your boss this is the book to get. Easy to read. Easy to use. Easy to love!

This book will not help you tell jokes. It describes how to make your presentations more entertaining. Tom Antion's secrets on room setup and how to open a speech are worth more than the price of the book. Whether you are speaking to a large group or to a small sales meeting, the tips in this book will help you get your point across.

For coverage, click on Table of Contents in the left-hand column of this page.

Tom Antion is a marketing genius who teaches speakers how to speak and how to sell themselves. A gifted professional speaker, he shares his years of experience in these pages.

As a professional speaker and the author of 113 books (including revisions and foreign-language editions) and over 500 magazine articles, I highly recommend this book to anyone who has to get their point across to groups. DanPoynter@ParaPublishing.com.

If any American leader is known for using wit and humor in difficult situations, it is John F. Kennedy. He knew that ANY situation can be made palatable with the proper use of humor. I approached Tom Antion's book (and videotape) with the same skepticism I use in all such purchases and was very pleasantly surprised. Tom has produced a basic reference work that will serve in any situation. I'm sure it would have been in JFK's personal library, just as it is now in mine. In preparing JFK and leadership speeches for delivery anywhere in the world, I routinely consult Tom Antion's reference works. I recommend them in any format as the foundation for a professional approach to communicating with others.

Francis G. McGuire, Director, John F. Kennedy Leadership Series (tm)

This is the wrap-up volume of the author's "Bromeliad" trilogy (the title of which has to do with tiny Amazonian frogs living in tree-top flowers, who know nothing about the world at large, or even that it exists) -- though it runs parallel, actually, to the second volume, which followed the exploits of Grimma and the nomes who stayed behind at the quarry while Masklin and a couple of others went to investigate the nearby airport. Now it turns out that, in their quest for the Ship waiting for thousands of years somewhere out in space, the three bickering adventurers have managed to stowaway aboard the Concorde and have gotten to Miami and then to Cape Canaveral. There, they meet other nomes, much more widely traveled than themselves (thanks to migrating geese), get close to a rocket launch, and make use of the Thing to contact the Ship. As always, Pratchett tells a delightful, very humane story with lots of humor (the nomes tend to be VERY literal), while at the same time commenting on subjects like interspecies relations, religious dogma, and the whole point of society. Written for adolescents but enjoyable for any thinking reader.

DON'T READ THIS BOOK INTILL YOU READ THE FIRST TWO BOOKS IN THE BROEIMLEAD TRILOGY. This book is about when Masklin (a nome) trys to find this one ship that while supposedly send the nomes to a different planet. This ship is faster than light. The one thing that leads them their is a thing. This thing is like a box with lots of electric inside, and only if this thing is by something that is powered by electric it works. Now in this book Masklin, Gurder, Angalo, and the thing go out to find the ship. At the beginning they fly on a airplane to Florida. When they get their they find more nomes (which they never knew that there was any other nomes). Now they have get the ship to them somehow. Read this wing of a book to find if they find the ship.

My Dad has been reading Terry Pratchett books and he thought I'd like this one. He was right! You should read this book , because it is very funny and exciting. The book is about three nomes that got stuck on Earth and need to take a space shuttle home. The nomes get a lot of useful help from Thing, a machine. But too bad when Thing runs out of "pow" (power)!
I don't have the first two books from this trilogy but I am getting them next!

Wings is the third and final volume of the Bromeliad (following Truckers and Diggers).

Masklin, Gurder and Angalo have just left the quarry and are heading to the airport in hope to go to Florida, where they can put the Thing on a space shuttle so that it can call the Ship. Following Grandson Richard, 39, they board the Concorde.

What somewhat surprised me with Wings is that it's not only the conclusion to a tremendous adventure: the story really gets a level deeper, as the relationship between the nomes and the Thing develops. And don't worry, you still get those hilarious puns such as the one about frogs who have "such a tiny life cycle it still had trainer wheels on it"!

The Bromeliad trilogy is a gripping story, extremely funny and easy to read, but it's also a story about how the world around you can always amaze you if you only look a bit further than just at your direct neighbourhood. I highly recommend it to both children and grown-ups alike!

The Bromeliad trilogy soars to a grand finale with "Wings," the companion volume to "Truckers" and "Diggers." This tale runs parallel to the second book of the series, and brimming over with Terry Pratchett's usual wit and satire... and a mild dose of insanity.

Now that humans are returning to the quarry where the tiny nomes live, the nomes must somehow find a new place to live -- and fast. So Masklin is following the instructions of the Thing (a computer who is smarter than all the other characters put together) and going on a secret mission with Angalo and the Abbot to Florida.

After they sneak aboard the Concorde, freak out the stewardess and hijack the plane, the nomes learn that none other than Richard Arnold (grandson of Arnold Bros, founder of The Store) is on board. Now they must somehow send the Thing into space, so it can contact the spaceship and whisk the nomes away. Easy? No way.

Technically, anybody who has read the end of "Diggers" will know exactly what will happen in "Wings." But like flying on the Concorde, it's the ride that's half the thrill. "Wings" is a little tighter and funnier than its predecessors, partly because it has a much smaller cast -- the small bickering trio, plus the Thing. It doesn't get much better than that.

The nomes are fun protagonists, partly because they're so likably naive about the world in general. If they were left alone, they would probably produce a cute little civilization, and their naivete produces plenty of entertaining humor (Concerning the sound barrier: "All right, own up. Who broke it?"). Pratchett manages to make us laugh with the nomes, not at that.

The long-suffering Masklin has a new slew of problems the moment he leaves, ranging from the Thing refusing to talk to him to Angalo razzing the stewardesses. Atheistic Angalo and the abbot just avoid biting out each other's throat. But it's the Thing's dry, superior guidance that really steals the show.

Pratchett brings his Bromeliad trilogy to a close full of action, suspense, and frogs. A witty and wild ride on the Concorde, and not one to be missed.

Vacca's new book provides a comprehensive overview of the emerging wireless data technology. The book is geared toward experienced Internet professionals who need to learn how to install wireless networks quickly. It provides numerous hands-on examples, such as an access network protocol, and useful discussions about issues such as the implementation of homeland security (currently most available protocols and products have huge holes). A large portion of the book is devoted to the design of wireless networks, dealing with issues such as standards, robustness, ease of installation and use, and, of course, security. Detailed schematics demonstrate typical filter and uplink applications. The final chapter offers a series of recommendations to support Vacca's assertion that wireless technology is the key to the future of communications and concludes that future networks will require a new methodology that integrates all layers of network design. The book is organized to move from an overview of this emerging technology through the planning and design, installation and deployment, and configuration phases. It also supplies advanced solutions to wireless design problems and new directions of the technology. Altogether a must for those people who are charged with implementing this type of network in their organizations.

This is the practical stuff you can't ever learn by going to grad school.
Wonderfully comprehensive and chalk full of highly useful information for today's high tech world. Wireless Data hits every conceivable corner of wireless technology with a well balanced mix of overview, technical depth, and hands on applications. The diagrams and illustrations are very well done. Highly recommended for the spectrum of tech managers, network engineers, and technicians. This book will be a mainstay for my reference library.

Vacca provides a unique value in his books in allowing the reader to drill down to the technical level required. This one is certainly no exception. His top-level scenarios are enlightening and encourage you to leap onto the technological bandwagon, but I particularly appreciate his caveats - particularly where he indicates what standardisation or legislation is required within the industry, as well as his very specific cautions against over-design within your application. Subsequently, he proceeds into the technical rationale for such limitations, and where it can be bypassed or overcome.

As I have spent the majority of my applications career interfacing between management/marketing ideals (necessary for progress) and technical viability within the available staff (typically pessimistic after the first few confrontations with external technical reality), I sincerely appreciate Vacca's substantiated presentations of current viability, emergent solutions, and futures.

JohnVacca has again written a book about a subject that has great application in the near future. As notebook computers are fast replacing desktop computers and as flat screen monitors are replacing CRT monitors, wireless data is replacing data transmission via cables of different types. Several companies have already replaced their local networks with wireless networks at work place where their employees can move about the work place and be connected to not only the company's Intranet but also the Internet. This book provides a good explanation in the understanding of wireless data transmission and the challenges for companies that provide wireless transmission to improve this technology as more companies and organizations will soon depend on this application to conduct business.

I have added also this new book by John vacca to my Company library. Practically all of John books end up being used to train all of our employees . You did it again John!
Keep at it , you are the best

Tullio Bortoletto

Jesus christ, i can't think of how many times i've referred to this book over the years, and i don't think i've even covered 1/3rd of the material. If you're a self-taught access programmer, you can only get so much from google searches and developers' forums. If you want to learn new concepts in depth and generate ideas for how to be a more effective programmer, i can't think of anything more helpful than reading this book one chapter at a time. For example, I wanted to learn about ADO, so I read the chapter on ADO. Without any specific goals, I read the chapter about forms and learned to substantially increase the user-friendliness of my forms. In general, this has made me a better "modular" program, and I think in terms of re-usable functions rather than task-by-task code.

Getz' writing style is remarkably lucid, and there's an example in writing and on CD for just about every concept he teaches.

i bought the paperback version and now that the binding has come apart i keep the book in about five or six different places. i also broke the straps on both of my south american backpacks trying to carry this book (each volume is about 1500 pages long...) If you're going to be programming Access for a while, i'd recommend getting a hardcover edition.

If you need to know anything about access 2002 this book has it! i use it all the time

What do I mean by the "gold standard?" As a professional Access developer, I use a lot of reference materials. Besides the Internet, my bookshelf is full of Acces, SQL Server, VBA, T-SQL, and Office reference books. But there is one publication that I always check first when I'm perplexed or curious. It's my gold standard if you will allow me that hyperbole. I'm speaking of the Access 2002 Developer's Handbook, published by Sybex.

Versions of the Access Developer's Handbook have been a staple of professional Access developers since the early days of the Microsoft Access product. My first attempt at serious Access development was during the days of version 1.1. Was that 1993? My team and I recognized the importance and power of this new Windows database product and started to build marketing applications using Access and macros(!) in Windows for Workgroups 3.11. I discovered a copy of the Access 2.0 Developer's Handbook as we migrated to Access v2 and I never looked back. I could not believe the wealth of information in that single volume. I didn't understand much of it, but that was the beauty of it. Here was a reference that revealed secrets and held promises of knowledge to be gained for the inspired reader. Incarnations of this book have remained at my right hand since the first day I opened it.

Whether you need to know more about tables, queries, forms, reports, collections, SQL, relational design, Jet security, multi-user issues, networked databases, or whatever, the Access 2002 Developer's Handbook is the reference for you. It's currently published in two volumes, Desktop and Enterprise editions. Buy both as a set. Combined, they are the gold standard of Microsoft Access reference materials.

Without question, the finest books available on Access database programming. I've purchased (and held onto) each edition since 95. I really cannot express in words my enthusiasm for this series. They aren't traditional 'learner' or traditional reference books, but they meet both needs -- read them once and refer back to them for years. Full of code samples that drop easily into your applications. If you work with Access on a regular basis, you REALLY, REALLY NEED TO HAVE the Access Developer's Handbook set.

If you are just a beginer you might find parts of the Developer's Handbook set difficult to understand, but as you enhance your skillsets you will find these to be a must have. For a serious Access Developer these books are a definitely a must have. I've written in-house applications for years since Access 2.0. Now, I'm writing commercial applications using Access 2002 and the Developer's Handbook set has been a tremendous resource. It covers things you just have to know if you are going to create serious and dependable software applications using Access. Plus, the files that come on the CD's come with code samples you can really make use of. Of all the people I've read of in the Access Industry, these guys are masters of Access. I'd listen to anything they have to say. They know their stuff, big time.