Microsoft Books

This was a great book both for me and my team. I've been in the software industry for many years. I started building a team of developers and needed an easy way to bring novice and experienced programmers together on a similar set of standards. This book provided us with the perfect framework from which to start our team. We've developed several major projects using the principles in this book and have experienced a great deal of success.

One warning, the book gets a bit tedious after the first half. If you're looking to improve your C programming skills, it gets really detailed into pointers and other fun, or not, stuff. Also, the examples are in VB.NET...but you still get the point.

If you're an experienced software developer or a newbee in the world of commercial computer programming this book will give a good kick in the right direction. Steve McConnel will keep you hooked by mixing the right guiding concepts with real-life knowledge and examples.

I'm currently studying computer science and have been reading this in my spare time. Skip your lectures. Just read this book! If you want to construct software in a timely, efficient, and complete manner--this is the definitive book to read. Not dry at all, Steve McConnell covers topics for all experience levels. Even if you're an experienced programmer, you will learn something from this great piece of literature.

I've only gone through the first few chapters thus far. So pending finishing my reading, I'll update this review. Unfortunately this might never happen as I find myself re-reading portions of the book to pick up new ideas and details for software construction!

it's a book that all programmers must to read. it explain a lot of interesting things about how to made good software!

I started by reading the first edition of this book. I got the second edition when I was almost finished with the first edition of this book.

After getting the new version of the book I decided to continue reading the old one because I found that there are quite a few differences between the old and the new edition.

This is perhaps one of the best books that I have ever read on programming in my life. The author Steve McConnell has put together a book that is independent of what ever programming language that is used. In the authors words. He wanted to write a good book on software construction because he had looked around and had not found any good books out there on the subject. I would have to agree with him there are not a lot of books on good programming technic. There are hundreds of books on this programming language or that programming language.

Code complete is so good that I feel every programmer should read it. It would be best if in the first year of college every single student read the book. I just don't know how it could fit into a regular curriculum. Even if it does not fit that well into a regular curriculum what is taught in this book is probably more important then what most people learn at school.

I like the book and would advise it to anyone that programs.

I am looking forward to the new edition because the old book didn't have much advice about object oriented programming. Mostly because it was a new way of programming when the book was first written and he didn't want to commit much information to it when object oriented programming was so new. He does talk a little about things that are outdated but the book is still one of the best.

I will wait a while before I read the second edition but I expect to be as satisfied with it as I was this one.

Great book that should be in every programmers library.

Very handy cookbook reference for my office bookshelf. I've used it a number of times, and it's more than paid for itself in expediting regularly-scheduled inquiries of our AD structure here at GEICO HQ.

Excellent reference if you work with AD on a regular basis either as an admin or a developer. Each "how to" offers methods for manually performing a specific task as well as (where possible) how to automate the task using code. Should be on every Windows admin/developer's desk.

Overall, this is a great book for reference.

There are a number of areas where I think the book falls short - all of the scripts are very hard coded scripts that don't tell you how to do some functions that would make their scripts actually useful (like "pull the list of users with attributes from a tab-delimited file and create them" or something similar, this would make mass creation of users actually useful, instead of "create user1, user2, user3, etc..."). I think that the writers expect you to be a VB expert (or at least close to it) if you're going to actually make the vb scripts useful.

Most of the scripts are "How to use a script to do the same functions that you can already do in AD with ADUC or another MMC", but I think that the most important thing for me about the book is what it inspires me to think of doing. Things that MS doesn't necessarily expect you to do. I'm still not seeing a way to add sidHistory to an object (MS does it with another applet - there is a way...), but there are so many things in the book that just have me thinking about how you can implement changes to an environment that MS says you can't do. What they really mean is "You can't do that with the GUI tools that we provide you".

I am so glad that this book was recommended to me by a guy I took a class on scripting from. I use this book everyday (almost). I even took it on vacation with me for light reading.

Hard to say in words to adequately describe how much I like this book. I highly recommend to anyone who works with AD.

