Intel does "AMD64" drivers

  • Thread starter Thread starter George Macdonald
  • Start date Start date
G

George Macdonald

It's right there in the .INF file dated 11/27/2004:

__________________________________________
; Intel 8255x-based PCI Ethernet Adapters
; PnP install script for Windows XP
;
; Version 8.0.15

[Version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %V_INTEL%
CatalogFile = e100b325.cat
DriverVer = 10/14/2004,8.0.15.0

[Manufacturer]
%V_INTEL% = Intel, NTx86, NTIA64, NTAMD64
..
..
___________________________________________

This is a WHQL ratified .INF file so does this mean that the EM64T versions
are not err, certified yet? Hmmm.
 
George said:
It's right there in the .INF file dated 11/27/2004:

__________________________________________
; Intel 8255x-based PCI Ethernet Adapters
; PnP install script for Windows XP
;
; Version 8.0.15

[Version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %V_INTEL%
CatalogFile = e100b325.cat
DriverVer = 10/14/2004,8.0.15.0

[Manufacturer]
%V_INTEL% = Intel, NTx86, NTIA64, NTAMD64
..
..
___________________________________________

This is a WHQL ratified .INF file so does this mean that the EM64T versions
are not err, certified yet? Hmmm.
Click to expand...

I think Microsoft's programming headers all refer to x64 as AMD64, since
that was the first one out.

Yousuf Khan
 
George said:
It's right there in the .INF file dated 11/27/2004:

__________________________________________
; Intel 8255x-based PCI Ethernet Adapters
; PnP install script for Windows XP
;
; Version 8.0.15

[Version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %V_INTEL%
CatalogFile = e100b325.cat
DriverVer = 10/14/2004,8.0.15.0

[Manufacturer]
%V_INTEL% = Intel, NTx86, NTIA64, NTAMD64
..
..
___________________________________________

This is a WHQL ratified .INF file so does this mean that the EM64T versions
are not err, certified yet? Hmmm.
Click to expand...

I think Microsoft's programming headers all refer to x64 as AMD64, since
that was the first one out.
Click to expand...

I'm no expert on .INF files but are you saying that the NTAMD64 is keyed to
M$ dictated fields for the driver install? This is an Intel-supplied file.
I got the impression that it was just a comment field here. Either way I
wouldn't think Intel would be "pleased".
 
George said:
I'm no expert on .INF files but are you saying that the NTAMD64 is keyed to
M$ dictated fields for the driver install? This is an Intel-supplied file.
I got the impression that it was just a comment field here. Either way I
wouldn't think Intel would be "pleased".
Click to expand...

Intel-supplied or not, the platform identifications are all based around
what Microsoft wants to call them (it's their operating system after
all). And I don't think it's really just a comment, it's probably being
used for something. If it is a comment, then likely it's one of those
"commented out" programmatic lines -- something that may have been used
in the past, or something that maybe used in the future, but currently
unused.

As for whether Intel will be pleased or not, who reads .INF files?

Yousuf Khan
 
Intel-supplied or not, the platform identifications are all based around
what Microsoft wants to call them (it's their operating system after
all). And I don't think it's really just a comment, it's probably being
used for something. If it is a comment, then likely it's one of those
"commented out" programmatic lines -- something that may have been used
in the past, or something that maybe used in the future, but currently
unused.
Click to expand...

Oh... "probably"?:-)
As for whether Intel will be pleased or not, who reads .INF files?
Click to expand...

..INF entries end up in the registry and I've had occasion to look through
many during installation of drivers etc.
 
Back
Top