Ah, i see that the ATAPI driver has your HWid. So, it's down to the signing that may only work with Vista64. You may find that signing is OK on a vanilla W7 pre-SP1 install (or not, yet i don't know if that may help).
I gather that the intermediate CA certificate didn't help?
For some "outside-of-the-box" thinking, here's hoping that the following may be an example.
The IT8211 ATAPI(IDE) driver seems to work on IT8212 RAID "hardware". The RAID driver may satisfy code-signing requirements of the executable (the .sys file), despite it not having an embedded signature, nor a signed .inf file as long as no other driver exists on a clean installation that Windows would weigh as "better". Why not try the RAID driver with a modified .inf, only containing your HWid? It was signed by "Microsoft Windows Hardware Compatibility Publisher" using 2048bit encryption.
Does this agree with the designated order you mentioned previously elsewhere in this forum, mr_smartepants?
;
; ITERAID2.INF
;
; INF file of IT8212 ATA RAID controller for Windows 64-bit
; Copyright (c) 2004-2010 ITE Tech. Inc. All rights reserved
;
; modified as a test to solve a problem with certification on IT8211, without supporting RAID
[Version]
Signature="$Windows NT$"
Provider=%ITE%
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Class=SCSIAdapter
CatalogFile=iteraid.cat
DriverVer=09/17/2007,1.7.2.9
[DestinationDirs]
DefaultDestDir = 12 ; DIRID_DRIVERS (this is IOSubsys on
; Win95, and System32\Drivers on NT)
;
; Driver information
;
[Manufacturer]
%ITE% = ITE.Mfg, Ntamd64, Ntia64
[ITE.Mfg]
%ITE.DeviceDesc0% = iteraid, PCI\VEN_1283&DEV_8211&SUBSYS_82111283 ; 8211/DX
[ITE.Mfg.Ntamd64]
%ITE.DeviceDesc0% = iteraid, PCI\VEN_1283&DEV_8211&SUBSYS_82111283 ; 8211/DX
[ITE.Mfg.Ntia64]
%ITE.DeviceDesc0% = iteraid, PCI\VEN_1283&DEV_8211&SUBSYS_82111283 ; 8211/DX
;
; General installation section
;
[iteraid]
AddReg=iteraid.AddReg
CopyFiles=iteraid.Miniport
Reboot
[iteraid.AddReg]
;
; File sections
;
[iteraid.Miniport]
iteraid.sys
;
; Service Installation
;
[iteraid.Services]
AddService = iteraid, 0x00000002 , iteraid_Service_Inst, iteraid_EventLog_Inst
[iteraid_Service_Inst]
DisplayName = %iteraid.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 0 ; SERVICE_SYSTEM_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
LoadOrderGroup = SCSI Miniport
ServiceBinary = %12%\iteraid.sys
AddReg = pnpsafe_pci_addreg
[iteraid_EventLog_Inst]
AddReg = iteraid_EventLog_AddReg
[iteraid_EventLog_AddReg]
HKR,,EventMessageFile,0x00020000,"%SystemRoot%\System32\IoLogMsg.dll;%SystemRoot%\System32\drivers\iteraid.sys"
HKR,,TypesSupported,0x00010001,7
[pnpsafe_pci_addreg]
HKR, "Parameters\PnpInterface", "5", 0x00010001, 0x00000001
;
; Source file information
;
[SourceDisksNames]
1 = %InstallDisk%,,,""
[SourceDisksFiles]
iteraid.sys = 1,,
[Strings]
ITE.DeviceDesc0 = "ITE IT8212 ATA RAID Controller"
InstallDisk = "ITE IT8212 ATA RAID Controller Driver Diskette"
ITE = "ITE Tech. Inc."
iteraid.SvcDesc="ITERAID_Service_Install"
Even if this does work, don't expect RAID configuration from boot
(or even functional RAID - trying RAID could be messy, the silicon might simply not exist to support it, the RAID BIOS is definitely lacking from your mobo's BIOS).
One other way this idea may break, is if the drive need be configured as JBOD prior to use. The 'crazy' .inf file may be another. The embedded HWid in silicon may be yet another, as the chip-maker likely had a forward eye to make this very idea impossible.
How forward-thinking was the naming of this topic, started by predator2003?
If anybody can expand upon this or other ideas to solve this issue with IT8211 controllers,
please join the forum and reply. Otherwise, i would simply recommend that this driver be in the Vista-Only folder in the x64 pack, if it is not already.
