• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Intel 'Driver' Am I being Dense?

Soldato
Joined
13 Jan 2004
Posts
21,169
As above, either I am being dense, blind, dumb or a mix/all of the above but I cannot for the life of me find a driver for Intel CPUs on Intels site.

Do they even have one?

AMD always had a driver available for download and the embedded Windows driver dated some time in 2004/2005 does not instill me with the most confidence :X

Troubleshooting some issues and wanted to make sure I had, if it even exists, the lastest driver.
 
There used to be a driver for P3's when XP first surfaced but that would surely be incorporated into an update of some sort.
 
:D :D Couldn’t be any more to the point, waits for the war to start! :p

Intel know x86 very well... Clone chips are 'ok' and often good value for money, and there is no hiding the fact that Athlon 64's were kicking Intel P4's where it hurts.

But compatibility..... there have been some interesting 'glitches'. Athlon64's use a cpu driver to ensure 'windows' compatibility, and thats fine. Its a reliable solution which really doesnt cause any problems.

I remember a few years back, 32bit Athlons used to render "Rubicite" armor in Everquest 1 in a dark blue colour. Infact the armour was bright red by design, and was red when played on an computer with an Intel processor. In the end the game was patched to detect the AMD processor and the armor ended up red on both brands.

But that always got me wondering, what bug in the Athlon triggered the 'red' armor to become 'blue'. Would you really want to have your bank balance stored on a computer which can give 'different' results when running the exact same program.

Of course Intel is not 'perfect' and I am sure many people remember the floating point bug on the original 'Pentium 60mhz and 66mhz' processors.
 
The AMD 'driver' was to fix issues with the chips. Intel made theirs correctly and didnt need it.



Big Grin . . . . :D

Have you heard of the Pentium flaw?? you know the chip that can't add numbers up properly... :D

edit: did i say add up, i mean divide *cough cough*
 
Last edited:
That was fixed aaages ago. Like 1996 ages ago. Phenom being broken is current and now. :p

but at least they admit it, Intel just shrug there shoulders as they new it would only affect 0.001% of there customers, and who would ever be able to prove it was the CPU at fault, what a crazy thought....
 
but at least they admit it, Intel just shrug there shoulders as they new it would only affect 0.001% of there customers, and who would ever be able to prove it was the CPU at fault, what a crazy thought....

Not true, Intel were very easy to deal with after the Pentium bug hit the news. They replaced my Pentium 60 with a 'fixed' model, was a very fast turn around too.

All chips have errata, and thats a problem when programming for multiple chips. Code that works perfectly on one system might have side effects on another. That even applys if you develop code on say an Intel P4, and then the end users is using a P3.
 
Not true, Intel were very easy to deal with after the Pentium bug hit the news. They replaced my Pentium 60 with a 'fixed' model, was a very fast turn around too.

All chips have errata, and thats a problem when programming for multiple chips. Code that works perfectly on one system might have side effects on another. That even applys if you develop code on say an Intel P4, and then the end users is using a P3.

but they knew about the bug before launch, obviously they had the fix in the pipeline, who wouldn't, I mean what does a CPU actually do all day, it crunches numbers, so if it cant do that properly then its a bit useless (well not completely as very few people would actually be effected).

but to think that nobody would actually work it out is a bit naive.

I was just making the point after PhillyDee's "The AMD 'driver' was to fix issues with the chips"

don't get me wrong, I currently own 2 Intel based PC's 1, AMD based one and am looking to go Quad Intel in the new year

Mistakes happen that's all, that why every single engineering discipline/company has a revision control system.
 
Back
Top Bottom