This book contains very comprehensive explanations and descriptions with practical examples which are sometimes not so familiar with me (I'm a physician.). overall, this is an excellent book and I regret not being able to meet such a book in a way more focussing on medical fields. But this has a critical shortcoming in book-binding. you should not read this book so many times to keep the original shape. that's a reason why I gave 4 stars.

When I study my MBA classes, this book helps me a lot. The book provides essential review of all Statistic knowledge in the beginning of each chaper, and then lead readers use SPSS step by step.
Especially the practical examples and funny illustration, I will say the book is the only one interesting and powerful Statistic book I can find. I highly recommand it for readers work for Marketing, Medical , Engineering , Finance, and MBA classes. The book can lead you to resolve many "real" problems.

The book is excellent in all ways: easy to read, fun to read, easy to understand.

No one likes statistics.... well some do, but it's a necessary evil of the program I'm in. As much as I dislike stats, this book made the computer portion of it much easier to understand and left me feeling better about my abilities in the subject.The Power of Inner Guidance: Seven Steps to Tune In and Turn On

I love this book. It covers everything from the most basic t-tests and ANOVAs to factor analysis. It tells you the basics of what the test is meant to do, what sort of data is appropriate for it and it tells you how to actually run and read the test in SPSS.

It isn't the best book for someone who wants a detailed explaination of how to calculate a statistical test by hand and it doesn't give extensive detail on the assummptions required for each test. Nonetheless, it's a great quick reference book, particularly if you've already had a statistics course and you just need a refresher. Graduate students will find it useful.

What can I say.. I was looking for a book about WPF. I saw many, and many until I found that one. Then I stopped looking for more :)

This book stands out as one of the easiest to read technical books. The book is in color, is divided into many chapters and sub-chapters, and written in a casual style, which makes it very enjoyable to read. The coverage of the content is top-notch, save for the chapter on data binding which I think lacked better examples. I think this book falls into the category of a cover-to-cover read; meaning it is easy to get through the book in a couple weeks. There are other books that I would recommend as a reference book that contain more detailed technical information. If you are new to WPF and are the type to read complete chapters and books, then definitely start with this one.

I have over 25 technical books on my shelf (and those are just the ones I have hung on to). Without a doubt this is one of, if not THE, best technical book I have ever read!

This book really captures the excitement that surrounds WPF and carries that through into a book. They layout is exceptional (colour print is much less tiring to read). The chapters are thorough, especially on the key areas.

As I read through, questions would pop into my head. "Hmmm I wonder how that works?". Then I would turn the page and right there would be a detailed explaination. I was rarely left wondering how things worked, or how pieces fit together.

Don't think - just buy it!

So much is alreay said about this great book, so I will be short. I have read plenty of books aimed at developers, and this is truly the one that have made the biggest impression.

This is a must-have for WPF developers, and I'm sure that this book will become a legend in it's field!

I am new to WPF but an experienced ASP.NET and Windows Forms developer. The book contains much information although, naturally, part of it is a little bit old. However, what most annoyed me was the writing style of the book which I experienced somehow clumsy compared to many other IT books. Although my written English is not the best possible (my mother tongue is Finnish and I live in Finland) I am very sensitive about incoherencies in English text.

A very good idea is using full color printing. It is clearer and can delight the reader!

Osmo Saarela, Finland

I bought the first edition of this book called Programming Windows Presentation Foundation (AKA Avalon) at the PDC in 2005 and read it completely on the plane home.

When I heard the second edition was released I didn't think much would have changed, but this is even better than the first edition. It's twice as big and covers all major (and not so major) topics in WPF (inc. an introduction to 3D and Silverlight).

I think this book will proof to be for WPF what Programming Windows, Fifth Edition is for WIN32 programming.

There isn't much yet on the internet about WPF, so if you want to get started using it, you really need a guide.

Not only is the book a well crafted introduction to WPF, I've just discovered that the downloadable source code makes an excellent companion to the book.

Questions that were not answered in another top-rated WPF book I found answered here... so whatever else you buy, get this book!

This book is the most in depth resource into WPF i have seen. And not just that, it gets to the good stuff that you'll actually use in your code and not just filler or lists of properties that you can get from intelisense. The examples are extremely useful.

The other benefit of this book is that it doesn't just tell you how to do things, but why. This is incredibly helpful in finding the best solution to your specific problem.

Thanks guys! great book!
Ralph

I say to ignore those reviews because they do not refer to this book. This is the second edition published August 28, 2007 with 863 pages. Those reviews are based off of the first edition published nearly two years before (September 12, 2005) and with only 447 pages.

