CHAPTER 2 PC Components, Features, and System Design 03 1738 Ch02 7/30/04 10:35 AM Page 26
Total Page：16
File Type：pdf, Size：1020Kb
03 1738 ch02 7/30/04 10:35 AM Page 25 CHAPTER 2 PC Components, Features, and System Design 03 1738 ch02 7/30/04 10:35 AM Page 26 26 Chapter 2 PC Components, Features, and System Design What Is a PC? I normally ask the question, “What exactly is a PC?” when I begin one of my PC hardware seminars. Of course, most people immediately answer that PC stands for personal computer, which in fact it does. They might then continue by defining a personal computer as any small computer system purchased and used by an individual. Unfortunately, that definition is not nearly precise or accurate enough for our purposes. I agree that a PC is a personal computer, but not all personal computers are PCs. For example, an Apple Macintosh system is clearly a personal computer, but nobody I know would call a Mac a PC, least of all Mac users! For the true definition of what a PC is, you must look deeper. Calling something a PC implies that it is something much more specific than just any personal com- puter. One thing it implies is a family relation to the original IBM PC from 1981. In fact, I’ll go so far as to say that IBM literally invented the type of computer we call a PC today; that is, IBM designed and cre- ated the very first one, and IBM originally defined and set all the standards that made the PC distinctive from other personal computers. Note that it is very clear in my mind—as well as in the historical record—that IBM did not invent the personal computer. (Most recognize the historical origins of the per- sonal computer in the MITS Altair, introduced in 1975.) So, IBM did not invent the personal computer, but it did invent what today we call the PC. Some people might take this definition a step further and define a PC as any personal computer that is “IBM compatible.” In fact, many years back, PCs were called either IBM compatibles or IBM clones, in essence paying homage to the origins of the PC at IBM. The reality today is that although IBM clearly designed and created the first PC in 1981 and con- trolled the development and evolution of the PC standard for several years thereafter, IBM is no longer in control of the PC standard; that is, it does not dictate what makes up a PC today. IBM lost control of the PC standard in 1987 when it introduced its PS/2 line of systems. Up until then, other companies that were producing PCs literally copied IBM’s systems right down to the chips; connec- tors; and even the shapes (form factors) of the boards, cases, and power supplies. After 1987, IBM abandoned many of the standards it created in the first place. That’s why for many years now I have refrained from using the designation “IBM compatible” when referring to PCs. If a PC is no longer an IBM-compatible system, what is it? The real question seems to be, “Who is in control of the PC standard today?” That question is best broken down into two parts. First, who is in control of PC software? Second, who is in control of PC hardware? Who Controls PC Software? Most of the people in my seminars don’t even hesitate for a split second when I ask this question; they immediately respond, “Microsoft!” I don’t think there is any argument with that answer. Microsoft clearly controls the operating systems used on PCs, which have migrated from the original MS-DOS to Windows 3.1/95/98/Me, Windows NT/2000, and now Windows XP. Microsoft has effectively used its control of the PC operating system as leverage to also control other types of PC software, such as utilities and applications. For example, many utility programs originally offered by independent companies, such as disk caching, disk compression, file defragmentation, file structure repair, and even simple applications such as calculator and notepad programs, are now bun- dled in (included with) Windows. Microsoft has even bundled more comprehensive applications such as Web browsers, ensuring an automatic installed base for these applications—much to the dismay of com- panies who produce competing versions. Microsoft has also leveraged its control of the operating system to integrate its own networking software and applications suites more seamlessly into the operating sys- tem than others. That’s why it now dominates most of the PC software universe, from operating systems to networking software to utilities, from word processors to database programs to spreadsheets. In the early days of the PC, when IBM was clearly in control of the PC hardware standard, it hired Microsoft to provide most of the core software for the PC. IBM developed the hardware, wrote the basic input/output system (BIOS), and then hired Microsoft to develop the disk operating system 03 1738 ch02 7/30/04 10:35 AM Page 27 What Is a PC? Chapter 2 27 (DOS), as well as several other programs and utilities for the PC. In what was later viewed as perhaps the most costly business mistake in history, IBM failed to secure exclusive rights to the DOS it had contracted from Microsoft, either by purchasing it outright or by an exclusive license agreement. Instead, IBM licensed it nonexclusively, which subsequently allowed Microsoft to sell the same MS-DOS code it developed for IBM to any other company that was interested. Early PC cloners such as Compaq eagerly licensed this same operating system code, and suddenly consumers could purchase the same basic MS-DOS operating system with several different company names on the box. In retro- spect, that single contractual error made Microsoft into the dominant software company it is today and subsequently caused IBM to lose control of the very PC standard it had created. As a writer myself (of words, not software), I can appreciate what an incredible oversight this was. Imagine that a book publisher comes up with a great idea for a very popular book and then contracts with and subsequently pays an author to write it. Then, by virtue of a poorly written contract, the author discovers that he can legally sell the very same book (perhaps with a different title) to all the competitors of the original publisher. Of course, no publisher I know would allow this to happen; yet that is exactly what IBM allowed Microsoft to do back in 1981. By virtue of its deal with Microsoft, IBM had essentially lost control of the software it commissioned for its new PC from day one. It is interesting to note that in the PC business, software enjoys copyright protection, whereas hardware can be protected only by patents, which are difficult, time-consuming, and expensive to get and which also expire after 17 years. To patent something requires that it be a unique and substantially new design. This made it impossible to patent most aspects of the IBM PC because it was designed using previously existing parts that anybody could purchase off the shelf! In fact, most of the important parts for the original PC came from Intel, such as the 8088 processor, 8284 clock generator, 8253/54 timer, 8259 interrupt controller, 8237 DMA (direct memory access) controller, 8255 peripheral interface, and 8288 bus controller. These chips made up the heart and soul of the original PC motherboard. Because the design of the original PC was not wholly patentable, anybody could duplicate the hardware of the IBM PC. All she had to do was purchase the same chips from the same manufacturers and suppli- ers IBM used and design a new motherboard with a similar circuit. Seemingly as if to aid in this, IBM even published complete schematic diagrams of its motherboards and all its adapter cards in very detailed and easily available technical reference manuals. I have several of these early IBM manuals and still refer to them from time to time for specific component-level PC design information. In fact, I still recommend these original manuals to anybody who wants to delve deeply into PC hardware design. The difficult part of copying the IBM PC was the software, which is protected by copyright law. Phoenix Software (today known as Phoenix Technologies) was among the first to develop a legal way around this problem, which enabled it to functionally duplicate (but not exactly copy) software such as the BIOS. The BIOS is defined as the core set of control software that drives the hardware devices in the system directly. These types of programs are normally called device drivers, so in essence, the BIOS is a collection of all the core device drivers used to operate and control the system hardware. The operating system (such as DOS or Windows) uses the drivers in the BIOS to control and communicate with the various hardware and peripherals in the system. ◊◊ See Chapter 5, “BIOS,” p. 397. Phoenix’s method for legally duplicating the IBM PC BIOS was an ingenious form of reverse-engineering. It hired two teams of software engineers, the second of which had to be specially screened to consist only of people who had never before seen or studied the IBM BIOS code. The first team did study the IBM BIOS and wrote as complete a description of what it did as possible. The second team read the description written by the first team and set out to write from scratch a new BIOS that did everything the first team described. The end result was a new BIOS written from scratch with code that, although not identical to IBM’s, had exactly the same functionality.