|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
the history of drivers
i've been having an on-going debate with a good friend of mine for about the last year or so...
the question is, why are drivers called drivers? do they really "drive" anything? according IBM they do: Quote:
according to my friend (who has an A+ certification) drivers do not drive squat. they are more of a communication device or "translator" ...i don't disagree with his definition, but i do disagree with his very stubborn opinion in that "drivers do not drive" so am i wrong? and if so, why are they called drivers? |
|
#2
|
||||
|
||||
|
RE: the history of drivers
http://encarta.msn.com/encyclopedia_761569716/Driver.html
Microsofts answer |
|
#3
|
|||
|
|||
|
RE: the history of drivers
i'm not an MSN Encarta Premium Subscriber. what does it say?
|
|
#4
|
||||
|
||||
|
RE: the history of drivers
I didnt realize i was
Code:
Driver, in computer science, a software program that expands the capabilities of a computer to control various input and output devices. A device is any machine component attached to a computer such as CD-ROM players, disk drives, keyboards, mice, modems, monitors and printers. Devices may be considered either peripheral or integral. A device is peripheral if the computer can function without it. A printer, for example, is a peripheral device because it is not essential to the operation of the computer. Monitors and keyboards, however, are essential to the function of a computer and are therefore considered integral devices. Many driver programs come as part of a computer’s operating system—the software that schedules tasks, allocates data storage, and coordinates data transmission between the computer, connected devices, and other computers. When connecting peripheral devices, the computer user often must load a new driver into the computer for each device. All devices require a driver program to function. Each model of a particular device usually comes with its own driver software. For example, each printer model, from each manufacturer, comes with its own driver software to be installed with the PC’s operating system software. In a computer, the driver serves as a translator between devices and the programs that send commands to the devices. For example, when a user selects the print command in a word-processing program, the program sends a generic command to the printer via the operating system. The driver intercepts this command and translates it, converting it into a specialized command that the printer can understand. The driver program then accesses the hardware registers of the device. Registers are storage areas within the device’s central processing unit (CPU). The number of registers and the size (number of bits) of each help determine the performance and speed of the device. Many drivers have an interrupt handler that notifies users if a device’s functioning is interrupted. The driver software may then supply the user with information on the status of the device or commands sent to the device and offer error or procedural messages. In DOS operating systems, driver files have extensions indicated by .sys. In Windows operating systems, drivers have extensions that read .drv. In Macintosh systems, the drivers are signified simply by the name of the device they control, such as “Laser Writer,” and are system extensions. Code:
Device Driver, in computer science, a software component that permits a computer system to communicate with a device. A printer driver is a device driver that translates computer data into a form understood by the intended printer. In most cases, the driver also manipulates the hardware in order to transmit the data to the device. However, device drivers associated with application packages typically perform only the data translation; these higher-level drivers then rely on lower-level drivers to actually send the data to the device. |
|
#5
|
|||
|
|||
|
RE: the history of drivers
okay that's all good information and all but it still doesn't answer the question.
why are they called "drivers" and do they actually drive? |
|
#6
|
|||
|
|||
|
RE: the history of drivers
Quote:
I'm not too fond of that definition. I would be more apt to say they are provide the instructions on how to operate a device. As such, the device can't operate without the device driver. The same with a car, we provide the instructions on how to operate the car and actually interface with said car (just like the device driver interfaces with the device). If it were not for us, the car would be a big hunk of metal that did nothing. The same with the device, without its driver, it would do nothing. I say it is a driver because it contains the knowledge and does the interfacing with the device. |
|
#7
|
|||
|
|||
|
RE: the history of drivers
ahh man... i've learned so much, yet learned so little...
more published resources: -------------------- "Device drivers “drive” devices in the sense that they tell controllers what to do." - Gregory D. Benson (Department of Computer Science) "Device drivers literally drive everything you're interested in--disks, monitors, keyboards, modems--everything outside the computer chip and memory." - Linux Device Drivers "The device driver drives the devices by allocating an instance of a USB host controller device driver to each device." - Xen Source technical friends: -------------------- Fr0g: i look at it this way. first, hardware does nothing with the operating system if something does not prompt it to. the software drives the hardware in the same sense that the user drives the computer. secondly, while it may be a silly term (after all, sound cards don't have steering wheels) there are virtually no other words that effectively describe the purpose of the so-called driver. tapeworm: so is it wrong, to say that a driver "drives"? Fr0g: no. english is imprecise tapeworm: why are they called drivers if they don't drive? Monkey: why are they called monitors if they don't monitor? tapeworm: a monitor allows you to monitor what's on the screen Monkey: a driver allows a USER to "drive" hardware tapeworm: so they do drive, with assistance? Monkey: no, USERS drive with assistance FROM the DRIVERS tapeworm: you're saying, that regardless of what these published experts say, they're wrong, and need to explain it better? Maverik: i didnt say that they are wrong for the record. i am saying they have only done their best to help the general public understand the concept, unfortunately they inadvertantly have used the wrong words to explain it, therefore creating this confusion among the industry... if you really dig deep enough into the argument you will realize that it is actually a huge 50/50 sided arguement among people in the industry... people that try to explain just take the easy way out to save a 4 hour conversaiton and just dumb it down for the public instead of actually explaing the process tapeworm: but is it wrong, to say that a driver "drives"? Maverik: yes it is becasue it creates the wrong represetation of what happens |
![]() |
| Viewing: Codewalkers Forums > General > General Chat > the history of drivers |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|