Using Amazon's 'Search inside this book' takes you to the 2005 edition also. That shows only 10 chapters while this edition has 17. Most of the negative comments from the 2 and 3 star reviewers seem to have been resolved.

The biggest strength of this book is that it focus on using WPF programatically, not just laying out XAML. This is extremely useful if you are writing an application for 3D data visualization or a database driven application. You get to learn to create event handlers, generate meshes... all programmatically. I also believe that this book is great, not just as a learning tool, but as a reference guide. It is the most comprehensive book on the subject and a must for the aspiring WPF developer.

If you just want to focus on XAML, however, I will have to recommend "Windows Presentation Foundation Unleashed" by Adam Nathan.

I have a friend that recommended me this book and I have to agree with him that this was a very well written book. Don't let the fact that the title says "Windows NT" discourage you from getting this book. There is a lot of useful information in this book that is still standard practice for scripting in Server 2003. Probably one of the few and only outdated commands in the book is the AT command that was replaced by SCHTASK. Even then, the author goes into detail on how these different commands work and how to use them in your work environment to you benefit. I recommend this book as a learning tool and as a reference for my fellow scripting brethren.

Great book on NT shell commands that Microsoft doesn't even document. Not even "command /?" gives you any help.

Great for reference and to learn.

Although this book was authored in 1998, it is still as relavent today with Windows Server 2003 as it was when Windows NT 4.0 was first released. The fact is that the Command Shell hasn't changed all that much over the years and Timothy Hill's book remains the best guide to using and writing command scripts that I could ever recommend. And with Windows Server 2003's push to be able to do everything from the command line that one can do from the GUI, it's even more important to fully understand how the Windows Command Shell works.

Windows NT Shell Scripting is less about Windows NT than it is about how to write shell scripts. It covers the details of using the Command Shell in interactive mode, its configuration and how the 32-bit Command Shell differs from the 16-bit DOS box. Then it delves into the structure and syntax of the Command Shell language, providing a clear understanding of how the program control features such as IF and FOR work. Finally, it shows you how to create sophisticated shell scripts using the internal commands and external command-line utilities included with Windows and their Resource Kits.

