Win7 x64 is super-critical about signed drivers and will ignore ones that are not signed or improperly signed. Otherwise, i would simply recommend that this driver be in the Vista-Only folder in the x64 pack, if it is not already. 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. For some “outside-of-the-box” thinking, here’s hoping that the following may be an example. I finally found a way to circumvent the bad signature: If anybody can expand upon this or other ideas to solve this issue with IT controllers, please join the forum and reply.
|Date Added:||14 January 2005|
|File Size:||6.46 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Skip to forum content DriverPacks. You are not logged in.
I cannot confirm that this is indeed the latest, nor vouch for it’s validity. Ntia64] ; added from iteatapi.
To wta this I used rt7lite http: 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 So, it’s down to the signing that may only work with Vista This means that it, as a kernel-mode driver, cannot be utilized unless driver-signing is turned off, or properly signed.
I can load the bit drivers, which leads me to it82111 that there is a problem with the bit driver signature but this is nothing more than a hunch. For some “outside-of-the-box” thinking, here’s hoping that the following may be an example.
I have tried several versions of the IT drivers, including those in the mass storage DP This is likely the certificate you would need now using bit. You may find that signing is OK on a vanilla W7 pre-SP1 install or not, yet i don’t know if that jt8211 help. There must be really something wrong with the signature of all those driver meaning that at ITE they consistenly do something wrongbut I don’t know what it could be, because the cat file seems ok except the certificates are all expired by now.
I’m guessing, I have no idea how windows uses the various driver signatures. I didn’t get to this over the weekend. 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?
It does real hardware acceleration of striping and mirroring operations. Active topics Unanswered topics. Posts [ 20 ].
[IMPL] IT ATA RAID Driver (Page 1) – Vista / 7 DriverPack Mass Storage – Forum
AddReg] ; ; File sections ; [iteraid. These drivers may help if those don’t work. AddReg] ; ; File sections ; [iteatapi.
This Driver isn’t in actual Driverpack 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. I streamlined the v1. I tried all the things you suggested already: RAID functions are implemented by an embedded microprocessor, thus is not a so called “Soft raid” controller.
WIM images in the right placebut I quite liked the simplicity of rt7lite. This week looks to be a busy one too. Along with any reply, would you please post your HWid’s?
Microsoft Update Catalog
The RAID driver may satisfy code-signing requirements of the executable the. The embedded HWid in silicon may be yet another, as the chip-maker likely had a forward eye to make this very idea impossible. I have added it manually during setup with W7 x64, works without problems http: One other way this idea may break, is if the drive need be configured as JBOD prior to use.