|
(OT) Steve Jobs.
On 10/19/2011 12:14 AM, Alan Baker wrote:
In , John wrote: On 10/18/2011 6:16 PM, Alan Baker wrote: In , John wrote: On 10/18/2011 1:13 PM, Alan Baker wrote: In , John wrote: On 10/18/2011 12:30 PM, RHF wrote: On Oct 18, 9:58 am, John wrote: On 10/18/2011 5:18 AM, D. Peter Maus wrote: On 10/17/11 20:04 , Howard Brazee wrote: On Mon, 17 Oct 2011 17:41:08 -0700 (PDT), RHF wrote: Friends Don't Let Friends Buy Apples/Macs. Friends let friends be their own people, making their own choices. The world needs more friends. Hey....making sense, here. Cut it out. Real friends sit they PC down besides the Mac users equipment and give them a demonstration ... one picture is worth 10,000 words ... Regards, JS Apple-holics 'Know' with a certainty that MACs are very "pc"*, and lowly PCs {The Machine} are not. -apple/macs-are-creative-tools-for-the-ennobled- -while-ms/pcs-are-simply-machines-for-the-masses- * 'pc' politically correct and elitist** ** 'i' am an Educator {in Education} and use an Apple/MAC therefore 'i' and 'it' are better than you and your lowly PC -or- ** 'i' am Creative {in the Arts etc...} and use an Apple/MAC therefore 'i' and 'it' are better than you and your lowly PC . Apple/MAC : A Statement of "Who I Am" -versus- MS/PC : A Statement of "What I Do" -result- Fashion Over Form-&-Function . . What I seen was bill gates become very obstinate and think that that there was no need for video as powerful as the computers ... MAC video graphic artists where forced into being ... now that windows went ahead and provided the supporting software/driver support, there is no finer video than you will find on PC's ... and the leading reason all no. one games usually only run on the PC, and windows ... to transcode them for another architecture/video support cuts too many capabilities from the game. Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers. As for your "too many capabilities from the game" claim... ...let's see a concrete example. Tell you what, this will get you started on who sets the specs and defines the driver: http://msdn.microsoft.com/en-us/libr...4644%28v=vs.85 %29 .aspx I never said that Microsoft doesn't set specs or defining things. You, again, seem to have a real problem with semantics ... usually a problem for those with no or inadequate educations. "YOU can build a driver using the Visual Studio development environment, or YOU can build a driver directly from the command line using the Microsoft Build Engine (MSBuild). To build drivers for Windows Developer Preview, Windows 7, and Windows Vista, use Visual Studio and MSBuild. To build drivers for Windows XP, YOU must use the Windows 7 WDK and the Windows Build Utility (Build.exe)." Do you see that word that I've capitalized? To whom do you think Microsoft is referring with the word "YOU" in that paragraph? The person/people who "build a bridge" are those completing the design, engineering and plans ... so it is with anything ... it is not "the guy with the shovel." Your analogy is so flawed I cannot even begin. The construction workers ... not the people who have designed the system and specs ... they simply assembly from the ms libraries ... No. It is absolutely nothing like that. Right, WHQL and the windows driver SDK is only a figment of software engineers imaginations ... ROFLOL But, the windows driver sdk could be rewritten and non-windows certified drivers created (indeed, I have used work-a-like driver SDKs, however, they cannot be used in the creation of windows WHQL drivers) ... duh! Linux is really only a rewrite of unix and was done to have a free OS ... You are a fool who wants to split hairs and change the discussion off to a tangent ... fool. Regards, JS |
(OT) Steve Jobs.
"Alan Baker" wrote in message ... In article , John Smith wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? |
(OT) Steve Jobs.
In article ,
John Smith wrote: On 10/19/2011 12:14 AM, Alan Baker wrote: In , John wrote: On 10/18/2011 6:16 PM, Alan Baker wrote: In , John wrote: On 10/18/2011 1:13 PM, Alan Baker wrote: In , John wrote: On 10/18/2011 12:30 PM, RHF wrote: On Oct 18, 9:58 am, John wrote: On 10/18/2011 5:18 AM, D. Peter Maus wrote: On 10/17/11 20:04 , Howard Brazee wrote: On Mon, 17 Oct 2011 17:41:08 -0700 (PDT), RHF wrote: Friends Don't Let Friends Buy Apples/Macs. Friends let friends be their own people, making their own choices. The world needs more friends. Hey....making sense, here. Cut it out. Real friends sit they PC down besides the Mac users equipment and give them a demonstration ... one picture is worth 10,000 words ... Regards, JS Apple-holics 'Know' with a certainty that MACs are very "pc"*, and lowly PCs {The Machine} are not. -apple/macs-are-creative-tools-for-the-ennobled- -while-ms/pcs-are-simply-machines-for-the-masses- * 'pc' politically correct and elitist** ** 'i' am an Educator {in Education} and use an Apple/MAC therefore 'i' and 'it' are better than you and your lowly PC -or- ** 'i' am Creative {in the Arts etc...} and use an Apple/MAC therefore 'i' and 'it' are better than you and your lowly PC . Apple/MAC : A Statement of "Who I Am" -versus- MS/PC : A Statement of "What I Do" -result- Fashion Over Form-&-Function . . What I seen was bill gates become very obstinate and think that that there was no need for video as powerful as the computers ... MAC video graphic artists where forced into being ... now that windows went ahead and provided the supporting software/driver support, there is no finer video than you will find on PC's ... and the leading reason all no. one games usually only run on the PC, and windows ... to transcode them for another architecture/video support cuts too many capabilities from the game. Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers. As for your "too many capabilities from the game" claim... ...let's see a concrete example. Tell you what, this will get you started on who sets the specs and defines the driver: http://msdn.microsoft.com/en-us/libr...f554644%28v=vs. 85 %29 .aspx I never said that Microsoft doesn't set specs or defining things. You, again, seem to have a real problem with semantics ... usually a problem for those with no or inadequate educations. "YOU can build a driver using the Visual Studio development environment, or YOU can build a driver directly from the command line using the Microsoft Build Engine (MSBuild). To build drivers for Windows Developer Preview, Windows 7, and Windows Vista, use Visual Studio and MSBuild. To build drivers for Windows XP, YOU must use the Windows 7 WDK and the Windows Build Utility (Build.exe)." Do you see that word that I've capitalized? To whom do you think Microsoft is referring with the word "YOU" in that paragraph? The person/people who "build a bridge" are those completing the design, engineering and plans ... so it is with anything ... it is not "the guy with the shovel." Your analogy is so flawed I cannot even begin. The construction workers ... not the people who have designed the system and specs ... they simply assembly from the ms libraries ... No. It is absolutely nothing like that. Right, WHQL and the windows driver SDK is only a figment of software engineers imaginations ... ROFLOL Do you now what an SDK is? Seriously? A "software development kit"; a set of tools to make developing software easier. And it's called the "WDK", John: the "Windows Driver Kit" Hardware manufacturers download the WDK... ....so that they can develop (write) drivers. Period. But, the windows driver sdk could be rewritten and non-windows certified drivers created (indeed, I have used work-a-like driver SDKs, however, they cannot be used in the creation of windows WHQL drivers) ... duh! Linux is really only a rewrite of unix and was done to have a free OS ... You do realize that there is an OS called "FreeBSD", right? You are a fool who wants to split hairs and change the discussion off to a tangent ... fool. It's not a hair. Microsoft doesn't write the drivers: the hardware manufacturers do. -- Alan Baker Vancouver, British Columbia http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg |
(OT) Steve Jobs.
In article ,
"Scout" wrote: "Alan Baker" wrote in message ... In article , John Smith wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? Scout: my discussions with John arose specifically about video cards. "Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers." Quickly: Tell us again who wrote the video card drivers on your system... -- Alan Baker Vancouver, British Columbia http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg |
(OT) Steve Jobs.
"Alan Baker" wrote in message ... In article , "Scout" wrote: "Alan Baker" wrote in message ... In article , John Smith wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? Scout: my discussions with John arose specifically about video cards. So? My default drivers is provided by gasp Microsoft. Indeed if Microsoft didn't provide a driver for video cards it would be extremely hard to install the O/S on the computer. "Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers." Yep, but Microsoft also produces drivers for graphics cards. Quickly: Tell us again who wrote the video card drivers on your system... Initially it was Microsoft. Later it was Nividia However, without that graphics card driver from Microsoft I would never have been able to instead the driver from Nividia. |
(OT) Steve Jobs.
In article ,
"Scout" wrote: "Alan Baker" wrote in message ... In article , "Scout" wrote: "Alan Baker" wrote in message ... In article , John Smith wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? Scout: my discussions with John arose specifically about video cards. So? My default drivers is provided by gasp Microsoft. For devices with extremely well-defined interfaces. You can have disk drivers by Microsoft because the drive manufactures work to the ATA spec, etc. Indeed if Microsoft didn't provide a driver for video cards it would be extremely hard to install the O/S on the computer. And because for basic drivers, the manufacturers make sure the cards follow a basic spec. "Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers." Yep, but Microsoft also produces drivers for graphics cards. Very basic ones, yes. Quickly: Tell us again who wrote the video card drivers on your system... Initially it was Microsoft. Later it was Nividia However, without that graphics card driver from Microsoft I would never have been able to instead the driver from Nividia. Nope. Not true. It would have been a good bit more difficult... ...but not impossible. But the point of this was that John was touting *Microsoft* for writing the drivers that make the high-performance video cards work in their high-performance mode... ....and it just isn't so. -- Alan Baker Vancouver, British Columbia http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg |
(OT) Steve Jobs.
On 10/25/2011 4:46 PM, Alan Baker wrote:
In , John wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. ROFLOL!!!!! Can't say semantics huh? Fords engineers write the specs and create the templates but because contractors manufacture the parts or assemble sub-assemblies, they build it ... ROFLOL What a fool ... microsoft writes the drivers, like I said ... Regards, JS |
(OT) Steve Jobs.
In article ,
John Smith wrote: On 10/25/2011 4:46 PM, Alan Baker wrote: In , John wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. ROFLOL!!!!! Can't say semantics huh? Fords engineers write the specs and create the templates but because contractors manufacture the parts or assemble sub-assemblies, they build it ... ROFLOL Not the same. What a fool ... microsoft writes the drivers, like I said ... No, they do not. -- Alan Baker Vancouver, British Columbia http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg |
(OT) Steve Jobs.
On 10/25/2011 5:08 PM, Alan Baker wrote:
In , . net wrote: "Alan wrote in message ... In , John wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? Scout: my discussions with John arose specifically about video cards. "Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers." Quickly: Tell us again who wrote the video card drivers on your system... Actually, you fudge again, whether by ignorance or design. As I said, gates envisioned a motherboard with a chip on it, for video, and would handle everything ... and, as I further stated, that did NOT work out well ... windows had to rewrite and adapt the windows video drivers to accompany much more powerful video ... and, of course, we are now at the point where video cards, in themselves, are as powerful as yesterdays computers ... Windows write the specs, which defines the drivers, although they may be assembled by software engineers working for others and off site ... not any different than hardware, really ... in the aspects of the model of patents, design, implementation, construction, manufacture, etc. If someone wants to interface their hardware with windows, windows is the piper and calls the tune ... "they" simply dance to it. Regards, JS |
(OT) Steve Jobs.
In article ,
John Smith wrote: On 10/25/2011 5:08 PM, Alan Baker wrote: In , . net wrote: "Alan wrote in message ... In , John wrote: Again, you prove yourself a fool, the high level drivers make the video calls to the devices ... the hardware manufactures simply have to translate those into assembly ... the same calls are made, but the firmware of the manufacturer translates those to fit its' hardware ... ATI will be much different the NVIDIA ... but windows makes the same calls from its high level driver(s) ... and, windows must provide what the game developers need, the instructions and calls, or it doesn't even get off the ground. Just because a video card slot exists on a motherboard DOES NOT mean windows has to support it ... It is the windows kernal which runs the games ... but hey, glad to be able to help you dispel your ignorance! :-) I'm sorry, but when you really don't know what you're talking about, you should just shut up. Create a video card, write drivers for it according to Windows published requirements and it will work... ...Microsoft doesn't have anything to do with it other than certifying the drivers after they've been written. What a dumb asshole ... you'd better make yourself familiar with the windows device driver tools and their specs, moron ... I am familiar with the process as you obviously are not, since you said that Microsoft writes the drivers for other companies' hardware when they most certainly do not. They most certainly do, or more accurately have ... now the hardware simply needs to have those translated ... new hardware can be constructed which can do a whole LOT of things that WHQL drivers, are not aware of and can't use ... not until the windows drivers and constructed, by microsoft, will those ever be used ... WHQL is the specification, is the test, is the standard for windows drivers ... it is the sole creation and property of microsoft. Like I say, you attempt to use semantics to prove black is really white ... No, John. Black is black and white is white. Microsoft writes the specs to which the driver's must be written... ...but the hardware manufacturers/vendors write them. Really? I've got a lot of drivers on my computer, and when I look at the data I find most are provided by Microsoft. In fact, the only drivers which aren't from Microsoft are those I installed or downloaded from a manufacturer. Disk Drivers - Drivers by Microsoft Disk Interface - Drivers by Microsoft Keyboard - Driver by Microsoft Mouse - Driver by Microsoft Monitor - Driver by Microsoft Ports - Driver by Microsoft CPU - Driver by Microsoft System Devices - Drivers by Microsoft USB - Driver by Microsoft Video Card - Driver by Nividia Ethernet - Driver by Intel Audio - Drivers by RealTec If the hardware manufacturers/venders write them, then why do they state they were provided by Microsoft? Seems to me if someone else provided the drivers, then they could sue Microsoft for false representation. So why haven't they? Scout: my discussions with John arose specifically about video cards. "Windows didn't "go ahead" and do that, John. The companies that build the graphics cards provide the drivers." Quickly: Tell us again who wrote the video card drivers on your system... Actually, you fudge again, whether by ignorance or design. As I said, gates envisioned a motherboard with a chip on it, for video, and would handle everything ... and, as I further stated, that did NOT work out well ... windows had to rewrite and adapt the windows video drivers to accompany much more powerful video ... and, of course, we are now at the point where video cards, in themselves, are as powerful as yesterdays computers ... Windows write the specs, which defines the drivers, although they may be assembled by software engineers working for others and off site ... not any different than hardware, really ... in the aspects of the model of patents, design, implementation, construction, manufacture, etc. If someone wants to interface their hardware with windows, windows is the piper and calls the tune ... "they" simply dance to it. Regards, JS I give up. You have no clue about how these things work and you won't listen. -- Alan Baker Vancouver, British Columbia http://gallery.me.com/alangbaker/100008/DSCF0162/web.jpg |
| All times are GMT +1. The time now is 04:36 PM. |
Powered by vBulletin® Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
RadioBanter.com