Not everything in this book has survived the test of time. The old task scheduler using the AT command, though still supported in current version of Windows, has been mostly replaced by more powerful Scheduled Tasks of Windows 2000 and later. And you will want to supplement this book with a modern reference of the utility programs available for Windows XP and Windows Server 2003 (such as OReilly's "Windows Server 2003 In A Nutshell"). Yet this represents only a small part of the book and majority of material stands up very well. Certainly there is no better and more in-depth tutorial for building command scripts than Timothy Hill's book.

I like this book because unlike many technical books, the first three chapters aren't a pedestrian introduction to the basic fundamentals. This book spends chapter 1 with insight, similar to the way Applied Cryptography immediately gives you knowledge. I'm an experienced NT command shell user, and this book was valuable for me as well.
The DOS shell has become a requirement and skill relegated to the background by the direction of Microsoft curriculum, this book explains it and teaches it.

The authors instructions are easy to follow, without doting like the Teach Yourself "whatever" in 24 hour books, Tim Hill doesn't waste your time, or your money.

If you have a bit of programming experience, this book together with access to the NT Resource Kit tools will provide you with the foundation for doing almost anything you could imagine within Windows NT Shell Scripting.

The book can be used both as a tutorial and a reference for Windows NT scripting and gives good examples of the commands, tools and concepts covered. For Windows NT, this book does the job as your Shell Scripting Bible in less than 400 pages.

Since Windows NT 4.0, a lot has happened in the Windows scripting field though. With the release of Windows 2000 and the subsequent Windows XP and .NET Server, shell scripting has become much more powerful. A second edition of this book covering the new commands and tools would be most welcome. Until one exists, you might also want to look at newer books covering shell scripting for operating systems based on the Windows NT kernel.

You might also want to look at other, often more powerful ways to script your Windows NT-based environment. For that matter I recommend looking at other books covering WSH (Windows Script Host), ADSI and WMI (Windows Management Instrumentation).

Most books on using presentation software seem to start with the assumption that the software makes sense and that organizing content is the secret to a good presentation. Here, Garr Reynolds strips away those assumptions and asks you to think of presentations as they truly are--visual stories. They're more like movies than books and Garr opens up the possibilities through a radically different approach to designing slides.

The book offers many beautiful examples and an engaging and reflective style that inspires you to create truly impactful presentations. These principles are particularly important for government communicators.

This book will change the way you use PowerPoint. It is a must for developing a great presentation. Excellent examples, great writing, and easy to employ ideas. It has opened my eyes and I will forever be changed in my use of PowerPoint slides. My presentations will be just plain better for the audience.

This book will revolutionize the way you present. It includes invaluable tips on how to plan your presentation, simplify your ideas, tell interesting stories, and put together a presentation that will hook your audience. A must read!

I can't add a great deal to the praise already stated for this great little book. It is a quick, easy read, but you have to read it -carefully-. This is about changing how you think about a presentation, not a checklist or a template for giving presentations.

At work, I cringe through many, many "Death b Powerpoint" presentations, and I get compliments from colleagues on mine. They grasp that there is something different about how I present, but they don't understand the philosophy enough to duplicate it. Get this book and all will be clear.

If you present highly technical information, you will have to modify some of the ideas in the book, because it is essential to make some of the slide more substantial, for instance with graphs prepared from a good graphing program (Something like Igor, NOT Excel). However, this is a minor modification, and the backbone of your presentation can follow the philosophy so clearly expressed in this book.

Very highly recommended.

This book is a must. If you are a Power Point serious user, and recognize that you (and the people in the auditorium) are tired with the "standard" way you do your presentations, you must buy and read this beautiful book. You will read it in hours - it is marvelous. I strongly recommend this one.

Very well written book. Enjoyed reading it, and finished it in two days. John Wood has done a tremendous service to Nepal and Cambodia (two countries in which I used to live and work). Amazing work that needed to be done. Great reading also in the book about some of the inner workings of Microsoft as well. Read this book!

This book had me bawling from the pictures and the vivid description, but more importantly, it inspired me to action. John has a way of resonating with his audience, expressing the importance of the cause, and showing you how your money can help directly. From the first page I didn't want the book to end, and on the last page I wanted to throw a fundraiser to build a library. If you're looking for a motivational and inspiring story, you should read this book. If you're looking to make a difference, you should take action after you finish this book.

I recommend this book for anyone who is interested in making a difference in the world or wants to get off the corporate treadmill. This is the story of one man who did both. He is obviously passionate about Room to Read, and the reader can't help but feel his passion. The only downside is that it reads too much like a lightly-edited journal at times--it gets a bit repetitive toward the end (I heard a lot about his "insane schedule").

I am amazed how inspiring this book is. To go from a high level global job at Microsoft, to something that truely makes you want to get out of bed in the morning is awesome. I am not a big reader, but finished this in 2 days.

This is a great book for anyone...John Woods story of leaving a great career, a girlfriend, and a life of luxury to help make the world a better place is a fun and inspirational read. A great tone of "this isn't for everyone, but was right for me" helps the reader enjoy the story without feeling like they should change the world in the same way. It gives you perspective and food for thought...absolutely fascinating.

Hard Drive: Bill Gates and the Making of the Microsoft Empire

This book is a must-read for people who consider themselves ambitious and driven. It taught me the importance of single-minded drive and determination, coupled with a passion for the line of work one is in. IT is a tough line of work to be in - jobs could be outsourced anytime, skills become redundant quickly and there isn't the glamor or get-fabulously-rich possibility of finance or investment banking... but this book demonstrates that as long as you are passionate about what you do, there is always room at the top. Take heart from it!

This is the definitive Book about Bill Gates (and the history of Windows). It covers all the management aspects of how he drove Microsoft and how the work became his life. The man doesn't do business... He LIVES it. And this book describes it in very much detail.

The details includes how Bill "turned over" IBM... Promissing them the OS/2 under the "NT Technology" flag and how he realeased Windows 95 and killed IBM forever from the Desktop business. It also shows Gates apreciation for Older woman (and many that took him to bed). As part of this "private" package, it also explains the problems that He had with Steve Ballmer. How Ballmer was showing poor management and leadership under Gates perspective and how Ballmer got over it and made his loyalty to Gates forever.

I was more interested on the part that explains how Microsoft Windows 1.0 was developed. How disastrous the first Office was compared to the competition and how they managed to "work around" and fix it, by "coping" the competition and improving it "the Microsoft way".

Buy this if you want to know how business can be done... or be "copied".

I can never figure why an author would write a book about someone they don't like. In the book "Google" by David A Vise, it's abundantly apparent that the author has a huge admiration for Brin and Page the founders of Google. Thus it made for a great book. Hard Drive comes across as a book that was purely written for the authors to profit and I didn't enjoy it half as much as the Google book, even though Bill Gates is my favourite entrepreneur.

Delightful book. Its one flaw is its addictiveness, I couldn't put it down which did cost me sleep (I'm an IT professional with an entrepreneur spirit- your results may vary).

