| Most people understand that the "hardware" | | | | Microsoft be held responsible for the quality |
| part of their computer is the real physical | | | | from a third-party?As I described in Part 1 |
| parts, like the keyboard, mouse, modem, hard | | | | of this article, the operating system doesn't |
| drive and so on. They understand that the | | | | interface directly to a hardware device. |
| "software" is computer bits stored on the | | | | There is a piece of software called a |
| hard drive, CD-ROM, or other storage media. | | | | "driver" that translates the hardware's |
| But most people are a little hazy about | | | | control signals to signals that the operating |
| exactly what a "driver" is.In this article, | | | | system expects, and translates signals from |
| I'm going to reveal in plain English what a | | | | operating system to the hardware's control |
| driver is, why we need drivers, and exactly | | | | signals. Obviously, the hardware manufacturer |
| where the drivers are hiding. To give you a | | | | provides the driver.Because the driver works |
| basic understanding, I'm going to go back, | | | | between the operating system and the |
| way back, to the early days of computers.The | | | | hardware, a bug in the driver can cause a |
| Early DaysThe year is 1981 and the world is | | | | serious problem. Many of the problems with |
| in the midst of a severe resession. IBM's | | | | Windows have come from bugs in third-party |
| main frame business has slowed and the | | | | drivers that Microsoft had nothing to do |
| company is losing money. Up until now they | | | | with. For this reason, Microsoft created a |
| had been laughing at the array of | | | | Hardware Quality Lab to test drivers. A |
| microcomputers on the market: Atari, | | | | hardware manufacturer can submit their driver |
| Commodore, sinclair. Toys really, mostly used | | | | for testing, and if it is passes rigorous |
| to play computer games.The problem was, these | | | | compatibility testing, it receives |
| "toys" were selling like hot cakes. IBM had | | | | Microsoft's digital signature.You may have |
| to get into that market and get into it fast. | | | | received a message during the installation of |
| They didn't have time to design and build a | | | | a hardware device warning that the driver was |
| computer complete enough to compete in the | | | | not signed. Why would a hardware manufacturer |
| market, so they built an "open system". They | | | | fail to have their driver certified by |
| used commonly available electronic components | | | | Microsoft? The computer hardware market is |
| and they published every design detail | | | | very competitive and the manufacturer might |
| (including the code), and they even provided | | | | want to bring a new product to market before |
| plug in slots so that others could build | | | | thorough testing can be completed. Or maybe |
| components for their computer.And people did | | | | they don't want to or can't afford to pay |
| provide components for the IBM PC. They | | | | Microsoft for certification. The question is, |
| provided video cards, memory expansion cards, | | | | should you click on the "Continue" button to |
| input-output port cards, game port cards, | | | | install the unsigned driver?In my experience, |
| hard disk interface cards, and much more. How | | | | I have never been able to trace a problem to |
| were all these various devices able to | | | | an unsigned driver. If it's your home |
| interface with the PC's operating system? | | | | computer and you performed a back-up |
| That's where a "driver" comes in.A hardware | | | | recently, go ahead and install the unsigned |
| device is constructed with various electronic | | | | driver. If it's a computer on a corporate |
| components using various control signals, but | | | | network, you may want to back-out of the |
| the software interface to the operating | | | | installation and see if you can locate a |
| system is standardized. A device's interface | | | | signed driver first. Many times a |
| to the operating system must follow the | | | | manufacturer will release a product with an |
| interface specification. A driver is a piece | | | | unsigned driver, then later provide a signed |
| of software that translates the hardware's | | | | driver as a free download from their |
| control signals to signals that the operating | | | | website.If you decide to go ahead and install |
| system expects, and translates signals from | | | | an unsigned driver, you can always update the |
| the operating system to the hardware's | | | | driver later. If your computer works with the |
| control signals.When the computer is started | | | | unsigned driver, I would not update the |
| up, it would look in the "system" directory | | | | driver. When it comes to updating drivers (or |
| for files with the extension ".drv" and load | | | | the computers BIOS) I go by the old saying, |
| them into memory. Specific files like | | | | "if it ain't broke don't fix it".To update a |
| autoexec.bat, config.sys, and win.ini were | | | | driver, select Start | Settings | Control |
| used to inform the operating system about | | | | Panel and double-click on the "System |
| drivers. Hardware would be configured through | | | | Properties" Utility. In the "System |
| these files, or through jumpers located on | | | | Properties" Utility, select the "Hardware" |
| the device itself.The driver specification | | | | tab and click on the "Device Manager" button. |
| evolved along with the PC. Today when a PC | | | | In the "Device Manager" window, right-click |
| starts, it executes the program which queries | | | | on the device in the list and select |
| the hardware components and builds the | | | | "Properties" in the popup menu. In the |
| registery key | | | | "Properties" dialog box, select the driver |
| HKEY_LOCAL_MACHINEHARDWARESYSTEMCurrentContro | | | | tab and click on the "Update Driver..." |
| lSet. This key exists only in memory and is | | | | button.In the "Properties" dialog box driver |
| created each time the computer boots. If all | | | | tab, you may have noticed the "Roll Back |
| the drivers are loaded successfully, a copy | | | | Driver" button. If your computer has problems |
| of the key is saved as ControlSet00X.Under | | | | with the new drive, you can click on the |
| the registery key CurrentControlSet, the | | | | "Roll Back Driver" button to roll back to the |
| subkey "Enum" contains a subkey for each | | | | previous the driver. Driver roll back saves |
| harware device on the computer. Each device | | | | only one previous driver, so if you update a |
| key contains fields for Hardware ID, Driver | | | | driver, then update it again, the original |
| ID, Device Parameters, and other | | | | driver is gone. If the computer has problems |
| configuration data. The 32-bit drivers are | | | | with the new driver, always roll back to the |
| files with the extension ".sys" and can be | | | | original driver before trying a different |
| found in the folder C:/winnt/system32.Driver | | | | one. That way you'll always have the original |
| SigningMicrosoft has been the brunt of much | | | | driver to roll back to.Copyright(C) Bucaro |
| criticism because of the poor reliability of | | | | TecHelp.Permission is granted for the below |
| the Windows Operating System. I feel that | | | | article to forward, reprint, distribute, use |
| much of this criticism is justified. On the | | | | for ezine, newsletter, website, offer as free |
| other hand, as I described in part 1 of this | | | | bonus or part of a product for sale as long |
| article, the PC was designed by IBM as an | | | | as no changes are made and the byline, |
| "open" system. Anyone can sell a hardware | | | | copyright, and the resource box below is |
| device (or software) for the PC. Should | | | | included. |