Just wanted to report, on my system in sig i tried the v12.9.4.1000 and v13.1.0.1058 (drivers only, no software), both work well but the v13 benchmark slightly faster so i will stick with those.
Using these drivers have solved the event viewer errors with my ssd on MS AHCI i would always get: “A TCG Command has returned an error.” Something to do with my sdd and it’s built in encryption ability. Also benchmarks overall slighty better then built in MS AHCI drivers.
Great job, my computer has been running great with these for days now.
I’m trying to gownload this drivers Modded+signed Intel RST drivers v11.2.0.1006, but when I finishing download and try to unpack it from RAR archive it’s says that archive is corrupted and I can’t unpack it. I tried download from both sources and from different computers but result the same.
All RAR archives of this Forum are packed with WinRAR v5.xx, which uses a better compression routine than the older v4.xx ones. So you have to use an up-to-date version of this tool, if you want to unzip the RAR archives properly.
I want to tell about my experience. I have: H110M DGS R3.0 motherboard. And trying install Win XP on this motherboard. Finaly I did it. but not with flash drive or CD-Rom. I used second hard drive. made it bootable(I have external cabby with usb interface) and then connect via SATA to motherboard. And when I’m booting from that secon drive I’m pressing F5, F6, F7 and then chooce Computer that system offer me. After windiws is finish instalation it’s have a lot of missing drivers. I found some drivers and install them but others can’t find: *PNP0700 PCI\VEN_8086&DEV_A12F&SUBSYS_A12F1849&REV_31 PCI\VEN_8086&DEV_1902&SUBSYS_19021849&REV_06 HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101&REV_1000 PCI\VEN_8086&DEV_A13A&SUBSYS_A13A1849&REV_31
Pressing the F6 key only makes sense, if you want to load a specific textmode driver and haven’t integrated it into the XP Image.
The first step is to find out, who is the manufacturer of the related device and which is the exact device model. You can do it by entering the related HardwareIDs into the Google Search. Example: PCI\VEN_8086&DEV_A12F&SUBSYS_A12F1849&REV_31 are the HardwareIDs of an Intel USB 3.0 Controller running with an Intel 100-Series Chipset system. An XP driver for these HardwareIDs doesn’t exist.
I can’t open the first package that is also intended for the 200 series. He always tells me that the archive is unknown or damaged. Can you fix this? Thanks in advance!
Regards DLG3000
EDIT by Fernando: Unneeded parts of the quoted post removed (to save space)
@ all: Upon demand I have modified and signed the latest available Intel RST(e) drivers of the v15.5, v15.7 and v15.8 development branches to make them installable onto nearly all Intel Chipset systems from ICH7 up running in AHCI or RAID mode. There is no guarantee, that they will properly with older, natively not supported Intel Chpset systems.
Update of the Start Post: Changelog:
new:
mod+signed 32/64bit Intel RST(e) AHCI+RAID drivers v15.5.5.1059 dated 06/01/2017, modified and digitally signed by me at 09/25/2017
The Intel RST(e) drivers of the v15 platform have been designed and optimized by Intel just for the newest Intel 100-/200-Series Chipsets. Due to the modification of the related INF files the above listed Intel RST drivers will be installable onto older Intel Chipset AHCI/RAID systems, but may not properly work. Users with an older Intel Chipset system should better take a driver, which belongs to the v13 or v14 platform. I am not responsable for potential problems they may get after the installation of these newest mod+signed drivers.
If not already previously done, don’t forget to import the Win-RAID CA Certificate, before you try to get any of my mod+signed drivers installed. The Certificate itself and the related CMD file are attached to all my mod+signed driverpacks.
Due to new security features of Win10 v1703 you may have to execute the CMD file from within the Command Prompt or Windows PowerShell (both options have to be run as Admin).
>Here< you can get additional informations about “modded” drivers and >here about how to get them properly installed.
Good luck with these freshly modded and digitally signed Intel AHCI/RAID drivers! Dieter (alias Fernando)
It seems i have an issue on H97 chipset when I’m trying to install 64bit Intel RST(e) Software v15.8.1.1007. After the installer removing the older version it’s rolling back and removing the changes. Same on clean install.
@realismo : Welcome to the Win-RAID Forum! Questions: 1. Why didn’t you uninstall the previously used Intel RST Software yourself from within the Control Panel? 2. Why did you try to install the v15 platform Intel RST(e) Drivers and Software at all?
It is not yet available for the public, but I have already started to build universally usable mod+signed 32/64bit Intel RST AHCI & RAID drivers v13.44.0.1026. My idea is to offer 32/64bit “F6 driverpacks”, which contain the new original Intel RST driver v13.44.0.1026 dated 02/22/2017, but do support a) all Intel SATA AHCI Controllers from ICH7 up, b) all Intel SATA RAID Controllers from ICH8R up and c) all Windows Operating Systems from XP up. The related packages are ready, but not yet tested. Are you interested? If yes, please give me infos about the Intel chipset, the Intel SATA mode and the OS you are using resp. you want to install.
Yes. DEV_A102 (Intel 100 Series), AHCI mode and Win10 64-bit v1709 build 16299.19, also a laptop with DEV_1C03 (Intel mobile 6 series), AHCI and same Win (was bsoding at boot with drivers from v15 but maybe these will work properly).
@MrRhade : Thanks for having tested my recently mod+signed Intel RST driver v13.44.0.1026 and for having posted your benchmark results.
@all: Since I recently got a brandnew Xiaomi Air 13.3 notebook with a KabyLake CPU, where I was able to additionally insert a 250 GB Samsung M.2 850 EVO SSD with AHCI interface for the storage of Data, I was able to test my mod+signed Intel AHCI driver v13.44.0.1026 with this Intel 200-Series Chipset Mobile system.
Here are my benchmark results: 1. AHCI driver = Win10 x64 v1709 in-box AHCI driver:
EDIT: I just have realized, that MrRhade and me used different variants of the Intel AHCI driver v13.44.0.1026. We both used the original Intel driver (having the identical code), but I gave them different names. The Intel AHCI driver MrRhade has used is named iaStor.sys, whereas I used the driver with its original name iaStorAV.sys. When I saw MrRhade`s screenshots, I instantly thought, that he was running an old Intel RST Software in the background, but I obviously was wrong. That is why I have deleted the related part of my post. I am sorry about the confusion.
Or did I miss something in this thread?
