TechDud wrote:

Along with any reply, would you please post your HWid's?

do you mean this stuff?

PCI\VEN_1283&DEV_8211&SUBSYS_82111283&REV_11
PCI\VEN_1283&DEV_8211&SUBSYS_82111283
PCI\VEN_1283&DEV_8211&CC_018000
PCI\VEN_1283&DEV_8211&CC_0180

TechDud wrote:

Even the driver for Vista_x64 from Windows Update Catalog didn't work on your board?

nope...

TechDud wrote:

Wouldn't one solution be to virtualize your OS?

not really, I really want to install window 7 on that old(ish) PC, on an IDE disk, that's all.

TechDud wrote:

I note that the 'sys file has an embedded digital signature.

... which I guess is the reason why the streamlined installation works?
The "load driver" step checks the cat file, finds something wrong and refuses to use the driver, but if the driver is already in the image, there is probably no cat check, only the sys (which is OK) is checked? I'm guessing, I have no idea how windows uses the various driver signatures.

TechDud wrote:

I wonder if the new Windows Updates in October requiring stronger certificates will effect any legacy drivers.

might well be it. As I said I'm no expert, but it makes sense...

TechDud wrote:

You do realize the implications of turning off signing on a live system; perhaps akin to driving the highway on a moonless night during a power-outage with no headlights & a cracked windshield at 40 below and no heater?

I'm not so worried, if my theory is correct, the sys file is correctly signed and checked, so my system should be fine, would you agree?

TechDud wrote:

Along with any reply, would you please post your HWid's?

sorry, I was on another PC yesterday so I couldn't check, and I'm at work now. That and... I'm really not so sure what you are talking about, how do I find out this HWID? I'll post it tonight when I get home.

about the "force unsigned" checkbox in rt7lite, that's probably not its actual name, I'm writing from a different PC from the one I used to do the integration.
/ForceUnsigned is the switch to use with DSIM to do the same thing.

Hi TechDud,

Thanks for the suggestions, sorry I'm late in replying myself, I didn't receive any notification of your post (I missed the "subscribe to this topic" checkbox...).

I tried all the things you suggested already: EIST is disabled (has to be for the board to work at all, at least with WinXP and Win7), I have the latest BIOS and I have downloaded all possible versions of the driver, including those you suggest. There must be really something wrong with the signature of all those driver (meaning that at ITE they consistenly do something wrong), but I don't know what it could be, because the cat file seems ok (except the certificates are all expired by now).

Anyway, for all those that have this problem and are looking for a solution: I finally found a way to circumvent the bad signature: I streamlined the v1.3.4.2 drivers (the latest from the ITE site) in the win7 installation image, so the whole "load driver" step was completely avoided, the driver was loaded automatically.
To do this I used rt7lite (http://www.rt7lite.com/). Just follow the instruction there, the only action required is "Integration" (http://www.rt7lite.com/faq6.html).
***********************************************************
REMEMBER to check the "force unsigned" checkbox or the driver won't load
***********************************************************

For the brave, the integration can also be done using DISM, a command line utility included in Win7 (after all it is just a matter of adding the driver files to the .WIM images in the right place), but I quite liked the simplicity of rt7lite.

Hi,
the thread is a bit old but it seems relevant to my problem, but let me know if you think I should've started a new thread.
I'm trying to install Windows 7 x64 on an IDE hard drive on an old Abit IB9, which supports IDE disks via the ITE 8211 controller, but when I try to load the drivers it refuses to do so, with a message saying "you need to load 32-bit drivers or signed 64-bit drivers".
I have tried several versions of the IT8211 drivers, including those in the mass storage DP 12.08, always with the same result.
I can load the 32-bit drivers, which leads me to think that there is a problem with the 64-bit driver signature (but this is nothing more than a hunch).
I'm completely out of ideas, what can I try next?