The Microsoft/Gates biography is impeccable in its wealth of interesting details and engaging story-telling.

Bill Gates is a fantastic decision maker. He would be as successful selling water or space suits, he just happened to be at the right time in the right booming industry and pushed with his business-business mentality to the limit. Right decision after right decision, the Microsoft journey is a story that any entrepreneur should nitpick and absorb as much as possible.

Of course, his terrible capitalistic drive is a perfect subject for a discussion on morals, social responsibility and related matters, but without a doubt when it comes to maximizing outcome while playing by our economic rules, Hard Drive tells a tale of epic proportions featuring a superhero / villain that rivals the best of science fiction.

This is really a story of how Gates led Microsoft to its apex, ending in about 1992. It is well written and a good balance bewteen criticism, an explanation of the business model, and historical detail. The story is, to put it mildly, remarkable no matter what you think of MS and Gates.

While a student at Harvard in December, 1974, Bill Gates III and Paul Allen informed Ed Roberts by telephone that they had invented a BASIC computer language for the MITS Altair 8080, which was the first "personal computer" kit for hobbyists. Could they license it along with each Altair kit, Gates asked, to customers for a royalty fee? It was an audacious proposal, because not only had Gates and Allen invented no such thing, but they neither owned an Altair kit nor did they even know the technical specifications for the Intel 8080 chip. Skeptical of their claim, Roberts replied that whoever demonstrated a working BASIC would win the account: Gates and Allen were in competition, he told them, with 50 other "geeks" who already had made the same claim. Gates and Allen then hunkered down for 8 weeks to write the first BASIC for a microcomputer. The resulting "software", which immediately won over Roberts, was the first application of what would become Microsoft BASIC. Gates was 19.

As the company founders, Gates and Allen shared a vision that virtually every home and every office desk would eventually have a PC on them, all operating with their software. To run Microsoft full time, Gates dropped out of Harvard in January, 1977. Their business quickly expanded beyond the Altair as competing brands of personal computers emerged, including the Tandy from Radio Shack and the Apple II computer; they were also called upon to program BASIC into a number of other electronic devices. All along, Gates' goal was to gain market share, in effect setting the software standard for most, if not all, PC users. As a true believer who intimately knew the product, Gates was the principal salesman, while Allen concentrated on technical development.

During this formative period, Microsoft's corporate culture was established. Perhaps as a result of hiring many of his programmers straight out of university, Microsoft's offices (and later the campus in Redmond, Washington) took on the look and feel of a college campus, that is, an informal and a freewheeling intellectual atmosphere with "late hours, loud music, walls full of junk, anything goes dress, Coke, adrenaline, unbuttoned behavior." Employees tended to be very young with a programmer or engineering mentality; they designed their products for tech-savvy customers - male in their early 20s - like themselves, a kind of fellowship for computer adepts. Like Gates, they loved to play with and program electronic gadgets.

Microsoft hired the brightest programmers with demonstrated practical abilities. Employees were also expected to work extremely long hours as a team toward a common goal, not as strident individualists. Gates encouraged them to develop their entrepreneurial passions, forcefully advancing their own ideas of useful products for new markets. Overseeing it all was Gates, who gained the reputation of a harsh and challenging critic with a relentless drive for excellence, whether to beat the competition or out of fear of falling behind in such a fast-changing industry. As the sole remaining founder after Allen's departure in 1983, Gates remained deeply involved in both technical and business details as well as the general direction of company strategy. Nonetheless, as the principal revenue generators, Microsoft's product groups increasingly became the seats of decision-making power, in spite of Gates' active engagement.

