1.

Solve : Difference between a controller and a driver?

Answer»

Sorry if this question has already been asked but I am having difficulty understanding the difference between the two. I'm pretty sure I understand that a controller is hardware and a DRIVER is software. At the same time I have also seen the two words used in the name of one thing and that doesn't help me much. Can someone explain what each of them do and how they differ from each other? Obviously, I'm not a pro by any stretch but I'm not fresh out of the box either when it comes to COMPUTERS. Thanks in advance!Quote from: imann08 on November 10, 2009, 01:55:44 PM

1. I understand that a controller is hardware and a driver is software.
2. At the same time I have also seen the two words used in the name of one thing and that doesn't help me much.
3. Can someone explain what each of them do and how they differ from each other?
...
1. You got it!
2. They are closely integrated and one may not work without the other.
3. Hard disk drive controllers, graphics controllers and others that don't immediately come to mind all are electronics than manipulate the function of another electronic device. The driver defines how that manipulation occurs within the Operating System. Hence the more accurate term: Device DriverBased on your description, it seems to me that it is the driver that is "controlling" what is going on or how it is going on and it is the controller that is driving the other piece of hardware based on how the driver is controlling it. If I am correct, each object should have been given a different name from the start. Is that correct or am I missing something?

BTW, I have seen them both referred to with the word device used before the name. Either device controller or device driver.a controller is hardware and a driver is software, we've established that-


A Controller is driven on the software side by a driver; otherwise, the controller wouldn't be able to be used by software.

Think of it this way- the Controller is the hardware device, The driver is the "translator" between the controller and the operating system.

For EXAMPLE, Windows all by itself cannot do anything with a IDE controller. The Driver is, basically, the code that let's it talk to it.

It's similar to the way you cannot USE, say, excel worksheets without having a program installed to view them- the functionality is not "built in". (Although the drivers for many common devices are installed when windows is installed, they aren't there from the get go.Thanks to both of you. I am getting it much better now. To BCP, I had heard of drivers described as a translator also.

I have been using this site for a couple of weeks now and I love it. This is my first use of the forums though. You'll probably be seeing much more of me so beware. I can be a royal pain in the arse. LOL Quote from: imann08 on November 10, 2009, 03:25:39 PM
I can be a royal pain in the arse. LOL

You will either be stripped of that habit right quick, or you'll FIT right in....

Either way it's not much of a choice, my condolences


Discussion

No Comment Found