As a software developer who's been lurking in the forums for a few months now, I'd like to put my 2 cents in on this thread:
1) The following quoted post, which references this CodeProject article on drivers, is slightly off the mark:
http://www.thecodeproject.com/system/tdriver.asp
The phrase "driver path" in that article has nothing to do with the "driver path" discussed in this thread.
Originally posted by: josh6079
Within the link I gave, here is the section that you, and I, were talking about:
LPTSTR driverPath; //driver disk path
LPTSTR driverDosName; //driver's dos name, to link with it
<...snip...>
The methods you can use in this class are:
InitDriver(...)
This function is used to initialize the parameters of the driver such as: driver name, driver path and driver dos name. If you only know the driver path, the funtion tries to get the rest of the parameters.
The part I bolded above is the part your selective reading skimmed over like redbox suggested.
The bolded, underlined, and italized part is the whole line which you cut out in a pathetic attempt to continue your ramblings.
Then under everything else, I underlined the main part that explains that a driver path is indeed a parameter for certain types of drivers.
Let me show you (again):
"to initialize the parameters of the driver such as: driver name,
driver path and driver dos name."
It does not say "data path", which you seem to think is interchangable.
Now before bring up any other worthless ramblings, can you simply answer the questions that you deem to be possible.
If you read the entire article, the author is providing an easy way for driver developers to load a driver
file (e.g. a file whose name ends in .SYS) from an application, in order to make testing easier.
In the
context of the article, "driver path" means the "location of the driver file" to be loaded. In other words, in that article the "driver path" specifies
where the driver is. In programming, "path" is a generic term for "file location" (including directory) and that's how it's used it that article.
In Windows, a "path" (or "pathname") is usually an drive name, followed by a directory (folder) name, followed by a filename. For example, the driver you want to load could be located at this path: C:\Windows\System32\DRIVERS\MyDriver.sys
I hate to say it, but at least on this score, BeggerKing is (half) right. The "driver path" in that article has nothing to do with the "driver path" that BFG10K originally brought up.
On the other hand, I don't think the way that BFG10K used the phrase "driver path" is wrong. This was the first place I could find mention of "driver path" in this thread:
Originally posted by: BFG10K
The driver path that is invoked is the SLI driver path, not the single GPU path.
I don't think he's wrong to use the phrase "driver path". What I understood from his posts is that he's saying when you use the 7950GX2, the Nvidia display driver does "whatever it needs to do for an
SLI solution", rather than "whatever it needs to do for a
single-GPU solution". Just because he used the phrase "driver path" is no reason to attack his arguments. It's like me asking somebody "What path of action are you going to take today?", instead of asking (more normally) "What are you going to do today?" Would I be "incorrect" to use an "unusual", yet grammatically correct phrase like "path of action"?
That CodeProject article is definitely not proof that "driver path" is an "industry-standard phrase" or anything like that.
If I wanted to load a document from an application, I could call its location the "document path". Or if I wanted to load an image, I could call its location the "image path". But that wouldn't give the phrases "document path" or "image path" any special meaning whatsoever.
2) Before anyone can begin to settle the argument of "Does the 7950GX2 count as a single card solution", shouldn't everybody agree on the definition of "card" and "single card solution" in the first place? Obviously no one does, so no one is gonna win this argument. Just like no one can agree on what the phrase "driver path" could/should mean.
This is how marketers rip us consumers off. They use fuzzy definitions of terms like "single-card solution" so that no one can prove/disprove that they are trying to trick us.
It's the same as "monitor size". When CRTs were popular, they quoted the diagonal size of the cabinet, which was usually about 1 inch longer than the viewable area. When LCDs came out, the industry started quoting actual viewing sizes (maybe because people complained about deceptive advertising?). Anyway, if you did not properly define "monitor size", then someone could look at a 15-inch (advertised) CRT and say, "No, that's
really a 14.1-inch monitor" (or whatever.)
Anyway, for what it's worth, I think that if you could define "single-card solution", then this argument would be settled pretty quickly.
Edited for spelling and clarity