At the end of 1979, Microsoft had $US 4 million in sales. Most of these revenues came from BASIC, which enabled programmers to create applications, such as word processing and accounting spread sheets. The level below BASIC and the other languages under development at Microsoft was the computer operating system, which performed the most elementary tasks required to run computers. With the prospect of providing software to IBM for the basic PC it was planning to market for a reasonable price, Gates and Allen began to acquire the rights to, and then develop, software for a computer operating system. Known later as DOS, it again set an industry standard that would enable Microsoft to efficiently develop languages and software applications in a single engineering environment rather than painstakingly customize them for a variety of incompatible operating systems. This would immensely simplify Microsoft's programming process as well as enhance its efficiency.

As Gates foresaw, this was a near-ideal position to occupy at the moment that the PC market was poised to grow explosively with the introduction of the inexpensive IBM PC, which was made of off-the-shelf components and hence easy to copy, or "clone". With the dual ownership of DOS and several major programming languages, Microsoft became one of the fastest growing companies in the world. By 1985, just prior to its IPO, on revenues of $US 140 million, Microsoft had a pre-tax profit margin of approximately 34%, no long-term debt, and cash reserves of $US 38 million. By 1987, the company surpassed Lotus to become the world's largest software vendor for PCs. Gates was on his way to become the richest man in the world, at least for a time.

However, the ownership of DOS and the programming languages would also, critics later claimed, confer an "unfair advantage" on the company. First, the Microsoft applications groups were accused to obtaining "inside information" from the operating systems group, which enabled them to design their products to function more quickly and smoothly than competitors could. Second, because each change in DOS required competitors to supply their latest products to Microsoft programmers to ensure compatibility, critics charged that this amounted to an inside peek into their strategy at the cutting edge of their capabilities. It was a symbiotic relationship that made many outside vendors - independent companies developing applications to run on Microsoft operating systems -uneasy and resentful. Third, DOS programmers were accused by rivals of inserting "hidden bugs" into the operating system in order to hinder the function of competing products, such as the Lotus spread sheet, damaging their competitive position and brand. The resulting negative publicity did a great deal of damage to the Microsoft brand, which began to be seen as the industry bully.

While Gates insisted that he had erected a "Chinese Wall" between Microsoft's applications division and its Operating System's Group, it was not enough to deter the Federal Trade Commission (FTC) from opening a probe into the company for anti-competitive practices that purportedly hurt consumers. By 1991, when the FTC probe became widely known, Microsoft controlled one-quarter of the applications market and dominated the operating systems market with Windows. There was speculation about the imminent breakup of Microsoft into separate companies for these markets, similar to the dismantlement of AT&T. For their part, defenders of Microsoft argued that it was winning because it was better and smarter, presenting its customers with superior products at bargain prices.

This a pretty much where the book stops, which badly dates it. Not only is the story of the anti-trust law suits left untold, but subsequent business developments - notably the internet - are not even mentioned. Thus, this is an excellent early history, but the reader must look elsewhere for more detail. Of the shelf of books on MS, in my opinion this is one of the best, and it was most useful to me for a research project. Recommended.

Since my book is older, it was a used version, the hints are for older things. It does have some helpful tools, but lots of the annoyances, I already knew about.

This book is written in a very easy to understand language. The hints are pratical and should help everyone in some way. Microsoft will not tell you much of how to make your operating system work the way YOU want it to. Steve Bass takes care of that. It is a valuable resource for anyone who has a PC, novice or experienced. I consider myself somewhat knowledgeable about computers and I even learned a few new tricks.

I am still pretty much a neophite where computers are concerned, so I bought this book hoping that it could get me out of the "messes" I'm always getting into. It really DOES help! Thank you!!! Steve Bass, I'm now searching for other books you have written.

This is the first computer book I actually said down and read, cover to cover. It holds your interest, and each tip gets you excited for the one to follow. I call it my AHA book. All the time you read it, you go "Aha! That's the problem!" or "Aha! That's how to get rid of that!". Can't recommend it highly enough.

I've read many computer books, and I have to say this is one of the most informative. More important, Steve provides hundreds of tips to overcome the small (and large) problems of Windows. It's nice to konw that even a well-known computer columnist experiences the same frustrations we ordinary users do. Happily, he willing to share the solutions he's found.

In my first reading, I discovered the answers to at least 7 windows annoyances I've encountered.

And instead of including a cost-raising CD, the publisher has made 100 utility programs available online, a better solution that including them on a quickly outdated disk.

A useful, and often amusing book.

You need it!